Closed sriemer closed 6 years ago
Dell MS111
Primax verification: https://www.dell.com/support/home/en/en/dedhs1/Configuration/ServiceTag/802RH32
@jikos: Is this enough to do two further HID_QUIRK_ALWAYS_POLL
patches?
Or does this have to wait until somebody verifies with usbhid.quirks
? TIA
Bought a Dell MS111 on eBay now for little money. Those are getting expensive now that they aren't produced any more. Produced around 2009..2014. Then superseded by MS116.
Regarding the HP mouse: https://devicehunt.com/view/type/usb/vendor/0461/device/4D0F confirms that it is an HP Optical Mouse. But which one?
Ubuntu certified it together with "HP 110 Desktop PC Desktop". When comparing pictures, it could be the HP X500 but this one is marked to have IDs 0x03f0:0x0941
at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840149. Must be older than that.
Rather seems to be the unbranded HP Portia mouse HP 697738-001.
The unbranded HP Portia mouse HP 697738-001 cannot be bought for a reasonable price in Germany. But cheap stocks are still available in the US.
I've received the Dell MS111-L (new old stock, manufactured in May 2014 in China, REV A06) now. But it identifies itself as USB_DEVICE_ID_LOGITECH_C077
(046d:c077
) for which HID_QUIRK_ALWAYS_POLL
is already set.
It looks like the Dell MS111 has been produced in two variants. The -L
stands here for Logitech and the Dell MS111-P should be the Primax variant I'm interested in.
Dell MS111-P identifies as 0x0461:0x4e22
confirmed. Found that mouse on the desk of a SUSE colleague. Bug confirmed. Disconnects every 62 seconds.
usbhid.quirks=0x0461:0x4e22:0x00000400
fixes this bug for the Dell MS111-P. I'll do the upstream patch for both mice.
I've got confirmation for the HP mouse as well now. usbhid.quirks=0x0461:0x4d0f:0x00000400
fixes it.
Patch sent to upstream. So closing.
Now I've also received my Dell MS111-P from eBay, used but in good condition. Looks like I started to collect the Dell standard mice. Collection:
413c:301a
)046d:c077
)0461:4e22
)I give all of those a Tux for Full Linux Support now while this has to wait a bit for the MS111-P.
Latest Microsoft/Primax mouse patches were only picked up to stable kernels back until v4.19
. Porting the patches to < v4.16
is trivial enough with this howto.
@bwhacks did the backports for Ubuntu kernel 3.16: https://www.spinics.net/lists/stable/msg282956.html https://www.spinics.net/lists/stable/msg283111.html
LGTM. Thanks!
Dell MS111-P opened to check PixArt IC in #18.
Continued in #15.
It looks like that there are PixArt mice with Primax vendor ID (
0x0461
) disconnecting every 30 or 60 seconds as well.Case 1: At https://narkive.com/XTZc8YG5.17, a guy named Jim Beard found this howto and activated
gpm
for product ID0x4d0f
. He claims this is an HP mouse. Without verification that kernel boot optionusbhid.quirks=0x0461:0x4d0f:0x00000400
works, I can't submit a kernel patch. But the thread suddenly stopped afterward.Yeah, this howto is useful! That guy also didn't know that
0x00000400
isHID_QUIRK_ALWAYS_POLL
. That bug in the howto is fixed by now.Second reference: https://www.linuxquestions.org/questions/linux-newbie-8/understand-how-linux-deals-with-devices-4175468331/
Case 2: At https://community.nxp.com/thread/316910 the guy claims to have a Dell MS111 mouse which turns out to be a PixArt with the Primax idVendor and idProduct
0x4e22
. I also need verification here thatHID_QUIRK_ALWAYS_POLL
fixes this.Possible second reference: https://forums.opensuse.org/showthread.php/511915-OpenSUSE-12-1-crashed-and-cannot-boot-cannot-identify-boot-disk The disconnect is around 60s away from first connect.
Who can verify that boot option
usbhid.quirks=0x0461:0x4e22:0x00000400
works?