linux-kernel - Re: Problem with ata layer in 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Jan 2008 11:32:41 -0500
From:	Gene Heskett <gene.heskett@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Richard Heck <rgheck@...jweil.com>,
	Daniel Barkalow <barkalow@...ervon.org>,
	Zan Lynx <zlynx@....org>,
	Calvin Walton <calvin.walton@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux ide Mailing list <linux-ide@...r.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24

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?

There is also this in the log since I logged in and startx'd:

Jan 29 11:21:26 coyote automount[1923]: create_udp_client:101: hostname lookup failed: Operation not permitted
Jan 29 11:21:26 coyote automount[1923]: create_tcp_client:321: hostname lookup failed: Operation not permitted
Jan 29 11:21:26 coyote automount[1923]: lookup_mount: exports lookup failed for .directory
Jan 29 11:21:26 coyote automount[1923]: lookup_mount: lookup(file): key ".directory" not found in map

however a stop and restart of k3b does not regenerate another set of those.
So I have NDI what actually generated those.

I also discovered that my build nvidia script needs at least one run of
the complete .run version to get all the right versions of the GL stuffs
installed.  That isn't related though, just a passing comment.

FWIW, this is a 2.6.24 kernel ATM, without that kernel argument acpi_use_timer_override.
If my theory is right, I should see some of those errors now.

-- 
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)
You can move the world with an idea, but you have to think of it first.

View attachment ".config" of type "text/plain" (62141 bytes)