Messages in this thread | | | Date | Wed, 04 Jan 2006 16:42:57 -0500 | From | andy liebman <> | Subject | Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel |
| |
rdunlap@xenotime.net wrote: > On Wed, 4 Jan 2006 andyliebman@aol.com wrote: > >> Can somebody tell me what changed in the 2.6.14 kernel that doesn't >> allow me to access my CDROM drive when my OS drive is SATA? >> >> I have an image of a working 2.6.14 system that was installed on an IDE >> drive. I restored the image to a SATA drive, changed a few lines in >> /etc/fstab and /etc/lilo.conf so that they refer to /dev/sd* devices >> instead of /dev/hd* devices. >> >> I also modified /etc/modprobe.conf so that it is identical to the file >> that Mandriva 2006 produces when installed directly to a SATA drive >> (but Mandriva 2006 has the 2.6.12.x kernel). >> >> I can't mount my CDROM when running 2.6.14.x >> >> I have googled this for several days. I have seen posts about passing >> options to the kernel and including extra lines in modprobe.conf like: >> >> libata atapi_enabled=1 > > should be: > libata.atapi_enabled=1 > if libata is built into the kernel image.
Well, I added that to my modprobe.conf file, remade the initrd. But then on rebooting I got a kernel panic -- VFS not able to sync root filesystem.
Any other ideas?
> >> Can't find the magic formula. Help would be appreciated. >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |