From: andy liebman <andyliebman@aol.com>
To: rdunlap@xenotime.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
Date: Wed, 04 Jan 2006 16:42:57 -0500 [thread overview]
Message-ID: <43BC4161.1030800@aol.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601041224180.19134@shark.he.net>
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.
>
next prev parent reply other threads:[~2006-01-04 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 19:54 Atapi CDROM, SATA OS drive, and 2.6.14+ kernel andyliebman
2006-01-04 20:13 ` Matan Peled
2006-01-04 20:24 ` andy liebman
2006-01-04 20:24 ` Randy.Dunlap
2006-01-04 21:42 ` andy liebman [this message]
2006-01-04 21:52 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BC4161.1030800@aol.com \
--to=andyliebman@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.