From: Rodrigo Souza de Castro <rcastro@ime.usp.br>
To: Alan <alan@clueserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with ASUS CUV4X-D board
Date: Sun, 5 Aug 2001 15:44:17 -0300 [thread overview]
Message-ID: <20010805154417.A691@vinci> (raw)
In-Reply-To: <20010805194247.190906E42@clueserver.org>
In-Reply-To: <20010805194247.190906E42@clueserver.org>; from alan@clueserver.org on Sun, Aug 05, 2001 at 10:27:34AM -0700
On Sun, Aug 05, 2001 at 10:27:34AM -0700, Alan wrote:
> 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...
I have this board with a dual P-III 1 GHz and it works fine
with 2.4.7. Make sure you have at least revision 1007A for you BIOS
(the latest is 1010) and disable MPS 1.4 in BIOS configuration.
--
Rodrigo S. de Castro <rcastro@ime.usp.br>
next prev parent reply other threads:[~2001-08-05 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 17:27 Problem with ASUS CUV4X-D board Alan
2001-08-05 18:44 ` Rodrigo Souza de Castro [this message]
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=20010805154417.A691@vinci \
--to=rcastro@ime.usp.br \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).