Thanks for the reply. > You are not running the latest kernel. Please update. This a) fixes > possible root exploits and b) may solve your problem with the SATA > drive. The current one is kernel-2.6.10-1.741_FC3. Okay ... I updated, now I'm running 2.6.10-1.741_FC3 as you indicated, but still no luck. > Any /var/log/messages entries when trying to mount CDs in the burner? Well ... that is part of the problem, I don't know *how* to mount it, or what to mount it with. It isn't listed in fstab, and when I look at the output from dmesg, I get: SCSI subsystem initialized ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 11 (level, low) -> IRQ 11 ata1: SATA max UDMA/100 cmd 0xFFFFFF000001C080 ctl 0xFFFFFF000001C08A bmdma 0xFFFFFF000001C000 irq 11 ata2: SATA max UDMA/100 cmd 0xFFFFFF000001C0C0 ctl 0xFFFFFF000001C0CA bmdma 0xFFFFFF000001C008 irq 11 ata1: dev 0 ATA, max UDMA/133, 398297088 sectors: lba48 ata1: dev 0 configured for UDMA/100 scsi0 : sata_sil ata2: dev 0 ATAPI, max UDMA/33 ata2(0): applying bridge limits ata2: dev 0 configured for UDMA/33 scsi1 : sata_sil Using cfq io scheduler Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Which seems to detect the optical drive with these line here: ata2: dev 0 ATAPI, max UDMA/33 ata2(0): applying bridge limits ata2: dev 0 configured for UDMA/33 But when I go into /dev, all I see is sda (actually, I see sdb and sdc, but those are my attached memory readers). So ... does this make any sense to you? It is like the drive is picked up and configured, but not made available to mount.
