From: "Stephen John Smoogen" <smooge@gmail.com>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: jeremy@emperorlinux.com, linux-kernel@vger.kernel.org,
linux-precision@dell.com
Subject: Re: 2.6.16.16 Lost CD-ROM Drive
Date: Thu, 1 Feb 2007 09:33:10 -0700 [thread overview]
Message-ID: <80d7e4090702010833u125346f9xc061651c904582f@mail.gmail.com> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA001C3A234@chicken.machinevisionproducts.com>
On 2/1/07, Brian D. McGrew <brian@visionpro.com> wrote:
> On Thu, 2007-02-01 at 07:00 -0800, Brian D. McGrew wrote:
> > Hey guys-
> >
> > Have a Precision workstation with SATA hard drive and SATA CD-ROM. If
> I
> > load Fedora Core 5 with a stock 2.6.15 kernel, life is good.
> >
> > However, I need to use 2.6.16.16. Once I build and install this
> kernel,
> > my CD-ROM drive is gone. There is a log entry in dmesg that says
> "ATAPI
> > not support. Ignoring."
> >
> > If I go into the BIOS and set the SATA operations to Legacy/Compatible
> > then everything is fine. I've rebuilt this kernel about 100 times
> > trying everything I can think of.
> >
> > When I have SATA set to legacy, the HDD and CD are detected as
> /dev/hd*
> > and when they're set to SATA Normal operation the HDD is detected as
> > /dev/sda. If I boot my old 2.6.15 (stock install) kernel then the CD
> is
> > found as /dev/sdc.
> >
> > I've even tried taking the installation default configuration file for
> > the 2.6.15 kernel and just wholesale copying it into my 2.6.16.16
> kernel
> > and build that way but still no go.
> >
> > What am I missing to get the 2.6.16.16 kernel to see a SATA CD-ROM
> drive
> > in normal, non-legacy move?
>
> Try booting 2.6.16 with the following options:
>
> libata.atapi_enabled=1 ide0=noprobe ide1=noprobe
> -----
>
> Still no go. /dev/sda* is created for the hard drive but no CD-ROM and
> the same ATAPI error in dmesg.
>
I would try the following:
yum update
and boot the kernel and see what modules are linked to the cdrom. I am
thinking it is the sr_mod module. I would check to see if its compiled
in the 2.6.16 code.
--
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
next prev parent reply other threads:[~2007-02-01 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 15:48 Brian D. McGrew
2007-02-01 16:33 ` Stephen John Smoogen [this message]
[not found] <fa.Qe/B25xsBoYC29PSTYgHZvs0dwA@ifi.uio.no>
2007-02-01 23:37 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 15:00 Brian D. McGrew
2007-02-01 15:05 ` Jeremy L. Moles
2007-02-01 15:11 ` Rogelio_Noriega
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=80d7e4090702010833u125346f9xc061651c904582f@mail.gmail.com \
--to=smooge@gmail.com \
--cc=brian@visionpro.com \
--cc=jeremy@emperorlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-precision@dell.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®