Activity log for bug #267838

Date Who What changed Old value New value Message
2008-09-08 16:59:34 Michael Hipp bug added bug
2008-09-16 10:26:16 Colin Watson debian-installer: status New Incomplete
2008-09-16 10:26:16 Colin Watson debian-installer: bugtargetdisplayname debian-installer (Ubuntu) cdrom-detect (Ubuntu)
2008-09-16 10:26:16 Colin Watson debian-installer: bugtargetname debian-installer (Ubuntu) cdrom-detect (Ubuntu)
2008-09-16 10:26:16 Colin Watson debian-installer: statusexplanation With the SATA drive, does the corresponding desktop CD detect the CD drive?
2008-09-16 10:26:16 Colin Watson debian-installer: title Bug #267838 in debian-installer (Ubuntu): "Intrepid installer doesn't detect SATA DVD-ROM" Bug #267838 in cdrom-detect (Ubuntu): "Intrepid installer doesn't detect SATA DVD-ROM"
2008-09-19 23:34:34 Wouter Stomp cdrom-detect: status Incomplete New
2008-09-19 23:34:34 Wouter Stomp cdrom-detect: statusexplanation With the SATA drive, does the corresponding desktop CD detect the CD drive?
2008-12-22 22:04:21 Colin Watson cdrom-detect: status New Incomplete
2008-12-22 22:04:21 Colin Watson cdrom-detect: statusexplanation OK, sorry for my delay in following up. Could you please post the output of 'sudo lspci -vvnn' from a running 8.10 desktop CD, so that I can see which driver is involved? I'm guessing that the problem is that the relevant kernel module isn't shipped in the right udebs so that the installer initrd can load it.
2009-01-11 17:01:18 Jon Ringer bug added attachment 'lscpi2-vvnn.out' (lscpi2-vvnn.out)
2009-02-07 14:35:01 Colin Watson cdrom-detect: status Incomplete Fix Released
2009-02-07 14:35:01 Colin Watson cdrom-detect: statusexplanation OK, sorry for my delay in following up. Could you please post the output of 'sudo lspci -vvnn' from a running 8.10 desktop CD, so that I can see which driver is involved? I'm guessing that the problem is that the relevant kernel module isn't shipped in the right udebs so that the installer initrd can load it. Thanks for the feedback (although Jon, in future note that in general it is very hard to tell whether your hardware detection bug is the same as somebody else's, and it is usually in your own best interest to file a *separate* bug rather than to attach information to an existing bug). I think that the odds are that this is fixed in Jaunty, now that pata_amd is built into the kernel, thereby eliminating most possibilities of divergence between the installer and the live CD. Michael Hipp, if you are still experiencing this problem with a current build of Jaunty, please do reopen this bug and provide the details I asked for in comments 5 and 7. If you are not Michael Hipp and you're experiencing a bug that looks like this, please resist the temptation to comment on or reopen this bug. Instead, you will be better off filing a new bug with details (i.e. does the live CD work, and lspci -vvnn).