Plug it back again

[nagybal]

After following the instructions in the readme file the script works just fine.

There is only one small problem. I need to plug the gamepad out and in again every time I reboot the PC.

I am using the n52te and openSuSe 11.1 x64

I have copied the 52-pystromo-suse.rules to /etc/udev/rules.d/

[Raumkraut (raumkraut)]

It would be useful to see an `ls -l /dev/input`, and then that same output for those nodes of your n52te after it's been re-plugged.

[nagybal (nagy-balage)]

Here you go:

bigb@linux-wsem:~> ls -l /dev/input
összesen 0
drwxr-xr-x 2 root root 60 jan 27 09.34 by-id
drwxr-xr-x 2 root root 140 jan 27 09.34 by-path
crw-rw----+ 1 root users 13, 64 jan 27 09.34 event0
crw-rw---- 1 root users 13, 65 jan 27 09.34 event1
crw-rw---- 1 root users 13, 66 jan 27 09.34 event2
crw-rw---- 1 root users 13, 67 jan 27 09.34 event3
crw-rw---- 1 root users 13, 68 jan 27 09.34 event4
crw-rw---- 1 root users 13, 69 jan 27 09.34 event5
crw-r----- 1 root root 13, 63 jan 27 09.34 mice
crw-r----- 1 root root 13, 32 jan 27 09.34 mouse0
crw-rw---- 1 root users 10, 223 jan 27 09.34 uinput
bigb@linux-wsem:~> ls -l /dev/input
összesen 0
drwxr-xr-x 2 root root 120 jan 27 12.26 by-id
drwxr-xr-x 2 root root 200 jan 27 12.26 by-path
crw-rw----+ 1 root users 13, 64 jan 27 09.34 event0
crw-rw---- 1 root users 13, 65 jan 27 09.34 event1
crw-rw---- 1 root users 13, 66 jan 27 09.34 event2
crw-rw---- 1 root users 13, 67 jan 27 09.34 event3
crw-rw---- 1 root users 13, 68 jan 27 09.34 event4
crw-rw---- 1 root users 13, 69 jan 27 09.34 event5
crw-rw---- 1 root users 13, 70 jan 27 12.26 event6
crw-rw----+ 1 root users 13, 71 jan 27 12.26 event7
crw-r----- 1 root root 13, 63 jan 27 09.34 mice
crw-r----- 1 root root 13, 32 jan 27 09.34 mouse0
crw-r----- 1 root root 13, 33 jan 27 12.26 mouse1
crw-rw---- 1 root users 10, 223 jan 27 09.34 uinput
bigb@linux-wsem:~>

[Raumkraut (raumkraut)]

Did you have the n52 plugged in when you did the first listing? Its nodes appear to be absent, so I'm assuming not..?

What exactly happens when you try to run pystromo *before* you replug the device? A crash/traceback?

[nagybal (nagy-balage)]

It was plugged in by the first listing. (I just rebooted the PC.) It seems to be that my linux is not getting any signals from the device without a reconnect. The output of the "ls -l /dev/input" is the same when i disconnect my t52te.

The remapper runs just fine by the first listing too... except there is nothing to remap :S :(

[Raumkraut (raumkraut)]

I can't imagine any reason why anything about Pystromo would cause that to happen. Did the n52 work like a normal keyboard before you installed Pystromo? If not, then it seems your issue isn't with Pystromo, but with Linux not recognising the device on boot. Though I'm not sure why that would happen, either.
It could be something to do with a USB hub/kvm/etc., if you've got an extra piece of hardware between the n52 and the computer..?

[nagybal (nagy-balage)]

I see. I cant remember. Its working as a regular keyboard if I plug it in when the SuSe is allready up.

I connect it directly to the back of my PC. No USB hub or a kvm.

Could you pls give me hints what shout I google? Is it a modul problem? Anthing to do with fstab?

There is an /etc/fstab entry:
/sys/bus/usb/drivers /proc/bus/usb usbfs devgid=1000,devmode=664 0 0

I setted this up when i needed to use USB devices with VirtualBox.

I dont know if it has anything to do with the "plug it back again" problem.

[Raumkraut (raumkraut)]

You could try asking for help on the Suse hardware forum (http://forums.opensuse.org/hardware/).

After a bit of googling (+linux -windows "usb device" "not detected at boot") I found a BSD(!) newsgroup thread (http://unix.derkeiler.com/Newsgroups/comp.unix.bsd.freebsd.misc/2008-03/msg00200.html) which, in the end, suggested you tun off "legacy USB support" in your BIOS.

I'm going to mark this bug as invalid, but I'd like know if/how you resolve your problem - if only so that any other people reading this bug aren't left hanging. :)