(EE) AIGLX: Screen 0 is not DRI capable
 

I am getting the following output from startx

I would post my configuration file but I can't figure out how to copy it.
I am using nano. What would be the equivalent of ^ac in windows for select_all+copy?

You really should check the wiki.x.org as suggested! http://wiki.x.org/wiki/FAQErrorMessa...b4f1c2724244ed scroll down to: I keep getting the message: "no screens found".

Okay, thank you.

Now X starts, but it's just a gray screen with a black X in the middle.

This AIGLX: Screen 0 is not DRI capable could be the problem. You could maybe try some of the suggestions in this thread: http://www.linuxquestions.org/questi...ver...-498247/ or google: AIGLX: Screen 0 is not DRI capable or do a search in this forum. If you're not bothered about using AIGLX then change your driver to vesa.

You should NEVER run X windows as root. That is the height of foolishness. Most distros don't even allow a root X session, unless you modify some configs. The reason for that is anything you do as root can affect the entire system. A large part of what makes linux so much more secure than certain other (Redmond based) systems is the longstanding security it has, including the use of non-root user accounts, which can't write or abuse system files. Running as user jim all I can mess up is /home/jim if I click on something malicious on a website. Running as root, your entire system can become compromised in a heartbeat. It is not worth it. Run as a user, and if you need root for a task, give the password.

Peace,
JimBass

Anyone that's ever done an
# rm -rf ./*
from a root shell knows this to be true. A malicious script can do this pretty easy. You shouldn't even unzip a file as root (unless you made the gz yourself) if you know what's good for you. That .05% chance that you will screw up hurts pretty bad when it actually happens on a system that matters.

I suggest you grab a distro install it and try this. Then imagine the server you just destroyed was your company's main db server ; )

-Viz

I'm about to leave but I will try using the vesa driver when I get back.

I will also switch to a normal user.
The reason I stayed root is because I thought the main reason non-root account usage was stressed so much was because of malware. Because of that, I remained root based on principle, since this will be a local server and there would be no reason for it to get any virii.
But I didn't think of the fact that I am fairly inexperienced with linux and might accidentally mess something up.


Thanks for your advice. If anyone else has any, please feel free to contribute and I will look at it when I get back.

K I did what was suggested, and fixed a couple more following errors by googling.

Now, I get the following output from a remote console, and a blank screen on the server.
Do you think it's the aiglx error causing this problem?

Ok, two things. First off, when you say this:

do you mean that you issue the startx command over a ssh session and expect the X session to happen on the screen? That won't work. All linuxes are true multi-user machines. That means if you startx over an ssh session, it only exists for that session, not visible on the machine. Think of it this way, if 4 users ssh in and all startx, which one would the server show on a monitor connected to it? The answer is none of them. If you want an X session to be on a connected monitor, you have to sign in locally and startx that way, or play with exporting the display variable to have it appear on a monitor. It will not just magically happen. Also, you have to have xforwarding enabled in the sshd_config file to get an x session forwarded over ssh.

Secondly to that, you have 2 errors that happen during the startup. The only one that is listed as a major error is this:

I don't know what AIGLX is, but xorg doesn't like something about it. I suggest you do as the startup output says, and check http://wiki.x.org. Also you have a problem with fonts, it complains about the fonts not existing, but it can work around that.

Peace,
JimBass

Yes, that's what I mean. I know you know alot more about linux than I do, but I don't know what to tell you because when I issue the startx command from liquidfx, I get output on that console and a blank screen on the bench.
(liquidfx is this computer, and bench is the server I installed gentoo on)

The reason I do it that way is so that I can see what's going on. If I issue the startx command locally on bench, I can't see the output because of the blank screen. I'm sure there's some command to work around that, but I don't know what it is.


I know that the error is with AIGLX, but I don't know what it is either.
I have checked wiki.x.org, and also googled it. I always look around before asking for help, hence my small post count here.

I noticed the font errors, but that's another problem for another time; right now I just want to get this working. All of the non-fatal errors can wait.

You have multiple sources of problems doing things that way. In addition to the problems getting X to run normally, you have the additional problem of getting it to run over a ssh session.

Everything that is appearing over the ssh session is also getting logged to /var/log/Xorg.0.log, so you don't need to worry about it not being logged. The entire output that you are finding over the ssh session will also be in that log file.

So in the first place, please issue the startx command on "the bench".

Also, I remember way back when the "startx" would give a graphical screen, but instead of starting gnome or KDE or whatever, it just gave you the bare minimum of X environments, which was a "blank" blue-green-grayish screen, no icons, no start button, or anything of that nature. IIRC, you had to right-click to get a choice of creating anything, like a terminal session.

Secondly, if startx fails on "the bench", then comment out the line in /etc/X11/xorg.conf that AIGLX, and see if that improves things any.

Peace,
JimBass

I'm doing it locally now.

There is nothing in xorg.conf that says AIGLX, so I can't comment it out.

Also, the blank screen is different when I use X instead of startx.

-startx results in just a black screen
-X results in a weird gray screen with a horizontal black bar about an inch away from the left edge of the screen.

That is odd, what is AIGLX? The xorg.conf file must be finding it somewhere, or it wouldn't call it. Can you post the xorg.conf file so we can have a look at it?

Did you install either Gnome, KDE, or any of the other multitudes of X window dressings that exist? If so, have you tried starting them directly, like startkde or startgnome rather than startx? I had never even heard of X being a command. That's a new one on me.

Peace,
JimBass

Yes, I have KDE installed. No, I haven't tried that; I thought X had to be run first.
Yeah X is a command.
I can't post my config file, I have no way of uploading it. That's why I was askign what the linux equivalent of ^ac is.

This is the output of startkde:

Yes you can post it, by copying the file across a ssh session to a machine with functioning graphical environment.

This command (issued from the liquidfx computer) would copy the xorg.conf file I want to see onto the liquidfx machine. I'll use pyro_in_a_cage as your username on both machines, obviously replace that with your real username(s). Also, if "thebench" isn't resolved by name, but by IP, than replace thebench with the IP.

That will put the file in your home directory on liquidfx, and from there you can open the file and copy/paste it into here.

I expect the problem is one line in xorg that needs to be edited out.

Peace,
JimBass