T14 After Warm Reboot Makes BIOS Beep, keyboard garbled at Boot Menu

sgharms

sgharms

OK super strange.

Life is good. I hit
Code: 
# reboot
.

System goes down. System comes up and makes a LOUD AS HELL WAKE UP THE BABY beep. I then get the beastie menu. But enter (c'mon I'm ready!) doesn't respond. Any number menu to change boot params or select a boot environment fails. I type frantically, some keys enter things like ~45 or some such. But basically the keyboard is non responsive. Reboot the machine using the power button, NO "wake-the-dead" beep and keyboard is fine. I didn't see anything in dmesg to suggest what's going on. Any ideas? This is a fresh 14.3-RELEASE installed system.

UPDATE:

After a few times of doing this, I noticed on the "bad" startups, there's a _very_ brief message before the boot menu wipes it out. I'm trying to figure out what it says...
 
Reset UEFI, disconnect the disk, boot from a flash drive. If that doesn't help, then disconnect all additional devices (Wi-Fi, Bluetooth,...).
I don't speak English completely. Do you mean "the laptop fell on the floor" or does the word "hit" mean you pressed enter after the reboot command?
 
USerID said:
Reset UEFI, disconnect the disk, boot from a flash drive. If that doesn't help, then disconnect all additional devices (Wi-Fi, Bluetooth,...).
I don't speak English completely. Do you mean "the laptop fell on the floor" or does the word "hit" mean you pressed enter after the reboot command?
Click to expand...
Fair question! I meant “pressed the button” — a very calm, very typical activity. And thanks for being brave enough to reply— I appreciate your bravery.
 
OK while trying to reproduce the error so that I could film it during boot up, I discovered something really interesting.

1. The error that was flashing too fast was a “Keyboard Stuck Key” error and then loud beep.
2. Here’s what’s really interesting. If I issue `reboot` from within Wayland — no problems, in numerous tests. I was so boggled by this result i had to do it several times. But if I do `reboot` from the vt, that’s where the (seemingly false) claim about stuck keyboard happens.

After we complete boot up (keyboard unresponsive during boot menu) here’s what a few seconds of tying to type and letting the console continue its spew looks like (attachment 2).
 

Attachments

  • IMG_0181.jpg
    IMG_0181.jpg
    91.9 KB · Views: 201
  • Borked Keyboad.png
    Borked Keyboad.png
    1.5 MB · Views: 176
eseipi said:
Sorry, I cannot help you with the issue, but I think it should be mentioned here that it's important to understand the difference between shutdown(8) and reboot(8) on FreeBSD if you want to use the latter. This difference has been discussed many times, but a quick search through these forums led me to this Thread 64197 as an example (tl;dr: use shutdown -r now when in doubt).
Click to expand...
Good reminders, thanks. It's been a while since I was on Solaris regularly (and even then the goal was generally not to reboot :)).
 
I suggest you check your keyboard. Seems to me could be broken. To me symptoms look like one key is locked, always pressed (J or H, or whatelse is on the same wire.) Another cause for a short circuit could also be the case.
If so there is no chance with an external keyboard. First thing you may try is feelingly touch all keys, see if you can find and loosen the blocked one.
If that's no help, you could remove the keyboard. I suppose T14 is kind of a laptop, so the kb will be most likely attached with a ribbon cable to the board. You need to be a bit careful while doing this, but it's doable. You'll find disassembling instructions (pictures/videos) for almost every piece of hardware. Follow those.
When the KB is removed, attach an external to it, as USerID suggested, and see if your system boots correctly again.
If so, see if you can repair your kb (sometimes cleaning is enough), or you need to look for an replacment.
 
Maturin That's certainly the approach I was adopting, but (and the weirdest thing is) if I issue shutdown -r now from within Wayland or X at a pseudoterminal, there is no beep! It's almost like there's some sort of hangover from the previous session. Also: I just installed the most recent version of the BIOS.
 
You must log in or register to reply here.
Back
Top