Re: Athlon: Try this (was: Re: Athlon bug stomping #2)

From: Vojtech Pavlik (vojtech@suse.cz)
Date: Sun Sep 16 2001 - 08:50:45 EST

Next message: Walter Hofmann: "oops with 2.2.19 in get_empty_inode"
Previous message: Steve Kieu: "2.4.10-pre7 compile error"
In reply to: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Next in thread: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Reply: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, Sep 16, 2001 at 02:53:17PM +0100, Alan Cox wrote:
> > > to 0x89 and it happilly lives... So maybe some BIOS vendors
> > > used KT133 instead of KT133A BIOS image?
> >
> > Same here ...
>
> 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.

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Walter Hofmann: "oops with 2.2.19 in get_empty_inode"
Previous message: Steve Kieu: "2.4.10-pre7 compile error"
In reply to: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Next in thread: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Reply: Alan Cox: "Re: Athlon: Try this (was: Re: Athlon bug stomping #2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Sep 23 2001 - 21:00:14 EST