2.5 neofb screen corruption leaving X

2.5 neofb screen corruption leaving X

Post by Reid Hekma » Wed, 07 May 2003 06:20:13



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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5 neofb screen corruption leaving X

Post by James Simmon » Wed, 07 May 2003 20:40:06


Quote:> 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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5 neofb screen corruption leaving X

Post by Reid Hekma » Thu, 08 May 2003 04:20:08



> > 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. corruption of process shared text with Solaris 2.5 on 670MP?

The problem:
My Sun 670MP has 4 processors and is running Solaris 2.5.  I submitted 4
background jobs using a sh script, and sent stdout to a log file, but
forgot to redirect stderr.  Each job ran the same FORTRAN executable, but
with different input parameters.  After running for day or so, all four
jobs died within a minute of each other (based on time stamp of log file).
One received a SIGSEGV signal, while the other three received a SIGILL.  

The question(s):
What is going on?  Could the first job be corrupting a shared copy of the
process text (the segmentation violation)?  How could this happen, and how
can I avoid it?

--

The Johns Hopkins University     |   PGP Key Length/ID = 1024/525D3439
Applied Physics Laboratory       |  
PGP Key fingerprint =  E2 F6 30 43 C1 CC 93 AA  D1 1F 7A B1 A9 63 82 A8

2. why so many "potential buffer overflow" alerts?

3. URGENT Help: tcp patch Sol 2.5 -> data corruption ??

4. Instrumenting code in linux ?

5. File corruption problem in Solaris 2.5

6. Finally managed to install RH 7 on my laptop...sheesh!

7. ext3 / reiserfs data corruption, 2.5-bk

8. KDE newbie needs help !!!

9. [2.5] USB core/config.c == memory corruption (resend)

10. NeWSprint under Solaris 2.5 -- jobs don't leave queue

11. Left vs. Ctl-Left vs. Alt-Left

12. x85 2.5 install leaves disk unusable for other OSes

13. multiple screen supported on Solaris 2.5 X86 ???