2.5 neofb screen corruption leaving X

2.5 neofb screen corruption leaving X

[Reid Hekman]

Description: The console is "blown up" upon leaving X with neofb
compiled in on an IBM TP600E. Characters are 2-3 times normal size, dots
are not in consecutive pixels but spaced several screen elements apart.
Lines are still spaced normally but the larger text overwrites the
previous line when they wrap. The system is still usable, but the
console is unreadable ;-) I can still go back into X just fine.

Environment: IBM Thinkpad 600E, NeoMagic 256AV, RedHat 8.0.94 (Phoebe)

lspci -v
01:00.0 VGA compatible controller: Neomagic Corporation NM2200
[MagicGraph 256AV] (rev 20) (prog-if 00 [VGA])
        Subsystem: IBM ThinkPad 570
        Flags: bus master, medium devsel, latency 128, IRQ 11
        Memory at e0000000 (32-bit, prefetchable) [size=16M]
        Memory at 70000000 (32-bit, non-prefetchable) [size=4M]
        Memory at 70400000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 1

cat /proc/cmdline 
ro root=/dev/hda2 video=neofb:1024x768-16

Kernels: Tested 2.5.67-2.5.69 and are affected, haven't gone back
further yet but I can test. RedHat 2.4.18 works correctly. 

Config is here: http://dslstatic-236-77.ideaone.net/2.5.69-config

dmesg output here: http://dslstatic-236-77.ideaone.net/kernmsg.txt

Thanks in advance,
Reid

Re: 2.5 neofb screen corruption leaving X

[James Simmons]

> Description: The console is "blown up" upon leaving X with neofb

Do you have the UseFBDev flag set in XF86Config? This should fix the 
problem.

Re: 2.5 neofb screen corruption leaving X

[Reid Hekman]

On Tue, 2003-05-06 at 13:25, James Simmons wrote:
> > Description: The console is "blown up" upon leaving X with neofb
> 
> Do you have the UseFBDev flag set in XF86Config? This should fix the 
> problem.

I added it, but it doesn't appear to have helped. Setting X to use the
fbdev driver works as expected, but isn't as purty once loaded :-(

Here's the relevant section of XF86Config:

Section "Device"
        Identifier  "Videocard0"
        Driver      "neomagic"
        VendorName  "Videocard vendor"
        BoardName   "NeoMagic MagicMedia 256AV (laptop/notebook)"
        VideoRam    2560
        Option      "OverlayMem" "829440"
        Option      "UseFBDev" "1"
        Option      "externDisp" ""
        Option      "internDisp" ""
EndSection

However, the following now appears in XFree86.0.log:

(==) NEOMAGIC(0): Write-combining range (0xe0000000,0x400000)
(II) NEOMAGIC(0): Stretching disabled
(II) NEOMAGIC(0): Using linear framebuffer at: 0xE0000000
(--) NEOMAGIC(0): 1048576 bytes off-screen memory available
(II) NEOMAGIC(0): Using H/W Cursor.
(II) NEOMAGIC(0): Overlay at 0x1b5400
(II) NEOMAGIC(0): Using 106 scanlines of offscreen memory
(II) NEOMAGIC(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        Solid Horizontal and Vertical Lines
        Offscreen Pixmaps
        Setting up tile and stipple cache:
                8 128x106 slots
(II) NEOMAGIC(0): Acceleration  Initialized
(==) NEOMAGIC(0): Backing store disabled
(==) NEOMAGIC(0): Silken mouse enabled
(**) Option "dpms"
(**) NEOMAGIC(0): DPMS enabled
(WW) NEOMAGIC(0): Option "UseFBDev" is not used           <-- What's Up?
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR

This is from RedHat's XFree86-4.2.99.901-20030213.0

I put the entire XFree86.0.log here:
http://dslstatic-236-77.ideaone.net/XFree86.0.log