You are not logged in.
I can confirm, that after the new Xorg server update 1.16.0-6, and using a different wm, I still have no input unless I use the workaround provided.
Offline
If I start X with an explicit vt argument like this setsid Xorg :0.0 -noreset -nolisten tcp vt1 & mouse and keyboard do work (and the command name turns into Xorg.bin). That is with the nouveau driver.
Offline
If I start X with an explicit vt argument like this setsid Xorg :0.0 -noreset -nolisten tcp vt1 & mouse and keyboard do work (and the command name turns into Xorg.bin). That is with the nouveau driver.
I just tried your start script, and I got a black screen. It must be because I use the NVIDIA proprietary driver instead of the nouveau one. Could you possibly make a string like you did for people who use the NVIDIA proprietary drivers?
Offline
Rather than asking to be spoonfed, what about diagnosing the actual issue? What is in the log after X fails to start properly?
Offline
Rather than asking to be spoonfed, what about diagnosing the actual issue? What is in the log after X fails to start properly?
I already mentioned earlier in the thread that my Xorg logs looked exactly like Procyon's logs that he posted near the beginning of the thread. I said that we both have the same error. Which was:
[ 271.744] (II) No input driver specified, ignoring this device.
[ 271.744] (II) This device may have been added with another device file.
There's no use of me double posting things I've already pointed out.
----------------------------------------------------------------------------------
EUREKA!!! I finally have input without using xf86-input-mouse and xf86-input-keyboard. Its all thanks to you Procyon. With a little more tweaks to my xorg.conf, I finally got my input to work. Its all thanks to that vt1 command line parameter. What a miracle. I have no idea how it fixed it, but it did.
My mouse acceleration script finally loads and I can notice a big difference. The mouse acceleration is completely disabled. It feels like it did in Debian sid. I had the 10-evdev.conf file all along. It was my the "usr/share/X11/xorg.conf.d" directory this whole time, with the 10-quirks.conf. This explains why I had no config files in the normal "/etc/X11/xorg.conf.d" folder. Everything just came together, with that simple vt1 command.
Thank you Procyon for the fix, and DaMadOne for the workaround to get me this far. Everything is finally back to normal. What a miracle. HALLELUJAH!!!
startx -- -nolisten tcp vt1
Last edited by shoober420 (2014-08-02 10:21:11)
Offline
Even nvidia works like this for me, same as yours. The vt1 argument was something alluded to in the bug report.
I just tried your start script, and I got a black screen.
Running just Xorg you have to source .xinitrc manually. I'm glad you got it working with startx as well.
Offline
@shoober420
Hello.
To clarify your case, could you tell if your keyboard and mouse are USB devices?
And it is not normal that you need to precise the vt number with startx, if you use systemd-logind to log in, and if you ran 'startx' in the console prompt of the tty where you logged in. If you don't do that, can you precise where exactly you run the 'startx' command, and how you login in your system?
Thanks to clarify these points.
I have no idea how it fixed it, but it did.
This is not so good, you just use something it happens to work without understanding why:
in a normally installed and configured Arch installation, this 'startx -- -nolisten tcp vt1' should not be necessary; just 'startx' should work out of the box.
So I guess there is something not correctly configured in your installation.
Offline
To clarify your case, could you tell if your keyboard and mouse are USB devices?
My mouse is USB, its an Intellimouse 3.0. My keyboard is PS/2, a SteelSeries 6Gv2.
If you don't do that, can you precise where exactly you run the 'startx' command, and how you login in your system?
I login from the terminal prompt after my machine boots. I use no login manager or other software like that. Just vanilla as possible.
So I guess there is something not correctly configured in your installation.
Or a bug with 1.16. I followed the wiki on installation of Arch exactly, so if somethings wrong, the wiki is wrong.
Last edited by shoober420 (2014-08-02 17:44:16)
Offline
berbae wrote:So I guess there is something not correctly configured in your installation.
Or a bug with 1.16. I followed the wiki on installation of Arch exactly, so if somethings wrong, the wiki is wrong.
Of course, it is always someone else's fault...
We are done here. Closing.
Offline