linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
	linux-kernel@vger.kernel.org, VDA@port.imtp.ilyichevsk.odessa.ua
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Sun, 16 Sep 2001 19:01:17 +0200	[thread overview]
Message-ID: <20010916190117.A6307@suse.cz> (raw)
In-Reply-To: <20010916155045.A5671@suse.cz> <E15idD9-0005LA-00@the-village.bc.nu>
In-Reply-To: <E15idD9-0005LA-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Sep 16, 2001 at 03:47:55PM +0100

On Sun, Sep 16, 2001 at 03:47:55PM +0100, 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 think it's possible to decide whether a chipset is KT133 or KT133A
> > based on the hostbridge revision. Mine is KT133 and is rev 03.
> 
> That tells you the chipset of the bridge. dmidecode dumps bios strings which
> may tell you the chipset the bios was actually for..

Ahh, yes.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-09-16 17:01 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 ` Athlon: Try this (was: Re: Athlon bug stomping #2) 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 [this message]
2001-09-16 16:52           ` Roberto Jung Drebes
2001-09-17  0:58             ` Petr Vandrovec
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=20010916190117.A6307@suse.cz \
    --to=vojtech@suse.cz \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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;
as well as URLs for NNTP newsgroup(s).