public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogerio Brito <rbrito@iname.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: More on the VIA KT133 chipset misbehaving in Linux
Date: Fri, 2 Feb 2001 12:55:35 -0200	[thread overview]
Message-ID: <20010202125535.A6248@iname.com> (raw)
In-Reply-To: <3A75278F.B41B492B@bigfoot.com>
In-Reply-To: <3A75278F.B41B492B@bigfoot.com>

On Jan 29 2001, Dylan Griffiths wrote:
> 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 know that I am late here, but I'm also using a via KT133
	chipset with a Duron 600MHz and I'm using a kernel 2.2.18 here
	with the IDE patches and I'm not seeing anything of the above
	problems. Everything just works fine.

	What are you using? I'm using an Asus A7V, with BIOS 1003 (I
	didn't upgrade it, since I'm terribly scarred of it going
	wrong and not being to boot again).

	This is with kernel 2.2.18 (no signs of filesystem corruption
	also, and I have UDMA/66 enabled, but my system is not exactly
	stressed).

> I think #2 is because e820h memory detection

	While I don't have problems with the Duron above, I do have a
	486 here with 8MB of memory that I intend to use as a router
	for my local LAN, but 2.4.0 only recognizes 7MB, while 2.2.18
	recognizes all 8MB. Under 2.4.0 (I haven't tried 2.4.1 yet), I
	used a mem=8M option and it worked fine, but I don't know if
	this is indeed safe or not (I'd guess that it would be, since
	the 2.2 kernels use all memory, but you never know).


	[]s, Roger...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-
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/

  parent reply	other threads:[~2001-02-02 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29  8:19 More on the VIA KT133 chipset misbehaving in Linux Dylan Griffiths
2001-01-29 11:14 ` 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 [this message]
  -- 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=20010202125535.A6248@iname.com \
    --to=rbrito@iname.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox