|
AIGLX: Screen 0 is not DRI capable
H1, I have recently reinstalled my Debian and upgraded it to lenny. Everything works properly except X server. There is only one error: "(EE) AIGLX: Screen 0 is not DRI capable". I googled around but no information was helpful. How can I fix it? Log is place below
Quote:
|
the easy way to just eliminate that error would be to comment out the load dri line in your xorg.conf
Code:
Section "Module"Is X not starting for you ? That error alone shouldn't stop X from loading... I have the same error in my logs and X is working just fine.. Code:
it-etch:/var/log# cat Xorg.0.log | grep EE |
The thing is that my xorg.conf is quite different
Quote:
My X server is starting but only black screen appears. My window manager is fluxbox. Can it cause this situation? |
You might want to try and turn off AIGLX in your xorg.conf to see if it changes anything.
Code:
Section "Serverflags" |
I have just tried it out but nothing happened.
There is one interesting thing. I added 'vga=771' to kenrel options in grub and now I can start X but not as root. I have to use another account to do so. Moreover, my fluxbox does not work. When X starts I can see only xterm and some free space around. However, I am not sure that this change made X to work. I have removed and installed blackbox and fluxbox a few times to find out what is going on. What else should I do to find the bug? |
Ahh look at that. You have an nvidia Graphics card..
Installing the nvidia drivers would probably resolve your graphics issues, since the nvidia drivers DO support direct rendering.. X is NOT supposed to start as ROOT that is a security risk and is disabled by default. you shouldn't be running as root for your normal user either.. Code:
default@debianetch:~$ glxinfoaptitude update aptitude install module-assistant build-essentail m-a prepare m-a update m-a a-i nvidia aptitude install nvidia-glx edit your xorg.config and change nv to nvidia |
farslayer, you said 'X is NOT supposed to start as ROOT'. However, befor reinstalation of system, I could start X as root. It was not disabled. Moreover, there was no problem with X befor.
Of course I will try to install Nvidia driver. Then I will write result |
farslayer, you said 'X is NOT supposed to start as ROOT'. However, befor reinstalation of system, I could start X as root. It was not disabled. Moreover, there was no problem with X befor.
Of course I will try to install Nvidia driver. Then I will write result |
Just because it can be done, does not mean that it should be done.
Running the entire system with Admin/root privileges is the Windows default way of doing things which is inherently insecure. Linux can be configured to operate that way, but why would anyone knowingly want to lower the security level of their machine ? |
BTW. I'm glad that there is no hindrance in using X by default. There would be another problem to deal with.
Very interesting thing happened - X and fluxbox is working now properly. Why? I would like to know myself. I tried newest fluxbox - X didn't worked, I installed older version - the same, I installed ntfs-3g and restarted my computer - X works. Then I installed nvidia driver - X still works. Additionally, there is no error in my Xorg.log. This is the end of Xorg.log Quote:
Quote:
|
Problem solved
I had this same problem.
I found out following: ---I could login using the console ---In the console I could start kdm using root ---Then I could NOT start X as it gave me this error message back ---To start X I needed to be root (this is a security breach!) but I did it ---Then X started and all seemed to work but after a few actions done (no matter what) the system freezed My problem was that I could not write to the /home folder as it was full! I deleted some files and all worked fine again without this problem! So you might have this problem too. Use df on the command prompt and see if the file system is not full anywhere. |
| All times are GMT -5. The time now is 07:45 AM. |