ATI FGLRX and Logging Off
Michael Bach (gmx)
bach.michael at gmx.net
Fri Apr 20 12:15:50 BST 2007
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:
Option "Composite" "Disable"
Option "AIGLX" "off"
my xorg.conf (clipped)
Identifier "S3 Inc. SuperSavage IX/C SDR"
Identifier "Generic Monitor"
Identifier "Default Screen"
Device "S3 Inc. SuperSavage IX/C SDR"
Monitor "Generic Monitor"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
# InputDevice "Synaptics Touchpad"
Larry Hartman wrote:
> 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)?
> 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):
>>> 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.
>> 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...
More information about the kubuntu-users