Puppy Linux Discussion Forum

[pakt]

There are occasional reports of USB 'mice' not working in Puppy 2.12. Most of the time this is due to the unreliable USB mouse detection code in /etc/rc.d/rc.local0.

Here is line 191 in rc.local0 that looks for a USB mouse:

[Kal]

Tried modifying rc.local0 on a working usb logitech optical mouse and it was inoperational on two reboots. Went to prompt and ran "modprobe usbhid", which brought it back. I put the original rc.local0 back the way it was.
Good Luck, Kal

[pakt]

Kal, could you run the following command with your USB mouse plugged in and post the results?

# cat /proc/bus/usb/devices

[Kal]

There is results:

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:02.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:02.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c03d Rev=20.00
S: Manufacturer=Logitech
S: Product=USB-PS/2 Optical Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.18.1 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:02.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=03f0 ProdID=7404 Rev= 1.00
S: Manufacturer=HP
S: Product=Deskjet 3740
S: SerialNumber=TH53P1621Q045Y
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
#

Kal

[pakt]

Well the detection string is there:

[pakt]

Here is my own setup. I'm using an external USB mouse and keyboard with my laptop.

It turns out I have an identical mouse to Kal's and my mod to rc.local0 has no problem detecting the Logitech mouse as a USB mouse:

[zigbert]

After trying your upgrade I still have to "modprobe usbhid" to get usb mouse to work. The ps2 touchpad works ok. (Puppy 2.12)

[rerwin]

I have a Microsoft wireless optical mouse that was only partially detected in 2.12 -- the pointer would not respond, but the wizard indicated a USB mouse (which I discovered by plugging in my ps/2 mouse).

I copied the new line 191, but it did not work until I added a second space character to it, between "HID" and ")". I suspect the forum text formatter squeezed out the second space character.

Now that the mouse works, I see that it behaves erratically. If I click on an item (button, URL link), nothing happens; but if I move the mouse slightly while clicking, the corresponding action occurs. In addition the response is sluggish and the cpu meter shows significant utilization. I have not checked to see if anyone else has reported this behavior.

I am testing this on a 400MHz, 160MB Aptiva

Richard

[Kal]

The first times did a cut, copy and paste off the site. Tried it again with your rc.local0 and on reboot the same dead mouse again. Noticed that my network was inop even after modprobing the mouse to life. Put original rc.local0 back and all is well.
Kal

[pakt]

[pakt]

[zigbert]

Yepp... This is great....just works

Takk!

[Kal]

Note, tried it again on other machine here with VIA chip set, using my mouse and no problem. Frugal install and all the same except for it's a Nvidia nforce2 chip set, on my computer it's a NO GO .
Good Luck, Kal

[lesliek]

Paul, you were trying to help me with a USB mouse problem in Puppy v 2.12 some time ago and my last post in that thread left me saying that I'd be buying another USB mouse to use with my MicroClient Jr.

I did that, but I'm afraid the problem's not been resolved by that new USB mouse. When I got back to the problem today, I fortuitously discovered this new thread begun by you.

I understand why you've changed the rc.local0 script to search for "Cls=03(HID ) Sub=01 Prot=02" and, indeed, the new mouse I bought shows that very information when I run "cat /proc/bus/usb/devices". The only problem is that it doesn't show that information when I run that command on my MC Jr with Puppy. The device doesn't even appear in the list of USB devices, nor does it work generally.

On the other hand, that information does appear when I run the command on my MC Jr with Damn Small Linux. (I've put the latter on a bootable USB flash drive, my Puppy being on the CF drive.) Also, the mouse works normally in DSL.

I really have no skill or knowledge in these matters, so I can only approach this very simplistically, but it seems obvious that, at the moment at which the rc.local0 script is run, the OS is not yet aware that it has a mouse hanging off the computer. It must know (or be capable of knowing) that it's got some kind of USB device there, because the mouse is getting power through the USB port (the mouse is lit up from the moment I turn on the computer), but it isn't able to get the necessary information to identify it as a USB mouse.

Can it be that editing some script that runs earlier than rc.local0 could solve my problem?

Thanks again,

Leslie

[zigbert]

This morning the upgraded script didn't load the usbhid module during bootup.