Logitech k400 keyboard and v3.2

[PaulCheffus]

Hi

Since upgrading from v3.1.9+ to 3.2.x my Logitch keyboard k400 which worked perfectly now doesn't work after doing a reboot. If I wait a few minutes after switching the power off before switching it back on the keyboard will work again until the next reboot.

Any ideas.

Cheers

Paul

[MaxK1]

Did you change settings in cmdline.txt? Kernel upgraded through rpi-update or did you roll your own?

[PaulCheffus]

Did you change settings in cmdline.txt? Kernel upgraded through rpi-update or did you roll your own?

Hi

No changes made to cmdline.txt by me and yes it was via rpi-update.

Cheers

Paul

[MaxK1]

There are a couple of new ones - you might want to look at what has changed:
http://www.raspberrypi.org/phpBB3/viewt ... 6&start=75

[PaulCheffus]

There are a couple of new ones - you might want to look at what has changed:
http://www.raspberrypi.org/phpBB3/viewt ... 6&start=75

Hi

Thanks for the information.

Is there a list anywhere showing them all and what each one actually affects / does?

Cheers

Paul

[MaxK1]

Not really - at least not a complete one that I have found. While the debugging is going on, I would expect names and possible suggested values to change, as well as new options to be added and older ones dropped. The latest crop of changes appear to fix a lot of peoples problems as well as improve performance. If you come across such a list, be sure to pass it on!

[MaxK1]

Forgot to ask - Did your problem get fixed?

[PaulCheffus]

Forgot to ask - Did your problem get fixed?

Hi

Not yet and as I haven't got a clue what they do or which to try it plus its intermittent it could take some time.

Cheers

Paul

[PaulCheffus]

Hi

Just noticed something while booting.

Keyboard working

Code: Select all

[    8.462764] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    8.478647] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    8.493357] Freeing init memory: 128K
[   11.000651] logitech-djreceiver 0003:046D:C52B.0003: hiddev0: USB HID v1.11 Device [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input2
[   11.416445] input: Logitech Unifying Device. Wireless PID:400e as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.0003/input/input0
[   11.469070] logitech-djdevice 0003:046D:C52B.0004: input: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-bcm2708_usb-1.3:1
[   16.595145] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   17.318702] ### snd_bcm2835_alsa_probe c04e4430 

Keyboard not working

Code: Select all

[    8.462764] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    8.478647] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    8.493357] Freeing init memory: 128K
[   11.000651] logitech-djreceiver 0003:046D:C52B.0003: hiddev0: USB HID v1.11 Device [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input2
[   16.595145] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   17.318702] ### snd_bcm2835_alsa_probe c04e4430 

It would appear that the device is not being recognised correctly in the second instance. Now the PI, keyboard and PSU have not changed so this must be something to do with the update from kernel 3.1.9+ to 3.2.x. This also happens if I add the following to cmdline.txt or leave it out

Code: Select all

dwc_otg.microframe_schedule=1 smsc95xx.turbo_mode=N sdhci-bcm2708.sync_after_dma=0 dwc_otg.fiq_fix_enable=1

Any ideas?

Cheers

Paul

[dom]

If I wait a few minutes after switching the power off before switching it back on the keyboard will work again until the next reboot.

This does sound like polyfuses that have tripped. Does the keyboard indicate the current consumed (e.g. 100mA?). Can you try it through a powered hub?

[MaxK1]

Not many... Is there a "connect" switch? New batteries?
I'm guessing that when it doesn't work it isn't "paired" with the dongle.

http://logitech-en-amr.custhelp.com/app ... 5/cl/us,en

Clutching at straws a bit, but it looks like the dongle can be used with several models.

[Sleep Mode zZ]

Maybe connected to this problem: I did apt-get upgrade yesterday and after rebooting my k400 did not function anymore. I then added the commandline arguments and my k400 returned to life.

[PaulCheffus]

If I wait a few minutes after switching the power off before switching it back on the keyboard will work again until the next reboot.

This does sound like polyfuses that have tripped. Does the keyboard indicate the current consumed (e.g. 100mA?). Can you try it through a powered hub?

Hi Dom

I don't believe this is related to polyfuses as I have just put one of my other SD cards in with 3.1.9+ preempt 202 and I can reboot it as much as I like and the keyboard always works.

I did notice this however from the boot of 3.1.9+

Code: Select all

[    6.197826] usb 1-1.3: Product: USB Receiver
[    6.210338] usb 1-1.3: Manufacturer: Logitech
[    6.237788] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
[    6.282951] generic-usb 0003:046D:C52B.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input0
[    6.332043] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/input/input1
[    6.383886] generic-usb 0003:046D:C52B.0002: input,hiddev0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input1
[    6.433381] generic-usb 0003:046D:C52B.0003: hiddev0: USB HID v1.11 Device [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input2
[   14.995835] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   15.361646] ### snd_bcm2835_alsa_probe c05ca8a0 ############### PROBING FOR bcm2835 ALSA device (0):(1) ###############

I also put the SD card with 3.2 on in the Pi and booted no keyboard, switched off exchanged cards for the one with 3.1.9 on and immediately powered on keyboard works again.

lsusb -v reports 98ma for the USB receiver.

Cheers

Paul

[PaulCheffus]

Maybe connected to this problem: I did apt-get upgrade yesterday and after rebooting my k400 did not function anymore. I then added the commandline arguments and my k400 returned to life.

Hi

Which command line arguments did you add? This has been happening to me ever since I upgraded to 3.2.

Cheers

Paul

[Sleep Mode zZ]

Which command line arguments did you add? This has been happening to me ever since I upgraded to 3.2.

sdhci-bcm2708.enable_llm=1 sdhci-bcm2708.sync_after_dma=0

[PaulCheffus]

Which command line arguments did you add? This has been happening to me ever since I upgraded to 3.2.

sdhci-bcm2708.enable_llm=1 sdhci-bcm2708.sync_after_dma=0

Hi

Thanks but that doesn't fix it for me it still fails on subsequent reboots.

Cheers

Paul

[Sleep Mode zZ]

Sorry to hear that it didn't help. On my pi it did the trick. Also it now works better than before. Before the firmware upgrade it did not react to "mouse" clicks consistently.

[LordDiGio]

I have the same problem with the same keyboard. After firmware update at the boot the keyboard doesn't work, I have to unplug\plug again the usb receiver to make it work. The firmware is the last available (kernel 3.2.27 compiled on Sept 4). I have an old raspbian image and with it everything is fine, but after I update the firmware the problem shows up.

[Sleep Mode zZ]

Sorry to hear that it didn't help. On my pi it did the trick. Also it now works better than before. Before the firmware upgrade it did not react to "mouse" clicks consistently.

Sorry, I was wrong, my k400 acts like the others. It just happened to not work a couple of times before I added the command lines and it happened to to work a couple of times after that. With more testing it have come clear that it is showing the same symptoms as PaulCheffus's and LordDiGio's keyboards.

[dom]

If someone can identify the first version of the firmware that broke things, that woud help.
GitHub has a compete history of older firmwares. It's likely just the kernel.img that's significant.

[Sleep Mode zZ]

uname -r tells 3.2.27+.
This introduced problems for me, I don't know what version was the last "problem free" (it was not as responsive as current, when the current works).

[thsBavR10]

I have the same problem with the same keyboard. After firmware update at the boot the keyboard doesn't work, I have to unplug\plug again the usb receiver to make it work. The firmware is the last available (kernel 3.2.27 compiled on Sept 4). I have an old raspbian image and with it everything is fine, but after I update the firmware the problem shows up.

me too, same situation, same "solution" (unplug / plug receiver).
I started with the very old Debian supplied on SD-Card sold (all working), and switched yesterday to the actual Rasbian, availabe on the website.
I can't clearly say, when the problem occured first (before/after firmware update).
Seems to be a general problem with that combination.

[MaxK1]

It seems there are 2 drivers for logitech in 3.27 and only 1 in 3.1... I don't have a logitech wireless keyboard to play with so I can't do anything to trouble shoot the problem. But if I did, I would look
at lsmod when the keyboard does and doesn't work and see if there is a change. I could be (very)
wrong, but it seems worth looking into...

[PaulCheffus]

If someone can identify the first version of the firmware that broke things, that woud help.
GitHub has a compete history of older firmwares. It's likely just the kernel.img that's significant.

Hi

From my post in the USB - the Elephant in our room
http://www.raspberrypi.org/phpBB3/viewt ... 00#p153821
it broke for me with this one.

Uname -a
Linux raspberrypi 3.2.27+ #12 PREEMPT Sun Aug 19 12:28:17 BST 2012 armv61 GNU/Linux

Vcgencmd
Aug 17 2012 23:48:58
Version 332044 (release)

Not sure what previous version I had but it would have been 3.1.9+ and PREEMPT at least #178 but probably higher. I can check the other card I have this evening to see what version that one is but I may not have updated it as recently.

Cheers

Paul

[Sleep Mode zZ]

Here is uname -a print (in case it reveals something relevant that the previous -r did not):
Linux raspberrypi 3.2.27+ #102 PREEMPT Sat Sep 1 01:00:50 BST 2012 armv6l GNU/Linux