LinuxQuestions.org - No USB Keyboard or USB Mouse with 12.2 and New Box

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - No USB Keyboard or USB Mouse with 12.2 and New Box (https://www.linuxquestions.org/questions/slackware-14/no-usb-keyboard-or-usb-mouse-with-12-2-and-new-box-741259/)

Woodsman

07-19-2009 06:23 PM

No USB Keyboard or USB Mouse with 12.2 and New Box (Solved)

I have a new box that eventually will become an HTPC. An Asus M3N78-EM motherboard, AMD 5050e 2.6 GHz Dual Core CPU, Western Digital WD6400AAKS hard drive, Lite-On iHAS324-08 24X SATA DVD, HDMI, DVI-D, VGA.

I have an Adesso RF wireless keyboard with a built-in trackball. The RF receiver is USB.

I connected a Logitech USB M-BJ58/M-BJ69 optical wheel mouse.

With Slackware 12.2, the wireless keyboard and Logitech mouse do not work.

I did some testing with some Live CDs. All USB ports are functional.

At boot, both in the BIOS setup screens and with the (GRUB) bootloader, the wireless keyboard works fine. The BIOS boot messages indicate 1 USB keyboard connected and two USB mice.

The wireless keyboard, built-in trackball, and Logitech mouse all work fine with the Live CDs. Several times I had a PS/2 keyboard connected as well and both keyboards and both mice (Logitech and trackball) worked with the Live CDs.

Running lsusb lists both the keyboard and Logitech mouse:

Code:

 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 004: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse

Bus 004 Device 002: ID 1241:f768 Belkin

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I can remove either device and lsusb updates correctly.

As mentioned, all USB ports are functional. When in X/KDE, I can insert a USB flash drive and the drive appears on the desktop. Konsole shows the device being mounted as well.

Nothing I do gets 12.2 to recognize the USB keyboard and mice.

This is not a fresh installation. I mirrored my office box drive partitions because of very similar specs. The office box uses a PS/2 keyboard and mouse. Updating various configuration files took only some nominal time and seemed like a more efficient route rather than a fresh installation. Seems to be the case because everything works great except the USB input devices. 12.2 just does not recognize them.

This is not an X/KDE problem because the wireless keyboard fails to function at the console, which is how I first noticed the problem. Only after starting X/KDE did I discover that neither mouse was working.

I appreciate any help. Thanks.

niels.horn

07-19-2009 06:26 PM

There have been some problems recognizing USB keyboards and mice in the past with certain BIOSes...
I remember something about a setting in a BIOS for "USB compatibility".

Maybe this is the case with your new computer?

Woodsman

07-19-2009 08:14 PM

Quote:

Maybe this is the case with your new computer?

Well, unlikely, as the BIOS boot screen displays the message of finding 1 USB keyboard and 2 USB mice. And the Live CDs had no such problems. :(

niels.horn

07-19-2009 08:39 PM

Did you check with the live cds which drivers are being used?
Live CDs can be good at automatically loading the right modules :)

Bruce Hill

07-19-2009 09:50 PM

Quote:

Originally Posted by Woodsman (Post 3613130)

This is not a fresh installation. I mirrored my office box drive partitions because of very similar specs. The office box uses a PS/2 keyboard and mouse.

Maybe it should be. I wonder if some udev rules aren't getting properly written?
I'm sure you unplugged them both, ran "udevadm monitor", and then plugged them back in.

I don't understand this:

Quote:

Originally Posted by Woodsman (Post 3613130)

Running lsusb lists both the keyboard and Logitech mouse:

Code:

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 004: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse

Bus 004 Device 002: ID 1241:f768 Belkin

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I ass-u-me maybe too much. You say "lsusb" lists them; but they're "not recognized".

You mean the Belkin device is the Adesso wireless kdb? My wireless kdb shows up as:

Code:

mingdao@silas64:~$ /sbin/lsusb | grep Logitech

Bus 002 Device 002: ID 046d:c512 Logitech, Inc. LX-700 Cordless Desktop Receiver

Yours doesn't appear to have a receiver connected.

Sorry for grabbing at straws, mate.

Woodsman

07-19-2009 10:08 PM

Quote:

Live CDs can be good at automatically loading the right modules

I did notice with lsmod that the hid, ohci1394, ehci-hcd, ohci-hcd, uhci_hcd, usbcore, and usbhid modules were loaded. I thought they might be the missing links. I tried loading them but no modules found. I then checked my config file for my kernel compile and except for the hid module, all the remainder are built-in. The odd thing is that I can insert a USB flash drive into any USB port and the system sees the new drive. Just not USB peripherals.

The BIOS sees the devices. The system sees the peripherals too, they just don't work.

Quote:

I wonder if some udev rules aren't getting properly written?

That is what I'm thinking. I have not touched the /lib/udev rules and I deleted all the /etc/udev rules and rebooted. No change.

Quote:

I'm sure you unplugged them both, ran "udevadm monitor", and then plugged them back in.

No, I hadn't. But now I have. :) Plugging in both individually resulted a bunch of udev gibberish but the word "add" appeared with each line. Conversely when I pulled each device I saw the word "remove" on each line.

Quote:

You say "lsusb" lists them; but they're "not recognized".

Perhaps "recognized" is not a good word. Specifically, no characters appear when I use the keyboard and the mouse pointer never moves.

Quote:

You mean the Belkin device is the Adesso wireless kdb?

Weird but yes. When I remove the receiver the Belkin device is gone. When I insert the receiver the Belkin device is listed.

Quote:

Sorry for grabbing at straws, mate.

I've been grabbing at straws all afternoon. :(

Bruce Hill

07-19-2009 10:16 PM

Might check something else:

Code:

mingdao@silas64:~$ lsmod | grep hid

hid_logitech          10976  0

usbhid                38176  1 hid_logitech

hid                    49152  2 hid_logitech,usbhid

I don't have a 2.6.27.7 (your sig indictates), but check this:

Code:

mingdao@jeremiah:~$ grep -i 'hid' kernel/linux-2.6.30.1/.config

CONFIG_BT_HIDP=m

CONFIG_HID_SUPPORT=y

CONFIG_HID=m

CONFIG_HID_DEBUG=y

CONFIG_HIDRAW=y

CONFIG_USB_HID=m

CONFIG_HID_PID=y

CONFIG_USB_HIDDEV=y

# Special HID drivers

CONFIG_HID_A4TECH=m

CONFIG_HID_APPLE=m

CONFIG_HID_BELKIN=m

CONFIG_HID_CHERRY=m

CONFIG_HID_CHICONY=m

CONFIG_HID_CYPRESS=m

CONFIG_HID_EZKEY=m

CONFIG_HID_KYE=m

CONFIG_HID_GYRATION=m

CONFIG_HID_KENSINGTON=m

CONFIG_HID_LOGITECH=m

CONFIG_HID_MICROSOFT=m

CONFIG_HID_MONTEREY=m

CONFIG_HID_NTRIG=m

CONFIG_HID_PANTHERLORD=m

CONFIG_HID_PETALYNX=m

CONFIG_HID_SAMSUNG=m

CONFIG_HID_SONY=m

CONFIG_HID_SUNPLUS=m

CONFIG_HID_TOPSEED=m

Woodsman

07-19-2009 10:40 PM

I just tried running lsusb with the Live CD (I don't know why I did not try that sooner). Same results. So the keyboard receiver and Logitech mouse are being identified the same.

Quote:

lsmod | grep hid

I ran lsmod hid. No effect. All the others are built in to the kernel.

Quote:

CONFIG_HID_BELKIN=m

CONFIG_HID_BELKIN=y :(

The Live CD is using a 2.6.26.8 kernel. Therefore there is no reason to belive the hardware is too new. Besides, the M3N78-EM board has been around for a while. That is why I went with the board --- good reviews and support.

Woodsman

07-19-2009 10:53 PM

Update: partial success.

I installed the huge kernel and booted with that. I was able to use the wireless keyboard. I used the vesa driver to boot into X/KDE and the mouse pointer worked.

Now to find the difference between the two kernel config files. :scratch:

Bruce Hill

07-19-2009 11:07 PM

Some Live CD is using 2.6.26.8 kernel; you are using 2.6.27.7?

Did you diff the module in that kernel vs. yours?

Code:

mingdao@jeremiah:~/kernel/linux-2.6.30.1$ diff -u /usr/src/linux-2.6.29.6/drivers/hid/hid-belkin.c drivers/hid/hid-belkin.c

--- /usr/src/linux-2.6.29.6/drivers/hid/hid-belkin.c    2009-07-03 07:41:20.000000000 +0800

+++ drivers/hid/hid-belkin.c    2009-07-03 07:52:38.000000000 +0800

@@ -101,5 +101,3 @@

 module_init(belkin_init);

 module_exit(belkin_exit);

 MODULE_LICENSE("GPL");

-

-HID_COMPAT_LOAD_DRIVER(belkin);

My usb.ids has that company elsewhere:

Code:

mingdao@jeremiah:~/kernel/linux-2.6.30.1$ grep 'Adesso' /usr/share/usb.ids

087c  Adesso/Kbtek America, Inc.

Heck, I'm sorry ... the straws are getting shorter ... time for a kip.

Bruce Hill

07-19-2009 11:10 PM

Quote:

Originally Posted by Woodsman (Post 3613346)

I'm sure you know, but just in case:

Code:

mingdao@jeremiah:/boot$ grep -i 'belkin' config-generic-2.6.29.5 config-huge-2.6.29.5

config-generic-2.6.29.5:CONFIG_OLD_BELKIN_DONGLE=m

config-generic-2.6.29.5:CONFIG_USB_BELKIN=y

config-generic-2.6.29.5:CONFIG_HID_BELKIN=m

config-generic-2.6.29.5:CONFIG_USB_SERIAL_BELKIN=m

config-huge-2.6.29.5:CONFIG_OLD_BELKIN_DONGLE=m

config-huge-2.6.29.5:CONFIG_USB_BELKIN=y

config-huge-2.6.29.5:CONFIG_HID_BELKIN=y

config-huge-2.6.29.5:CONFIG_USB_SERIAL_BELKIN=m

Woodsman

07-19-2009 11:51 PM

Solved

I just recompiled a new kernel.

I found Bluetooth support disabled. Some folks might think, "Well duh!" but the keyboard is my first RF device ever so that part does not surprise me. Disabling stuff is a carry over from the days when I owned only old hardware and needed to reduce cruft. With my newish office box last year I had to enable a lot of features but some of that baggage remains. I prefer my file systems built-in rather than deal with initrds, therefore starting from scratch with the generic kernel might be a plausible idea someday. The new box will serve as a playground for several weeks before I focus seriously on HTPC features. So I might do just that.

I also found a couple of USB HID options not set. I enabled them as modules.

All three peripherals (Logitech mouse, trackball, and keyboard) now function as expected.

Some days this just isn't fun! :scratch: A PB&J snack has helped somewhat recover my disposition. ;)

Bruce Hill

07-20-2009 12:11 AM

Man, what I wouldn't give for some Goober Grape!

You might check the thread thing where it's now setup to mark
the first post [SOLVED] so it shows in the forum posts.

Glad you got a new box, and have it working. I'm doing my own
bit of experimenting with Slackware for x86_64 on two comps in
anticipation of the 13.0 release. I'd really like to install it to the
wife and daughter's PC, but if I bork their box I'll have to stop
everything until it's fixed, or I'm in the doghouse.

My Lenovo laptop has a bluetooth receiver built in, and some time
between Slackware-12.2 and when I installed Slackware64 -current,
then along the updates, it quit coming on. After a few days of
investigating, it turns out to be thinkpad-acpi at fault. This is
my first bluetooth device, so I understand the new ground.

I'll have to wait for the kernel devls to get rfkill rewritten,
then maybe get my Broadcom receiver put into thinkpad-acpi.

Woodsman

07-20-2009 12:28 AM

Quote:

You might check the thread thing where it's now setup to mark
the first post [SOLVED] so it shows in the forum posts.

I would if I knew how. I edited the title but the change does not appear in the thread listings. :scratch:

Bruce Hill

07-20-2009 12:47 AM

Try this thread -- as I had to do.

All times are GMT -5. The time now is 08:42 PM.