[00:43] <shtylman> cjwatson: you around?
[00:46] <cjwatson> shtylman: sort of (don't ask to ask, though, just ask)
[00:47] <shtylman> cjwatson: :)
[00:47] <shtylman> so we are trying to install hardy (yea... its old) on a new IBM x3550
[00:47] <shtylman> and during the server install
[00:48] <shtylman> several things go wrong... the first of which is it can't find the cdrom module
[00:48] <shtylman> like the install boots
[00:48] <shtylman> and we go through the language page
[00:48] <shtylman> but then it says: "No common CD-ROM drive was detected"
[00:48] <shtylman> even though it booted from a cd?!
[00:49] <shtylman> does any of that sound familiar?
[00:49] <shtylman> and is there a way around it (which still installing from a cd) ?
[00:50] <cjwatson> "even though it booted from a cd"> a lot of people have this confusion - booting from a CD means that the BIOS could read the CD, whereas the error message means that Linux can't read the CD
[00:50] <shtylman> but how can linux not read the cd if the installer started?
[00:50] <cjwatson> usually this means that either the kernel doesn't support the CD for some reason, or it requires a new module which isn't in the cdrom initrd
[00:50] <cjwatson> the installer started by means of the BIOS reading data from the CD
[00:50] <shtylman> I see
[00:50] <cjwatson> starting the installer does not require Linux to read from the CD
[00:51] <cjwatson> remember, the first bit of the installer lives entirely in the kernel and initrd, and those are both read from the CD by the bootloader (using the BIOS)
[00:51] <shtylman> I see
[00:52] <shtylman> dmesg does say it detected sr0 tho
[00:52] <shtylman> for a cdrom device... or is that unrelated?
[00:52] <cjwatson> I think it's only part of it
[00:52] <shtylman> basically saying it can see it ... but can't really use it
[00:53] <cjwatson> you're not using the netboot installer burned to a CD or anything funny like that?
[00:54] <shtylman> nope
[00:55] <cjwatson> right.  it's probably a kernel bug (I think).  they'll need to know the PCI id of your CD-ROM controller
[00:55] <cjwatson> (lspci)
[00:55] <shtylman> k
[00:56] <shtylman> well... its fixed in lucid ... so yea...
[00:56] <shtylman> ok..that issue asside... as there is a more pressing issue I wanted to ask about
[00:56] <shtylman> we can do a net install to bypass this cdrom issue
[00:56] <shtylman> so that is ok..
[00:56] <shtylman> but then... it doesn't detect any harddrives...
[00:57] <shtylman> now.. the is interesting for a few reasons
[00:57] <cjwatson> sort of sounds like the CD is fucked.  what URL did you get it from?
[00:57] <cjwatson> or I suppose it could be that it's completely failing to deal with the PCI controller or something
[00:57] <shtylman> the raid controller the drives are connected to are the same controllers as in another box (which is running hardy) ... yet in this new box they are not detected
[00:58] <shtylman> the failing to talk to pci would most certainly line up with the hdd/raid detection issue
[00:58] <shtylman> as lspci does list both
[00:58] <cjwatson> it would, but it's not the only possible cause
[00:58] <shtylman> I see
[00:58] <cjwatson> it might not even be the most likely one
[00:58] <shtylman> thoughts?
[00:58] <cjwatson> 00:57 <cjwatson> sort of sounds like the CD is fucked.  what URL did you get it from?
[00:58] <shtylman> checking
[01:00] <shtylman> ubuntu's website
[01:00] <cjwatson> sorry, not specific enough
[01:01] <shtylman> :)
[01:01] <shtylman> it was a while ago
[01:01] <cjwatson> I need a URL on releases.ubuntu.com or cdimage.ubuntu.com, or one of their mirrors
[01:01] <shtylman> should we try a new image?
[01:01] <cjwatson> the reason I ask is that sometimes the kernel version on the CD and the kernel udebs shipped on the CD get out of sync, and then nothing works
[01:01] <cjwatson> this can particularly be the case if you picked a random daily build rather than a proper blessed release
[01:02] <shtylman> this is 8.04.1
[01:02] <shtylman> but I do understand the concern
[01:02] <shtylman> we can try a new iso image... but the hdd issue comes up over netboot as well
[01:04] <shtylman> are there any other steps I could take wrt the hdd detection?
[01:05] <shtylman> something I should look for?
[01:06] <cjwatson> netboot is actually much more vulnerable to kernel version skew
[01:06] <shtylman> great :)
[01:06] <cjwatson> but for the rest, it would really be better to ask the kernel team, I'm not great at debugging this kind of thing
[01:07] <shtylman> noted
[01:07] <shtylman> as a parting note: http://ubuntuforums.org/showthread.php?t=1219514
[01:07] <shtylman> that mount cdrom is the same issue
[01:07] <shtylman> same machine as well
[01:08] <shtylman> but the "fixes" seem very shady to me
[01:10] <cjwatson> judging from that thread, frankly, it sounds like you have a new SATA controller (which both hard disks and the CD-ROM drive are hanging off) that simply isn't supported by 8.04
[01:11] <shtylman> :)
[01:11] <cjwatson> 8.04.4 is worth a try but I wouldn't hold out much hope
[01:11] <shtylman> k
[01:11] <cjwatson> this is more plausible than my PCI controller hypothesis above (PCI doesn't change that much ...) and explains the symptoms in the same way
[01:11] <shtylman> k
[01:14] <shtylman> cjwatson: well...I appreciate the help
[01:14] <shtylman> I will poke around
[01:30] <CIA-3> ubiquity: cjwatson * r3914 ubiquity/ (4 files in 3 dirs):
[01:30] <CIA-3> ubiquity: Keep track of how partitioning progress is displayed without requiring
[01:30] <CIA-3> ubiquity: an argument to be passed to progress_stop (LP: #535630).
[01:34] <cjwatson> shtylman: is bug 526534 still open?
[01:34] <ubottu> Launchpad bug 526534 in ubiquity "kubuntu ubiquity crashes after first page" [Undecided,New] https://launchpad.net/bugs/526534
[01:35] <cjwatson> oh, I guess it might be, the bug summary is not really an accurate summary of what's left of the bug after Riddell's workaround
[01:36] <cjwatson> guess somebody needs to experimentally unhide the progress bar on a live image and see if it still crashes
[01:36] <shtylman> cjwatson: oh.. that was a weird crash
[01:36] <shtylman> I have unhid it
[01:36] <shtylman> and have never run into that crash
[01:36] <shtylman> I think riddell did the install today with the new progress bar and it was ok
[01:37] <shtylman> cjwatson: im not sure if that problem is reproducable
[01:40] <CIA-3> ubiquity: cjwatson * r3915 ubiquity/ (d-i/manifest debian/changelog): Automatic update of included source packages: user-setup 1.28ubuntu5.
[01:42] <cjwatson> ok, well, somebody with relevant clue should update the bug 'cos it's on the beta-1 milestone list :)
[01:43] <shtylman> cjwatson: haha... ok.. I will mark it as closed cause it is as far as we are concerned...
[01:44] <shtylman> cjwatson: although the failed to lock is kinda upsetting
[01:44] <shtylman> and Riddell did mention having "some sort" of permission problem
[01:44] <shtylman> but it wasn't related to the installer crashing
[01:44] <shtylman> so that bug report has probly gotten out of hand and can be closed anyway
[01:48] <cjwatson> you might also find those permissions problems have gone away (or at least got less serious) due to my KApplication initialisation change in 2.1.32
[01:48] <shtylman> cjwatson: yea..i saw comments for that...
[01:48] <shtylman> hopefully that have
[01:48] <shtylman> *they
[01:49] <CIA-3> ubiquity: cjwatson * r3916 ubiquity/debian/changelog: releasing version 2.1.34
[02:44] <CIA-3> ubiquity: cjwatson * r3917 ubiquity/debian/ (changelog ubiquity-frontend-kde.install):
[02:44] <CIA-3> ubiquity: * KDE frontend:
[02:44] <CIA-3> ubiquity:  - There are no more files matching gui/qt/images/*.jpg. Don't try to
[02:44] <CIA-3> ubiquity:  install them.
[02:48] <CIA-3> ubiquity: cjwatson * r3918 ubiquity/debian/changelog: releasing version 2.1.35
[12:55] <davmor2> cjwatson: I'm still getting the issue with the software updates popup when I enter live desktop.
[13:15] <CIA-3> partman-base: cjwatson * r188 ubuntu/ (debian/changelog parted_server.c):
[13:15] <CIA-3> partman-base: Apply optimal alignment constraints to new partitions, or when
[13:15] <CIA-3> partman-base: maximising an extended partition (LP: #530071).
[13:36] <charlie-tca> Desktop images are broken for Xubuntu today: The following packages have unmet dependencies: libjpeg-progs: Depends: libjpeg7 but it is not installable  E: Broken packages
[13:37] <cjwatson> not really an installer issue :)
[13:37] <charlie-tca> Thanks
[13:38] <cjwatson> http://people.canonical.com/~ubuntu-archive/testing/lucid_probs.html lists it - it's just uninstallable, period
[13:39] <charlie-tca> Does it have to removed from the image, then?
[13:39] <cjwatson> I suspect libjpeg-progs is in fact required
[13:39] <cjwatson> some numpty removed libjpeg7 from the archive before we were actually ready to get rid of it, I think
[13:40] <cjwatson> sigh, MARTIN
[13:41] <charlie-tca> great...
[13:41] <cjwatson> needs some proper repair work
[14:03] <ev> lol
[14:11] <charlie-tca> Oh, you know I reported a bug against that new installer screen ?
[14:11] <charlie-tca> bug 536838
[14:11] <ubottu> Launchpad bug 536838 in ubiquity "[Lucid] Desktop cd starts at install screen with no quit/cancel option " [Undecided,New] https://launchpad.net/bugs/536838
[14:11] <charlie-tca> Takes 8 minutes to get to it
[14:14] <persia> charlie-tca: What would you expect "Quit" or "Cancel" to do?  How about "Restart" and "Shutdown" instead?  (the 8 minutes being a different issue).
[14:15] <charlie-tca> They don't work
[14:15] <charlie-tca> That was a different bug
[14:16] <charlie-tca> I would expect at least to be able to do something. the choices allowed are really limited
[14:16] <charlie-tca> I could accept restart or shutdown, though
[14:16] <persia> I'm just not sure I understand what either "Quit" or "Shutdown" would be supposed to do at that point.
[14:16] <charlie-tca> Right now, when it fails, you can't even debug it
[14:16] <persia> Err, "Quit" or "Cancel".
[14:17] <charlie-tca> It won't even allow you to switch to another tty
[14:18] <charlie-tca> Something to let me say "oops, I didn't want this afterall" ?
[14:18] <cjwatson> Quit would quit the installer and drop to a live session.
[14:18] <charlie-tca> Right now, it is called a hard power off, turn the system back on, then I can remove the cd
[14:19] <cjwatson> although as it happens "Try 10.04" would have the same effect
[14:19] <charlie-tca> I used to be able to remove the cd at the menu and use Ctrl+Alt+del to restart, now I can't
[14:19] <cjwatson> won't even allow you to switch to another tty> that is *not* within the installer's control
[14:20] <cjwatson> it's a bug somewhere else
[14:20] <cjwatson> we couldn't prevent that in installer code even if we wanted to
[14:20] <charlie-tca> I see
[14:20] <charlie-tca> anyway to get a debug for that?
[14:21] <cjwatson> I would wait until Keybuk uploads his plymouth work before bothering
[14:21] <charlie-tca> okay
[14:21] <cjwatson> that's the sort of thing that plymouth bugs could break
[14:22] <ogra> is that on gfxboot ?
[14:22] <ogra> i mean the stage thats described in the bug
[14:22] <cjwatson> no.
[14:23] <CIA-3> kickseed: cjwatson * r279 ubuntu/ (debian/changelog kickseed.sh):
[14:23] <CIA-3> kickseed: Drop nouveau preseeding, no longer needed with the drm backport in
[14:23] <CIA-3> kickseed: 2.6.32-16 kernels.
[14:23] <cjwatson> for Ubuntu images, the choice now normally appears at the start of the installer
[14:24] <cjwatson> unless you press a key within five seconds of the bootloader starting up
[14:24] <ogra> ah
[14:24] <ogra> i havent seen any x86 since felt 10 years :)
[14:24] <ogra> at least image/installer wise
[14:25] <CIA-3> kickseed: cjwatson * r280 ubuntu/debian/changelog: releasing version 0.53ubuntu4
=== mcasadevall is now known as NCommander
[16:56] <ev> forgot about this - http://chipx86.github.com/gtkparasite/ - should come in handy
[17:11] <cr3> is there a way to preseed ubiquity to prevent it from attempting to install additional packages from the CD, re bug #534605?
[17:11] <ubottu> Launchpad bug 534605 in ubiquity "During netinstall, ubiquity prompts when failing to install packages from the CD." [Undecided,New] https://launchpad.net/bugs/534605
[17:12] <cr3> this happens when attempting to netinstall on a system which happens to have a cdrom drive, no problem on netbooks which typically don't have a cdrom drive
[17:13] <persia> cr3: Is that netboot only, or does the same happen with alternate install from USB?
[17:14] <cr3> persia: haven't tried usb installs in a while
[17:16] <persia> Just wondering if it comes from overly broad interpretation of what it means for an optical drive to be available, or if it's specific to netboot.
[17:17] <persia> But someone else might have deeper insight into what you could check.
[17:17] <michaelforrest> 0xb8b1a8
[17:18] <persia> ?
[18:08] <shtylman> cjwatson: fyi 8.04.4 worked... it was able to see the drives when using netboot (bypassing the cd issue altogether)
[18:08] <shtylman> thanks for pointing me to that
[18:16] <cjwatson> oh cool, that was a bit of a long shot
[19:22] <CIA-3> partman-base: cjwatson * r189 ubuntu/ (debian/changelog parted_server.c partman-command):
[19:22] <CIA-3> partman-base: Add an ALIGNMENT_OFFSET command which can be used to detect whether a
[19:22] <CIA-3> partman-base: partition is misaligned.
[19:27] <CIA-3> debian-installer: cjwatson * r1256 ubuntu/ (build/config/armel/dove.cfg debian/changelog): Move Dove images to 2.6.32-202 kernels.
[20:51] <CIA-3> debian-installer: cjwatson * r1257 ubuntu/ (38 files in 2 dirs): Update help translation files.
[20:57] <CIA-3> debian-installer: cjwatson * r1258 ubuntu/debian/changelog: releasing version 20081029ubuntu90
[21:01] <CIA-3> partman-base: cjwatson * r190 ubuntu/debian/changelog: releasing version 138ubuntu3
=== robbiew is now known as robbiew_
[23:11] <CIA-3> wubi: Agostino Russo * r174 trunk/ (4 files in 2 dirs): Updated references to 10.04/lucid