linux-kernel - x86_64 SATA DVD drive + libata trouble

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-next>] [day] [month] [year] [list]

Date:	Fri, 9 Nov 2007 19:33:01 +0100
From:	Bernd Strieder <strieder@...ormatik.uni-kl.de>
To:	linux-kernel@...r.kernel.org
Subject: x86_64 SATA DVD drive + libata trouble

Hello,

please CC me, I'm not subscribed.

If any kernel developer is interested in more specific information 
please mail me, I can build kernels, I can apply patches, though 
have not done it regularly.

I'd like to get the DVD drive working somehow. I have googled a lot 
and did not find any more ideas what to do. Some good keywords to 
find a solution would suffice at that end.

Rough problem description:

I have a Tyan mainboard with NVIDIA chipset CK804. The only 
SATA/IDE device is a SATA DVD combo, the harddisks are on a RAID 
controller from 3ware. The harddisks are fine.

The openSuSE 10.3 boot dvds fail after booting from the BIOS, the 
installation kernel cannot use the DVD drive. That kernel uses 
libata and sata_nv pata_amd as drivers. The drive is recognized 
but it cannot be used. This is the situation probably during 
install from DVD and now in the running system after a network 
install it persists.

Reading from the dvd device /dev/sr0 with dd stops after at most 
119kb of rubbish read. Mounting fails with superblock not found.
When trying to remove the pata_amd module I get an Oops. I tried to 
remove the modules to have a chance to reload them with other 
options (atapi_enable), but that did not help, even after 
rebooting.

A vanilla 2.6.23.1 kernel behaves even less friendly, the dd 
on /dev/sr0 causes a hard reset.

So there are clearly some problems with libata in this system.

I have failed switching away from libata getting the drive to be 
recognized at all.

Thanks for any help,

Bernd Strieder

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/