wireless keyboard

Asked by Felicia Patterson

I use Ubuntu 10.04 and love it except my Microsoft wireless USB keyboard will only partially work with Ubuntu. I am typing on it now, but the number pad and home, delete, insert, etc buttons do no work. They work fine if I am using Windows. I tried going to System/Preferences/Keyboard, but my particular keyboard is not listed there and of course the installation disc which came with the keyboard only opens in Windows. Please help.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xserver-xorg-input-keyboard Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
delance (olivier-delance) said :
#1

I also have a Microsoft Wireless keyboard: model 1000 (and 2000 for mouse). Which is your model ?
Can you plug keyboard, wait a little and run command "lsusb". E.g. I get:
delance@delance-desktop:~$ lsusb
Bus 002 Device 002: ID 045e:00f9 Microsoft Corp. Wireless Desktop Receiver 3.1
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#2

Can you also give the output of:

lsb_release -a; uname -a

Revision history for this message
Felicia Patterson (wildabouttweety) said :
#3

My keyboard is a Microsoft Wireless 6000 v3.0
I don't have a clue about running commands or what you are asking for. I know very little about computers except how to use the software and internet.

Revision history for this message
Ubfan (ubfan1) said :
#4

Start a terminal with the keys all together Ctrl-Alt-t or select the menu item Applications/accessories/terminal.
then type exactly (or better yet, cut and paste from these messages the commands requested:
lsusb
lsb_release -a
uname -a
Then cut and paste the output back here.

Revision history for this message
Felicia Patterson (wildabouttweety) said :
#5

patterson@ubuntu:~$ lsusb
Bus 005 Device 002: ID 03f0:c302 Hewlett-Packard DeskJet D2300
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 045e:071d Microsoft Corp.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
patterson@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.2 LTS
Release: 10.04
Codename: lucid
patterson@ubuntu:~$ uname -a
Linux ubuntu 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11 19:00:09 UTC 2011 i686 GNU/Linux
patterson@ubuntu:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#6

ok if you run:

xev

and press the buttons which are inactive, do they generate events?

Revision history for this message
Felicia Patterson (wildabouttweety) said :
#7

KeyRelease event, serial 36, synthetic NO, window 0x4800001,
    root 0x101, subw 0x4800002, time 33578681, (26,50), root:(705,100),
    state 0x10, keycode 87 (keysym 0xffb1, KP_1), same_screen YES,
    XLookupString gives 1 bytes: (31) "1"
    XFilterEvent returns: False

MotionNotify event, serial 36, synthetic NO, window 0x4800001,
    root 0x101, subw 0x4800002, time 33580513, (26,51), root:(705,101),
    state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 36, synthetic NO, window 0x4800001,
    root 0x101, subw 0x4800002, time 33580513, (26,51), root:(705,101),
    state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 36, synthetic NO, window 0x4800001,

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#8

What did you press (and what order) to generate those?

Revision history for this message
Felicia Patterson (wildabouttweety) said :
#9

I pressed the numbers on the number pad starting with "1" all through "9" and then hit "Num Lock".

Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#10

All I can recommend is log a bug. Not sure

Revision history for this message
Felicia Patterson (wildabouttweety) said :
#11

thanks for trying