On Wed, 11 Oct 2000, Alan Cox wrote:
> > > have the rules for testing if the driver/host/device register and report
> > > that all signals are valid and stable.
> >
> > Yes, I had some "interesting" modifications to a lot of my /usr when I
> > tried to activate UDMA4 under RH7.0 (I don't believ
On Wed, 11 Oct 2000, Alan Cox wrote:
Alan... The following errors are what I am getting with your
pre-2.2.18pre15 release.
Does this mean anything. It only concerns ONE of my two physical drives.
I can take it out but it works fine with 2.2.17 ??
> > hda: dma_intr: status=0x51 { DriveReady See
On Wed, 11 Oct 2000, Chris Evans wrote:
> ...
> # IDE patch provides UDMA66 support, but is known to corrupt filesystems
> # on a few systems, so is not applied by default.
> Patch151: linux-2.2.16-ide-2805.patch
> ...
> # Dangerous IDE patch available but off by default
> #%patch151 -p1
> ..
Send me the follow files out of proc please.
/proc/ide/hdx/identify (x == a,b,c,d)
/proc/ide/piix
/proc/ide/ide0/config files
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Pl
On Wed, 11 Oct 2000, Alan Cox wrote:
> The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised
> it got upset 8)
Ah yes you're correct. I saw the patch in the kernel SRPM but didn't look
far enough to see:
...
# IDE patch provides UDMA66 support, but is known to corrupt fi
On Wed, 11 Oct 2000, Alan Cox wrote:
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> Bad CRC is a cable error. That could be misconfiguration but could also be
> crap cables
It went away when I enabled PIIX4 support
> > have the rules for testing if the driver/host/device register and report
> > that all signals are valid and stable.
>
> Yes, I had some "interesting" modifications to a lot of my /usr when I
> tried to activate UDMA4 under RH7.0 (I don't believe my hardware is
> capable of UDMA4!)
The 2.2 ke
On Tue, 10 Oct 2000, Andre Hedrick wrote:
> Also set this option "CONFIG_IDEDMA_IVB" because you are in the
> transistion period of drive manufacturing.
Turned that on, applied the patch. BTW, your patch seems to make the
"Speed warnings" failure _more_ likely??
Still refuses to activate UDMA3
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Bad CRC is a cable error. That could be misconfiguration but could also be
crap cables
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Also set this option "CONFIG_IDEDMA_IVB" because you are in the
transistion period of drive manufacturing.
On Tue, 10 Oct 2000, Chris Evans wrote:
>
> On Tue, 10 Oct 2000, Andre Hedrick wrote:
>
> > Basically you have drive that caught in the word93 rules change.
> >
> > However, the error y
On Tue, 10 Oct 2000, Andre Hedrick wrote:
> Basically you have drive that caught in the word93 rules change.
>
> However, the error you got were real and the kernel did properly respeed
> the drive to one step slower. The problem above prevented you from going
> from ATA66 to ATA44, thus you f
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell to ATA33.
You RHS 7.0 kernel does not have all t
12 matches
Mail list logo
