All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: More on the VIA KT133 chipset misbehaving in Linux
Date: Mon, 29 Jan 2001 12:36:14 -0600	[thread overview]
Message-ID: <3A75B81E.DE8FB783@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101290853030.26212-100000@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:
> mine (gigabyte ga-7zm) shows NONE of these under 2.4.0 or the last
> 100 or so pre-2.4 kernels.  I have no idea what it does on obsolete kernels.

The symptoms have occured on a Gigabyte 7-ZX-1 and a 7-VX-1.  I have a bit
of a suspicion that the 250W power supplies aren't enough for it, but won't
be able to check this until after LWE.
 
> > 3) The clock drifts slowly (more so under heavy load than light load),
> > leaking time.
> 
> this is perfectly normal for all computers; it's why ntpd exists.
> I collect my ntp drifts, and they look perfectly normal (compared
> to drifts over the same period on two other linux boxes and a Sun 420R.)


This isn't 5 seconds in a month or two like my old K6-III/EPoX MVP3-G
setup.  This is 10 minutes every 9-12 hours.  When I woke up this morning,
my clock was off by 15 minutes.  That's a bit abnormal 

> > 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
> 
> perhaps you should upgrade your bios.

Very much so.  I'll have to wait until I can get a DOS boot disk, though,
since flashing doesn't work well in Linux ;)
 
> #1 is usually a sign that gpm/X are not talking the same mouse protocol
> as your mouse.  my board gets along swimmingly with my mouseman/fx
> (I've probably never had anything else on it.)

No GPM.  Logitech PS/2 mouse with imps2.  Microsoft Intelli PS/2 mouse does
the same.

--
    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/

       reply	other threads:[~2001-01-29 18:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10101290853030.26212-100000@coffee.psychology.mcmaster.ca>
2001-01-29 18:36 ` Dylan Griffiths [this message]
2001-02-02 16:30 More on the VIA KT133 chipset misbehaving in Linux Dunlap, Randy
2001-02-05  3:00 ` 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
2001-01-29  8:19 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

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=3A75B81E.DE8FB783@bigfoot.com \
    --to=dylan_g@bigfoot.com \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --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.