Logitech G15 under Slackware 11, g15daemon not working.
 

Hi all,

I have a box running Slackware 11 (2.6.17.13), with an AMD Athlon 2700+, 1.5GB of RAM, on an ASUS A7V333-X.

I've tried compiling and installing the latest version of everything from the G15tools homepage at http://g15tools.sourceforge.net/, with no luck.

Funny thing is, if I use g15lcd, it works well and then hangs at random, shutting off the keyboard to the point where even the regular keys don't work. It also becomes impossible to kill the process, requiring a restart (if anyone knows how to kill a process that does this, I'm all ears).

I have uinput set to load at startup in my rc.local file and it's loaded into memory:
I can see where g15daemon is grabbing the device in the logs. From /var/log/messages:
And I know that the uinput device is being created in devices... although I don't know if the daemon is looking for the right device.
I'm stumped. I've tried the latest svn code. I've tried moving backwards in versions. All to the same results, the g15 only works with g15lcd (not very well... as mentioned), but not with the g15daemon. Also, I've tried using the debug option on the g15daemon but it doesn't output anything useful. Anyone have any ideas? I hope it's just something I'm overlooking.

EDIT: When I meant not working, I mean that the keys do not function under the daemon. The lcd doesn't work under either the daemon or g15lcd, but that doesn't concern me at the moment. I really just want to be able to map all the keys.

Hi,
When you say the LCD doesnt work, do you mean you dont even see a clock when g15daemon is running? g15daemon will display a clock when the lcd is not being used. It sounds like the daemon refused to start for some reason - would you mind pasting the output of g15daemon -d here? it might help point me point you in the right direction :)

The Uinput node is definately in the right place. When running g15daemon in debug mode, does it stay in the foreground or exit immediately?

I only see the Logitech logo displayed on the LCD, which stops flashing after the daemon is loaded. It never changes to a clock.

Loading the daemon with the '-d' option gives me:
and nothing else.

'g15daemon -v' yields:
'ls /proc/bus/usb' yields:
I am wondering if udev has anything to do with this. Are there any permissions that could be standing between the daemon and proper functionality? Also, could this be a hardware change on the part of the manufacturer?

Thank you for your fast reply and all your help.

A developer working on the g15 suite was nice enough to give me suggestions. Turns out that the keyboard was attached through a USB hub. I removed the hub and the friggin thing sprung to life. Thank you so much Mike!

Moral of the story: always check the hub when troubleshooting. Doh! :rolleyes:

Hello,

I also have a G15 on a Slackware box with kernel 2.6.20.
uinput is loaded and device uinput is existing. When i start g15daemon, i got this error :
An Error Occurred - 3 : ( Unable to configure the linux kernel UINPUT driver ) received

Starting g15daemon with -d give me this :
/# g15daemon -d
usb_set_debug: Setting debugging level to 1 (on)
usb_os_init: Found USB VFS at /dev/bus/usb
libg15: Found 1 supported devices
libg15: Trying to find Logitech G15
libg15: Found Logitech G15, trying to open it
libg15: Device has 1 possible configurations
libg15: Device has 1 Alternate Settings
libg15: Interface 0 has 2 Endpoints
libg15: Found "Extra Keys" endpoint 1 with address 0x81 maxtransfersize=32
libg15: Found "LCD" endpoint 2 with address 0x2 maxtransfersize=32
libg15: Done opening the keyboard
Unable to create UINPUT device.
Unable to setup the UINPUT device. Exiting

I trid differents things, none are running

Any idea ??

Thanks

Hi

I had the same problem. Just execute "modprobe uinput" and it works.

Hi, Sorry for late answer but i wrote :

Bye, ^_^