> > This problem is only seen on VIA chipsets so far. Never on AMD ones.
> > This leads me to the current tentative diagnosis of 'VIA chipset bug'
>
> Thanks, at least that clears up some of the mystery. Do you foresee any
> problems with running on this setup using a kernel compiled for Athlon
On Mon, Apr 30, 2001 at 06:07:36PM +0100, Alan Cox wrote:
> > Could this be a sign of a faulty 3DNOW! core in my CPU? If so, do you
> > know of any utilities I could run that test these instructions? (For
> > Linux or Windows.)
>
> This problem is only seen on VIA chipsets so far. Never on AMD
> Could this be a sign of a faulty 3DNOW! core in my CPU? If so, do you
> know of any utilities I could run that test these instructions? (For
> Linux or Windows.)
This problem is only seen on VIA chipsets so far. Never on AMD ones. This leads
me to the current tentative diagnosis of 'VIA chips
I believe I've narrowed down the cause of my oopses/panics:
If I build with CONFIG_MK7 but comment out
define_bool CONFIG_X86_USE_3DNOW y
in the MK7 part of arch/i386/config.in, the 2.4.4 kernel appears to run
perfectly.
On a side note, if I leave arch/i386/config.h untouched but fo
Hi,
About a week ago, I bought an AMD Thunderbird 1.2GHz CPU with a 266MHz
frontside bus, along with an Epox 8KTA3 motherboard.
If I boot into 2.2.18pre2, which was the version on the old hard drive I'm
using for testing, everything runs just fine. However, if I boot into a
2.4.x kernel, eithe
5 matches
Mail list logo
