-------- Forwarded Message -------- From: R S Chakravarti <chakrsc@rediffmail.com> To: ben@decadent.org.uk Subject: Re: Re: Bug#644747: linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom Date: 9 Oct 2011 04:36:25 -0000 Thanks for responding. Hope you don't mind a personal reply this time (I don't know what I'm expected to do "officially"!). I tried "modprobe sr_mod" but it didn't get loaded. I'm attaching the dmesg file you asked for. On Sat, 08 Oct 2011 23:53:47 +0530 wrote >On Sat, 2011-10-08 at 23:21 +0530, R S Chakravarti wrote: > Package: linux-2.6 > Version: 3.0.0-5 > Severity: important > > Dear Maintainer, > *** Please consider answering these questions, where appropiate *** > > * What led up to the situation? I noticed that it didn't mount the > CDROM. > * What exactly did you do (or not do) that was effective (or > ineffective)? I added the entry "cdrom" in /etc/modules. > * What was the outcome of this action? The module "cdrom" gets loaded > but /dev/sr0 is not created. > * What outcome did you expect instead? I thought /dev/sr0 would be > created. The 'cdrom' module is not a driver but is *used* by drivers. The driver for the SATA interface (ata_piix in this case) is supposed to detect SATA devices and request the appropriate driver for the device types found (sr_mod for a CD-ROM). Since sr_mod has not been loaded, it appears that the problem is in device detection. (And loading sr_mod should have no more effect than loading cdrom, because no device has been found for it to bind to.) > *** End of the template - remove these lines *** > > > > -- Package-specific info: > ** Version: > Linux version 3.0.0-2-amd64 (Debian 3.0.0-5) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-9) ) #1 SMP Fri Oct 7 20:48:45 UTC 2011 > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-3.0.0-2-amd64 root=UUID=2237ebe0-15cb-40db-bed9-d4f5ff052689 ro single > > ** Tainted: O (4096) > * Out-of-tree module has been loaded. > > ** Kernel log: > [ 20.693330] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 > [ 20.693453] HDA Intel 0000:00:1b.0: irq 43 for MSI/MSI-X > [ 20.693483] HDA Intel 0000:00:1b.0: setting latency timer to 64 [...] Unfortunately this log starts too late. Please could you send the /var/log/dmesg file. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison
Attachment:
dmesg
Description: Binary data