I am on Xubuntu 13.10 64 bit. This question tells you everything you need to know about my graphic card.
Yesterday I had a problem, my graphic card driver failed, now if I login to xubuntu default desktop, all I see is a black screen however I can login to xfce session
The output of inxi -G
:
Graphics: Card-1: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Card-2: Advanced Micro Devices [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series]
X.Org: 1.14.5 drivers: fglrx,intel Resolution: [email protected]
GLX Renderer: AMD Radeon HD 6400M Series GLX Version: 4.2.12337 - CPC 13.101
xsession-errors
Script for cjkv started at run_im.
Script for default started at run_im.
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Xsession: X session started for elie at Mon Mar 10 10:16:26 EET 2014
localuser:elie being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Script for cjkv started at run_im.
Script for default started at run_im.
Script for cjkv started at run_im.
Script for default started at run_im.
libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
gnome-session-is-accelerated: llvmpipe detected.
x-session-manager[2113]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Xsession: X session started for elie at Mon Mar 10 10:17:23 EET 2014
localuser:elie being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Script for cjkv started at run_im.
Script for default started at run_im.
Script for cjkv started at run_im.
Script for default started at run_im.
libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
gnome-session-is-accelerated: llvmpipe detected.
x-session-manager[2466]: CRITICAL: We failed, but the fail whale is dead. Sorry....
/var/log/Xorg.0.log.old and /etc/X11/xorg.conf. Note that I no longer have xorg.conf, because I followed the answers below, but even if I generate new file, It will be looking like the file above, I tried it.
Your
xorg.conf
has two device sections:This is causing your machine to attempt to load both the
fglrx
and theintel
drivers. While it is actually possible to use multiple graphics cards on Linux, I doubt you can do that with an integrated (intel) and a dedicated (ATI) one. It is very likely that removing theintel
section will return everything to normal (assuming thefglrx
driver works on your system but as I understand it used to, so it probably will). So, comment out theintel
section and keep onlyfglrx
:Then restart X and, assuming there is no other issue, everything should be fine.
If not, you can try creating a new
xorg.conf
using ATI's configuration tool,aticonfig
:If you do go down this road, I also recommend you read through that program's options, they're quite extensive:
Finally, the Arch wiki page on ATI/AMD cards is a great source of information on this kind of thing.
Try to purge the GC drivers and reinstall:
If that doesn't fix it, time to edit XConfigs!
I think you could try to uninstall first your third-party driver. Then try delete
sudo rm /etc/X11/xorg.conf
and reboot. XSERVER will create a new one.A shot in the dark --- let's suppose is not the graphic drivers. What is failing seems to be the
x-session-manager
script, due to a bug in libGL.So I would try:
1) calling manually
startx
in a terminal. If the graphic screen appears, the drivers are working ok, and the problem is somewhere else. (You'll probably have just one naked terminal in it).2) Try to reconfigure
gdm
orlightdm
. By the way, I could not start xubuntu desktop with lightdm windows manager, I had to install gdm. So could beAnd/or the corresponding
sudo apt-get install gdm
if you do not have it.3) going deeper, it may be the 3D graphics failing. Have you installed
xorg-edgers
or something like that? Maybe it is a recent bug in it.4) and as a last resort, you can try some non-accelerated desktop, like Gnome classic or Ubuntu 2D.
5) Try to login as a guest user to see if the problem is related to some strange configuration file.
6) and as a voodoo-kind of thing: check is there is some strange dot file (with
ls - lad .*
) owned by root stick in your home dir --- I once had a $DEITY-know-how-was-there.Xauthority
file owned by root that blocked all my logins...Hope this helps... but probably not.