Re[2]: SGI O2 kernel fb driver vs Xserver [SOLVED]

Андрей Рандрианасулу randrianasulu at mail.ru
Wed Mar 11 00:12:38 PDT 2009



-----Original Message-----
From: Michel DДnzer <michel at daenzer.net>
To: Андрей Рандрианасулу <randrianasulu at mail.ru>
Date: Mon, 09 Mar 2009 08:52:22 +0100
Subject: Re: SGI O2 kernel fb driver vs Xserver

> On Sun, 2009-03-08 at 18:17 +0300, Андрей Рандрианасулу wrote:
> > 
> > -----Original Message-----
> > From: Андрей Рандрианасулу<randrianasulu at mail.ru>
> > To: xorg at lists.freedesktop.org
> > Date: Sun, 08 Mar 2009 15:00:32 +0300
> > Subject: SGI O2 kernel fb driver vs Xserver
> > 
> > > Hi list!
> > > 
> > > I have SGI O2 workstation, and gentoo Linux distro 
> > > installed in root-on-NFS mode. Kernel - self-compiled 2.6.29-rc5-0300 (with gcc-4.3.3), system was mostly recompiled with glibc-2.9, gcc 4.3.3, binutils 2.19.1. Console apps works fine, in framebuffer mode (1024x768-24 at 75, allocation of 4mb RAM was defined  at compile time).
> > > 
> > > But xserver (1.5.3 + gentoo patches) gives me error:
> > > 
> > > (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode                  
> > > (EE) FBDEV(0): mode initialization failed
> > > 
> > > I think this msg comes from hw/xfree86/fbdevhw/fbdevhw.c and was added in late 2006
> > > 
> > > commit f6815cb68b0f6698497348fc6e4214dacef33b95
> > > Author: Michel DÃ?nzer <michel at tungstengraphics.com>
> > > Date:   Sat Dec 30 10:18:28 2006 +0100
> > > 
> > >     fbdevhw: Consolidate modeset ioctl calling, report failure if it modifies mo
> > > de.
> > > 
> > > Google points me at https://bugzilla.novell.com/show_bug.cgi?id=285523 , i'm in process of rebuilding xserver (just 1.5.3, without gentoo-specific patches) with debug set to 1. If i run into same kind of bug - it should be fixed on kernel (fb driver) side?
> > > 
> > > i'll open freedesktop.org bug with additional info, when compilation finishes ... 
> > > (at least some kernel fb drivers give very same error message - 
> > > http://www.mail-archive.com/debian-arm@lists.debian.org/msg09406.html)
> > 
> > small update - 
> > 
> > sgio2 xorg-server-1.5.3 # X
> > 
> > X.Org X Server 1.5.3
> > Release Date: 5 November 2008
> > X Protocol Version 11, Revision 0
> > Build Operating System: Linux 2.6.29-rc6-00217-g823b387 mips64 
> > Current Operating System: Linux sgio2 2.6.29-rc6-00217-g823b387 #11 Tue Mar 3 13:52:25 GMT 2009 mips64
> > Build Date: 08 March 2009  01:06:00PM
> >  
> >         Before reporting problems, check http://wiki.x.org
> >         to make sure that you have the latest version.
> > Markers: (--) probed, (**) from config file, (==) default setting,
> >         (++) from command line, (!!) notice, (II) informational,
> >         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > (==) Log file: "/usr/var/log/Xorg.0.log", Time: Sun Mar  8 17:38:05 2009
> > (==) Using config file: "/etc/X11/xorg.conf"
> > (EE) Failed to load module "summa" (module does not exist, 0)
> > fbdevHW: Init 0
> > fbdevHW: VerifyModes 0
> > fbdevHW: UseBuildinMode 0
> > fbdevHW: MapVidmem 0
> > fbdevHW: LinearOffset 0
> > fbdevHW: Save 0
> > fbdevHW: SetMode 0
> > xfree init mode:        25172   640 657 753 800   480 491 493 525
> > fbdev init mode:        39726   640 17 96 47   480 11 2 32   32 8:8:8
> > (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode
> > fbdev returned mode:    39726   640 18 96 46   480 12 2 31   32 8:8:8
> > (EE) FBDEV(0): mode initialization failed
> 
> It does look like the kernel framebuffer device may be broken, though
> you could also try xserver 1.6, some of these checks have been relaxed a
> little.
> 

Sorry for false alarm - it was configuration problem :( (no "Modes" line for my default depth)

Now X starts, at 24bpp. twm and xterm are ok, gtk2 app (gqview) show some green rectangles under all it's text/icons in menus and toolbars. But at least X starts now.

Anyway, i will try xserver-1.6 just because long-unused things tend to broke.

Sorry again.



More information about the xorg mailing list