Re: Fnatic RUSH mechanical keyboard ignores keypress

To: Andrius V <vezhlys%gmail.com@localhost>
Subject: Re: Fnatic RUSH mechanical keyboard ignores keypress
From: "Jonathan A. Kollasch" <jakllsch%kollasch.net@localhost>
Date: Thu, 12 Dec 2019 13:16:21 -0600
Could you also provide (under Linux) the output of:

usbhid-dump -e desc -t 1 -d 0x195d

with the keyboard in both 6KRO and NKRO modes?

	Jonathan Kollasch

On Thu, Dec 12, 2019 at 02:01:49AM +0200, Andrius V wrote:
> Hi,
> 
> I tested the the keyboard before and after pull-up. Indeed, it
> actually changed the behavior, results of testing were the following:
> * Before the pull up keyboard worked in 6KRO mode only. Switching to
> NKRO was failing to attach the keyboard with the message "ukbd1:
> attach failed, too many modifier keys". However, it was still possible
> to switch back to 6KRO without reboot.
> 
> uhidev0 at uhub5 port 2 configuration 1 interface 0
> uhidev0: Fnatic Gear RUSH Mechanical Keyboard, rev 2.00/1.09, addr 3, iclass 3/1
> ukbd0 at uhidev0: 8 modifier keys, 6 key codes
> wskbd0 at ukbd0: console keyboard, using wsdisplay0
> uhidev1 at uhub5 port 2 configuration 1 interface 1
> uhidev1: Fnatic Gear RUSH Mechanical Keyboard, rev 2.00/1.09, addr 3, iclass 3/0
> uhid0 at uhidev1: input=4, output=0, feature=0
> uhidev2 at uhub5 port 2 configuration 1 interface 2
> uhidev2: Fnatic Gear RUSH Mechanical Keyboard, rev 2.00/1.09, addr 3, iclass 3/0
> ukbd1 at uhidev2
> ukbd1: attach failed, too many modifier keys
> 
> * After the pull up keyboard started to work in NKRO mode only.
> However, after switching to 6KRO mode keyboard stops working.
> Switching back to NKRO doesn't work from NetBSD, keyboard stays in the
> same mode, reboot is required (or reconnect keyboard to other PC) and
> mode switch performed in the other OS. dmesg is slightly different
> between two modes:
> 
> 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
> 
> Linux accordingly:
> usb 1-12.2: new full-speed USB device number 5 using xhci_hcd
> usb 1-12.2: New USB device found, idVendor=195d, idProduct=2029, bcdDevice= 1.09
> usb 1-12.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 1-12.2: Product: RUSH Mechanical Keyboard
> usb 1-12.2: Manufacturer: Fnatic Gear
> input: Fnatic Gear RUSH Mechanical Keyboard as
> /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12.2/1-12.2:1.0/0003:195D:2029.0005/input/input22
> hid-generic 0003:195D:2029.0005: input,hidraw1: USB HID v1.11 Keyboard
> [Fnatic Gear RUSH Mechanical Keyboard] on usb-0000:01:00.0-12.2/input0
> input: Fnatic Gear RUSH Mechanical Keyboard as
> /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12.2/1-12.2:1.1/0003:195D:2029.0006/input/input23
> hid-generic 0003:195D:2029.0006: input,hidraw2: USB HID v1.11 Device
> [Fnatic Gear RUSH Mechanical Keyboard] on usb-0000:01:00.0-12.2/input1
> 
> usb 1-12.2: new full-speed USB device number 8 using xhci_hcd
> usb 1-12.2: New USB device found, idVendor=195d, idProduct=2030, bcdDevice= 1.09
> usb 1-12.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 1-12.2: Product: RUSH Mechanical Keyboard
> usb 1-12.2: Manufacturer: Fnatic Gear
> input: Fnatic Gear RUSH Mechanical Keyboard as
> /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12.2/1-12.2:1.0/0003:195D:2030.000C/input/input29
> hid-generic 0003:195D:2030.000C: input,hidraw1: USB HID v1.11 Keyboard
> [Fnatic Gear RUSH Mechanical Keyboard] on usb-0000:01:00.0-12.2/input0
> input: Fnatic Gear RUSH Mechanical Keyboard as
> /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12.2/1-12.2:1.1/0003:195D:2030.000D/input/input30
> hid-generic 0003:195D:2030.000D: input,hidraw2: USB HID v1.11 Device
> [Fnatic Gear RUSH Mechanical Keyboard] on usb-0000:01:00.0-12.2/input1
> input: Fnatic Gear RUSH Mechanical Keyboard as
> /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12.2/1-12.2:1.2/0003:195D:2030.000E/input/input31
> hid-generic 0003:195D:2030.000E: input,hidraw3: USB HID v1.11 Keyboard
> [Fnatic Gear RUSH Mechanical Keyboard] on usb-0000:01:00.0-12.2/input2
> 
> Regards,
> Andrius V
> 
> 
> On Thu, Dec 5, 2019 at 11:49 PM Andrius V <vezhlys%gmail.com@localhost> wrote:
> >
> > Now that you mentioned switching between modes, it finally made sense
> > why keyboard suddenly stopped working across systems which were
> > working previously. I just tested switching between modes and keyboard
> > still works on NKRO mode even on current/NetBSD 9, etc. Apparently, I
> > accidentally switched to 6KRO at some point. Thus, keyboard "stops"
> > working specifically on 6KRO mode only. It also doesn't seem that I
> > can switch from 6KRO back to NKRO in NetBSD though (keyboard reacts to
> > an attempt by turning off/on but apparently stays in 6KRO mode. I need
> > to boot into Linux, make a switch and reboot to make it work again).
> > Switching to 6KRO immediately renders the keyboard unusable
> > immediately. I guess with a bit more guidance I can get required data.
> > Modifying/building kernel is not an issue for me. Do those reports
> > need to be specifically performed in NetBSD? Thank you.
> >
> >
> > On Thu, Dec 5, 2019 at 8:40 PM Jonathan A. Kollasch
> > <jakllsch%kollasch.net@localhost> wrote:
> > >
> > > Almost certianly my:
> > > https://releng.netbsd.org/cgi-bin/req-7.cgi?show=1503
> > >
> > > I really need to see all of the problem keyboard's HID descriptors,
> > > which, unfortunately, isn't easy to do without modifying the NetBSD kernel.
> > >
> > > Seeing some dumps of the report data coming in would also be useful in
> > > both NKRO and 6KRO modes, which could be possible to get already with
> > > enough (build-time?) debugging enabled.
> > >
> > >         Jonathan Kollasch
> > >
> > > On Thu, Dec 05, 2019 at 09:44:36AM +0200, Andrius V wrote:
> > > > On netbsd-7-0 and and netbsd-7-1 branches keyboard still work
> > > > properly, not on netbsd-7 and up though. I guess I will try to find
> > > > affecting pull-up. Currently don't see any clear candidate for
> > > > regression.
> > > >
> > > > On Sat, Oct 5, 2019 at 4:49 PM Andrius V <vezhlys%gmail.com@localhost> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Version seems to be irrelevant, since the keyboard stopped working on
> > > > > any NetBSD setup from 7.2 to the latest current branch based on my
> > > > > testing. Also it doesn't matter on which computer system it is
> > > > > attached (as well as if it is amd64 or i386 port). From the first
> > > > > glance, it would imply some hardware issue but the keyboard works fine
> > > > > with all the other operating systems (I tested Windows 10, Manjaro
> > > > > Linux, FreeBSD 12, OpenBSD 6.6 Beta). It worked well in NetBSD
> > > > > recently too... I don't believe that dmesg will show any relevant
> > > > > information since I don't see any changes, I guess some USB debugging
> > > > > may reveal more information? Nevertheless you can find dmesg below:
> > > > >
> > > > > NetBSD 9.0_BETA (GENERIC) #18: Tue Oct  1 22:31:00 EEST 2019
> > > > >     andriusv@localhost:/home/andriusv/netbsd-src/sys/arch/amd64/compile/GENERIC
> > > > > total memory = 32719 MB
> > > > > avail memory = 31739 MB
> > > > > cpu_rng: RDSEED
> > > > > WARNING: ZFS on NetBSD is under development
> > > > > ZFS filesystem version: 5
> > > > > timecounter: Timecounters tick every 10.000 msec
> > > > > Kernelized RAIDframe activated
> > > > > running cgd selftest aes-xts-256 aes-xts-512 done
> > > > > timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
> > > > > BIOSTAR Group X370GT5 ( )
> > > > > mainbus0 (root)
> > > > > ACPI: RSDP 0x00000000000F05A0 000024 (v02 ALASKA)
> > > > > ACPI: XSDT 0x00000000DBFA80A0 0000C4 (v01 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: FACP 0x00000000DBFAD588 000114 (v06 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: DSDT 0x00000000DBFA8200 005386 (v02 ALASKA A M I    01072009
> > > > > INTL 20120913)
> > > > > ACPI: FACS 0x00000000DC044E00 000040
> > > > > ACPI: APIC 0x00000000DBFAD6A0 00015E (v03 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: FPDT 0x00000000DBFAD800 000044 (v01 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: FIDT 0x00000000DBFAD848 00009C (v01 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: SSDT 0x00000000DBFAD8E8 0000C8 (v02 ALASKA CPUSSDT  01072009 AMI
> > > > >  01072009)
> > > > > ACPI: SSDT 0x00000000DBFAD9B0 008C98 (v02 AMD    AMD ALIB 00000002
> > > > > MSFT 04000000)
> > > > > ACPI: SSDT 0x00000000DBFB6648 003230 (v01 AMD    AMD AOD  00000001
> > > > > INTL 20120913)
> > > > > ACPI: MCFG 0x00000000DBFB9878 00003C (v01 ALASKA A M I    01072009
> > > > > MSFT 00010013)
> > > > > ACPI: BHMB 0x00000000DBFB98B8 000474 (v01 ALASKA A M I    00000001 AMI
> > > > >  00000001)
> > > > > ACPI: HPET 0x00000000DBFB9D30 000038 (v01 ALASKA A M I    01072009 AMI
> > > > >  00000005)
> > > > > ACPI: SSDT 0x00000000DBFB9D68 000024 (v01 AMDFCH FCHZP    00001000
> > > > > INTL 20120913)
> > > > > ACPI: UEFI 0x00000000DBFB9D90 000042 (v01 ALASKA A M I    00000002
> > > > >  01000013)
> > > > > ACPI: TPM2 0x00000000DBFB9DD8 000038 (v04 ALASKA A M I    00000001 AMI
> > > > >  00000000)
> > > > > ACPI: IVRS 0x00000000DBFB9E10 0000D0 (v02 AMD    AMD IVRS 00000001 AMD
> > > > >  00000000)
> > > > > ACPI: SSDT 0x00000000DBFB9EE0 001A58 (v01 AMD    AMD CPU  00000001 AMD
> > > > >  00000001)
> > > > > ACPI: CRAT 0x00000000DBFBB938 000BD0 (v01 AMD    AMD CRAT 00000001 AMD
> > > > >  00000001)
> > > > > ACPI: CDIT 0x00000000DBFBC508 000029 (v01 AMD    AMD CDIT 00000001 AMD
> > > > >  00000001)
> > > > > ACPI: SSDT 0x00000000DBFBC538 001D4A (v01 AMD    AmdTable 00000001
> > > > > INTL 20120913)
> > > > > ACPI: SSDT 0x00000000DBFBE288 0000BF (v01 AMD    AMD PT   00001000
> > > > > INTL 20120913)
> > > > > ACPI: WSMT 0x00000000DBFBE348 000028 (v01 ALASKA A M I    01072009 AMI
> > > > >  00010013)
> > > > > ACPI: 8 ACPI AML tables successfully acquired and loaded
> > > > > ioapic0 at mainbus0 apid 13: pa 0xfec00000, version 0x21, 24 pins
> > > > > ioapic1 at mainbus0 apid 14: pa 0xfec01000, version 0x21, 32 pins
> > > > > cpu0 at mainbus0 apid 0
> > > > > cpu0: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu0: package 0, core 0, smt 0
> > > > > cpu1 at mainbus0 apid 2
> > > > > cpu1: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu1: package 0, core 1, smt 0
> > > > > cpu2 at mainbus0 apid 4
> > > > > cpu2: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu2: package 0, core 2, smt 0
> > > > > cpu3 at mainbus0 apid 8
> > > > > cpu3: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu3: package 0, core 4, smt 0
> > > > > cpu4 at mainbus0 apid 10
> > > > > cpu4: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu4: package 0, core 5, smt 0
> > > > > cpu5 at mainbus0 apid 12
> > > > > cpu5: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu5: package 0, core 6, smt 0
> > > > > cpu6 at mainbus0 apid 1
> > > > > cpu6: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu6: package 0, core 0, smt 1
> > > > > cpu7 at mainbus0 apid 3
> > > > > cpu7: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu7: package 0, core 1, smt 1
> > > > > cpu8 at mainbus0 apid 5
> > > > > cpu8: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu8: package 0, core 2, smt 1
> > > > > cpu9 at mainbus0 apid 9
> > > > > cpu9: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu9: package 0, core 4, smt 1
> > > > > cpu10 at mainbus0 apid 11
> > > > > cpu10: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu10: package 0, core 5, smt 1
> > > > > cpu11 at mainbus0 apid 13
> > > > > cpu11: AMD Ryzen 5 1600 Six-Core Processor            , id 0x800f11
> > > > > cpu11: package 0, core 6, smt 1
> > > > > acpi0 at mainbus0: Intel ACPICA 20190405
> > > > > acpi0: X/RSDT: OemId <ALASKA,  A M I ,01072009>, AslId <AMI ,00010013>
> > > > > acpi0: autoconfiguration error: invalid PCI address for D01E
> > > > > acpi0: MCFG: segment 0, bus 0-63, address 0x00000000f8000000
> > > > > acpi0: SCI interrupting at int 9
> > > > > acpi0: fixed power button present
> > > > > timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
> > > > > hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
> > > > > timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
> > > > > AMDN (PNP0C01) at acpi0 not configured
> > > > > IOMA (PNP0C02) at acpi0 not configured
> > > > > APSP (PNP0C02) at acpi0 not configured
> > > > > attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
> > > > > pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
> > > > > spkr0 at pcppi1: PC Speaker
> > > > > wsbell at spkr0 not configured
> > > > > midi0 at pcppi1: PC speaker
> > > > > sysbeep0 at pcppi1
> > > > > SIO1 (PNP0C02) at acpi0 not configured
> > > > > pckbc1 at acpi0 (PS2K, PNP0303-0) (kbd port): io 0x60,0x64 irq 1
> > > > > UAR1 (PNP0501) at acpi0 not configured
> > > > > S900 (PNP0C02) at acpi0 not configured
> > > > > acpibut0 at acpi0 (PWRB, PNP0C0C-170): ACPI Power Button
> > > > > GPIO (AMDI0030) at acpi0 not configured
> > > > > TPM (MSFT0101) at acpi0 not configured
> > > > > AWR0 (PNP0C02) at acpi0 not configured
> > > > > ABR0 (PNP0C02) at acpi0 not configured
> > > > > ABR1 (PNP0C02) at acpi0 not configured
> > > > > ABR2 (PNP0C02) at acpi0 not configured
> > > > > ABR3 (PNP0C02) at acpi0 not configured
> > > > > ABR4 (PNP0C02) at acpi0 not configured
> > > > > ABR5 (PNP0C02) at acpi0 not configured
> > > > > ABR6 (PNP0C02) at acpi0 not configured
> > > > > ABR7 (PNP0C02) at acpi0 not configured
> > > > > AWR1 (PNP0C02) at acpi0 not configured
> > > > > ABR8 (PNP0C02) at acpi0 not configured
> > > > > ABR9 (PNP0C02) at acpi0 not configured
> > > > > ABRA (PNP0C02) at acpi0 not configured
> > > > > ABRB (PNP0C02) at acpi0 not configured
> > > > > ABRC (PNP0C02) at acpi0 not configured
> > > > > ABRD (PNP0C02) at acpi0 not configured
> > > > > ABRE (PNP0C02) at acpi0 not configured
> > > > > ABRF (PNP0C02) at acpi0 not configured
> > > > > PTIO (AMDIF030) at acpi0 not configured
> > > > > acpitz0 at acpi0 (THRM)
> > > > > acpitz0: levels: critical 127.0 C, passive cooling
> > > > > acpiwmi0 at acpi0 (AOD, PNP0C14-AOD): ACPI WMI Interface
> > > > > acpiwmibus at acpiwmi0 not configured
> > > > > ACPI: Enabled 1 GPEs in block 00 to 1F
> > > > > attimer1: attached to pcppi1
> > > > > pci0 at mainbus0 bus 0: configuration mode 1
> > > > > pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
> > > > > amdsmn0 at pci0 dev 0 function 0: AMD Family 17h System Management Network
> > > > > amdzentemp0 at amdsmn0: AMD CPU Temperature Sensors (Family17h)
> > > > > vendor 1022 product 1451 (IOMMU system) at pci0 dev 0 function 2 not configured
> > > > > pchb0 at pci0 dev 1 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > ppb0 at pci0 dev 1 function 1: vendor 1022 product 1453 (rev. 0x00)
> > > > > ppb0: PCI Express capability version 2 <Root Port of PCI-E Root
> > > > > Complex> x4 @ 2.5GT/s
> > > > > pci1 at ppb0 bus 1
> > > > > pci1: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > xhci0 at pci1 dev 0 function 0: vendor 1022 product 43b9 (rev. 0x02)
> > > > > xhci0: interrupting at msi0 vec 0
> > > > > xhci0: xHCI version 1.10
> > > > > usb0 at xhci0: USB revision 3.1
> > > > > usb1 at xhci0: USB revision 2.0
> > > > > ahcisata0 at pci1 dev 0 function 1: vendor 1022 product 43b5 (rev. 0x02)
> > > > > ahcisata0: 64-bit DMA
> > > > > ahcisata0: AHCI revision 1.31, 8 ports, 32 slots, CAP
> > > > > 0xef36ff27<SXS,PSC,SSC,PMD,SPM,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SSS,SSNTF,SNCQ,S64A>
> > > > > ahcisata0: interrupting at msi1 vec 0
> > > > > atabus0 at ahcisata0 channel 0
> > > > > atabus1 at ahcisata0 channel 1
> > > > > atabus2 at ahcisata0 channel 2
> > > > > atabus3 at ahcisata0 channel 3
> > > > > atabus4 at ahcisata0 channel 4
> > > > > atabus5 at ahcisata0 channel 5
> > > > > atabus6 at ahcisata0 channel 6
> > > > > atabus7 at ahcisata0 channel 7
> > > > > ppb1 at pci1 dev 0 function 2: vendor 1022 product 43b0 (rev. 0x02)
> > > > > ppb1: PCI Express capability version 2 <Upstream Port of PCI-E Switch>
> > > > > pci2 at ppb1 bus 2
> > > > > pci2: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb2 at pci2 dev 0 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb2: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > ppb2: link is x1 @ 2.5GT/s
> > > > > pci3 at ppb2 bus 3
> > > > > pci3: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > re0 at pci3 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet
> > > > > (rev. 0x16)
> > > > > re0: interrupting at msix2 vec 0
> > > > > re0: Ethernet address xx:xx:xx:xx:xx:xx
> > > > > re0: using 256 tx descriptors
> > > > > rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
> > > > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
> > > > > ppb3 at pci2 dev 1 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb3: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > ppb3: link is x1 @ 2.5GT/s
> > > > > pci4 at ppb3 bus 4
> > > > > pci4: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb4 at pci4 dev 0 function 0: vendor 1b21 product 1080 (rev. 0x03)
> > > > > pci5 at ppb4 bus 5
> > > > > pci5: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb5 at pci2 dev 2 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb5: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > pci6 at ppb5 bus 6
> > > > > pci6: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb6 at pci2 dev 3 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb6: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > pci7 at ppb6 bus 7
> > > > > pci7: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb7 at pci2 dev 4 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb7: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x2 @ 5.0GT/s
> > > > > pci8 at ppb7 bus 8
> > > > > pci8: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > vendor 14e4 product 168e (ethernet network, revision 0x10) at pci8 dev
> > > > > 0 function 0 not configured
> > > > > vendor 14e4 product 168e (ethernet network, revision 0x10) at pci8 dev
> > > > > 0 function 1 not configured
> > > > > ppb8 at pci2 dev 6 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb8: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > pci9 at ppb8 bus 9
> > > > > pci9: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > ppb9 at pci2 dev 7 function 0: vendor 1022 product 43b4 (rev. 0x02)
> > > > > ppb9: PCI Express capability version 2 <Downstream Port of PCI-E
> > > > > Switch> x1 @ 5.0GT/s
> > > > > ppb9: link is x1 @ 2.5GT/s
> > > > > pci10 at ppb9 bus 10
> > > > > pci10: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > athn0 at pci10 dev 0 function 0: Atheros AR9287
> > > > > athn0: rev 2 (2T2R), ROM rev 4, address xx:xx:xx:xx:xx:xx
> > > > > athn0: interrupting at ioapic1 pin 3
> > > > > athn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> > > > > athn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
> > > > > 24Mbps 36Mbps 48Mbps 54Mbps
> > > > > pchb1 at pci0 dev 2 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > pchb2 at pci0 dev 3 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > ppb10 at pci0 dev 3 function 1: vendor 1022 product 1453 (rev. 0x00)
> > > > > ppb10: PCI Express capability version 2 <Root Port of PCI-E Root
> > > > > Complex> x16 @ 8.0GT/s
> > > > > pci11 at ppb10 bus 11
> > > > > pci11: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > radeon0 at pci11 dev 0 function 0: vendor 1002 product 6811 (rev. 0x81)
> > > > > hdaudio0 at pci11 dev 0 function 1: HD Audio Controller
> > > > > hdaudio0: interrupting at msi3 vec 0
> > > > > hdafg0 at hdaudio0: vendor 1002 product aa01
> > > > > hdafg0: HDMI00 2ch: Digital Out [Jack]
> > > > > hdafg0: HDMI01 2ch: Digital Out [Jack]
> > > > > hdafg0: HDMI02 2ch: Digital Out [Jack]
> > > > > hdafg0: HDMI03 2ch: Digital Out [Jack]
> > > > > hdafg0: HDMI04 2ch: Digital Out [Jack]
> > > > > hdafg0: HDMI05 2ch: Digital Out [Jack]
> > > > > hdafg0: 2ch/0ch 32000Hz 44100Hz 48000Hz PCM16 AC3
> > > > > pchb3 at pci0 dev 4 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > pchb4 at pci0 dev 7 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > ppb11 at pci0 dev 7 function 1: vendor 1022 product 1454 (rev. 0x00)
> > > > > ppb11: PCI Express capability version 2 <Root Port of PCI-E Root
> > > > > Complex> x16 @ 8.0GT/s
> > > > > pci12 at ppb11 bus 12
> > > > > pci12: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > vendor 1022 product 145a (non-essential instrumentation, subclass
> > > > > 0x00) at pci12 dev 0 function 0 not configured
> > > > > vendor 1022 product 1456 (miscellaneous crypto) at pci12 dev 0
> > > > > function 2 not configured
> > > > > xhci1 at pci12 dev 0 function 3: vendor 1022 product 145c (rev. 0x00)
> > > > > xhci1: interrupting at msi4 vec 0
> > > > > xhci1: xHCI version 1.0
> > > > > usb2 at xhci1: USB revision 3.0
> > > > > usb3 at xhci1: USB revision 2.0
> > > > > pchb5 at pci0 dev 8 function 0: vendor 1022 product 1452 (rev. 0x00)
> > > > > ppb12 at pci0 dev 8 function 1: vendor 1022 product 1454 (rev. 0x00)
> > > > > ppb12: PCI Express capability version 2 <Root Port of PCI-E Root
> > > > > Complex> x16 @ 8.0GT/s
> > > > > pci13 at ppb12 bus 13
> > > > > pci13: i/o space, memory space enabled, rd/line, wr/inv ok
> > > > > vendor 1022 product 1455 (non-essential instrumentation, subclass
> > > > > 0x00) at pci13 dev 0 function 0 not configured
> > > > > ahcisata1 at pci13 dev 0 function 2: vendor 1022 product 7901 (rev. 0x51)
> > > > > ahcisata1: 64-bit DMA
> > > > > ahcisata1: AHCI revision 1.31, 8 ports, 32 slots, CAP
> > > > > 0xf737ff07<PSC,SSC,PMD,FBSS,SPM,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SMPS,SSNTF,SNCQ,S64A>
> > > > > ahcisata1: interrupting at msi5 vec 0
> > > > > atabus8 at ahcisata1 channel 0
> > > > > atabus9 at ahcisata1 channel 1
> > > > > atabus10 at ahcisata1 channel 2
> > > > > atabus11 at ahcisata1 channel 3
> > > > > atabus12 at ahcisata1 channel 4
> > > > > atabus13 at ahcisata1 channel 5
> > > > > atabus14 at ahcisata1 channel 6
> > > > > atabus15 at ahcisata1 channel 7
> > > > > hdaudio1 at pci13 dev 0 function 3: HD Audio Controller
> > > > > hdaudio1: interrupting at msi6 vec 0
> > > > > hdafg1 at hdaudio1: vendor 10ec product 0892
> > > > > hdafg1: DAC00 8ch: Speaker [Jack]
> > > > > hdafg1: DAC01 2ch: HP Out [Jack]
> > > > > hdafg1: DIG02 2ch: SPDIF Out [Jack]
> > > > > hdafg1: ADC03 2ch: Line In [Jack], Mic In [Jack]
> > > > > hdafg1: ADC04 2ch: Mic In [Jack]
> > > > > hdafg1: 8ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16
> > > > > PCM20 PCM24 AC3
> > > > > audio0 at hdafg1: playback, capture, full duplex, independent
> > > > > audio0: slinear_le:16 8ch 48000Hz, blk 40ms for playback
> > > > > audio0: slinear_le:16 2ch 48000Hz, blk 40ms for recording
> > > > > spkr1 at audio0: PC Speaker (synthesized)
> > > > > wsbell at spkr1 not configured
> > > > > piixpm0 at pci0 dev 20 function 0: vendor 1022 product 790b (rev. 0x59)
> > > > > piixpm0: polling
> > > > > iic0 at piixpm0 port 0: I2C bus
> > > > > iic1 at piixpm0 port 1: I2C bus
> > > > > iic2 at piixpm0 port 2: I2C bus
> > > > > iic3 at piixpm0 port 3: I2C bus
> > > > > pcib0 at pci0 dev 20 function 3: vendor 1022 product 790e (rev. 0x51)
> > > > > pchb6 at pci0 dev 24 function 0: vendor 1022 product 1460 (rev. 0x00)
> > > > > pchb7 at pci0 dev 24 function 1: vendor 1022 product 1461 (rev. 0x00)
> > > > > pchb8 at pci0 dev 24 function 2: vendor 1022 product 1462 (rev. 0x00)
> > > > > pchb9 at pci0 dev 24 function 3: vendor 1022 product 1463 (rev. 0x00)
> > > > > pchb10 at pci0 dev 24 function 4: vendor 1022 product 1464 (rev. 0x00)
> > > > > pchb11 at pci0 dev 24 function 5: vendor 1022 product 1465 (rev. 0x00)
> > > > > pchb12 at pci0 dev 24 function 6: vendor 1022 product 1466 (rev. 0x00)
> > > > > pchb13 at pci0 dev 24 function 7: vendor 1022 product 1467 (rev. 0x00)
> > > > > isa0 at pcib0
> > > > > com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> > > > > acpicpu0 at cpu0: ACPI CPU
> > > > > acpicpu0: C1: FFH, lat   1 us, pow     0 mW
> > > > > acpicpu0: C2: I/O, lat 400 us, pow     0 mW
> > > > > acpicpu0: P0: FFH, lat   1 us, pow  3960 mW, 3200 MHz
> > > > > acpicpu0: P1: FFH, lat   1 us, pow  2940 mW, 2800 MHz
> > > > > acpicpu0: P2: FFH, lat   1 us, pow  1350 mW, 1550 MHz
> > > > > acpicpu0: T0: I/O, lat   1 us, pow     0 mW, 100 %
> > > > > acpicpu0: T1: I/O, lat   1 us, pow     0 mW,  88 %
> > > > > acpicpu0: T2: I/O, lat   1 us, pow     0 mW,  76 %
> > > > > acpicpu0: T3: I/O, lat   1 us, pow     0 mW,  64 %
> > > > > acpicpu0: T4: I/O, lat   1 us, pow     0 mW,  52 %
> > > > > acpicpu0: T5: I/O, lat   1 us, pow     0 mW,  40 %
> > > > > acpicpu0: T6: I/O, lat   1 us, pow     0 mW,  28 %
> > > > > acpicpu0: T7: I/O, lat   1 us, pow     0 mW,  16 %
> > > > > acpicpu1 at cpu1: ACPI CPU
> > > > > acpicpu2 at cpu2: ACPI CPU
> > > > > acpicpu3 at cpu3: ACPI CPU
> > > > > acpicpu4 at cpu4: ACPI CPU
> > > > > acpicpu5 at cpu5: ACPI CPU
> > > > > acpicpu6 at cpu6: ACPI CPU
> > > > > acpicpu7 at cpu7: ACPI CPU
> > > > > acpicpu8 at cpu8: ACPI CPU
> > > > > acpicpu9 at cpu9: ACPI CPU
> > > > > acpicpu10 at cpu10: ACPI CPU
> > > > > acpicpu11 at cpu11: ACPI CPU
> > > > > timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
> > > > > autoconfiguration error: ERROR: 4400 cycle TSC drift observed
> > > > > uhub0 at usb0: NetBSD (0000) xHCI root hub (0000), class 9/0, rev
> > > > > 3.00/1.00, addr 0
> > > > > uhub0: 8 ports with 8 removable, self powered
> > > > > uhub1 at usb1: NetBSD (0000) xHCI root hub (0000), class 9/0, rev
> > > > > 2.00/1.00, addr 0
> > > > > uhub1: 14 ports with 14 removable, self powered
> > > > > uhub2 at usb2: NetBSD (0000) xHCI root hub (0000), class 9/0, rev
> > > > > 3.00/1.00, addr 0
> > > > > uhub2: 4 ports with 4 removable, self powered
> > > > > uhub3 at usb3: NetBSD (0000) xHCI root hub (0000), class 9/0, rev
> > > > > 2.00/1.00, addr 0
> > > > > uhub3: 4 ports with 4 removable, self powered
> > > > > IPsec: Initialized Security Association Processing.
> > > > > ahcisata0 port 0: device present, speed: 6.0Gb/s
> > > > > ahcisata0 port 4: device present, speed: 3.0Gb/s
> > > > > autoconfiguration error: ahcisata0 port 4: clearing WDCTL_RST failed
> > > > > for drive 15
> > > > > autoconfiguration error: ahcisata0 port 0: clearing WDCTL_RST failed
> > > > > for drive 15
> > > > > autoconfiguration error: ahcisata0 port 4: drive 15 reset failed, disabling PMP
> > > > > autoconfiguration error: ahcisata0 port 0: drive 15 reset failed, disabling PMP
> > > > > ahcisata0 port 4: device present, speed: 3.0Gb/s
> > > > > ahcisata0 port 0: device present, speed: 6.0Gb/s
> > > > > umass0 at uhub0 port 6 configuration 1 interface 0
> > > > > umass0: StoreJet Transcend (0x174c) StoreJet Transcend (0x5106), rev
> > > > > 3.00/80.00, addr 1
> > > > > umass0: using SCSI over Bulk-Only
> > > > > scsibus0 at umass0: 2 targets, 1 lun per target
> > > > > sd0 at scsibus0 target 0 lun 0: <StoreJet, Transcend, 0> disk fixed
> > > > > sd0: 238 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 500118192 sectors
> > > > > uhub4 at uhub1 port 5: vendor 05e3 (0x5e3) USB2.0 Hub (0x608), class
> > > > > 9/0, rev 2.00/32.98, addr 2
> > > > > uhub4: single transaction translator
> > > > > sd0: GPT GUID: aa426d16-0d0e-40a1-90e7-9a75f7b5c75f
> > > > > dk0 at sd0: "67b20926-002a-424f-a169-2c7efc563bb9", 614401 blocks at
> > > > > 4097, type: msdos
> > > > > dk1 at sd0: "5d7e40e5-4454-4a98-a81e-c5223d78f161", 421527550 blocks
> > > > > at 618498, type: ext2fs
> > > > > dk2 at sd0: "ed7d719c-6ef4-451f-9732-2e4dd981273b", 35925033 blocks at
> > > > > 464178417, type: <unknown>
> > > > > dk3 at sd0: "731c9349-02e0-471d-93db-99f63c06afe8", 42032369 blocks at
> > > > > 422146048, type: ffs
> > > > > uhub4: 4 ports with 4 removable, self powered
> > > > > ubt0 at uhub3 port 1
> > > > > ubt0: vendor 0a12 (0xa12) Bluetooth2.1+EDR CLASS1 (0x01), rev 2.00/52.76, addr 1
> > > > > wd0 at atabus0 drive 0
> > > > > wd0: <KINGSTON SKC400S37512G>
> > > > > wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> > > > > wd0: 476 GB, 992277 cyl, 16 head, 63 sec, 512 bytes/sect x 1000215216 sectors
> > > > > wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
> > > > > (Ultra/133), WRITE DMA FUA, NCQ (32 tags)
> > > > > wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6
> > > > > (Ultra/133) (using DMA), NCQ (31 tags)
> > > > > uhidev0 at uhub4 port 2 configuration 1 interface 0
> > > > > uhidev0: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2029), rev
> > > > > 2.00/1.09, addr 3, iclass 3/1
> > > > > ukbd0 at uhidev0: 8 Variable keys, 6 Array codes
> > > > > wskbd0 at ukbd0: console keyboard
> > > > > uhidev1 at uhub4 port 2 configuration 1 interface 1
> > > > > uhidev1: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2029), rev
> > > > > 2.00/1.09, addr 3, iclass 3/0
> > > > > uhid0 at uhidev1: input=4, output=0, feature=0
> > > > > uhidev2 at uhub4 port 3 configuration 1 interface 0
> > > > > uhidev2: Kensington (0x47d) Kensington USB/PS2 Orbit (0x1022), rev
> > > > > 1.10/4.00, addr 4, iclass 3/1
> > > > > ums0 at uhidev2: 2 buttons
> > > > > wsmouse0 at ums0 mux 0
> > > > > uhidev3 at uhub1 port 11 configuration 1 interface 0
> > > > > uhidev3: CASUE (0x2a7a) CASUE USB Keyboard (0x9a18), rev 1.10/0.01,
> > > > > addr 5, iclass 3/1
> > > > > ukbd1 at uhidev3: 8 Variable keys, 6 Array codes
> > > > > wskbd1 at ukbd1 mux 1
> > > > > uhidev4 at uhub1 port 11 configuration 1 interface 1
> > > > > uhidev4: CASUE (0x2a7a) CASUE USB Keyboard (0x9a18), rev 1.10/0.01,
> > > > > addr 5, iclass 3/0
> > > > > uhidev4: 2 report ids
> > > > > uhid1 at uhidev4 reportid 1: input=1, output=0, feature=0
> > > > > uhid2 at uhidev4 reportid 2: input=3, output=0, feature=0
> > > > > uhidev5 at uhub1 port 12 configuration 1 interface 0
> > > > > uhidev5: SteelSeries (0x1038) SteelSeries Rival 110 Gaming Mouse
> > > > > (0x1729), rev 1.10/0.34, addr 6, iclass 3/0
> > > > > uhid3 at uhidev5: input=32, output=32, feature=0
> > > > > uhidev6 at uhub1 port 12 configuration 1 interface 1
> > > > > uhidev6: SteelSeries (0x1038) SteelSeries Rival 110 Gaming Mouse
> > > > > (0x1729), rev 1.10/0.34, addr 6, iclass 3/1
> > > > > ums1 at uhidev6: 6 buttons and Z dir
> > > > > wsmouse1 at ums1 mux 0
> > > > > WARNING: 6 errors while detecting hardware; check system log.
> > > > > boot device: wd0
> > > > > root on wd0a dumps on wd0b
> > > > > /: replaying log to memory
> > > > > root file system type: ffs
> > > > > kern.module.path=/stand/amd64/9.0/modules
> > > > > kern info: [drm] initializing kernel modesetting (PITCAIRN
> > > > > 0x1002:0x6811 0x1458:0x2015).
> > > > > kern info: [drm] register mmio base: 0xfcf00000
> > > > > kern info: [drm] register mmio size: 262144
> > > > > kern info: ATOM BIOS: GV
> > > > > radeon0: info: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
> > > > > radeon0: info: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF
> > > > > kern info: [drm] Detected VRAM RAM=800M, BAR=256M
> > > > > kern info: [drm] RAM width 256bits DDR
> > > > > Zone  kernel: Available graphics memory: 11320654 kiB
> > > > > Zone   dma32: Available graphics memory: 2097152 kiB
> > > > > kern info: [drm] radeon: 2048M of VRAM memory ready
> > > > > kern info: [drm] radeon: 2048M of GTT memory ready.
> > > > > kern info: [drm] Loading pitcairn Microcode
> > > > > kern info: [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes
> > > > > kern info: [drm] Internal thermal controller with fan control
> > > > > kern info: [drm] radeon: dpm initialized
> > > > > kern info: [drm] GART: num cpu pages 524288, num gpu pages 524288
> > > > > kern info: [drm] PCIE GART of 2048M enabled (table at 0x0000000000277000).
> > > > > radeon0: info: WB enabled
> > > > > radeon0: info: fence driver on ring 0 use gpu addr 0x0000000080000c00
> > > > > and cpu addr 0x0xffffdec290e6cc00
> > > > > radeon0: info: fence driver on ring 1 use gpu addr 0x0000000080000c04
> > > > > and cpu addr 0x0xffffdec290e6cc04
> > > > > radeon0: info: fence driver on ring 2 use gpu addr 0x0000000080000c08
> > > > > and cpu addr 0x0xffffdec290e6cc08
> > > > > radeon0: info: fence driver on ring 3 use gpu addr 0x0000000080000c0c
> > > > > and cpu addr 0x0xffffdec290e6cc0c
> > > > > radeon0: info: fence driver on ring 4 use gpu addr 0x0000000080000c10
> > > > > and cpu addr 0x0xffffdec290e6cc10
> > > > > radeon0: info: fence driver on ring 5 use gpu addr 0x0000000000075a18
> > > > > and cpu addr 0x0xffffac025aeb5a18
> > > > > radeon0: autoconfiguration error: error: VCE init error (-22).
> > > > > kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> > > > > kern info: [drm] Driver supports precise vblank timestamp query.
> > > > > radeon0: info: radeon: MSI limited to 32-bit
> > > > > radeon0: interrupting at ioapic1 pin 30 (radeon0)
> > > > > kern info: [drm] radeon: irq initialized.
> > > > > kern info: [drm] ring test on 0 succeeded in 2 usecs
> > > > > kern info: [drm] ring test on 1 succeeded in 1 usecs
> > > > > kern info: [drm] ring test on 2 succeeded in 1 usecs
> > > > > kern info: [drm] ring test on 3 succeeded in 6 usecs
> > > > > kern info: [drm] ring test on 4 succeeded in 5 usecs
> > > > > kern info: [drm] ring test on 5 succeeded in 2 usecs
> > > > > kern info: [drm] UVD initialized successfully.
> > > > > kern info: [drm] ib test on ring 0 succeeded in 0 usecs
> > > > > kern info: [drm] ib test on ring 1 succeeded in 0 usecs
> > > > > kern info: [drm] ib test on ring 2 succeeded in 0 usecs
> > > > > kern info: [drm] ib test on ring 3 succeeded in 0 usecs
> > > > > kern info: [drm] ib test on ring 4 succeeded in 0 usecs
> > > > > kern info: [drm] ib test on ring 5 succeeded
> > > > > kern info: [drm] Radeon Display Connectors
> > > > > kern info: [drm] Connector 0:
> > > > > kern info: [drm]   DP-1
> > > > > kern info: [drm]   HPD4
> > > > > kern info: [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
> > > > > kern info: [drm]   Encoders:
> > > > > kern info: [drm]     DFP1: INTERNAL_UNIPHY2
> > > > > kern info: [drm] Connector 1:
> > > > > kern info: [drm]   HDMI-A-1
> > > > > kern info: [drm]   HPD5
> > > > > kern info: [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
> > > > > kern info: [drm]   Encoders:
> > > > > kern info: [drm]     DFP2: INTERNAL_UNIPHY2
> > > > > kern info: [drm] Connector 2:
> > > > > kern info: [drm]   DVI-I-1
> > > > > kern info: [drm]   HPD6
> > > > > kern info: [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c
> > > > > kern info: [drm]   Encoders:
> > > > > kern info: [drm]     DFP3: INTERNAL_UNIPHY
> > > > > kern info: [drm]     CRT1: INTERNAL_KLDSCP_DAC1
> > > > > kern info: [drm] Connector 3:
> > > > > kern info: [drm]   DVI-D-1
> > > > > kern info: [drm]   HPD1
> > > > > kern info: [drm]   DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c
> > > > > kern info: [drm]   Encoders:
> > > > > kern info: [drm]     DFP4: INTERNAL_UNIPHY1
> > > > > radeondrmkmsfb0 at radeon0
> > > > > radeondrmkmsfb0: framebuffer at 0xffffac025b8fc000, size 1920x1080,
> > > > > depth 32, stride 7680
> > > > > wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100
> > > > > emulation), using wskbd0
> > > > > wsmux1: connecting to wsdisplay0
> > > > > wskbd1: connecting to wsdisplay0
> > > > > /: replaying log to disk
> > > > > /usr: replaying log to disk
> > > > > wsdisplay0: screen 1 added (default, vt100 emulation)
> > > > > wsdisplay0: screen 2 added (default, vt100 emulation)
> > > > > wsdisplay0: screen 3 added (default, vt100 emulation)
> > > > > wsdisplay0: screen 4 added (default, vt100 emulation)
> > > > > /home: replaying log to disk
> > > > >
> > > > > On Sat, Oct 5, 2019 at 5:51 AM Jonathan A. Kollasch
> > > > > <jakllsch%kollasch.net@localhost> wrote:
> > > > > >
> > > > > > On Sat, Oct 05, 2019 at 12:02:38AM +0300, Andrius V wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > Recently (around a week ago) I faced an issue with my mechanical
> > > > > > > keyboard (Fnatic Gear Rush) that it doesn't react to any keypress
> > > > > > > anymore (in general I can't use it as a keyboard). Weirdly enough this
> > > > > > > issue is present in any NetBSD setup (tested netbsd-9, current and
> > > > > > > even older 8.1 setup which definitely worked before). It powers up, it
> > > > > > > is visible in dmesg, its USB hub works (mouse connected to it works
> > > > > > > without issues), Num/Caps Lock LED light reacts, if I click it on
> > > > > > > other attached keyboard, but pressing any button has no effect. Other
> > > > > > > non-mechanical "cheap" USB keyboards work without issues. Initially, I
> > > > > > > though it may be related to my recent UEFI update but it fails to work
> > > > > > > on other systems too. The original system is Ryzen 5 1600 based on
> > > > > > > Biostar x370gt5 motherboard. The keyboard itself is definitely fine
> > > > > > > and perfectly works on any other operating system I have (Manjaro,
> > > > > > > Windows 10), including UEFI/BIOS interface. Any ideas what may be
> > > > > > > causing this weird behavior? Thank you.
> > > > > > >
> > > > > > > from dmesg:
> > > > > > > uhidev0: Fnatic Gear (0x195d) RUSH Mechanical Keyboard (0x2029), rev
> > > > > > > 2.00/1.09, addr 8, iclass 3/1
> > > > > > >
> > > > > >
> > > > > > What version of NetBSD?
> > > > > >
> > > > > > More dmesg context would be useful too.
> > > > > >
> > > > > >         Jonathan Kollasch
Follow-Ups:
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
References:
- Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Jonathan A. Kollasch
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Jonathan A. Kollasch
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
- Re: Fnatic RUSH mechanical keyboard ignores keypress
  - From: Andrius V
Prev by Date: Re: adding support for a possibly unsupported M.2 harddrive?
Next by Date: Request for testing: i915 + suspend, or i915 heavy use
Previous by Thread: Re: Fnatic RUSH mechanical keyboard ignores keypress
Next by Thread: Re: Fnatic RUSH mechanical keyboard ignores keypress
Indexes:
Home | Main Index | Thread Index | Old Index