From: Alan <alan@clueserver.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Problem with ASUS CUV4X-D board
Date: Sun, 5 Aug 2001 10:27:34 -0700 [thread overview]
Message-ID: <20010805194247.190906E42@clueserver.org> (raw)
I am running this under 2.4.3. I will be testing 2.4.7 this afternoon to see
if I can fix the problem.
The board works fine with a uniprocessor kernel.
When booking under the stock mandrake 8.0 kernel, I get cascading error
messages about clock problems and blaming a VIA686A chipset.
This has a VT82C686B PCI chipset.
I tried to find info on the web on this and was not ver successful. (This is
at a friend's house. He is out in the middle on nowhere and is lucky if he
get 28.8k connections.)
It this one of the non-correctable VIA chipsets? Is there a workaround for
this?
It is a dual P-III 733 with a gig of ram. I would hate to see it go to waste.
(Actually it will because it is not at MY house, but that is another
problem. ]:> )
I was going to get one of these boards. I am glad I did not...
next reply other threads:[~2001-08-05 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 17:27 Alan [this message]
2001-08-05 18:44 ` Problem with ASUS CUV4X-D board Rodrigo Souza de Castro
2001-08-06 23:49 ` Alan
2001-08-05 18:45 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010805194247.190906E42@clueserver.org \
--to=alan@clueserver.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.