Per my other email -- did you try the legacy IDE driver
instead of libata? Can you provide a boot log from that for Tejun?
Further to this the PATA to SATA bridge being used in this case is:
http://www.jmicron.com/JM20330.html
..as you will see only PIO and UDMA modes are supported.
-
To
I'm betting that the SATA/PATA converter is getting confused with
the ata_piix driver's attempt to use MDMA2 on it.
PIO appears to be working fine -- the BIOS uses it to boot,
and libata uses it to do the IDENTIFY operation.
So, try this hack, which should force ata_piix to use only PIO
Here's a slightly modified hack, which should leave your SATA
drive working as well as the CF card.
Tejun / Alan : do we really want to continue attempting mdma2
on a modern chipset such as ICH8 ???
The best mdma2 can do is the same throughput as pio4,
and the bus occupancy is so high
You can certainly also thank Tejun and Jeff,
for making libata so easy to tune with a one-liner liner like this!
Per my other email -- did you try the legacy IDE driver
instead of libata? Can you provide a boot log from that for Tejun?
Too true.. thanks Tejun, Jeff and Alan also.. much
,
-Original Message-
From: Mark Lord [mailto:[EMAIL PROTECTED]
Sent: Thursday, 28 June 2007 12:08 AM
To: Andrew Hall
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
Subject: Re: CF flash PATA on libata failure to attach
Andrew Hall wrote:
This looks a lot like the other CF-card problem
Hello,
I have been wrestling now for several days trying to get a Compact Flash
(IDE) card detected and mounted properly under any version of Linux 2.6.x.
using ICH8 hardware. My understanding is that this hardware uses a SATA to
PATA bridge, and so I have tried unsuccessfully to use the newer
This looks a lot like the other CF-card problem that was being debugged
here over the past week -- the one where POLLING had to be turned on.
Robert de Rooy (copied) was the reporter for that one.
Perhaps you two could compare notes ?
Cheers
Thanks for getting back to me. I read through
Does piix driver work? If so, can you post boot dmesg and the result
of
'hdparm -I /dev/hdX'?
I've still been battling to get this hardware detected with any of the
drivers mentioned previously except the newer libata piix driver. However
when using the old driver and using all-generic-ide
Does piix driver work? If so, can you post boot dmesg and the result
of
'hdparm -I /dev/hdX'?
Unfortunately it doesn't seem to be detected at all, although I'm not
exactly sure which driver you're referring to. I have tried:
New ATA drivers:
Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
I think Tejun would like you to patch the PCI ID for your ICH8
into the Old ATA/IDE PIIXn driver, and then try that.
Maybe I'm a bit slow on the uptake, but how exactly do I do this patch the
PCI ID into the driver? I run a monolithic kernel will all these drivers
compiled in. None of them
I suppose you were using ata_piix too in older kernel, right? Can you
post the boot dmesg of 2.6.19? We used to ignore mwdma mode before and
enabled it at some point after that. That may be the cause here.
Also, please try the attached patch on top of 2.6.20.
Sorry guys, I've actually
For some reason, mwdma doesn't work in libata now. I'm not sure why
tho. Alan, can you enlighten us?
No idea at all. All my hardware is still happy. 2.6.20 is an old
kernel
however so it does predate the fixes you did for ata_piix mode setup ?
Old - yes, but more stable in all other
ata1.00: configured for MWDMA2
For some reason, mwdma doesn't work in libata now. I'm not sure why
tho. Alan, can you enlighten us?
If the CF is having trouble with DMA, how do I specifically turn off DMA
only on this one bus?
-
To unsubscribe from this list: send the line unsubscribe
13 matches
Mail list logo
