Alan,
I just gave 2.6.16-rc1-mm5 a shot on my old VIA-based Duron machine,
and everything seems to work fine. I notice PATA CD-ROMs still aren't
being recognised (with libata.atapi_enabled=1) which is a bit of a
shame, but fortunately I won't be needing to use the CD-ROM on this
machine at all. In fact this machine has so little use that I'm quite
happy to surrender it to testing.
HTH,
Chris
PS: relevant details below:
[ 17.983579] libata version 1.20 loaded.
[ 17.983639] pata_via 0000:00:07.1: version 0.1.2
[ 17.983675] PCI: Via IRQ fixup for 0000:00:07.1, from 255 to 0
[ 17.983929] ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma
0xFFA0 irq 14
[ 18.140987] ata1: dev 0 cfg 49:2f00 82:74eb 83:43ea 84:4000
85:7469 86:0002 87:4000 88:203f
[ 18.141001] ata1: dev 0 ATA-5, max UDMA/100, 60036480 sectors: LBA
[ 18.141094] via_do_set_mode: Mode=12 ast broken=N udma=100 mul=3
[ 18.141191] via_do_set_mode: Mode=69 ast broken=N udma=100 mul=3
[ 18.141517] ata1: dev 0 configured for UDMA/100
[ 18.141579] scsi0 : pata_via
[ 18.141961] Vendor: ATA Model: IBM-DTLA-307030 Rev: TX4O
[ 18.142200] Type: Direct-Access ANSI SCSI
revision: 05
[ 18.142532] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma
0xFFA8 irq 15
[ 18.452348] scsi1 : pata_via
[ 18.452687] SCSI device sda: 60036480 512-byte hdwr sectors (30739
MB)
[ 18.452801] sda: Write Protect is off
[ 18.452852] sda: Mode Sense: 00 3a 00 00
[ 18.452874] SCSI device sda: drive cache: write back
[ 18.453085] SCSI device sda: 60036480 512-byte hdwr sectors (30739
MB)
[ 18.453187] sda: Write Protect is off
[ 18.453236] sda: Mode Sense: 00 3a 00 00
[ 18.453258] SCSI device sda: drive cache: write back
[ 18.453325] sda: sda1 sda2
[ 18.463389] sd 0:0:0:0: Attached scsi disk sda
0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/
VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at ffa0 [size=16]
Capabilities: [c0] Power Management version 2
00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: a1 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00
On Mer, 2006-02-08 at 09:58 +0000, Chris Boot wrote:
> and everything seems to work fine. I notice PATA CD-ROMs still aren't
> being recognised (with libata.atapi_enabled=1) which is a bit of a
> shame, but fortunately I won't be needing to use the CD-ROM on this
> machine at all. In fact this machine has so little use that I'm quite
> happy to surrender it to testing.
What ports are the CDROM devices attached to. I'd expect to see them
found and reported as "being ignored" so it may indicate a bigger
problem.
Alan Cox wrote:
> On Mer, 2006-02-08 at 09:58 +0000, Chris Boot wrote:
>> and everything seems to work fine. I notice PATA CD-ROMs still aren't
>> being recognised (with libata.atapi_enabled=1) which is a bit of a
>> shame, but fortunately I won't be needing to use the CD-ROM on this
>> machine at all. In fact this machine has so little use that I'm quite
>> happy to surrender it to testing.
>
> What ports are the CDROM devices attached to. I'd expect to see them
> found and reported as "being ignored" so it may indicate a bigger
> problem.
>
>
The HDD (that works) is Primary Master, the CD-RW is Secondary Master. I'll give
-rc2-mm1 a shot later today, and maybe even -rc2 with your separate patches and
let you know.
HTH,
Chris
--
Chris Boot
[email protected]
http://www.bootc.net/
Chris Boot wrote:
> Alan Cox wrote:
>> On Mer, 2006-02-08 at 09:58 +0000, Chris Boot wrote:
>>> and everything seems to work fine. I notice PATA CD-ROMs still
>>> aren't being recognised (with libata.atapi_enabled=1) which is a
>>> bit of a shame, but fortunately I won't be needing to use the
>>> CD-ROM on this machine at all. In fact this machine has so little
>>> use that I'm quite happy to surrender it to testing.
>>
>> What ports are the CDROM devices attached to. I'd expect to see them
>> found and reported as "being ignored" so it may indicate a bigger
>> problem.
>>
>>
>
> The HDD (that works) is Primary Master, the CD-RW is Secondary Master.
> I'll give -rc2-mm1 a shot later today, and maybe even -rc2 with your
> separate patches and let you know.
2.6.16-rc2-mm1 behaved the same way as 2.6.16-rc1-mm5.
2.6.16-rc2-ide2 detects the drive properly:
[ 17.263614] libata version 1.20 loaded.
[ 17.263689] pata_via 0000:00:07.1: version 0.1.3
[ 17.263725] PCI: Via IRQ fixup for 0000:00:07.1, from 255 to 0
[ 17.263936] ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xFFA0
irq 14
[ 17.426003] ata1: dev 0 cfg 49:2f00 82:74eb 83:43ea 84:4000 85:7469
86:0002 87:4000 88:203f
[ 17.426016] ata1: dev 0 ATA-5, max UDMA/100, 60036480 sectors: LBA
[ 17.426115] via_do_set_mode: Mode=12 ast broken=N udma=100 mul=3
[ 17.426210] via_do_set_mode: Mode=69 ast broken=N udma=100 mul=3
[ 17.426536] ata1: dev 0 configured for UDMA/100
[ 17.426597] scsi0 : pata_via
[ 17.426991] Vendor: ATA Model: IBM-DTLA-307030 Rev: TX4O
[ 17.427230] Type: Direct-Access ANSI SCSI
revision: 05
[ 17.430290] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xFFA8
irq 15
[ 17.749845] ata2: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000
86:0000 87:0000 88:0000
[ 17.749855] ata2: dev 0 ATAPI, max MWDMA2
[ 17.752637] via_do_set_mode: Mode=12 ast broken=N udma=100 mul=3
[ 17.755464] via_do_set_mode: Mode=34 ast broken=N udma=100 mul=3
[ 17.758726] ata2: dev 0 configured for MWDMA2
[ 17.761523] scsi1 : pata_via
[ 17.765617] Vendor: HL-DT-ST Model: CD-RW GCE-8240B Rev: 1.07
[ 17.768613] Type: CD-ROM ANSI SCSI
revision: 05
[ 17.771861] SCSI device sda: 60036480 512-byte hdwr sectors (30739 MB)
[ 17.774809] sda: Write Protect is off
[ 17.777649] sda: Mode Sense: 00 3a 00 00
[ 17.777676] SCSI device sda: drive cache: write back
[ 17.780665] SCSI device sda: 60036480 512-byte hdwr sectors (30739 MB)
[ 17.783570] sda: Write Protect is off
[ 17.786433] sda: Mode Sense: 00 3a 00 00
[ 17.786459] SCSI device sda: drive cache: write back
[ 17.789322] sda: sda1 sda2
[ 17.802723] sd 0:0:0:0: Attached scsi disk sda
[ 17.886602] sr0: scsi3-mmc drive: 24x/40x writer cd/rw xa/form2 cdda tray
[ 17.889558] Uniform CD-ROM driver Revision: 3.20
[ 17.892641] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 17.892737] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 17.895786] sr 1:0:0:0: Attached scsi generic sg1 type 5
My next step will be to play with the CD drive. Any hints on
stress-testing the drive? Obviously writing a CD then comparing to the
ISO will be one step, but any others?
HTH,
Chris
On Mer, 2006-02-08 at 15:44 +0000, Chris Boot wrote:
> My next step will be to play with the CD drive. Any hints on
> stress-testing the drive? Obviously writing a CD then comparing to the
> ISO will be one step, but any others?
The PATA specific code is almost entirely in the setup stages. Once the
setup is done then (with the exception of early PIIX devices, radisys,
triflex and a couple of other oddities) there is no "new" code actually
being run.
Alan
On 8 Feb 2006, at 17:26, Alan Cox wrote:
> On Mer, 2006-02-08 at 15:44 +0000, Chris Boot wrote:
>> My next step will be to play with the CD drive. Any hints on
>> stress-testing the drive? Obviously writing a CD then comparing to
>> the
>> ISO will be one step, but any others?
>
> The PATA specific code is almost entirely in the setup stages. Once
> the
> setup is done then (with the exception of early PIIX devices, radisys,
> triflex and a couple of other oddities) there is no "new" code
> actually
> being run.
>
> Alan
>
Well, I've just tried 2.6.16-rc2-ide2 on another VIA-based machine
and it seems to work just fine, allowing me to say CONFIG_IDE=n :-)
The CD drives work just fine including writing CDs, so I'm going to
try writing a DVD soon, which should stress it a little more.
However, I keep getting the following messages in dmesg:
[4294985.285000] Assertion failed! qc->n_elem > 0,drivers/scsi/libata-
core.c,ata_fill_sg,line=2635
[4294985.377000] Assertion failed! qc->n_elem > 0,drivers/scsi/libata-
core.c,ata_fill_sg,line=2635
This seems mostly harmless as everything seems to just work, but
curious nonetheless.
HTH,
Chris
--
Chris Boot
[email protected]
http://www.bootc.net/