On Tue, 27 Feb 2001, Vojtech Pavlik wrote:
> On Mon, Feb 26, 2001 at 03:23:18PM -0500, Mark Hahn wrote:
> > > the cable length in mind. Anybody out there know if there's a max cable
> > > length for the ATA/100 spec??
> >
> > 18", like *all* ide/ata cables.
>
> Actually the ATA/66 and
On Tue, 27 Feb 2001, Vojtech Pavlik wrote:
On Mon, Feb 26, 2001 at 03:23:18PM -0500, Mark Hahn wrote:
the cable length in mind. Anybody out there know if there's a max cable
length for the ATA/100 spec??
18", like *all* ide/ata cables.
Actually the ATA/66 and ATA/100 cables are
On Mon, Feb 26, 2001 at 03:23:18PM -0500, Mark Hahn wrote:
> > the cable length in mind. Anybody out there know if there's a max cable
> > length for the ATA/100 spec??
>
> 18", like *all* ide/ata cables.
Actually the ATA/66 and ATA/100 cables are specified to be exactly 18",
not longer, not
> the cable length in mind. Anybody out there know if there's a max cable
> length for the ATA/100 spec??
18", like *all* ide/ata cables.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
At 01:56 PM 2/25/2001 +, Alan Cox wrote:
> > hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
> > ide0: reset: success
> >
> > Again, if it's really a cable problem, then ASUS is selling
> > cables that don't work with
jerry ([EMAIL PROTECTED])>I also am using the cable supplied with the mobo
(Abit kt7) so I
do not
> think it is ASUS specific. More likey it is releated to the
> VIA chipset and/or driver.
>
> If I compile kernel with "Generic PCI bus-master DMA support"
> and run "hdparm -d1 /dev/hda" I
jerry ([EMAIL PROTECTED])I also am using the cable supplied with the mobo
(Abit kt7) so I
do not
think it is ASUS specific. More likey it is releated to the
VIA chipset and/or driver.
If I compile kernel with "Generic PCI bus-master DMA support"
and run "hdparm -d1 /dev/hda" I get 700%
At 01:56 PM 2/25/2001 +, Alan Cox wrote:
hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
ide0: reset: success
Again, if it's really a cable problem, then ASUS is selling
cables that don't work with UDMA66 (but
the cable length in mind. Anybody out there know if there's a max cable
length for the ATA/100 spec??
18", like *all* ide/ata cables.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, Feb 26, 2001 at 03:23:18PM -0500, Mark Hahn wrote:
the cable length in mind. Anybody out there know if there's a max cable
length for the ATA/100 spec??
18", like *all* ide/ata cables.
Actually the ATA/66 and ATA/100 cables are specified to be exactly 18",
not longer, not
...
> It happens when dma is enabled by hdparm -d1 /dev/hda or when dma is
> enabled automatically by the kernel.
>
> I have an Abit kt7 mb with the kt133 chipset,Athlon 900 , 128MB mem,
> quantum fireball 20G disk, gcc 2-95-2 , glibc 2-2-1.
>
> There are no problems with dma disabled.
>
> I
I also am using the cable supplied with the mobo (Abit kt7) so I do not
think it is ASUS specific. More likey it is releated to the
VIA chipset and/or driver.
If I compile kernel with "Generic PCI bus-master DMA support"
and run "hdparm -d1 /dev/hda" I get 700% performance increase
on hdparm -t
> hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
> ide0: reset: success
>
> Again, if it's really a cable problem, then ASUS is selling
> cables that don't work with UDMA66 (but they sell it as
> UDMA66).
To get ATA66
In article <20010225060326.K127@pervalidus> you wrote:
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I think I saw that with broken Drives, too.
Greetings
Bernd
-
To unsubscribe from this list: send the line "unsubscribe
Alan Cox wrote:
>> I was not sure if the VIA82CXXX option should be set with the
>> via kt133 chipset , but setting it results in hundreds of
>> hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
>> hda: dma_intr:error=0x84 { DriveStatusError BadCRC }
>> mesages along with the uhci:
Alan Cox wrote:
I was not sure if the VIA82CXXX option should be set with the
via kt133 chipset , but setting it results in hundreds of
hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr:error=0x84 { DriveStatusError BadCRC }
mesages along with the uhci: errors
In article 20010225060326.K127@pervalidus you wrote:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I think I saw that with broken Drives, too.
Greetings
Bernd
-
To unsubscribe from this list: send the line "unsubscribe
hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
ide0: reset: success
Again, if it's really a cable problem, then ASUS is selling
cables that don't work with UDMA66 (but they sell it as
UDMA66).
To get ATA66 working
I also am using the cable supplied with the mobo (Abit kt7) so I do not
think it is ASUS specific. More likey it is releated to the
VIA chipset and/or driver.
If I compile kernel with "Generic PCI bus-master DMA support"
and run "hdparm -d1 /dev/hda" I get 700% performance increase
on hdparm -t
...
It happens when dma is enabled by hdparm -d1 /dev/hda or when dma is
enabled automatically by the kernel.
I have an Abit kt7 mb with the kt133 chipset,Athlon 900 , 128MB mem,
quantum fireball 20G disk, gcc 2-95-2 , glibc 2-2-1.
There are no problems with dma disabled.
I was not
> I get the following message when copying a 300MB directory under 2.4.2.
>
> uhci:host system error, PCI problems?
> uhci:host controller halted, very bad
The USB code should recover from that , if it doesnt report it to the USB
folks.
> I was not sure if the VIA82CXXX option should be set
I get the following message when copying a 300MB directory under 2.4.2.
uhci:host system error, PCI problems?
uhci:host controller halted, very bad
This does not happen under 2.4.1 and it happens every time under 2.4.2.
The system still runs fine except for usb mouse.
All of the files in the
I get the following message when copying a 300MB directory under 2.4.2.
uhci:host system error, PCI problems?
uhci:host controller halted, very bad
This does not happen under 2.4.1 and it happens every time under 2.4.2.
The system still runs fine except for usb mouse.
All of the files in the
I get the following message when copying a 300MB directory under 2.4.2.
uhci:host system error, PCI problems?
uhci:host controller halted, very bad
The USB code should recover from that , if it doesnt report it to the USB
folks.
I was not sure if the VIA82CXXX option should be set with
24 matches
Mail list logo
