RE: More on the VIA KT133 chipset misbehaving in Linux

RE: More on the VIA KT133 chipset misbehaving in Linux

[Dunlap, Randy]

> From: Rogerio Brito [mailto:rbrito@iname.com]
> 
> 	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).

Fixed in 2.4.1 and its pre-patches.

~Randy

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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Rogerio Brito]

On Feb 02 2001, Dunlap, Randy wrote:
> > From: Rogerio Brito [mailto:rbrito@iname.com]
> > 
> > 	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.
> 
> Fixed in 2.4.1 and its pre-patches.

	Thank you very much, Randy. I'll compile 2.4.1 or anything
	newer than this and I'll report back my results.


	Thank you very much again, 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/

Re: More on the VIA KT133 chipset misbehaving in Linux

[Dylan Griffiths]

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/

Re: More on the VIA KT133 chipset misbehaving in Linux

[Quim K Holland]

>>>>> "DG" == Dylan Griffiths <Dylan_G@bigfoot.com> writes:

DG> The VIA KT133 chipset exhibits the following bugs under Linux
DG> 2.2.17 and 2.4.0:
DG> 1) PS/2 mouse cursor randomly jumps to upper right hand corner
DG> of screen and locks for a bit
DG> 2) Detects a maximum of 64mb of ram, unless worked around by the
DG> "mem=" switch
DG> 3) The clock drifts slowly (more so under heavy load than light
DG> load), leaking time.

I am not a guru, but AOpen AK73PRO which uses VIA KT133 does not
show any of these symptoms that you describe (I cannot be sure
about #3 since I run ntp).  You may want to make your hardware
description a bit more specific to help gurus to help you...


------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/


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

Re: More on the VIA KT133 chipset misbehaving in Linux

[David Raufeisen]

On Monday, 29 January 2001, at 01:20:15 (-0800),
Quim K Holland wrote:

>> "DG" == Dylan Griffiths <Dylan_G@bigfoot.com> writes:
>> 
> DG> The VIA KT133 chipset exhibits the following bugs under Linux
> DG> 2.2.17 and 2.4.0:
> DG> 1) PS/2 mouse cursor randomly jumps to upper right hand corner
> DG> of screen and locks for a bit
> DG> 2) Detects a maximum of 64mb of ram, unless worked around by the
> DG> "mem=" switch
> DG> 3) The clock drifts slowly (more so under heavy load than light
> DG> load), leaking time.
> 
> I am not a guru, but AOpen AK73PRO which uses VIA KT133 does not
> show any of these symptoms that you describe (I cannot be sure
> about #3 since I run ntp).  You may want to make your hardware
> description a bit more specific to help gurus to help you...
> 

I experience #2 and #3 on the following board w/ VIA KT133:

BIOS Vendor: American Megatrends Inc.
BIOS Version: 62710
BIOS Release: 07/15/97
Board Vendor: Gigabyte Technology Co. Ltd..
Board Name: 7ZX.
Board Version: 1.0.

ntpdate is run at boot..  

2:14am  up 14:59,  3 users,  load average: 0.00, 0.00, 0.00

And i just ran it again after running uptime, it showed the following:

29 Jan 02:15:20 ntpdate[3879]: step time server 164.67.62.194 offset 11.398730 sec

This is 2.4.1per11 btw.

-- 
David Raufeisen <david@fortyoz.org>
Cell: (604) 818-3596
-
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/

Re: More on the VIA KT133 chipset misbehaving in Linux

[Mark Hahn]

> I am not a guru, but AOpen AK73PRO which uses VIA KT133 does not
> show any of these symptoms that you describe (I cannot be sure
> about #3 since I run ntp).  You may want to make your hardware

my ga-7zm shows none of them either (I also run ntp, and the board 
has a perfectly normal drift history.)

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

More on the VIA KT133 chipset misbehaving in Linux

[Dylan Griffiths]

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/

Re: More on the VIA KT133 chipset misbehaving in Linux

[Adrian Cox]

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

This happens to me about once a month on a BX chipset PII machine here,
and on a KT133 chipset machine I have.  I have to hit ctrl-alt-backspace
to regain control of the console. I always assumed it was a bug in X,
but it never caused me enough trouble to actually make me pursue it.

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

Re: More on the VIA KT133 chipset misbehaving in Linux

[safemode]

Adrian Cox wrote:

> 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
>
> This happens to me about once a month on a BX chipset PII machine here,
> and on a KT133 chipset machine I have.  I have to hit ctrl-alt-backspace
> to regain control of the console. I always assumed it was a bug in X,
> but it never caused me enough trouble to actually make me pursue it.
>
> - Adrian
>

turn off gpm..   fixes the mouse problem immediately.   as in killall -9 gpm
before starting X.


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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Adrian Cox]

safemode wrote:
> Adrian Cox wrote:
> > Dylan Griffiths wrote:
> > > 1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
> > > locks for a bit
> > This happens to me about once a month on a BX chipset PII machine here,
> > and on a KT133 chipset machine I have.  I have to hit ctrl-alt-backspace
> > to regain control of the console. I always assumed it was a bug in X,
> > but it never caused me enough trouble to actually make me pursue it.
> turn off gpm..   fixes the mouse problem immediately.   as in killall -9 gpm
> before starting X.

I don't even have gpm installed on these machines, precisely for this
reason. Whatever it is, it isn't gpm. But I also believe it isn't Via,
and I'm not convinced that it's the kernel.

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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Lars Gaarden]

Adrian Cox wrote:
> 
> 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
> 
> This happens to me about once a month on a BX chipset PII machine here,
> and on a KT133 chipset machine I have.  I have to hit ctrl-alt-backspace
> to regain control of the console. I always assumed it was a bug in X,
> but it never caused me enough trouble to actually make me pursue it.

Useless datapoint:
I've experienced the same a few times on an old Pentium computer.
Mouse pointer jumps to upper right corner, and locks hard.
Intel chipset, not sure if it is FX or HX. Matrox Mill2 graphics card.
Kernel is 2.2.16-ish on a modified RH6.1. XFree 3.3.6. gpm is running.

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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Matthew Fredrickson]

On Mon, Jan 29, 2001 at 11:14:02AM +0000, Adrian Cox wrote:
> 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
> 
> This happens to me about once a month on a BX chipset PII machine here,
> and on a KT133 chipset machine I have.  I have to hit ctrl-alt-backspace
> to regain control of the console. I always assumed it was a bug in X,
> but it never caused me enough trouble to actually make me pursue it.

It happens to me also.  In fact, I posted a message a week or two ago
asking if anybody else had similar trouble and if anybody knew anything
about it.  I eventually just quit using the ps/2 mouse port and hooked my
mouse up to the usb port to get it fixed.  It irritated me a great deal
though until I finally just switched it over to usb.

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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Benson Chow]

Datapoint

I have a chaintech 7AIA KT133-based TB motherboard.  I use a USB mouse so
I can't verify #1.  However it(2.4.0-release) autodetects all my memory
and I don't see a big enough clock drift even with 100% cpu utilization
(don't know about high disk utilization though)

Are you sure you don't have OS/2 mode or memory hole enabled in bios?  Not
sure if it matters but it could...  Also USB mouse support, make sure it's
disabled in BIOS?  Just guessing some things to look at.

-bc

On Mon, 29 Jan 2001, Dylan Griffiths wrote:

> Date: Mon, 29 Jan 2001 02:19:27 -0600
> 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
>
> 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.
>


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

Re: More on the VIA KT133 chipset misbehaving in Linux

[Rogerio Brito]

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/