Re: Via KT600 support?

[Joe Harrington]

> I also have an Asus A7V600. I'm unsure of the board revision, but I'm
> running BIOS 1005.
 
I am glad to see a positive report with this botherboard (actually,
that was a typo but it's perfectly true, so I'll leave it).  The
problem has turned out to be faulty memory, so I apologize to the list
for wasting your time.  So nobody complains, I used 4 different sticks
of SimpleTech memory in this machine, all with the same results.  They
passed 24 hours of memtest86 with no errors.  But, replacing them with
some Corsair memory fixed the problem.  A Simpletech rep says the
batch that my 4 sticks come from was not a particularly bad batch, but
they are sending boards from another batch that they use in more
applications in hope that it fixes the problem.  They also say this
chipset is particularly finicky about memory.  Needless to say, I
won't be sending them any more of my hard-earned cash: If it says
PC2700 on it, it should perform that way.  This was not "value RAM" to
me.

In case anyone else has similar trouble, I'll answer some of your
questions so it's easier to identify:

> > VC messages indicate problems in different programs each time.
> > Generally the failure happens during package installation, but
> > sometimes it happens earlier.  After the first indication of a
> > problem, one can generally still switch VCs, but eventually that stops
> > working, too.  Frequently, there are several programs indicating
> > problems in the VC screens.

> What are you seeing? Segfaults? Panics? Have you tried the memtest86
> boot option (from the FC1 CDs)?

I ran memtest86 for a day with no errors.  Is there something that can
be done to make its tests more definitive?  Clearly this tool didn't
find the problem, but a few minutes of transferring files did.

VC4 gave messages including:
EIP is at (some process or kernel routine name, different each time)
then a stack and call trace (again, different each time)
then sometimes
Kernel panic: 
also sometimes
Kernel BUG in buffer.c:
sometimes there are several sets of data including the EIP message,
stack trace, etc. for different programs/kernel routines at once.

Sometimes the installer just quits, saying it exited abnormally, and
it does a graceful shutdown without any VC4 errors.

The clues in your report will help a lot now that I have this thing
working.  I wish there were a website for such info, like there is for
laptops.

Thanks again for your report.

--jh--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/