From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: More on the VIA KT133 chipset misbehaving in Linux
Date: Mon, 29 Jan 2001 02:19:27 -0600 [thread overview]
Message-ID: <3A75278F.B41B492B@bigfoot.com> (raw)
The VIA KT133 chipset exhibits the following bugs under Linux 2.2.17 and
2.4.0:
1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
locks for a bit
2) Detects a maximum of 64mb of ram, unless worked around by the "mem="
switch
3) The clock drifts slowly (more so under heavy load than light load),
leaking time.
I think #2 is because e820h memory detection is not properly implemented on
the KT133 chipset, or because of some silly BIOS bug that VIA has not
addressed. I have no idea yet why #1 and #3 happen. If any gurus out there
have any pointers on where I can look, and what I should prod, I know my way
around with a compiler and editor ;)
--
www.kuro5hin.org -- technology and culture, from the trenches.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-29 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 8:19 Dylan Griffiths [this message]
2001-01-29 11:14 ` More on the VIA KT133 chipset misbehaving in Linux Adrian Cox
2001-01-29 11:30 ` safemode
2001-01-29 11:40 ` Adrian Cox
2001-01-29 11:48 ` Lars Gaarden
2001-01-30 1:02 ` Matthew Fredrickson
2001-01-29 16:01 ` Benson Chow
2001-02-02 14:55 ` Rogerio Brito
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 9:20 Quim K Holland
2001-01-29 10:20 ` David Raufeisen
2001-01-29 14:14 ` Mark Hahn
[not found] <Pine.LNX.4.10.10101290853030.26212-100000@coffee.psychology.mcmaster.ca>
2001-01-29 18:36 ` Dylan Griffiths
2001-02-02 16:30 Dunlap, Randy
2001-02-05 3:00 ` Rogerio Brito
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=3A75278F.B41B492B@bigfoot.com \
--to=dylan_g@bigfoot.com \
--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.