I have pushed a commit to master and release which disables the FADT probe (it can be turned on again with a tunable). I just changed the global from 1 to 0. Please re-test with the latest DragonFly_RELEASE_5_4 sources and tell us if that fixed the issue.
-Matt On Sun, Dec 9, 2018 at 12:12 PM Matthew Dillon <[email protected]> wrote: > We have a second person with the same problem. Michael suggests trying to > backout commit 131acb0380e93664f106117ebf8ba322a3d1b7c4 > > Basically, start with a 5.4 base (not 5.2), use a usb keyboard temporarily. > > cd /usr > make src-create > > Make sure you are on the correct release: > > cd /usr/src > git checkout DragonFly_RELEASE_5_4 > > Then try reverting the specified commit and rebuild the kernel, install > it, reboot, and see if the keyboard works. > > cd /usr/src > git revert 131acb0380e93664f106117ebf8ba322a3d1b7c4 > (assuming it works) > make -j 8 nativekernel > make installkernel > sync > reboot > > -Matt > > On Sun, Dec 9, 2018 at 11:20 AM Matthew Dillon <[email protected]> > wrote: > >> You are the second person to report this. Check a few things. The >> laptop keyboard is clearly attaching via atkbd in both dmesg's. The >> question is why isn't it registering keystrokes. So lets check whether you >> are getting interrupts on irq 1. You can observe this with: >> >> vmstat -i -v >> >> The count should normally be non-zero, and when you hit a key on the >> laptop keyboard, the count should increase by 2 each time. >> >> -Matt >> >
