Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init

Steven Walter
2001-01-05T21:16:51Z

On Fri, Jan 05, 2001 at 11:31:23AM -0500, Chris Kloiber wrote:
>
> Possibly related symptoms:
>
> kernel 2.4.0-ac1 compiled with gcc version 2.96 20000731 (Red Hat Linux
> 7.0)
>
> last 2 lines in dmesg output:
> mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x1000000
> mtrr: 0xd8000000,0x2000000 overlaps existing 0xd8000000,0x1000000
>
> cat /proc/mtrr
> reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
> reg01: base=0xd8000000 (3456MB), size= 16MB: write-combining, count=1
> reg05: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=1
>
>
> My video card is Voodoo3/3000/AGP and my motherboard is an MSI-6330
> (Athlon Tbird 800)
> I am experiencing text console video corruption. In tdfxfb mode or
> regular vesafb it looks like a horizontal line of color pixels that
> grows, in 'regular' text mode I get flashing characters or the font
> degrades into unreadable mess. X is fine.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

I can confirm these symptoms on my system with a Voodoo3/3000/PCI and a
SiS530 motherboard (AMD K6/2). I get both the "mtrr: ... overlaps
existing ..." message some extent of the text corruption. With VESA fb,
I get the random lines of colored pixels. With tdfxfb, the most
noticable problem is that the cursor is several times larger than it
should be (like 1"x1"). Additionally, with the standard console, upon
switching from X, 1 or 2 cells with have randomly colored letters in
them, and some letters ("h" particularly) always appear incorrectly.

--
-Steven
"Voters decide nothing. Vote counters decide everything."
-Joseph Stalin