lidation failed (errno=-5)
ata1.00: disabled
ata1: EH complete
At this point the CF is inoperable. I've had no issue prior to 2.6.20. Is
this a known issue? Is there a fix?
--
View this message in context:
http://www.nabble.com/CF-flash-IDE-failure-to-attach-with-2.6.20%2B-tf3939321.html#a1
Andrew_hall wrote:
> We have a series of machines that use CF as a boot media. Since upgrading to
> 2.6.20 (tried .9-.14), system will boot (from the flash media) but then fail
> to initialise the same media. Here is the dmesg from 2.6.20.14:
>
> ata_piix :00:1f.2: version 2.00ac7
> ata_piix 0
On Mon, 18 Jun 2007 20:26:11 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Andrew_hall wrote:
> > We have a series of machines that use CF as a boot media. Since upgrading to
> > 2.6.20 (tried .9-.14), system will boot (from the flash media) but then fail
> > to initialise the same media. Here is t
> >
> > 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
> > 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 "unsubscr
Andrew Hall wrote:
>>> 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,
> 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 actuall
Andrew Hall wrote:
>> 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.
>
>
> 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 suppo
Andrew Hall wrote:
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 PA
> 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 th
> 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
12 matches
Mail list logo
