You are not logged in.
Did a fresh install of Arch on my laptop last night, looking to use the window manager i3 which I have installed but when i run "exec i3" it logs me out, indicating some sort of failure in the session. Tried "startx" and noticed that didn't work either.
"grep EE /var/log/Xorg.0.log" shows me the following errors in the log:
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) Failed to load module "modesetting" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
Extensively read the Intel and Xorg pages on the wiki and googled for an hour or two, tried to create some custom configurations for Xorg but nothing has worked so far.
It appears to be some issue with the driver in combination with Xorg. I've tried updating, then uninstalling and reinstalling the packages (the three Xorg packages + Intel driver) and specifying what driver and acceleration mode Xorg should use (intel and sna). No luck so far.
Anyone here who is having the same problem or know the solution?
Last edited by olger (2013-02-24 19:45:22)
Offline
Those aren't errors. Post the full log.
Offline
The EE messages above just mean you don't have those drivers installed, but they are mainly meant as fallback drivers..
remove/rename any xorg.conf files and also non-default files /etc/X11/xorg.conf.d so X has to use autoconfiguration.
Then run startx as root, and post the complete xorg0.log (it will likely be large, better use a pastebin site)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Why would he need to start X as root? That's never required and shouldn't be done.
Offline
Gusar,
starting X as root uses a minimal configuration.
Since no .xinitrc .xsession etc are present for root that can be very useful to check if basic X works.
Last edited by Lone_Wolf (2013-02-24 14:34:01)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Not really, because if nothing is configured (and the defaults of xterm and twm aren't installed), X will simply quit, and people will ask what's wrong even though things are fine.
Offline
Not really, because if nothing is configured (and the defaults of xterm and twm aren't installed), X will simply quit, and people will ask what's wrong even though things are fine.
Well maybe I am asking the wrong question then, because I think that might be exactly whats happening. I think maybe my problem is simply related to the window manager, i3.
Here's a link to my log anyways, if anyone wants to take a look and help me exclude Xorg from the list of potential causes:
https://gist.github.com/anonymous/f85c2a1f2a0319198a09
My original problem was that running "exec i3" gives me a blank screen followed by the login screen. I remember running "startx" at another installation I was troubleshooting and getting the very basic Xorg interface, but I dont have xterm or twm installed right now so thats probably why it's just shutting down when I run "startx".
Offline
Well maybe I am asking the wrong question then, because I think that might be exactly whats happening.
Indeed that's what's happening. Your X works fine. If you install twm and xterm you'll see it. For i3, a simple
echo "exec i3" >> ~/.xinitrcshould do it.
Offline
Yeah got it all up and running now, it didn't work because i forgot to copy a skeleton xinitrc and just made a new one. Hours wasted because of that dumb mistake...
Thanks for your help guys, marking this as solved. ![]()
Offline