From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Roberto Jung Drebes <drebes@inf.ufrgs.br>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Mon, 17 Sep 2001 02:58:26 +0200 [thread overview]
Message-ID: <20010917025826.E6825@ppc.vc.cvut.cz> (raw)
In-Reply-To: <E15icMH-0005H3-00@the-village.bc.nu> <Pine.GSO.4.21.0109161350370.20722-100000@jacui>
In-Reply-To: <Pine.GSO.4.21.0109161350370.20722-100000@jacui>
On Sun, Sep 16, 2001 at 01:52:36PM -0300, Roberto Jung Drebes wrote:
> On Sun, 16 Sep 2001, Alan Cox wrote:
> > One way to test this hypthesis maybe to run dmidecode on the machines and
> > see if they report KT133 or KT133A. Its also possible some BIOS code does
> > blindly program bit 7 even tho its reserved and should have been kept
> > unchanged.
>
> I'm not sure if this is the output you are talking about (I see no KT133
> strings on it) but here it goes (this motherboard uses KT133A and
> exhibits the bug):
>
> Handle 0x0001
> DMI type 1, 25 bytes.
> System Information Block
> Vendor: VIA Technologies, Inc.
> Product: VT8363
> Version:
> Serial Number:
VT8363 is basic KT133. KT133A == VT8363A, at least according
to VT8363A datasheet...
> Handle 0x0002
> DMI type 2, 8 bytes.
> Board Information Block
> Vendor: <http://www.abit.com.tw>
> Product: 8363-686A(KT7,KT7A,KT7A-RAID,KT7E)
> Version:
> Serial Number:
... but there are listed both KT133 and KT133A based motherboards,
so maybe it is intentional?
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next prev parent reply other threads:[~2001-09-17 1:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <372BFCD7961@vcnet.vc.cvut.cz>
2001-09-14 18:43 ` VDA
2001-09-14 23:16 ` Alan Cox
2001-09-15 17:44 ` Nicholas Knight
2001-09-15 23:23 ` Alan Cox
2001-09-15 18:02 ` Jonathan Morton
2001-09-16 1:52 ` Petr Vandrovec
2001-09-16 7:21 ` Steffen Persvold
2001-09-16 8:08 ` Jan Niehusmann
2001-09-19 3:47 ` Albert D. Cahalan
2001-09-16 11:02 ` Vojtech Pavlik
2001-09-16 13:53 ` Alan Cox
2001-09-16 13:50 ` Vojtech Pavlik
2001-09-16 14:47 ` Alan Cox
2001-09-16 17:01 ` Vojtech Pavlik
2001-09-16 16:52 ` Roberto Jung Drebes
2001-09-17 0:58 ` Petr Vandrovec [this message]
2001-09-17 1:37 ` Ignacio Vazquez-Abrams
2001-09-17 14:59 ` Jonathan Morton
2001-09-18 11:27 ` jury gerold
2001-09-20 23:38 ` bill davidsen
2001-09-14 7:34 Athlon bug stomping #2 Roberto Jung Drebes
2001-09-14 8:27 ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 18:19 ` Byron Stanoszek
2001-09-15 18:00 ` Liakakis Kostas
2001-09-15 20:28 ` VDA
2001-09-15 7:15 ` brian
2001-09-19 1:30 ` brian
2001-09-16 21:53 ` Carsten Leonhardt
2001-09-19 3:55 ` Dan Hollis
2001-09-14 9:26 ` Jeff Lightfoot
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=20010917025826.E6825@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drebes@inf.ufrgs.br \
--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
all inboxes | Powered by JetHome®