On Sun, 6 Oct 2002, David wrote:
> On Sat, 5 Oct 2002, James Ralston wrote:
>
> > On Sat, 5 Oct 2002, David wrote:
> >
> > > Automatic configuration of the RAM timings ("By SPD") doesn't
> > > work on this motherboard.
> >
> > WORKSFORME; I've never had any problems with the "By SPD" setting
>
On Sat, Oct 05, 2002 at 05:01:49PM +0800, JCS wrote:
> On Saturday 05 October 2002 16:43, Arjan van de Ven wrote:
> > > hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >
> > BadCRC errors are a cable issue. The drive se
JCS wrote:
On Saturday 05 October 2002 16:43, Arjan van de Ven wrote:
hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
BadCRC errors are a cable issue. The drive sends its data and includes a
crc checksum; the controller re
On Saturday 05 October 2002 16:43, Arjan van de Ven wrote:
> > hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> BadCRC errors are a cable issue. The drive sends its data and includes a
> crc checksum; the controller rece
On another vt8233a topic: it seems there are more people than us who are
having problems - here's what bugzilla says:
11 bugs found.
ID Sev Pri Plt Owner State Result Summary
54905 nor nor i38 [EMAIL PROTECTED] ASSIUnable to get sound
from VIA VT82C686(Appollo Super AC97/Aud
56505 nor
On Sat, 5 Oct 2002, James Ralston wrote:
> On Sat, 5 Oct 2002, David wrote:
> > Automatic configuration of the RAM timings ("By SPD") doesn't work
> > on this motherboard.
> WORKSFORME; I've never had any problems with the "By SPD" setting on
> my Asus A7V333, regardless of the BIOS version (curren
James Ralston wrote:
On Sat, 5 Oct 2002, Paul Gear wrote:
...
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide1: reset: success
The dma_intr errors and the ide reset repeat several times during
the boot. After it's booted, a
Arjan van de Ven wrote:
hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
BadCRC errors are a cable issue. The drive sends its data and includes a
crc checksum; the controller receives the data and notices the data is
corrupt
> hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
BadCRC errors are a cable issue. The drive sends its data and includes a
crc checksum; the controller receives the data and notices the data is
corrupted via the checksum.
On Sat, 5 Oct 2002, David wrote:
> > > I had some major stability problems at first with my A7V333,
> > > until I worked around the BIOS bugs. No problems since. :)
> >
> > What BIOS does the A7V333 use? What were the symptoms of your
> > stability problems?
>
> Automatic configuration of the
Hi.
I have a Gigabyte GA-7VRXP. Upgrading from 7.3, I now have DMA on my
hard drives (yay!) but I've lost my USB hi-fi link device. usbview
doesn't even see it (boo).
I've not noticed stability problems, but I'll leave it running to see
how it goes.
b
Peter L. Hurd wrote:
Hey All,
I've se
On Sat, 5 Oct 2002, Paul Gear wrote:
> Here's what happens on my system on IDE initialization:
>
> VP_IDE: IDE controller on PCI bus 00 dev 89
> PCI: Hardcoded IRQ 14 for device 00:11.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> ide: Assuming 33MHz system
iming.h wasn't updated. That is *not*
the case; ide-timing.h was patched as well.
In short, not only did Red Hat incorporate my vt8233a southbridge
patch into the kernel, they pulled more recent bits than I used.
(I'll go update my web page accordingly.)
> Machines running the u
On Sat, 5 Oct 2002, Paul Gear wrote:
> David wrote:
> >Does it work okay if you unplug the DVD drive? Have you tried replacing
> >or re-positioning the ATA cable?
> I'll try some of these after i've finished my assignment for college... ;-)
Good idea. :)
> Have you shared a bus between a DVD &
David wrote:
...
VP_IDE: VIA vt8233a (rev 00) IDE UDMA133 controller on pci00:11.1
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
hda: MAXTOR 6L080J4, ATA DISK drive
hdc: MAXTOR 6L080J4, ATA DISK drive
hdd: LI
On Sat, 5 Oct 2002, Paul Gear wrote:
> >On 4 Oct 2002, Peter L. Hurd wrote:
>
> I'm using a Gigabyte 7VRX (same chipset as the Asus, IIRC) with an
> Athlon 1800+, and i'm experiencing the same problems with IDE errors
> that Peter is (see below).
> ...
> It still doesn't seem to be right. Here'
David wrote:
On 4 Oct 2002, Peter L. Hurd wrote:
I've seen some mention of this in this list already, and I'd like to add
my 2c.
The kernel in 8.0 does not play well with the southbridge vt8233a
chipset.
It works fine on my A7V333.
I'm using a Gigabyte 7VRX (same chipset as the Asu
17 matches
Mail list logo
