Date: Sat, 10 Aug 2019 20:00:09 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 233884] Corsair CORSAIR K70 RGB MK.2 / K63 / K63 Wireless not working Message-ID: <bug-233884-19105-MklphudhiC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233884-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-233884-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233884 ali@mashtizadeh.com <ali@mashtizadeh.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ali@mashtizadeh.com --- Comment #12 from ali@mashtizadeh.com <ali@mashtizadeh.com> --- With regards to the K70 RGB MK.2. The keyboard works fine inside of the BIOS/EFI and FreeBSD bootloader. Something during initialization seems wro= ng.=20 I have the boot proto quirk set. Corsair K70 RGB MK.2 Aug 10 15:51:44 market kernel: ugen0.10: <Corsair CORSAIR K70 RGB MK.2 Mechanical Gaming Keyboard> at usbus0 Aug 10 15:51:44 market kernel: ukbd2 on uhub1 Aug 10 15:51:44 market kernel: ukbd2: <Corsair CORSAIR K70 RGB MK.2 Mechani= cal Gaming Keyboard, class 0/0, rev 2.00/3.24, addr 15> on usbus0 Aug 10 15:51:44 market kernel: ukbd_attach: Parsing HID descriptor of 192 b= ytes Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left control Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right control Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left shift Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right shift Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left alt Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right alt Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left GUI Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right GUI Aug 10 15:51:44 market kernel: ukbd_parse_hid: Ignoring keyboard event cont= rol Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard numlock Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard capslock Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard scrolllock Aug 10 15:51:44 market kernel: ukbd_attach: Forcing boot protocol Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left control Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right control Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left shift Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right shift Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left alt Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right alt Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found left GUI Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found right GUI Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard event array Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard numlock Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard capslock Aug 10 15:51:44 market kernel: ukbd_parse_hid: Found keyboard scrolllock Aug 10 15:51:44 market kernel: ukbd_set_leds: leds=3D0x00 Aug 10 15:51:44 market syslogd: last message repeated 1 times Aug 10 15:51:44 market kernel: kbd4 at ukbd2 Aug 10 15:51:44 market kernel: ukbd_set_leds_callback: len=3D1, id=3D0 Aug 10 15:51:44 market kernel: uhid3 on uhub1 Aug 10 15:51:44 market kernel: uhid3: <Corsair CORSAIR K70 RGB MK.2 Mechani= cal Gaming Keyboard, class 0/0, rev 2.00/3.24, addr 15> on usbus0 USBDUMP: Pressing 'a' on both Corsair: m15:42:05.751977 usbus0.10 SUBM-INTR-EP=3D00000081,SPD=3DFULL,NFR=3D1,SLEN= =3D0,IVAL=3D1 frame[0] READ 64 bytes 15:42:05.751979 usbus0.10 DONE-INTR-EP=3D00000081,SPD=3DFULL,NFR=3D1,SLEN=3D24,IVAL=3D1,ERR=3D0 frame[0] READ 21 bytes 0000 01 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 0010 00 00 00 00 00 -- -- -- -- -- -- -- -- -- -- -- |..... | 15:42:05.818975 usbus0.10 SUBM-INTR-EP=3D00000081,SPD=3DFULL,NFR=3D1,SLEN= =3D0,IVAL=3D1 frame[0] READ 64 bytes 15:42:05.818976 usbus0.10 DONE-INTR-EP=3D00000081,SPD=3DFULL,NFR=3D1,SLEN=3D24,IVAL=3D1,ERR=3D0 frame[0] READ 21 bytes 0000 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 0010 00 00 00 00 00 -- -- -- -- -- -- -- -- -- -- -- |..... | Another Keyboard: a15:42:28.670668 usbus0.5 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D= 0,IVAL=3D10 frame[0] READ 8 bytes 15:42:28.670669 usbus0.5 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 04 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:42:28.766665 usbus0.5 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 15:42:28.766666 usbus0.5 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |........=20=20=20 Reading the bug reports from the ckb-next it seems they have added quirks to linux, which add sleeps to some part of the keyboard initialization. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233884-19105-MklphudhiC>