M Martin Michlmayr #
Message details and related content
I just upgraded my Netwinder from 2.4.27 to 2.6.15 and the framebuffer no longer works. Console works but when I start X.org I first get a corrupted screen and a little bit later the whole machine hangs. There's no panic or any information on the serial console. I've no idea how to debug this but I'm happy to provide information to developers willing to take a look. The output of dmesg from 2.4 and 2.6 are attached; the output from X.org as well. 0000:00:09.0 VGA compatible controller: Intergraphics Systems CyberPro 2000A (rev 01) (prog-if 00 [VGA]) Subsystem: Unknown device 0202:0202 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at c0000000 (32-bit, non-prefetchable) [size=16M] Expansion ROM at 80040000 [disabled] [size=64K] Kernel config on 2.4: CONFIG_FB=y CONFIG_FB_CLGEN=y CONFIG_FB_CYBER2000=y CONFIG_FB_VGA16=y CONFIG_FB_VIRTUAL=m CONFIG_FBCON_ADVANCED=y CONFIG_FBCON_MFB=y CONFIG_FBCON_CFB2=y CONFIG_FBCON_CFB4=y CONFIG_FBCON_CFB8=y CONFIG_FBCON_CFB16=y CONFIG_FBCON_CFB24=y CONFIG_FBCON_CFB32=y CONFIG_FBCON_VGA_PLANES=y CONFIG_FBCON_VGA=y CONFIG_FBCON_FONTS=y Kernel config on 2.6: CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y CONFIG_FB_CYBER2000=y The X.org logs show no difference between 2.4 and 2.6 (but 2.4 works while 2.6 doesn't):
--- Xorg.0.log-2.4 2006-01-10 22:26:31.000000000 +0000
+++ Xorg.0.log-2.6 2006-01-10 22:26:31.000000000 +0000@@ -3,16 +3,16 @@ Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.4.27-netwinder armv4l [ELF] -Current Operating System: Linux netwinder 2.4.27-netwinder #1 Sat Oct 29 19:55:43 BST 2005 armv4l +Current Operating System: Linux netwinder 2.6.15 #13 Tue Jan 10 22:06:13 GMT 2006 armv4l Build Date: 30 November 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present -OS Kernel: Linux version 2.4.27-netwinder (vince@gerald) (gcc version 2.95.3 20010315 (release)) #1 Sat Oct 29 19:55:43 BST 2005 +OS Kernel: Linux version 2.6.15 (Debian 2.6.15-1) (luther@debian.org) (gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)) #13 Tue Jan 10 22:06:13 GMT 2006 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 10 22:10:56 2006 +(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 10 22:16:27 2006 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0)
@@ -417,4 +417,3 @@ Warning: font renderer for ".bdf.Z" already registered at priority 0 Warning: font renderer for ".bdf.gz" already registered at priority 0 Warning: font renderer for ".pmf" already registered at priority 0 -Could not init font path element unix/:7100, removing from list!
This is with depth 16. With depth 4, I get the following on 2.6: (**) FBDEV(0): Depth 4, (--) framebuffer bpp 4 (==) FBDEV(0): Default visual is StaticColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: CyberPro2010 (video memory: 2048kB) (II) FBDEV(0): checking modes against framebuffer device... (II) FBDEV(0): mode "800x600" test failed (II) FBDEV(0): mode "640x480" test failed (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 640x480 (pitch 640) (**) FBDEV(0): Built-in mode "current": 25.2 MHz, 31.5 kHz, 59.9 Hz (II) FBDEV(0): Modeline "current" 25.17 640 656 744 800 480 489 491 525 -hsync +vsync +csync (++) FBDEV(0): DPI set to (100, 100) (EE) FBDEV(0): unsupported number of bits per pixel: 4 Interestingly, after this the console no longer shows anything (but the machine still works). But the real problem is the corruption plus crash with depth 16. -- Martin Michlmayr http://www.cyrius.com/