User Tools

Site Tools


problems_with_usb_keyboards_after_pirlp_install

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
problems_with_usb_keyboards_after_pirlp_install [2013/03/14 13:04]
142.103.194.1
problems_with_usb_keyboards_after_pirlp_install [2013/03/14 13:26]
72.37.171.132
Line 1: Line 1:
 =====Problems using your USB keyboard after installing IRLP on a Raspberry Pi===== =====Problems using your USB keyboard after installing IRLP on a Raspberry Pi=====
  
-This article describes the background, symptoms, causes, and a workaround ​for issues with your USB keyboard after installing IRLP on a Raspberry Pi.+This article describes the background, symptoms, causes, and workarounds ​for issues with your USB keyboard after installing IRLP on a Raspberry Pi.
  
 ---- ----
Line 22: Line 22:
 There are a few symptoms you may see: There are a few symptoms you may see:
   * The same USB keyboard you used for the initial setup (before executing the get-irlp-files script) no longer works.   * The same USB keyboard you used for the initial setup (before executing the get-irlp-files script) no longer works.
-  * On initial boot up, your node does not say its IP address. +  * On initial boot up, your node does not say its IP address ​when the keyboard is plugged in
-  * The network looks like it is working, but it can not get an IP address from a DHCP server.+  * The network looks like it is working, but it can not get an IP address from a DHCP server ​when the keyboard is plugged in.
   * The USB keyboard does not work properly (some keys are transposed, keys are missed, reaction time is slow).   * The USB keyboard does not work properly (some keys are transposed, keys are missed, reaction time is slow).
  
Line 30: Line 30:
 The most likely cause is the parameter used to lower the speed of the USB port. This can be removed so that the Pi system can be configured/​programmed,​ and then replaced later. The most likely cause is the parameter used to lower the speed of the USB port. This can be removed so that the Pi system can be configured/​programmed,​ and then replaced later.
  
-====The Workaround====+====Workarounds==== 
 + 
 +The best workaround is to boot the Pi without the keyboard, and then use Secure Shell (SSH) to access the node to perform all configuration and setup. The other workaround is to temporarily remove the USB speed parameter.
  
 The file that contains the boot-time parameter you need to change is cmdline.txt. It is accessible by putting the SD card into another computer and viewing the contents of the first partition. The file is also editable on the Pi itself - /​boot/​cmdline.txt. A reboot is required in order for the change to take effect. The file that contains the boot-time parameter you need to change is cmdline.txt. It is accessible by putting the SD card into another computer and viewing the contents of the first partition. The file is also editable on the Pi itself - /​boot/​cmdline.txt. A reboot is required in order for the change to take effect.
  
-WARNING - If you take the SD card from the Pi and plug it into a Windows PC, it may ask you to format the disk because of the second partition it does not recognize. DO NOT format the partition, or you will lose your Pi installation.+**WARNING** - If you take the SD card from the Pi and plug it into a Windows PC, it may ask you to format the disk because of the second partition it does not recognize. DO NOT format the partition, or you will lose your Pi installation.
  
-The parameter is dwc_otg.speed=1. If you remove this from the cmdline.txt file, your USB keyboard ​will start to work again.+The parameter is dwc_otg.speed=1. If you remove this from the cmdline.txt file, the USB host controller will operate at USB 2.0 speeds, and your USB keyboard ​may start to work again.
  
-Then do what is required to make the Pi work on the network and ensure it is accessible using Secure Shell (SSH). Then place the parameter back into the cmdline.txt file, and reboot. Your Pi computer is now ready to function properly.+Then do what is required to make the Pi work on the network and ensure it is accessible using SSH. Then place the parameter back into the cmdline.txt file, and reboot. Your Pi computer is now ready to function properly.
  
 It is possible that a future firmware update will fix this, but I would not hold out hope. It is possible that a future firmware update will fix this, but I would not hold out hope.
problems_with_usb_keyboards_after_pirlp_install.txt · Last modified: 2013/03/14 13:26 by 72.37.171.132