Puppy Linux Discussion Forum

[pakt]

* FINALLY FOUND AN OFFICIAL DOCUMENT *

Ok, here it is: 'Device Class Definition for Human Interface Devices (HID)' on the USB Implementor's Forum: http://www.usb.org/developers/devclass_docs/HID1_11.pdf

To detect the keyboard:

Page 67: E.3 Interface Descriptor (Keyboard)
Class code (HID code assigned by USB) 0x03
Subclass code 0x01
Protocol code 0x01

To detect the mouse:

Page 70: E.7 Interface Descriptor (Mouse)
Class code (HID code assigned by USB) 0x03
Subclass code 0x01
Protocol code 0x02


Paul

[ricstef]

Paul,
My m$ wireless USB mouse worked fine before but I applied your change anyway just to confirm your excellent work. So it was no surprise to me that the mouse worked just fine after rebooting.
However, knowing what can happen if I ASSUME that the change took effect, I proceeded to verify that the present version of /etc/rc.d/rc.local0 indeed contained your change at line 192 ... YES ... it did !!!

Nice work, Paul.

Richard.

[pakt]

For those wishing to test both USB keyboard and USB mouse detection using the Class/Subclass/Protocol method, I have added a second modified rc.local0 file as an attachment to the first post in this thread.

Paul

[John Doe]

Just remastered a CD and I'm calling my friend in a couple minutes. I'll give you a post back after the "zboard" test.

I did just test a Dynex USB mouse that I have. It works great with the new method.

Will this stuff "plug-n-play" after it's all tested? i noticed it didn't just get recognized when I plugged it in, but only when it's booted. Does puppy have some type of loop somewhere or event that can load up drivers when USB connections are made? Maybe even a Load USB Devices button in the Wizards menu would be sufficient if the other option isn't available.

[John Doe]

IT WORKED!!

Puppy roared to life and the zboard worked, using the new method.

Great work Paul!

[BarryK]

Paul, this is really great, you've fixed the usb keyboard detection
problem as well! I've downloaded the latest rc.local0.gz.
Looks like a definite goer for Pup 2.13!

[Crash]

I tested two different USB mice on two different computers. The mice are:

Microsoft Wireless Notebook Optical Mouse
Logitech Cordless Optical Mouse

The two computers are:

Soyo K7VMP motherboard homebrew, Athlon XP 2400+, KM400 chip set, 256MB RAM
E-Machine, Athlon 64 3200+, 1GB RAM

I disabled the hard drives in both computers, booting off two live version 2.12 CDs, one with the old version of rc.local0, one with the new version.

The new rc.local0 works fine with the Logitech mouse on the Soyo computer. USB Mouse Support can be either on or off in the BIOS setup.

The old rc.local0 does not work with the Logitech mouse on the Soyo computer.

On the Soyo computer, either the old or new rc.local0 works with Microsoft mouse. USB Mouse Support can be either on or off in the BIOS setup.

On the E-Machine, the Logitech mouse works with the new rc.local0 whether or not USB Legacy Support is enabled in BIOS.

The old rc.local0 does not work with the Logitech mouse on the E-Machine.

On the E-Machine, the Microsoft mouse works with either the old or new version, whether or not USB Legacy Support is enabled in BIOS.

In conclusion, the new rc.local0 results were completely positive for these tests.

[pakt]

Yes, I think this will be a reliable method for detecting USB mice and keyboards.

Many thanks to all the Puppy enthusiasts who tested and returned feedback

Paul

[jairomacon]

I switched to Puppy 2.12 recently. I was confused in problem with my USB mouse in it. using your tweaks I resolved It. I switched to Puppy 2.12 recently. I was confused in problem with my USB mouse in it. Using your tweaks I resolved it. Further I had a problem with it's detection,some power supply was laking in it. Then severally it was happened that mouse can't not work for a while & then it start working.