Steven Walter <[EMAIL PROTECTED]> writes:
> On Sun, Dec 10, 2000 at 06:20:31PM +, David Wragg wrote:
> > If I understood why the MTRR driver was doing something on the K6-2,
> > then model-specific differences might make some sense. But currently,
> > I don't see why there would be any differ
Hello,
On Sun, 10 Dec 2000, Victor J. Orlikowski wrote:
> You appear to be right, sir.
> The SVGA xserver was what I was using. Changing over to use the S3
> server, and then adding back in MTRRs, seems to have solved the
Hm, I have to see whether GX2 works with the S3V server.
You appear to be right, sir.
The SVGA xserver was what I was using. Changing over to use the S3
server, and then adding back in MTRRs, seems to have solved the
trouble. I'll let you know if it returns, but for now, all appears
well.
Victor
--
Victor J. Orlikowski
==
[EMAIL PR
Hello,
On Sat, 9 Dec 2000, Victor J. Orlikowski wrote:
> After doing some googling
> It would appear that, in Family 5, Model 8, Stepping 12 of the K6-2,
> AMD used a different CPU core, that was more similar to the K6-3, and
> that there is a slightly odd way of doing write-combini
On Sun, Dec 10, 2000 at 06:20:31PM +, David Wragg wrote:
> If I understood why the MTRR driver was doing something on the K6-2,
> then model-specific differences might make some sense. But currently,
> I don't see why there would be any difference between "MTRR disabled"
> and "MTRR enabled,
"Victor J. Orlikowski" <[EMAIL PROTECTED]> writes:
> This is precisely my problem.
> K6-2, model 8, stepping 12.
> Thus far, everything is *fine*, as long as MTRR is not compiled into
> the kernel.
> If MTRR is compiled into the kernel, I get lock-ups in X *only*, and
> the entire machine locks.
After doing some googling
It would appear that, in Family 5, Model 8, Stepping 12 of the K6-2,
AMD used a different CPU core, that was more similar to the K6-3, and
that there is a slightly odd way of doing write-combining.
Perhaps this is the problem?
Anyone with more knowledge on the AMD co
This is precisely my problem.
K6-2, model 8, stepping 12.
Thus far, everything is *fine*, as long as MTRR is not compiled into
the kernel.
If MTRR is compiled into the kernel, I get lock-ups in X *only*, and
the entire machine locks.
I have no data on other CPUs; as I said, I previously had a P166
Hello,
On Sat, 9 Dec 2000, Victor J. Orlikowski wrote:
> However, in X I get *random* lock-ups (sometimes when gdm
> starts, sometimes when using gmc, etc.)
> Disabling MTRR seems to have cured the problem, for now (I
> haven't *seen* anything random *yet*; I'll
My apologies for following myself up. Here is slightly more info, if
it will help.
Linux version 2.2.18pre25 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #2 Sat Dec 9 09:39:50 EST 2000
Detected 400915 kHz processor.
Console: colour dummy device 80x25
Calibra
Hello all,
Recently, I upgraded my poor Socket7 system from a P166 to a AMD
K6-2 running at 400 MHz.
The only change I made to my kernel config with the upgrade was
to add in MTRR support.
My kernel is a stock 2.2.18pre25, with the addition of the S3
framebuffe
11 matches
Mail list logo
