You are not logged in.
Hi folks!
I'm new to Arch, my first installation, but I used to use Gentoo in the past. Got a problem with making X to run. I followed the guide from the wiki, but I didn't manage it to work.
I'm using nVidia drivers from 173xx branch (GF 5900XT). Hal is working properly, I hope - /etc/rc.d/restart successes w\o errors.
At first, I tried to run X without xorg.conf and it complained about missing 'nv' and 'vesa' (i hope) modules. Then, after running nvidia-configure (/etc/X11/xorg.conf was successfully created) and startx - screen blanks (no nVidia logo shown) and after ~3 seconds it comes back with massage "waiting for X server to shut down". In /var/log/Xorg.0.log there were no lines starting with (EE).
Then I tried to configure X with "X -configure". After making new config and replacing the older one at /etc/X11/xorg.conf and running X with command startx (as user), it complained about missing type1 and truetype modules ((EE) lines as far as I remember). After installing missing packages/modules:
http://dpaste.com/60888/
it still won't start. Screen blanks, no nVidia logo shown, and later comes back with well known screen ( usual text... look over /var/log/Xorg.0.log for more details...). Only message after default text id "waiting for X server to shut down", with no (WW) nor (EE) lines above.
More useful data comes:
Xorg.0.log
http://dpaste.com/60883/
xorg.conf
http://dpaste.com/60885/
tail of dmesg
http://dpaste.com/60887/
If you need anything else to see, request!
Any idea? To me, it looks like nvidia driver bug or some xorg bug (or maybe just a misconfiguration)
In ~/.xinitrc stays only "exec startfluxbox", but even with empty file, situation is the same.
Thank you in advance,
Daniel
Last edited by daniel1988 (2009-07-14 03:50:06)
Offline
Hello, welcome to Arch!
You should read about the new feature of Xorg, input hotplugging: http://wiki.archlinux.org/index.php/Beg … otplugging
A more detailed explanation can be found here: http://wiki.archlinux.org/index.php/Xor … otplugging
Be sure to copy the fdi file in the correct directory.
Since I am using also the 173xx branch, here is my xorg.conf, hope it will be useful for you:
http://dpaste.com/60927/
EDIT: Not 100% sure but I seem to recall that the nvidia driver has some problems when you don't set the default depth. Add that line
Last edited by arkham (2009-06-28 20:55:27)
"I'm Winston Wolfe. I solve problems."
~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~
Offline
After some hours of googling & similar, I managed to make it work!
Thank you for pointing me in the right direction!
Cheers,
Daniel
Offline
Sorry for the bump, but I am having the same exact issue. How did you solve it? I've tried quite a number of things. I highly doubt you are going to see this anyway.
Offline
I can't really tell you what did the stuff. Check if you are using latest versions of everything (from core, extra and community repos), if hal is working correctly. I'm using xorg.conf made with nvidia-xconfig (very similar with arkham's one).
One more thing, check what the lines with (WW) in /var/log/Xorg.0.log are related to. They could make problems! Anything except this:
# cat /var/log/Xorg.0.log | grep "(WW)"
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) Warning, couldn't open module freetype
could be a potential problem.
If you think I can help you anything more than this, fell free to ask.
Cheers,
Daniel
Offline
Wow, I just got it. nano (or gedit from root) /home/USERNAME/.xinitrc and uncomment your window manager of choice (for me "exec gnome-session"), I could have sworn I added exec gnome-session. Oh well. Thanks.
Offline