At 13:06 8-6-2001 -0400, Nathan J. Mehl wrote:
In the immortal words of Seth Mos (knuffie@xxxxxxxxx):
> Please run this through ksymoops please. If you can boot the machine
> succesfully. If it does boot, does it panic or oops after some time
> or stressing?
> That would be most helpful.
> Have you tried eliminating some of the attached hardware (usb
> hardware for instance).
Generally speaking, when the system _does_ boot, it appears to be
Ahh, I sea that it has a via chipset onboard. Include warning neon sign <here>
Firstly I would sugest updating your bios please.
Via chipset have a grey history of doing funny things and in general behave
in non yet to be described ways on things other then windows :-/
It looks like related to dma issues on the IDE controller.
I could be wrong though, I am not well versed in reading ksymoops output.
Here is a test of various via boards.
Here is a Quote:
"We've been in touch with Alan Cox, top-level Linux kernel developer, to
see exactly what issues they've been seeing with this chipset and this is
what we found out:"
"We were seeing problems with large IDE loads on Linux for a long time yet
VIA would not answer it. VIA still haven't provided good info to the Linux
community. In fact most of what people know even in the non NDA'd BIOS
writing world is by studying how the BIOS changes the behavior. So if your
vendor doesn't have a fix, or you have a Intel/VIA combo setup with no
known fix you are on rocky territory still."
I suggest getting your newest bios and try to build and install a newer
kernel. The newer kernels have better handling of the via chipset.
Read the whole review if you want to know what the general issues are.
I'm gonna wait for a nVIDIA nForce mainboard, yummi :P
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.