Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
dmesg | grep cd
[ 0.710854] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.710893] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 0.710897] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 0.710959] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 0.714856] ehci_hcd 0000:00:1a.7: debug port 1
[ 0.714864] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 0.714881] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf9ffe800
[ 0.720037] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 0.720093] usb usb1: Manufacturer: Linux 3.6.7-4.fc17.x86_64 ehci_hcd
[ 0.720341] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 0.720345] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 0.720404] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 0.724316] ehci_hcd 0000:00:1d.7: debug port 1
[ 0.724323] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 0.724339] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf9ffe400
[ 0.730049] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 0.730078] usb usb2: Manufacturer: Linux 3.6.7-4.fc17.x86_64 ehci_hcd
[ 0.730306] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.730319] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.730344] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 0.730348] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 0.730401] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 0.730435] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000b800
[ 0.730480] usb usb3: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 0.730663] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 0.730667] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 0.730717] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 0.730748] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000b880
[ 0.730791] usb usb4: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 0.730983] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 0.730987] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 0.731043] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[ 0.731066] uhci_hcd 0000:00:1a.2: irq 18, io base 0x0000bc00
[ 0.731108] usb usb5: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 0.731290] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 0.731294] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 0.731341] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[ 0.731364] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000b080
[ 0.731407] usb usb6: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 0.731583] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 0.731586] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 0.731635] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[ 0.731668] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000b400
[ 0.731711] usb usb7: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 0.731892] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 0.731896] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 0.731946] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[ 0.731969] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000b480
[ 0.732020] usb usb8: Manufacturer: Linux 3.6.7-4.fc17.x86_64 uhci_hcd
[ 1.281015] usb 4-2: new low-speed USB device number 2 using uhci_hcd
Is there a way to force Fedora to scan again to add my drive? As I said before, I was able to boot into a liveCD from it.
So, it sees your hard drives but it doesn't even recognize that you have the optical drive even plugged in. There isn't even a device path to reference. I don't know what else to suggest other than see if another distro will recognize it, but I'm doubting it at this point.
Maybe someone more experienced than me will have some suggestions?
As I see it, the drive is not identifying. That's very unusual. If you boot on it, it may even work. But the BIOS has a record of what's installed and can simply address the correct bus and set it reading on block 1.
I would suspect connections, power supply. Then I would time out, and call it a failed drive. It's unusual but not unknown for a circuit failure to kill a disk. Absolutely nothing else suggests itself.
This weekend I'll take a look at the BIOS, confirm once more whether it can boot a liveCD, and report back. when I did some googling, I did see a SuSe user complaining that a kernel change had left his ATA optical drives inaccessible while his SATA one would work. I do know that I have tried two different PATA drives in this computer with the same symptoms. So if anything hardware is broken, it'd have to be the MOBO, not the drive. Unless I coincidentally have two broken PATA optical drives? Which mathematically COULD happen, but is unlikely.