[hardy beta] cd/dvd not detected after installation

[signal11]

(originally aded this as comment to #85578, but that bug is against an old kernel version and marked 'wontfix')

((There are several bugs in the database, which seem to be related to the problem that CD/DVD device detection fails if there is an atapi CD/DVD secondary with a primary SATA hdd. Why is there no meta-bug for all of these? How can one know whether to report as a new bug, or add to an existing one?))

My atapi cd/dvd device is not detected in 8.04 beta after installation (but is was obviously detected during install, since I could install without problems from cd); primary device is a sata hdd. This is only on 8.04 beta, 7.10 works fine. My 8.04 beta is updated with all the latest packages.

On 8.04 (kernel 2.6.24-16-generic) dmesg says:

 [ 29.534657] scsi0 : ata_piix
[ 29.534684] scsi1 : ata_piix
[ 29.535063] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18a0 irq 14
[ 29.535065] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18a8 irq 15
[ 29.760057] Clocksource tsc unstable (delta = -1360909435 ns)
[ 29.764044] Time: hpet clocksource has been installed.
[ 29.783869] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 29.809898] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
[ 29.809930] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[ 29.810022] scsi2 : ata_piix
[ 29.810123] scsi3 : ata_piix
[ 29.810800] ata3: SATA max UDMA/133 cmd 0x18f8 ctl 0x18cc bmdma 0x18e0 irq 19
[ 29.810802] ata4: SATA max UDMA/133 cmd 0x18f0 ctl 0x18c8 bmdma 0x18e8 irq 19
[ 29.978147] ata3.00: ATA-8: TOSHIBA MK2051GSY, LD000A, max UDMA/100
[ 29.978150] ata3.00: 390721968 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 29.986096] ata3.00: configured for UDMA/100
[ 30.151558] scsi 2:0:0:0: Direct-Access ATA TOSHIBA MK2051GS LD00 PQ: 0 ANSI: 5
[ 30.156507] Driver 'sd' needs updating - please use bus_type methods
[ 30.156543] sd 2:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[ 30.156550] sd 2:0:0:0: [sda] Write Protect is off
[ 30.156552] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.156562] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 30.156596] sd 2:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[ 30.156602] sd 2:0:0:0: [sda] Write Protect is off
[ 30.156604] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.156614] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 30.156616] sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 >
[ 30.285499] sd 2:0:0:0: [sda] Attached SCSI disk
[ 30.288416] sd 2:0:0:0: Attached scsi generic sg0 type 0

while on 7.10 it says (note the detected atapi device):

[ 4.932000] scsi0 : ata_piix
[ 4.932000] scsi1 : ata_piix
[ 4.932000] ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x000118a0 irq 14
[ 4.932000] ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x000118a8 irq 15
[ 5.308000] ata1.01: ATAPI: TSSTcorp CDDVDW SN-S082H, SB00, max UDMA/33
[ 5.500000] ata1.01: configured for UDMA/33
[ 5.696000] scsi 0:0:1:0: CD-ROM TSSTcorp CDDVDW SN-S082H SB00 PQ: 0 ANSI: 5
[ 5.696000] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 5.884000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
[ 5.884000] PCI: Setting latenc...

[Leann Ogasawara (leannogasawara)]

Care to attach your full dmesg output as well? Thanks.

[jepler (jepler)]

I have the same problem. I installed from alpha4 or alpha5 (2.6.24-11) and did not have this problem. However, with 2.6.24-16.30 my cdrom is not detected.

[jepler (jepler)]

Kernel boot-time messages. cdrom drive is not detected.

[jepler (jepler)]

I should note that the cdrom drive has worked properly in a variety of other ubuntu versions, including 6.06/amd64 and 7.10/i386.

[jepler (jepler)]

Booting from an alpha cdrom, the drive is detected. uname -a says: Linux ubuntu 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 x86_64 GNU/Linux

[signal11 (kwichmann)]

When booting from the beta install cd, the drive is detected.

[signal11 (kwichmann)]

The CD/DVD drive is not detected when booting from the installed system. I thought it might be related to the initramfs, i.e. that the initramfs on the installer cd includes modules that are not included when the initramfs for the installed system is generated. I would like to check this, but where do I get a list of the modules included in the installer initramfs?

[zertz (zertz)]

is anyone aware that this bug hasn't been fixed in hardy final? there is another bug report i have been following, however its importance on being fixed is not as urgent as this particular ticket despite it being the same problem.

https://bugs.launchpad.net/bugs/220957

[signal11 (kwichmann)]

No, it isn't. And since it's 'triaged', rather than 'in progress', it seems that nobody is working on it. It's apparently not targeted for 8.04.1...

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[walaric (nicolas-angot)]

I currently work on the intrepid release with the last update of the 2.6.27 kernel (2.6.27.9) and the problem is still here. Some users fixed the problem installing lilo instead of grub. I tried to load different modules (libata, atapiix,...) with the kernel. I don't want to replace grub by lilo to fix the issue. Any feedback?

[signal11 (kwichmann)]

Personally, I solved the problem by deactivating the cd/dvd drive in the BIOS (yes.. it sounds weird.. but for some reason, the kernel recognizes the drive when it's off in the BIOS.. and the drive works perfectly fine). I didn't bother checking with some other kernel.. I have a few bugs running (under different login names, because sometimes I forget mine), and feedback from Ubuntu is really abysmal. I'm tired of filing bugs, providing details as requested, only to get the impression that nobody works on the issue.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]