Having major probs after the upgrade to the latest X w/hotplugging.
X starts, but keyboard and mouse are dead. The wiki page is really vague - I'm not really sure what/how I'm supposed to configure to make this work. It says I want to update the entries for things like input.xkb.layout, input.xkb.variant, input.xkb.rules, input.xkb.model, input.xkb.options, etc. in the 10-keymap.fdi file. But update them to what? I'm not sure what the values should be. Also, that only explains keyboard. Why isn't mouse working?
Xorg.0.log tells me:
(II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput.
I have these packages installed, and HAL running:
xf86-input-evdev 2.0.7-1 xf86-input-keyboard 1.3.1-1 xf86-input-mouse 1.3.0-1 xf86-video-ati 6.9.0-5 xf86-video-vesa 2.0.0-2
Also, I can't currently disable hotplugging, since I don't have an xorg.conf file. (X has always been able to start fine without one; I believe it uses its own stock/internal one.) Do I really need to go through the pain of generating a conf file just to get this turned off??? There's got to be SOME way to get this to work.
Help appreciated!
DR
Do you have hal running when you start X? (/etc/rc.d/hal start)
On Mon, Dec 1, 2008 at 2:11 PM, David Rosenstrauch darose@darose.netwrote:
Having major probs after the upgrade to the latest X w/hotplugging.
X starts, but keyboard and mouse are dead. The wiki page is really vague - I'm not really sure what/how I'm supposed to configure to make this work. It says I want to update the entries for things like input.xkb.layout, input.xkb.variant, input.xkb.rules, input.xkb.model, input.xkb.options, etc. in the 10-keymap.fdi file. But update them to what? I'm not sure what the values should be. Also, that only explains keyboard. Why isn't mouse working?
Xorg.0.log tells me:
(II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput.
I have these packages installed, and HAL running:
xf86-input-evdev 2.0.7-1 xf86-input-keyboard 1.3.1-1 xf86-input-mouse 1.3.0-1 xf86-video-ati 6.9.0-5 xf86-video-vesa 2.0.0-2
Also, I can't currently disable hotplugging, since I don't have an xorg.conf file. (X has always been able to start fine without one; I believe it uses its own stock/internal one.) Do I really need to go through the pain of generating a conf file just to get this turned off??? There's got to be SOME way to get this to work.
Help appreciated!
DR
André Ramaciotti wrote:
Do you have hal running when you start X? (/etc/rc.d/hal start)
Yes.
But it looks as if hal is somehow not picking up any evdev/x11 input devices:
[darose@darsys9 10osvendor]$ hal-device | grep input [darose@darsys9 10osvendor]$
WTF?!?!?
Tnx,
DR
David Rosenstrauch wrote:
André Ramaciotti wrote:
Do you have hal running when you start X? (/etc/rc.d/hal start)
Yes.
But it looks as if hal is somehow not picking up any evdev/x11 input devices:
[darose@darsys9 10osvendor]$ hal-device | grep input [darose@darsys9 10osvendor]$
WTF?!?!?
Tnx,
DR
Ah - figured it out: evdev kernel module wasn't being automatically loaded in my rc.conf.
Sorry for the noise.
DR
David Rosenstrauch darose@darose.net:
Ah - figured it out: evdev kernel module wasn't being automatically loaded in my rc.conf.
Sorry for the noise.
That's no noise! That could be my solution too. Atm, I disabled the automatic search via ServerFlags - just three seconds before I went mad.
Perhaps I try it - but I think this hotplugging isn't that important for a desktop pc like mine.
Johannes Held schrieb:
David Rosenstrauch darose@darose.net:
Ah - figured it out: evdev kernel module wasn't being automatically loaded in my rc.conf.
The X server runs as root, so it should be capable of loading evdev (although I think udev should autoload it).
Sorry for the noise.
That's no noise! That could be my solution too. Atm, I disabled the automatic search via ServerFlags - just three seconds before I went mad.
Perhaps I try it - but I think this hotplugging isn't that important for a desktop pc like mine.
I don't know for whom it would be important at all! I have a laptop, and I never needed any input hotplugging:
1) With the kbd driver, all keyboards are picked up automatically. Okay, they all have the same layout, but can you assign different layouts with input hotplugging (if so, it might actually be useful). 2) I configured my touchpad with the synaptics driver. 3) For everything else, I have this generic mouse section: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "ImPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection This picks up all my USB or bluetooth mice automatically when I connect them (maybe ExplorerPS/2 is better so it will pick up extra buttons on mice that have them). If you have serial or PS/2 mice, then hotplugging is not for you anyway.
If anyone has a setup that he needed input hotplugging for, I'd be very interested to hear, because I cannot think of one.
Thomas Bächler wrote:
- With the kbd driver, all keyboards are picked up automatically.
Okay, they all have the same layout, but can you assign different layouts with input hotplugging (if so, it might actually be useful).
Yep, you can do matching on properties, brand name, type etc and specify options depending on it.
On Mon, Dec 1, 2008 at 11:00 AM, Thomas Bächler thomas@archlinux.org wrote:
Johannes Held schrieb:
David Rosenstrauch darose@darose.net:
Ah - figured it out: evdev kernel module wasn't being automatically loaded in my rc.conf.
The X server runs as root, so it should be capable of loading evdev (although I think udev should autoload it).
Sorry for the noise.
That's no noise! That could be my solution too. Atm, I disabled the automatic search via ServerFlags - just three seconds before I went mad.
Perhaps I try it - but I think this hotplugging isn't that important for a desktop pc like mine.
I don't know for whom it would be important at all! I have a laptop, and I never needed any input hotplugging:
- With the kbd driver, all keyboards are picked up automatically. Okay,
they all have the same layout, but can you assign different layouts with input hotplugging (if so, it might actually be useful). 2) I configured my touchpad with the synaptics driver. 3) For everything else, I have this generic mouse section: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "ImPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection This picks up all my USB or bluetooth mice automatically when I connect them (maybe ExplorerPS/2 is better so it will pick up extra buttons on mice that have them). If you have serial or PS/2 mice, then hotplugging is not for you anyway.
If anyone has a setup that he needed input hotplugging for, I'd be very interested to hear, because I cannot think of one.
Hah, thanks Thomas, I didn't want to be the one to say it. My system has worked fine with "hotplugging" for the past 5 years or so. I always wondered what sort of crazy esoteric systems needed this stuff such that editing some confusing XML files was a good tradeoff
I completely agree.... you can hardly call this hotplugging anyway as I had to configure my touchpad in the obscure hal fdi file :( Hotplugging is there to make life easier, not harder I thought...
Greetings, Erwin
On Monday 01 December 2008 18:08:23 Aaron Griffin wrote:
Hah, thanks Thomas, I didn't want to be the one to say it. My system has worked fine with "hotplugging" for the past 5 years or so. I always wondered what sort of crazy esoteric systems needed this stuff such that editing some confusing XML files was a good tradeoff
Aaron Griffin wrote:
On Mon, Dec 1, 2008 at 11:00 AM, Thomas Bächler thomas@archlinux.org wrote:
Johannes Held schrieb:
David Rosenstrauch darose@darose.net:
Ah - figured it out: evdev kernel module wasn't being automatically loaded in my rc.conf.
The X server runs as root, so it should be capable of loading evdev (although I think udev should autoload it).
Sorry for the noise.
That's no noise! That could be my solution too. Atm, I disabled the automatic search via ServerFlags - just three seconds before I went mad.
Perhaps I try it - but I think this hotplugging isn't that important for a desktop pc like mine.
I don't know for whom it would be important at all! I have a laptop, and I never needed any input hotplugging:
- With the kbd driver, all keyboards are picked up automatically. Okay,
they all have the same layout, but can you assign different layouts with input hotplugging (if so, it might actually be useful). 2) I configured my touchpad with the synaptics driver. 3) For everything else, I have this generic mouse section: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "ImPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection This picks up all my USB or bluetooth mice automatically when I connect them (maybe ExplorerPS/2 is better so it will pick up extra buttons on mice that have them). If you have serial or PS/2 mice, then hotplugging is not for you anyway.
If anyone has a setup that he needed input hotplugging for, I'd be very interested to hear, because I cannot think of one.
Hah, thanks Thomas, I didn't want to be the one to say it. My system has worked fine with "hotplugging" for the past 5 years or so. I always wondered what sort of crazy esoteric systems needed this stuff such that editing some confusing XML files was a good tradeoff
I agree with this as well. But I also understand the logic the X dev team is trying to follow. On paper, the idea sounds nice. I reverted to hardcoded devices in xorg.conf because I don't run HAL on my desktop and on my laptop, the synaptics touchpad doesn't support tapping anymore. When I apply the synaptics example in the forum (http://bbs.archlinux.org/viewtopic.php?pid=456689#p456689) the tapping is not sensitive enough (while the Xorg default is just perfect for me).
Last but not least the wiki is indeed pretty vague, missing practical examples and linking to the forum (inherently an unreliable source).
Glenn
On Mon, Dec 1, 2008 at 11:08 AM, Aaron Griffin aaronmgriffin@gmail.com wrote:
On Mon, Dec 1, 2008 at 11:00 AM, Thomas Bächler thomas@archlinux.org wrote:
If anyone has a setup that he needed input hotplugging for, I'd be very interested to hear, because I cannot think of one.
Hah, thanks Thomas, I didn't want to be the one to say it. My system has worked fine with "hotplugging" for the past 5 years or so. I always wondered what sort of crazy esoteric systems needed this stuff such that editing some confusing XML files was a good tradeoff
I'll speak up.
I have a Logitech USB mouse that I use on my main machine. I have no other pointing devices, but this mouse does happen to have extra buttons that don't work by default except when configuring evdev to use the *exact* USB device it is assigned to in /dev; I can't use the /dev/mouse thingy or whatever for it.
If I unplug this mouse to go use it on my laptop, and then come back to my desktop and plug it in, it fails to work at all because I can't use the /dev/mouse device and the USB device number assignment changes, even if I plug it into the exact same port. So input hotplugging is perfect for me, and I didn't have to tweak a single file to get it to work (other than remove crud from my xorg.conf which is now much more manageable).
-Dan
On Mon, Dec 1, 2008 at 4:22 PM, Dan McGee dpmcgee@gmail.com wrote:
On Mon, Dec 1, 2008 at 11:08 AM, Aaron Griffin aaronmgriffin@gmail.com wrote:
On Mon, Dec 1, 2008 at 11:00 AM, Thomas Bächler thomas@archlinux.org wrote:
If anyone has a setup that he needed input hotplugging for, I'd be very interested to hear, because I cannot think of one.
Hah, thanks Thomas, I didn't want to be the one to say it. My system has worked fine with "hotplugging" for the past 5 years or so. I always wondered what sort of crazy esoteric systems needed this stuff such that editing some confusing XML files was a good tradeoff
I'll speak up.
I have a Logitech USB mouse that I use on my main machine. I have no other pointing devices, but this mouse does happen to have extra buttons that don't work by default except when configuring evdev to use the *exact* USB device it is assigned to in /dev; I can't use the /dev/mouse thingy or whatever for it.
If I unplug this mouse to go use it on my laptop, and then come back to my desktop and plug it in, it fails to work at all because I can't use the /dev/mouse device and the USB device number assignment changes, even if I plug it into the exact same port. So input hotplugging is perfect for me, and I didn't have to tweak a single file to get it to work (other than remove crud from my xorg.conf which is now much more manageable).
Ah, I see. I wonder why they didn't just work that into evdev though.
arch-general@lists.archlinux.org