On Monday 26 November 2001 18:07, you wrote:
> Hi people,
>
>       Is there someone using MDK 8.0 and/or MDK 8.1 with Asus mobo A7A
> (Ali chipset) and/or A7M (AMD chipset)?  I intend to mount a Athlon 1.4
> with DDR memory and I want to be sure it will work fine. I would use a
> RIVA TNT graphic card too.
>
>       Both chipset are unknown to me (but I know VIA pretty well to not
> want it anymore).
>
>       I did not decide if I'll use MDK 8.0 or 8.1 (the ideal would be a
> 8.05 :), so that's why I would like to have a up-to-date computer, but
> stable and compatible.
>
>       I would thank any suggestion.


You should be concerned if it has a Winbond clock chip since the error 
messages will drive you nuts. Here is teh etxt of a reply about this matter.

I am ditching my ASUS A7A266 mobo for an Abit KG7.

Hoyt


RE: [expert] VIA686A Error Message on a non-VIA686A mobo  (Jose M. Sanchez,  
Tue Nov 20 23:45:17 2001)
 
The problem is not with the ALiMagik or Via chipsets at all!

It's with the brain damaged Winbond Clock chip used on almost all Via
and ALiMagik motherboards.

This timer VARIES in pulse duration and interval, resulting in highly
inaccurate timer references.

Linux is reporting the error, and actually tries to do something about
it. Winblows disregards it. 

If you run winblows you'll see the error manifest as the clock wandering
as much as 15minutes a day. It will also show up if you use the
motherboard monitoring utilities. You'll see power spikes, temperatures
and fan speeds that are erroneous, causing the ASUS monitoring utility
to pop up all the time with warnings.

There is NO fix, and changing out the motherboard for another ALiMagik
or VIA puts you right back into the same boat.

WinBond is aware of the problem but seemingly reluctant to warn the
designers about it as it would present a VERY costly hit for them.

Your only recourse is to disable this error message in the logger. I've
been thinking about changing the timer.c and timer.h files in the kernel
to avoid the error generation. Each error generated causes things to
pause momentarily to handle the event.

This response belongs in the FAQ, as I've posted it routinely once a
month.

-JMS

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to