* Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
@ 2006-01-04 19:54 andyliebman
2006-01-04 20:13 ` Matan Peled
2006-01-04 20:24 ` Randy.Dunlap
0 siblings, 2 replies; 6+ messages in thread
From: andyliebman @ 2006-01-04 19:54 UTC (permalink / raw)
To: linux-kernel
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
Can't find the magic formula. Help would be appreciated.
Andy Liebman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
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
1 sibling, 1 reply; 6+ messages in thread
From: Matan Peled @ 2006-01-04 20:13 UTC (permalink / raw)
To: andyliebman; +Cc: linux-kernel
andyliebman@aol.com wrote:
> 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.
If all your drives are S/ATA, your CDROM should be the only /dev/hd? device.
if you try 'ls /dev/hd?', doesn't it show anything?
--
[Name ] :: [Matan I. Peled ]
[Location ] :: [Israel ]
[Public Key] :: [0xD6F42CA5 ]
[Keyserver ] :: [keyserver.kjsl.com]
encrypted/signed plain text preferred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
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 ` Randy.Dunlap
2006-01-04 21:42 ` andy liebman
1 sibling, 1 reply; 6+ messages in thread
From: Randy.Dunlap @ 2006-01-04 20:24 UTC (permalink / raw)
To: andyliebman; +Cc: linux-kernel
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.
> Can't find the magic formula. Help would be appreciated.
--
~Randy
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
2006-01-04 20:13 ` Matan Peled
@ 2006-01-04 20:24 ` andy liebman
0 siblings, 0 replies; 6+ messages in thread
From: andy liebman @ 2006-01-04 20:24 UTC (permalink / raw)
To: chaosite; +Cc: linux-kernel
Says "no such file or directory" for ANY /dev/hd*. And Mandrake's
hardware detection doesn't show any other hard drive device other than
the OS drive.
chaosite@gmail.com wrote:
> andyliebman@aol.com wrote:
>> 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.
>
> If all your drives are S/ATA, your CDROM should be the only /dev/hd?
> device.
>
> if you try 'ls /dev/hd?', doesn't it show anything?
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
2006-01-04 20:24 ` Randy.Dunlap
@ 2006-01-04 21:42 ` andy liebman
2006-01-04 21:52 ` Randy.Dunlap
0 siblings, 1 reply; 6+ messages in thread
From: andy liebman @ 2006-01-04 21:42 UTC (permalink / raw)
To: rdunlap; +Cc: linux-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.
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Atapi CDROM, SATA OS drive, and 2.6.14+ kernel
2006-01-04 21:42 ` andy liebman
@ 2006-01-04 21:52 ` Randy.Dunlap
0 siblings, 0 replies; 6+ messages in thread
From: Randy.Dunlap @ 2006-01-04 21:52 UTC (permalink / raw)
To: andy liebman; +Cc: rdunlap, linux-kernel
On Wed, 4 Jan 2006, andy liebman wrote:
> 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.
or Unable to mount root filesystem ??
Are your SCSI & SATA drivers built as loadable modules or
built into the kernel image?
Why use an inited at all?
> Any other ideas?
>
> >
> >> Can't find the magic formula. Help would be appreciated.
--
~Randy
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-01-04 21:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2006-01-04 21:52 ` Randy.Dunlap
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.