LinuxQuestions.org - wireless keyboard drivers

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - wireless keyboard drivers (https://www.linuxquestions.org/questions/linux-hardware-18/wireless-keyboard-drivers-370137/)

wireless keyboard drivers

I recently obtained a wireless leyboard and mouse of CANYON type CN-RF3COMBO-US.
I have an AMD64 (1GB mem, 120 GB disks) with linux 2.6.12-1.1447_FC4 (64-bit mode).
Does anybody know how to get it working on a linux system. When I connect it the receiver light is lit and - according to the helpdesk - I have to make the connections between the receiver and the keyboard and mouse by pressing 20 sec. on two recessed buttons on the devices. OK I all did this when it was connected and restarted the computer. System did not react to the keyboard or the mouse. However in the syslog I found information that the keyboard was recognised with the line: "kernel: input: AT Translated Set 2 keyboard on isa0060/serio0"
followed by: "hal.hotplug[5346]: DEVPATH is not set (subsystem input)"
The keyboard functions correctly on an XP system.
Has anybody ideas?
Joep

Are you installing Linux and it does not see the keyboard or mouse or do you have a running linux distro and you just changed out the mouse and keyboard?

If the later post your /etc/X11/xorg.cof.

Lets see that because I have a Logitech wireless keyboard and mouse and see how it differs. Currently not at it to post. I assume it all plugs into a single usb cable?

I also assume XP will work fine reboot to reboot without using the reconnect butons? Doubt that this is your issue.

Brian1

Brian
Thanks for your reply.
In the first place for reminding me dat XF86Config is replaced by xorg.conf(!). I had completely forgotten. In the second place I had connected the keyboard (CANYON CR-RF3COMBO-US) using the PS2 connectors. I had it plugged into my laptop (AMD64 XP) using the USB connector as it has only a PS2 mouse port.
I have found out - on the XP-system) that you first have to make the connection to the PC and then connect separately the mouse and the keyboard to the receiver using a minuscule recessed button on the mouse as well as the keyboard. Is that the same on the Logitech board?
Section "InputDevice"
In xorg.conf the input section now is standard:
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
Is there a special entry for an USB wireless keyboard and where do I find the necessary definitions. (I assume it's in your xorg.conf) and is it automatically added or must it ne done by hand.
Joep

Brian (and others)
I just plugged the keyboard into an USB socket and lo and behold the keyboard and mouse are working!!.
I only get still te following messages:
"Oct 6 10:11:49 laguna kernel: input: USB HID v1.00 Keyboard [Device USB Device] on usb-0000:00:02.1-1
Oct 6 10:11:49 laguna kernel: input: USB HID v1.00 Mouse [Device USB Device] on usb-0000:00:02.1-1
Oct 6 10:11:49 laguna hal.hotplug[31985]: DEVPATH is not set (subsystem input)
Oct 6 10:11:49 laguna hal.hotplug[31983]: DEVPATH is not set (subsystem input)".
So it still complains about a DEVPATH that's' not set. Maybe sombody knows what it means and how to solve it.
Joep

From what I have read it is not a bir problem. I think it is using links related to sysfs which is being phased out. There is a little info in the kernel source at /usr/src/linux/Documentation/driver-model/porting.txt': If you don't have the kernel source then you will not have this doc. You can download a kernel at http://www.kernel.org and read about it. There is not much on it though. If wish to further your investigation then use google at http://www.google.com/linux . This link works better than just google. Use a search string like DEVPATH is not set.

Other than that glad you got it going on the USB side. I am not sure but I know on IBM notebooks they have a single ps/2 port. You can get a ps/2 y cable that you can plug a keyboard and mouse into at the same time. I have one but never tried on my Prostar notebook.

My pointing devices is the synaptic touchpad and a mouse0. There are quite a few post here and on the net related to topic like this.

I know when a mouse is plugged in it creates a device block in /dev/input. also some new items in /sys/bus/usb/devices. The mouse is a USB mouse. Figure you might want to check out those items.

Heres a copy of my xorg.conf.

Code:



# XFree86 4 configuration created by pyxf86config



Section "ServerLayout"

        Identifier    "Default Layout"

        Screen      0  "Screen0" 0 0

        InputDevice    "Mouse0" "CorePointer"

        InputDevice    "Keyboard0" "CoreKeyboard"

        InputDevice    "Synaptics" "AlwaysCore"

EndSection



Section "Files"



# RgbPath is the location of the RGB database.  Note, this is the name of the 

# file minus the extension (like ".txt" or ".db").  There is normally

# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)

# By default, Red Hat 6.0 and later now use a font server independent of

# the X server to render fonts.

        RgbPath      "/usr/X11R6/lib/X11/rgb"

        FontPath    "unix/:7100"

EndSection



Section "Module"

        Load  "dbe"

        Load  "extmod"

        Load  "fbdevhw"

        Load  "glx"

        Load  "record"

        Load  "freetype"

        Load  "type1"

        Load  "synaptics"

        Load  "dri"

EndSection



Section "InputDevice"



# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))

#        Option        "Xleds"                "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#        Option        "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the

# lines below (which are the defaults).  For example, for a non-U.S.

# keyboard, you will probably want to use:

#        Option        "XkbModel"        "pc102"

# If you have a US Microsoft Natural keyboard, you can use:

#        Option        "XkbModel"        "microsoft"

#

# Then to change the language, change the Layout setting.

# For example, a german layout can be obtained with:

#        Option        "XkbLayout"        "de"

# or:

#        Option        "XkbLayout"        "de"

#        Option        "XkbVariant"        "nodeadkeys"

#

# If you'd like to switch the positions of your capslock and

# control keys, use:

#        Option        "XkbOptions"        "ctrl:swapcaps"

# Or if you just want both to be control, use:

#        Option        "XkbOptions"        "ctrl:nocaps"

#

        Identifier  "Keyboard0"

        Driver      "kbd"

        Option            "XkbModel" "pc105"

        Option            "XkbLayout" "us"

EndSection



Section "InputDevice"

        Identifier  "Mouse0"

        Driver      "mouse"

        Option            "Protocol" "IMPS/2"

        Option            "Device" "/dev/input/mice"

        Option            "ZAxisMapping" "4 5"

        Option            "Emulate3Buttons" "yes"

EndSection



Section "InputDevice"

        Identifier  "Synaptics"

        Driver      "synaptics"

        Option            "Device" "/dev/input/mice"

        Option            "Protocol" "auto-dev"

        Option            "Emulate3Buttons" "yes"

EndSection



Section "Monitor"

        Identifier  "Monitor0"

        VendorName  "Monitor Vendor"

        ModelName    "LCD Panel 1280x1024"

        HorizSync    31.5 - 67.0

        VertRefresh  50.0 - 75.0

        Option            "dpms"

EndSection



Section "Device"

        Identifier  "Videocard0"

        Driver      "radeon"

        VendorName  "Videocard vendor"

        BoardName  "ATI Radeon Mobility M9"

EndSection



Section "Screen"

        Identifier "Screen0"

        Device    "Videocard0"

        Monitor    "Monitor0"

        DefaultDepth    24

        SubSection "Display"

                Viewport  0 0

                Depth    16

                Modes    "800x600" "640x480"

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    24

                Modes    "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"

        EndSubSection

EndSection



Section "DRI"

        Group        0

        Mode        0666

EndSection

Hope this helps out
Brian1

Thanks, Brian
I followed your suggestion and found some clarification via the url you gave. However I didn't find the Documentation directory in my source directory (I don't have the link of linux to the latest kernel in my src directory). In e.g. the directory /usr/src/kernels/2.6.12-1.1456_FC4-x86_64 no subdirectory Documentation exists. My distribution is Fedora FC4 so maybe it's distribution specific.
We have practically the same xorg only you have 2 extra sections, one for the synaptic touchpad and the first section "server" which I am missing.
The keyboard functions OK but I don't like its touch (well it's a very cheap keyboard). The mouse functions OK.
Thanks for all your information and till a next time.
Joep