linux-kernel - Re: 2.6.20-rc6 libata PATA ATAPI CDROM is not working

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200702171352.09778.bzolnier@gmail.com>
Date:	Sat, 17 Feb 2007 13:52:09 +0100
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Joel Soete <soete.joel@...rlet.be>
Cc:	Tejun Heo <htejun@...il.com>, Luming Yu <luming.yu@...il.com>,
	Alan Cox <alan@...hat.com>, Ioan Ionita <opslynx@...il.com>,
	Alan <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	jgarzik@...ox.com
Subject: Re: 2.6.20-rc6 libata PATA ATAPI CDROM is not working


On Saturday 17 February 2007 13:07, Joel Soete wrote:
> 
> Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> > 
> > On Tuesday 13 February 2007 18:35, Joel Soete wrote:
> > 
> >> scsi3 : ata_piix
> >> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> >> ata1.00: ata1: dev 0 multi count 16
> >> ata1.00: configured for UDMA/33
> > 
> > <...>
> > 
> >> scsi 3:0:0:0: Direct-Access     ATA      QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
> > 
> > IDE driver with CONFIG_IDEDMA_IVB=y should give you UDMA/66.
> > 
> I didn't find this config option but most probably because I remove IDE support from my kernel to test this libata?

Yes, it is the last option in the IDE config menu.

> mmm btw, I still have to check how to access my floppy with libata?
> 
> that said as far as:
> # dmesg
> [snip]
> ata_piix 0000:00:07.1: version 2.00ac7
> ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
> ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
> scsi3 : ata_piix
> [snip]
> (sorry, it seems that I forgot to copy it)
> 
> it make sense to me to limit to this bus capability?

Yes, since the controller's max UDMA mode is UDMA/33.

> > Could you send me output of "hdparm --Istdout /dev/sdc" command?
> > 
> # hdparm --Istdout /dev/sdc
> 
> /dev/sdc:
> 045a 3fff 0000 0010 7e00 5332 003f 0000
> 0000 5154 3937 3330 3036 3332 3633 3937
> 2020 2020 2020 2020 0003 0344 0004 4130
> 332e 3039 3030 5155 414e 5455 4d20 4649
> 5245 4241 4c4c 6c63 7431 3020 3135 2020
> 2020 2020 2020 2020 2020 2020 2020 8010
> 0000 0f00 4000 0200 0200 0007 3fff 0010
> 003f fc10 00fb 0110 a500 01bf 0000 0007
> 0003 0078 0078 0078 0078 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 001e 0011 346b 4001 4000 3468 0001 4000
> 041f 0008 0000 0000 fffe 0040 0000 0000

the word 88 == 0x041f => max UDMA mode is UDMA/66

the word 93 == 0x0040 => no 80-wire cable detected

However it doesn't really matter because controller itself
is limited to UDMA/33.

Thanks,
Bart
-
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/