Logitech k400 keyboard and v3.2

[thegr8brian]

This patch linked from the ubuntu ticket looks interesting.

https://lkml.org/lkml/2012/8/20/378

[MaxK1]

It does look interesting.... Unfortunately I can't check to see if the driver already contains this patch at this time.

[PaulCheffus]

Hi

This would suggest as Dom mentioned a while back that it is the mainstream Debian distro that is at fault which I believe Raspbian is derived from.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658029

Cheers

Paul

[MaxK1]

Paul - did you ever try the workaround I suggested? Since it worked for some, that suggests that it is related to the USB subsystem ( a non-trivial problem and actively being worked on) and not the Logitech driver itself. (Although there may be some other issues with the Logitech driver. It has been changed in newer Linux kernels)

[PaulCheffus]

Paul - did you ever try the workaround I suggested? Since it worked for some, that suggests that it is related to the USB subsystem ( a non-trivial problem and actively being worked on) and not the Logitech driver itself. (Although there may be some other issues with the Logitech driver. It has been changed in newer Linux kernels)

Hi

I have been using the unplug and plug back in workaround once it has booted as occasionally it works without this.

Cheers

Paul

[ski522]

Add me to the list of it not working...neither removing/inserting the module via rc.local works or physically inserting/removing the usb receiver works. Guess I'll wait at this point as it looks like the problem might be related to the Debian distro.

[Lemme]

Hi - I have a question regarding this issue, as I have the same problems with my keyboard.
Has this issue been escalated in any way, is the problem visible for the developers? I was just wondering if the problem is actually being worked on, is there some sort of error log where it is described and it's progress?

[MaxK1]

It would be real handy if someone could fire up a 3.2.27 system on an x86 machine and verify that either:
a - the problem exists (which would mean it's the Logitech driver)
b - it doesn't ever have a problem (which would mean it's the Synoptics USB driver.

My money is on b....

[AnotherMuggle]

I have posted a hacky workaround for anyone who is interested. I posted in this thread, and it is currently waiting for approval by an admin.

http://www.raspberrypi.org/phpBB3/viewt ... 46&t=18139

[AndersKOlsson]

Hi,

I found one solution to this problem, which I thought could be of interest.

In the bootup messages on my system, I saw that there was a problem to open "/dev/input/event*". I added a line with

Code: Select all

evdev

to the end of "/etc/modules", since this is the module for event devices. Since then, I haven't had to re-plug my receiver any more.

I'm not quite sure what what this actually achieved, "hid_logitech_dj" should surely already depend on this module. Also I'm having a hard time reproducing it, since things still work when I remove the line from "/etc/modules". I assume this has to do with the dev tree now having the devices created.

[dliloch]

solved the issue for me! thanks!

[michaelp]

Sorry but I am lost by all of this.
I bought a Logitech K400 having read it worked fine, but now find that although it did, it doesn't now.
1. What is the best workaround, the one posted by AnotherMuggle or the 'evdev' one above?
2. It appears it is a Debian bug that has been resolved - will this appear in a new Raspbian at some point?
3. Which is the best keyboard to choose in the Raspi-config list for the K400?
Thank you
Michael

[PaulCheffus]

Sorry but I am lost by all of this.
I bought a Logitech K400 having read it worked fine, but now find that although it did, it doesn't now.
1. What is the best workaround, the one posted by AnotherMuggle or the 'evdev' one above?
2. It appears it is a Debian bug that has been resolved - will this appear in a new Raspbian at some point?
3. Which is the best keyboard to choose in the Raspi-config list for the K400?
Thank you
Michael

Hi

1) AnotherMuggle's workaround works for me.
2) Don't know but I hope so.
3) Not sure what you mean here as when I set mine up I didn't choose a keyboard in the Raspi-config.

Cheers

Paul

[ski522]

As the prior posted mention try the following

Code: Select all

sudo nano /etc/rc.local

add the following to the bottom and reboot. See if that clears it up.

Code: Select all

printf "Remove hid-logitech-dj\n"
sleep 5 
rmmod hid-logitech-dj 
sleep 5 
printf "Insert hid-logitech-dj\n"
modprobe hid-logitech-dj

reboot

[itsonlyme]

On the last few boots mine seems to be working fine. I have never applied any of the above workarounds but have regularly updated.

Has it been fixed, or am I just having a lucky few days?

[helix]

Added the two lines to /etc/rc.local:

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi

rmmod hid-logitech-dj
modprobe hid-logitech-dj
exit 0

This worked for me too. Thanks Sleep Mode zZ!!

Just for good measure I also added AnotherMuggle's workaround.

[Sleep Mode zZ]

This worked for me too. Thanks Sleep Mode zZ!!

I will remind that the workaround is originally from MaxK1, not from me. Glad that it was helpful.

I also remind that it is hard to make definitive conclusions about the helpfulness of a workaround because the keyboard might work even ten boots in a row and then fail the eleventh boot...

On the last few boots mine seems to be working fine. I have never applied any of the above workarounds but have regularly updated.

Has it been fixed, or am I just having a lucky few days?

Could be lucky days... Do the success still continue?
I still need occasionally to replug - so it is not fixed on my system. (I only update & upgrade with apt-get, not with rpi-update.)

[itsonlyme]

It was lucky days, although the times I need to unplug and re-plug are far less than "lucky" start-ups

[Mordecay]

Hello
'm Still new to Linux and the RPI.

Where can I "/ etc / rc.local:" see?

Thanks in advance for the help.

[ski522]

from a shell prompt

Code: Select all

sudo nano /etc/rc.local

[pmendiuk]

The work arounds didn't work for me. I have to unplug/replug at every boot.

[PaulCheffus]

The work arounds didn't work for me. I have to unplug/replug at every boot.

Hi

Are you using a later version 3.6.x as I found the workaround has the opposite effect with this version and removing the workaround makes it work correctly. I am assuming the underlying issue has now been fixed as this keyboard worked with 3.1.9 but then broke in 3.2.27 and is now working again in 3.6.11.

Cheers

Paul

[anasm]

Thank you very much MaxK1.
I'm not very familiar with Linux and was disapointed when i had to plug / unplung my k400 dongle at anytime I boot or reboot my rpi and i had no solution and no ability to find one.
I ve tryed a google search with my keyboard name associated to "raspberry" found this forum and your miracle solution which is still working after many reboots.
Good luck to the others.

[Mekai]

I cant get this to work with the newest version of Raspbian, anyone else having problems ?

The

Code: Select all

rmmod hid-logitech-dj
modprobe hid-logitech-dj

Dosnt work for me

[PaulCheffus]

I cant get this to work with the newest version of Raspbian, anyone else having problems ?

The

Code: Select all

rmmod hid-logitech-dj
modprobe hid-logitech-dj

Dosnt work for me

Hi

I had to remove those lines to get the keyboard to work with 3.6.11 with them in the keyboard needed to be unplugged and plugged back in before it worked.

Cheers

Paul