| View previous topic :: View next topic |
| Author |
Message |
psy_ill
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 106
|
 Posted: Wed Nov 16, 2005 3:53 pm Post subject: hotplug and coldplug refuse to load joydev for me |
 |
|
When I plug my Logitech Dual Action gamepad in, I want /dev/input/js0 and /dev/js0 to appear. The problem is, they don't.
I have all the necessary kernel modules, udev, hotplug and coldplug installed.
If I restart my system with the gamepad plugged in, the device nodes are not created.
If I do
and then insert the gamepad, the device nodes appear as they should.
I tried to trick hotplug into loading joydev for me by adding the following to /etc/hotplug/usb.handmap
| Code: |
joydev 0x0003 0x046d 0xc216 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000
|
Nothing happens. (Yes, I have checked that the vendor id and device id are right, I ran lsusb to figure them out.)
This is from /var/log/everything/current
| Code: |
Nov 16 17:15:32 [kernel] input: USB HID v1.10 Joystick [Logitech Logitech Dual Action] on usb-0000:00:11.4-1
Nov 16 17:15:32 [udev] main: action, subsystem or devpath missing
|
Clearly, there is something fishy about udev, but it doesn't seem to matter (am I right?)
The log doesn't differ from when I load joydev first, then plug in the gamepad, the only thing which differs is the appearance of the device nodes.
So the main problem is, I don't want to load joydev myself before I plug in my gamepad, I want coldplug or hotplug (depending on whether I boot with the gamepad plugged in or I plug the gamepad in after the booting) to do that for me.
How do I set up such a configuration and why doesn't the line in usb.handmap work? |
|
| Back to top |
|
 |
davidgurvich
Veteran
Joined: 23 Apr 2004
Posts: 1063
|
| Posted: Wed Nov 16, 2005 4:24 pm Post subject: |
|
|
Try adding the module to
/etc/modules.autoload.d/ |
|
| Back to top |
|
|
psy_ill
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 106
|
| Posted: Wed Nov 16, 2005 4:35 pm Post subject: |
|
|
Well, yes, thanks for your tip, but that is not what I want to do.
I do not want to load any presumably unnecessary modules at boot.
The whole point in using hotplug is that modules are loaded and device nodes created when you plug the device in, avoiding putting load on your system when there is no need to do so. |
|
| Back to top |
|
|
AJM
Apprentice
Joined: 25 Sep 2002
Posts: 195
Location: Aberdeen, Scotland
|
| Posted: Wed Nov 16, 2005 6:08 pm Post subject: |
|
|
Funnily enough, after upgrading from 2.6.11.10 to 2.6.12.5 the other day one of my joysticks stopped working (gameport initialisation problem). Upgrading to the latest prerelease sorted that, but then the joystick devices weren't being created at boot (I have all the joystick stuff compiled in). The sticks were both being detected correctly, just no /dev entries.
Upgrading udev, hal and dbus to ~x86 fixed it, although I'm not entirely sure why the problem ocurred in the first place.
| psy_ill wrote: | | The whole point in using hotplug is that modules are loaded and device nodes created when you plug the device in, avoiding putting load on your system when there is no need to do so. |
Fair enough, but really the load caused by having joystick drivers loaded is going to be minute.
I've always found getting gameport joysticks working under linux with modular drivers to be flaky, USB ones less so.
AJ |
|
| Back to top |
|
|
psy_ill
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 106
|
| Posted: Thu Nov 17, 2005 9:13 am Post subject: |
|
|
Even though I'm not using hal/dbus, these packages rely on hotplug so the problem remains.
I have upgraded hotplug/coldplug to the latest ~x86, and I still can't get things to work. |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Fri Nov 18, 2005 7:54 pm Post subject: |
|
|
I'm not sure it's related, but when I use coldplug many modules don't just get autoloaded for me. For example ide-cd for enabling the optical driver doesn't get auto loaded by coldplug, the modules controlling cpu fan speed doesn't auto load by coldpug and some others too. Also ACPI related modules do not autoload.
I'm wondering what's the idea behind that - if coldplug is supposed to replace modules.autoload.d/kernel-2.6 - why doesn't it really autoload everything needed? in the end there are still things to be loaded manually like you said... |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
