ATI FGLRX and Logging Off

Michael Bach (gmx) bach.michael at
Mon Apr 23 21:27:56 UTC 2007

Hello Again,

the weekend has passed and there's time again for kubuntu. Here is how a 
quick search on the web and a quick fix helped:

To start with, I was able to fix the libGL error message issue. The bug 
report in [1] brought the solution. Important are three posts in [1]:
- Joachim Frieben  said on 2007-04-22:  (permalink)
- Joachim Frieben  said on 2007-04-22:  (permalink)
- Giorgio Vazzana  said on 2007-04-22:  (permalink)

I basically downloaded the combined driver (savage and drm) source from 
the link provided by J. Frieben. I then followed the instructions by G. 
Vazzana. After restarting my system, I did not have the LibGL error 
messages, and 3D works quite quick (my personal and very subjective 
tremulous and ppracer benchmark). The procedure by G. Vazzana basically 
produces a new graphics driver kernel object "savage.ko" and a direct 
rendering driver "drm.ko". Those two modules are then just copied into 
the directory where the original modules sit. I found it very 
interesting to compare the file-sizes of the newly created files:

root at miami:~# cd /lib/modules/2.6.20-15-generic/kernel/drivers/char/drm/
root at miami:/lib/modules/2.6.20-15-generic/kernel/drivers/char/drm# ls 
-la savage.ko*
-rw-r--r-- 1 root root 425657 2007-04-23 13:55 savage.ko
-rw-r--r-- 1 root root  39868 2007-04-15 10:07 savage.ko.feisty
root at miami:/lib/modules/2.6.20-15-generic/kernel/drivers/char/drm# ls 
-la drm.ko*
-rw-r--r-- 1 root root 3160043 2007-04-23 13:58 drm.ko
-rw-r--r-- 1 root root   98456 2007-04-15 10:07 drm.ko.feisty
root at miami:/lib/modules/2.6.20-15-generic/kernel/drivers/char/drm# 

The *.feisty files are the originals. The others are the ones I 
compiled. There are probably some make rules causing the huge increase 
in size.

Although the fix by Frieben and Vazzana works fine, I still wonder if 
this procedure (copying manually created driver objects) tampers with 
the package manager? Can somebody please report.

Second is the login problem. To make it short, the above fix does not 
influence the login problem! To reduce possibilities, I did the following:
I installed gdm, set gdm as the login manager, and logging in and out 
works. Same for xdm. This is after I applied the above fix. But still, 
kdm does not work.

regards, Mike


Larry Hartman wrote:
> Mike
> If you haven't done so already, backup your xorg.conf and try adding the two 
> options and the two sections you listed....they all have a direct impact on 
> FLGRX operation.  I am thinking that the two sections will solve the GLXinfo 
> issue.
> Larry
> On Friday 20 April 2007 07:15:50 am Michael Bach (gmx) wrote:
>> Hi Larry,
>> here is my xorg.conf. I removed the font paths and "Input Devices",
>> makes it a bit more readable. Significantly different are the options in
>> your xorg.conf that go along with the "Device":
>> 	Option 		"VideoOverlay" 		"on"
>> 	Option 		"OpenGLOverlay" 	"off"
>> I assume this controls the graphics driver "fglrx"?
>> Also, I am not using the:
>> Section "Extensions"
>> 	Option	    "Composite" "Disable"
>> EndSection
>> Section "ServerFlags"
>>          Option  "AIGLX" "off"
>> EndSection
>> Mike
>> my xorg.conf (clipped)
>> ==========
>> Section "Module"
>>          Load    "i2c"
>>          Load    "bitmap"
>>          Load    "ddc"
>>          Load    "dri"
>>          Load    "extmod"
>>          Load    "freetype"
>>          Load    "glx"
>>          Load    "int10"
>>          Load    "type1"
>>          Load    "vbe"
>>          Load    "v4l"
>> EndSection
>> Section "Device"
>>          Identifier      "S3 Inc. SuperSavage IX/C SDR"
>>          Driver          "savage"
>>          BusID           "PCI:1:0:0"
>> EndSection
>> Section "Monitor"
>>          Identifier      "Generic Monitor"
>>          Option          "DPMS"
>>          HorizSync       28-51
>>          VertRefresh     43-60
>> EndSection
>> Section "Screen"
>>          Identifier      "Default Screen"
>>          Device          "S3 Inc. SuperSavage IX/C SDR"
>>          Monitor         "Generic Monitor"
>>          DefaultDepth    16
>>          SubSection "Display"
>>                  Depth           1
>>                  Modes           "1024x768"
>>          EndSubSection
>>          SubSection "Display"
>>                  Depth           4
>>                  Modes           "1024x768"
>>          EndSubSection
>>          SubSection "Display"
>>                  Depth           8
>>                  Modes           "1024x768"
>>          EndSubSection
>>          SubSection "Display"
>>                  Depth           15
>>                  Modes           "1024x768"
>>          EndSubSection
>>          SubSection "Display"
>>                  Depth           16
>>                  Modes           "1024x768"
>>          EndSubSection
>>          SubSection "Display"
>>                  Depth           24
>>                  Modes           "1024x768"
>>          EndSubSection
>> EndSection
>> Section "ServerLayout"
>>          Identifier      "Default Layout"
>>          Screen          "Default Screen"
>>          InputDevice     "Generic Keyboard"
>>          InputDevice     "Configured Mouse"
>> #       InputDevice     "stylus" "SendCoreEvents"
>> #       InputDevice     "cursor" "SendCoreEvents"
>> #       InputDevice     "eraser" "SendCoreEvents"
>> #       InputDevice     "Synaptics Touchpad"
>> EndSection
>> Section "DRI"
>>          Mode    0666
>> EndSection
>> Larry Hartman wrote:
>>> Mike:
>>> Bug # 107975 on Launchpad.  The bug reporting tool came up on the last
>>> time it happened, so I proceded to report it.
>>> My GLXinfo appears to come up properly.  I did get similar GLX/DRI errors
>>> yesterday from FGLRXinfo when I first started the troubleshooting but
>>> somehow managed to tweak it out by changes to my xorg.conf.  I had to
>>> essentially ditch my previous xorg.conf from Kubuntu 6.10 and rebuild
>>> from scratch.  Not sure what it didn't like from the old file as the new
>>> one seems to have all of the same elements....
>>> Does your xorg.conf differ significantly from mine (see first post)?
>>> Larry
>>> On Friday 20 April 2007 06:26:40 am Michael Bach (gmx) wrote:
>>>> Same problem for me on an IBM Thinkpad T23 2647
>>>> I ran 6.10 with an automatically configured xorg.config with no
>>>> problems. Even 3D stuff like Tremulous and ppracer were on decent speed
>>>> with the standard savage driver. Yesterday I installed 7.04 and problems
>>>> appeared. (The problems even persisted with using the xorg.conf from
>>>> 6.10):
>>>> First:
>>>>> When I log in, I can do a shutdown and a restart from the GUI.  I can
>>>>> not do an end session.  When clicking the button, kdm does not load and
>>>>> I get the Kubuntu usplash.
>>>> Exactly the same on my system.
>>>> Second:
>>>> running glxinfo brings the following:
>>>> [mike at miami][~]$  glxinfo
>>>> name of display: :0.0
>>>> libGL error: drmMap of framebuffer failed (Invalid argument)
>>>> libGL error: reverting to (slow) indirect rendering
>>>> display: :0  screen: 0
>>>> direct rendering: No
>>>> server glx vendor string: SGI
>>>> server glx version string: 1.2
>>>> I googled for "libGL error: drmMap of framebuffer failed (Invalid
>>>> argument)" and various results came up. Possible solutions range from
>>>> dri kernel module recompile to creating symlinks of kernel objects or
>>>> recompiling the graphics driver.
>>>> I have not started looking into any of these solutions. I hope that a
>>>> working update to whatever the problem is becomes available soon.
>>>> A workaround I discovered:
>>>> I never liked the splashscreens (probably an old slackware heritage), so
>>>> I configured my /boot/grub/menu.lst and removed the "quiet"
>>>> kerneloption, changed to "nosplash" and use 1024*768 framebuffer
>>>> "vga=791". As a result, my system boots very verbosely (that's actually
>>>> one of the things I really like about Linux) and I eventually end up in
>>>> kdm. When I log in, and then out, kdm does not reappear, but a login
>>>> propmt shows up. When I login with my credentials, I can go back into
>>>> KDE with startx.
>>>> This is just a workaround.
>>>> Having found a few solutions to problem, I dare a little to go through
>>>> the kernel and/or graphics driver recompile lottery...
>>>> Mike

More information about the kubuntu-users mailing list