Same problem on Thinkpad T60 running 3.0.0-14-generic with a non-native but compatible CD drive (took it from a T40, iirc): /dev/sr0 only created with acpi=off boot parameter. There is no BIOS setting to disable the drive (re comment #18). The drive model is in the log (during acpi=off boot only):
The drive used to be detected by Ubuntu fine at some point in the past (I don't remember if this was before or after grub->grub2 update, but I don't think I ever used lilo). Should this bug be marked as a [regression]? Is there any debugging information that can be provided? Should we file an upstream report if it has been positively determined that this is induced by grub?
Same problem on Thinkpad T60 running 3.0.0-14-generic with a non-native but compatible CD drive (took it from a T40, iirc): /dev/sr0 only created with acpi=off boot parameter. There is no BIOS setting to disable the drive (re comment #18). The drive model is in the log (during acpi=off boot only):
kernel: [ 1.043753] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-ROM GDR8083N 0K03 PQ: 0 ANSI: 5
kernel: [ 1.050088] sr0: scsi3-mmc drive: 10x/24x cd/rw xa/form2 cdda tray
kernel: [ 1.050092] cdrom: Uniform CD-ROM driver Revision: 3.20
kernel: [ 1.050215] sr 1:0:0:0: Attached scsi CD-ROM sr0
The drive used to be detected by Ubuntu fine at some point in the past (I don't remember if this was before or after grub->grub2 update, but I don't think I ever used lilo). Should this bug be marked as a [regression]? Is there any debugging information that can be provided? Should we file an upstream report if it has been positively determined that this is induced by grub?