On Sun, 2012-04-01 at 18:20 -0500, hcm...@hosscomm.com wrote: > The device in question is SATA - this is very similar to bug#583949 that's one > of the reasons I went ahead and filed. > Attached are the files you requested > /var/log/dmesg and contents of /proc/partitions.
From /var/log/dmesg I can see that the DVD writer was detected at boot time: > [ 1.612267] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 1.624957] ata1.00: ATAPI: LITE-ON DVDRW LH-20A1L, BL05, max UDMA/100 > [ 1.638229] ata1.00: configured for UDMA/100 > [ 1.653753] scsi 0:0:0:0: CD-ROM LITE-ON DVDRW LH-20A1L BL05 > PQ: 0 ANSI: 5 [...] > [ 1.838813] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 > cdda tray > [ 1.838818] Uniform CD-ROM driver Revision: 3.20 > [ 1.838947] sr 0:0:0:0: Attached scsi CD-ROM sr0 But the device is not available in the kernel now: > major minor #blocks name > > 8 0 244198584 sda > 8 1 1073152 sda1 > 8 2 1 sda2 > 8 5 18553856 sda5 > 8 6 11717632 sda6 > 8 7 7811072 sda7 > 8 8 205037568 sda8 > 8 16 244198584 sdb > 8 17 14745600 sdb1 > 8 18 1 sdb2 > 8 21 73241600 sdb5 > 8 22 78124032 sdb6 > 8 23 78083072 sdb7 So there must have been some error that caused it to be disabled. > I have the kernel log if you need it. > Thanks for your assistance. Yes, please look for any messages about ata1, scsi0 or sr0. > Regression? I am not sure. The device has proven it worked in the past I am > not quite certain how long... IT worked great under lenny. I had to replace > the motherboard a few months back and loaded squeeze from scratch. This is > the first time I needed to burn something or use it since. [...] So this is a regression but not necessarily recent (in terms of kernel versions). Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction.
signature.asc
Description: This is a digitally signed message part
