Re: Problem with ata layer in 2.6.24

From: Gene Heskett
Date: Tue Jan 29 2008 - 12:05:11 EST


On Tuesday 29 January 2008, Mikael Pettersson wrote:
>Gene Heskett writes:
> > On Tuesday 29 January 2008, Alan Cox wrote:
> > >> As slight change here, I was going to use the same .config as
> > >> 2.6.24-rc8, but just discovered that neither rc8 nor final is finding
> > >> the drivers for my
> > >
> > >If it is not finding a driver that is nothing to do with libata. It
> > > means it's not being loaded by the distribution, or the distribution
> > > kernel is too old (2.6.22) for the hardware - in which case see the
> > > Fedora respins which are on 2.6.23.something right now.
> > >
> > >Alan
> >
> > Home built kernel Alan. But you are as good as anyone to tell me what I
> > need to turn on in order for this dvdwriter to be enabled:
> > [ 28.862478] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max
> > UDMA/66 ....
> > [ 28.908647] ata2.00: limited to UDMA/33 due to 40-wire cable
> > [ 29.081253] ata2.00: configured for UDMA/33
> > ....
> > it has had several 80 wire cables tried, hasn't fixed this, and does not
> > seem to effect its operation when it does work.
> > ....
> > [ 29.132405] scsi 1:0:0:0: CD-ROM LITE-ON DVDRW SHM-165H6S
> > HS06 PQ: 0 ANSI: 5 ....
> > [ 43.450795] scsi 1:0:0:0: Attached scsi generic sg1 type 5
> > -------
> > No further mention of it in dmesg, and k3b cannot find the drive at any
> > /dev/sgX address.
> >
> > .config attached, what else do I need to turn on?
>
>...
>
> > # CONFIG_BLK_DEV_SR is not set
>
>For starters, enable CONFIG_BLK_DEV_SR.

That could stand to be moved or renamed, it is well buried in the menu for the
REAL scsi stuffs, which I don't have any of. Enabled & building now.
Thanks.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
An air of FRENCH FRIES permeates my nostrils!!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/