"Device or resource busy" under Intrepid

I've now managed to replicate the behaviour using 8.10 in a virtual machine (now that I've *finally* got USB working in Virtualbox). Consequently, I've also developed a workaround that gets Pystromo working.
Basically, you need to stop Xorg from using its evdev driver for input devices. We do this by modifying what HAL (Hardware Abstraction Layer) has to say about such devices:

1. Modify your /etc/X11/xorg.conf to add InputDevice sections for keyboard and mouse. I copied these sections from my current Hardy install, so you may not need all the keyboard Options, or may need to change some:

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
EndSection

2. Place the attached 52-pystromo.fdi file in /usr/share/hal/fdi/policy/20thirdparty/

3. `sudo /etc/init.d/hal restart`

4. Log out (which will restart X), and when you log back in Pystromo should be able to grab the device nodes it needs.

NB: Be prepared to boot/switch to a console to revert any changes, in case this doesn't work and X doesn't start! I've done a lot of rooting around and messing about on my VM install, but AFAICT these four steps *should be* all that you need to do.

Followed your steps to resolve the "Device or resource busy" bug. However, after I log back in and attempt the remap again I get:

barronmb@Marcy-X:~/.config/pystromo$ ./pystromo-remap.py -m default.map
Traceback (most recent call last):
  File "./pystromo-remap.py", line 51, in <module>
    output = devices.OutputDevice()
  File "/home/barronmb/.config/pystromo/lib/devices.py", line 665, in __init__
    self.node = ioctl.OutputNode()
  File "/home/barronmb/.config/pystromo/lib/ioctl.py", line 237, in __init__
    raise LookupError ('no uinput device-nodes found')
LookupError: no uinput device-nodes found

I'm not quite sure why it says this... as evdev is clearly still reading my n52. It still has the default mappings. Perhaps there is an additional step that we need to complete? Any chance that you can figure this out?

Note: My xorg.conf file already had the keyboard and mouse listed and using kbd and mouse drivers.

Disregard last... I forgot to use "sudo". Whoops. Once "sudo" is used it works properly.

xorg.conf as requested in question 58813

Xorg log from an X restart with 52-pystromo.fdi installed

Xorg log without 52-pystromo.fdi installed

Xorg log from an X restart with 52-pystromo.fdi installed with modifications given by Raumkraut

Xorg log without 52-pystromo.fdi installed

Chris, just wondering if you ever found a solution to this? When I put the 52-pystromo.fdi file in the specified dir, my keyboard and mouse lock up. Although as mentioned by another user here, the command works ok in a TTY terminal as opposed to gnome console.

No I havn't. I was going to try some new settings in the file to see if that fixed it but hadn't gotten around to it yet. I just noticed the tty workaround and it works for me as well so at least I can now use my nostromo. The thing I was going to try next was to look through old x.conf configurations to try and find all the old keyboard and mouse settings and put those in the file.

Thanks guys for the info. TTY worked for me also. For other TRUE beginners like me:
ctrl+alt+f1 at gnome login to get to tty
ctrl+alt+f7 to get back to gnome

-as

Just wanted to say that this workaround worked (as the term "workaround" implies) for me.

Ubuntu 8.10 x86_64

Thank you for your wonderful program!!!!

I was having issues with the keyboard and mouse locking up. BOrat pointed me to: http://sourceforge.net/forum/forum.php?thread_id=2058408&forum_id=207570

This helped me run the output.map. Still could not map keys with Pystromo but after this I was able to make the Nostromo_config work with the sourceforge drivers.

Okay, in my Intrepid VM (reinstall thereof) the workaround I posted initially still works, and so does the "AutoAddDevices" solution suggested on the page Justin linked to. So now I'd suggest adding the following to xorg.conf:

Section "ServerFlags"
 Option "AutoAddDevices" "false"
EndSection

Using just that, I didn't need to install any FDI file or such.
Bug description update imminent.

In Fedora 10/11/12 this same issue makes my Logitech MX518 mouse stop working but not my 10 year old generic "optical mouse". I don't see the fdi file doing any harm or good with either mouse. Adding the "AutoAddDevices" line to xorg.conf does fix the issue with the MX518 but why is this not happening to the older mouse?

Also, if I unplug the MX518 from the USB port, run the pystromo script, and then plug in the mouse, it works! Anyone know what's going on here?

Another note: the TTY execution trick does not seem to work in Fedora 11/12 (wasn't able to try on 10 when I had it).