NetBSD Problem Report #55019

From www@netbsd.org  Wed Feb 26 09:51:53 2020
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 084241A9213
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 26 Feb 2020 09:51:53 +0000 (UTC)
Message-Id: <20200226095152.1041C1A9217@mollari.NetBSD.org>
Date: Wed, 26 Feb 2020 09:51:52 +0000 (UTC)
From: vezhlys@gmail.com
Reply-To: vezhlys@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Fnatic Gear Rush Pro keyboard ignores keypress on 6KRO mode
X-Send-Pr-Version: www-1.0

>Number:         55019
>Category:       kern
>Synopsis:       Fnatic Gear Rush Pro keyboard ignores keypress on 6KRO mode
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jakllsch
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 26 09:55:00 +0000 2020
>Closed-Date:    
>Last-Modified:  Fri Nov 04 19:48:26 +0000 2022
>Originator:     Andrius V
>Release:        NetBSD 9.0
>Organization:
>Environment:
>Description:
Creating a bug report based on discussions from this thread:

http://mail-index.netbsd.org/current-users/2019/10/04/msg036716.html

Fnatic Gear Rush Pro doesn't react to keypress on 6KRO mode. Switching from 6KRO to NKRO also is not possible in NetBSD (need to reattach keyboard to other system). NKRO mode works well, it is possible to switch 6KRO as well (though, rendering myself without functional keyboard). In general keyboard is recognized and visible in dmesg in both modes. Integrated USB hub works in all cases (attached devices don't stop working regardless the mode).

As per discussions, this commit was the one when it started to behave as it is now https://releng.netbsd.org/cgi-bin/req-7.cgi?show=1503, but prior it the keyboard was only working on 6KRO mode instead. usbhid-dump reports were provided in original thread, but I can reattach if needed.

dmesg messages
6KRO dmesg:

uhub4 at uhub1 port 12: Genesys Logic (0x5e3) USB2.0 Hub (0x608),
class 9/0, rev 2.00/32.98, addr 17
uhub4: single transaction translator
uhub4: 4 ports with 4 removable, self powered
uhidev1 at uhub4 port 2 configuration 1 interface 0
uhidev1: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2029), rev
2.00/1.09, addr 18, iclass 3/1
ukbd0 at uhidev1
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev2 at uhub4 port 2 configuration 1 interface 1
uhidev2: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2029), rev
2.00/1.09, addr 18, iclass 3/0
uhid0 at uhidev2: input=4, output=0, feature=0

NKRO dmesg:
uhub4 at uhub1 port 12: Genesys Logic (0x5e3) USB2.0 Hub (0x608),
class 9/0, rev 2.00/32.98, addr 19
uhub4: single transaction translator
uhub4: 4 ports with 4 removable, self powered
uhidev1 at uhub4 port 2 configuration 1 interface 0
uhidev1: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2030), rev
2.00/1.09, addr 20, iclass 3/1
ukbd0 at uhidev1
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev2 at uhub4 port 2 configuration 1 interface 1
uhidev2: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2030), rev
2.00/1.09, addr 20, iclass 3/0
uhid0 at uhidev2: input=4, output=0, feature=0
uhidev3 at uhub4 port 2 configuration 1 interface 2
uhidev3: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2030), rev
2.00/1.09, addr 20, iclass 3/0
ukbd1 at uhidev3
wskbd2 at ukbd1 mux 1
wskbd2: connecting to wsdisplay0

Regards,
Andrius V
>How-To-Repeat:
Boot with the keyboard attached in 6KRO mode or switch keyboard to 6KRO by clicking Fn+N.
>Fix:

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->jakllsch
Responsible-Changed-By: martin@NetBSD.org
Responsible-Changed-When: Wed, 26 Feb 2020 10:04:26 +0000
Responsible-Changed-Why:
over to original commiter - Jonathan, could you please have a look?


From: "Jonathan A. Kollasch" <jakllsch@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/55019 CVS commit: src/sys/dev/usb
Date: Wed, 9 Feb 2022 18:09:49 +0000

 Module Name:	src
 Committed By:	jakllsch
 Date:		Wed Feb  9 18:09:48 UTC 2022

 Modified Files:
 	src/sys/dev/usb: uhidev.c

 Log Message:
 Do not explicitly set the HID Report Protocol upon attach, some devices
 don't like it and should be in Report Protocol after enumeration/reset
 anyway.

 May address PR kern/55019.


 To generate a diff of this commit:
 cvs rdiff -u -r1.81 -r1.82 src/sys/dev/usb/uhidev.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->feedback
State-Changed-By: jakllsch@NetBSD.org
State-Changed-When: Wed, 09 Feb 2022 18:12:06 +0000
State-Changed-Why:
potential fix committed; please check


From: Andrius V <vezhlys@gmail.com>
To: gnats-bugs@netbsd.org
Cc: jakllsch@netbsd.org, netbsd-bugs@netbsd.org, gnats-admin@netbsd.org
Subject: Re: kern/55019 (Fnatic Gear Rush Pro keyboard ignores keypress on
 6KRO mode)
Date: Wed, 9 Feb 2022 23:32:48 +0200

 Hi,

 Yes, it fixes the issue. I can switch between modes and use them
 without any problems now.

 On Wed, Feb 9, 2022 at 8:12 PM <jakllsch@netbsd.org> wrote:
 >
 > Synopsis: Fnatic Gear Rush Pro keyboard ignores keypress on 6KRO mode
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: jakllsch@NetBSD.org
 > State-Changed-When: Wed, 09 Feb 2022 18:12:06 +0000
 > State-Changed-Why:
 > potential fix committed; please check
 >
 >
 >

From: Andrius V <vezhlys@gmail.com>
To: jakllsch@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, 
	gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/55019 (Fnatic Gear Rush Pro keyboard ignores keypress on
 6KRO mode)
Date: Sun, 13 Feb 2022 02:11:05 +0200

 Should we pull the fix to netbsd-9 or I should just close PR?

 On Wed, Feb 9, 2022 at 11:35 PM Andrius V <vezhlys@gmail.com> wrote:
 >
 > The following reply was made to PR kern/55019; it has been noted by GNATS.
 >
 > From: Andrius V <vezhlys@gmail.com>
 > To: gnats-bugs@netbsd.org
 > Cc: jakllsch@netbsd.org, netbsd-bugs@netbsd.org, gnats-admin@netbsd.org
 > Subject: Re: kern/55019 (Fnatic Gear Rush Pro keyboard ignores keypress on
 >  6KRO mode)
 > Date: Wed, 9 Feb 2022 23:32:48 +0200
 >
 >  Hi,
 >
 >  Yes, it fixes the issue. I can switch between modes and use them
 >  without any problems now.
 >
 >  On Wed, Feb 9, 2022 at 8:12 PM <jakllsch@netbsd.org> wrote:
 >  >
 >  > Synopsis: Fnatic Gear Rush Pro keyboard ignores keypress on 6KRO mode
 >  >
 >  > State-Changed-From-To: open->feedback
 >  > State-Changed-By: jakllsch@NetBSD.org
 >  > State-Changed-When: Wed, 09 Feb 2022 18:12:06 +0000
 >  > State-Changed-Why:
 >  > potential fix committed; please check
 >  >
 >  >
 >  >
 >

State-Changed-From-To: feedback->pending-pullups
State-Changed-By: jakllsch@NetBSD.org
State-Changed-When: Wed, 16 Feb 2022 14:05:38 +0000
State-Changed-Why:
pullup requested [pullup-9 #1428]


From: "Martin Husemann" <martin@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/55019 CVS commit: [netbsd-9] src/sys/dev/usb
Date: Wed, 16 Feb 2022 14:36:12 +0000

 Module Name:	src
 Committed By:	martin
 Date:		Wed Feb 16 14:36:12 UTC 2022

 Modified Files:
 	src/sys/dev/usb [netbsd-9]: uhidev.c

 Log Message:
 Pull up following revision(s) (requested by jakllsch in ticket #1428):

 	sys/dev/usb/uhidev.c: revision 1.82

 Do not explicitly set the HID Report Protocol upon attach, some devices
 don't like it and should be in Report Protocol after enumeration/reset
 anyway.

 May address PR kern/55019.


 To generate a diff of this commit:
 cvs rdiff -u -r1.75.2.1 -r1.75.2.2 src/sys/dev/usb/uhidev.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: pending-pullups->closed
State-Changed-By: jakllsch@NetBSD.org
State-Changed-When: Thu, 17 Feb 2022 13:04:14 +0000
State-Changed-Why:
pullup completed


State-Changed-From-To: closed->open
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Fri, 04 Nov 2022 19:48:26 +0000
State-Changed-Why:
Change was backed out.


>Unformatted:

Home	PR Database Search