Re: Keyboard unavailable at boot

["Rocky Hotas" <rockyhotas%post.com@localhost>]

Hello Dan, hi all, 
here follow some updates as regards the USB keyboard.

> Sent: Thursday, November 23, 2017 at 3:01 AM
> From: "Dan LaBell" <dan4l-nospam%verizon.net@localhost>
> To: "Rocky Hotas" <rockyhotas%post.com@localhost>
> Subject: Re: Keyboard unavailable at boot
>
> Is it OK if you cycle power, and don't use Linux?

Yes: if NetBSD was the last OS before shutting down or resetting, it's
ok.

>. And your reset button
> works at boot prompt?

Yes.

> If so, I'm guessing Linux messed with some  
> vectors,
> and didn't put them back, is is possible to make linux do a "harder'  
> reboot?

I don't know Linux enough to know how to make a harder reboot.
Unfortunately, the `reboot' and `shutdown' manpages don't mention
anything useful (only display options, nothing useful here).
Moreover, when the keyboard is not detected, no USB port works: I
tested all of them with a USB key. All the USB ports are off.

> And you save dmesg output  for working, and non-working, and then  
> diff them?

This is the output of the diff:

233c233
< timecounter: Timecounter "TSC" frequency 3398219560 Hz quality 3000
---
> timecounter: Timecounter "TSC" frequency 3398197560 Hz quality 3000
264a265,278
> uhidev0 at uhub3 port 7 configuration 1 interface 0
> uhidev0: Logitech USB Keyboard, rev 1.10/64.00, addr 3, iclass 3/1
> ukbd0 at uhidev0
> wskbd0 at ukbd0: console keyboard, using wsdisplay0
> uhidev1 at uhub3 port 7 configuration 1 interface 1
> uhidev1: Logitech USB Keyboard, rev 1.10/64.00, addr 3, iclass 3/0
> uhidev1: 3 report ids
> uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
> uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
> uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
> uhidev2 at uhub3 port 8 configuration 1 interface 0
> uhidev2: PixArt Microsoft USB Optical Mouse, rev 1.10/1.00, addr 4, iclass 3/1
> ums0 at uhidev2: 3 buttons and Z dir
> wsmouse0 at ums0 mux 0

Basically, there are different frequency in the timecounter and the
presence of keyboard and mouse.
Anyway: replacing the kernel only with NetBSD 7.1_STABLE (201711220540Z)
or with 8.0_BETA (201711211410Z) this issue disappears.
Thank you for your help,

Rocky