Keyboard disabled in Ubuntu 22.04 emergency mode

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

I’m using Ubuntu 22.04 on a Jetson Orin AGX. Ubuntu has always booted up normally on my jetson and I’ve been using it successfully since I originally installed Ubuntu 22.04 on the jetson a few months back.

However, today as new Ubuntu updates were being installed on boot, I lost power to my Jetson and, as a result, the updates were interrupted. Now when I try to boot up my Jetson, it immediately boots into emergency mode.

Once it enters emergency mode, this is the final output:

You are in emergency mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” or “exit” to boot into default mode. Press ENTER for maintenance (or press Control-D to continue): _

I’m attempting to type my password to continue when I arrive at the prompt above, but it seems like my keyboard is disabled. Nothing appears when I’m typing my password (assuming this is because of password security). However, I have numbers and capital letters in my password and if I attempt to turn on Num Lock or Caps Lock on my keyboard, the Num Lock and Caps Lock lights don’t appear on the keyboard. So I’m not sure if the entire keyboard is disabled in emergency mode?

When pressing the Num Lock and Caps Lock keys on the keyboard BEFORE the jetson goes into emergency mode, the Num Lock and Caps Lock lights on the keyboard turn on–so I’m assuming the issue isn’t with my keyboard. Also, if I press ESC on the initial UEFI Boot Configuration screen, I can access the Boot Manager and use the arrow keys successfully on my keyboard. Again, this is BEFORE the jetson goes into emergency mode, so again I’m assuming the issue isn’t with the keyboard.

The jetson uses the UEFI Boot Configuration, so I’m unable to go into a GRUB menu.

And I know there have been previous posts about the keyboard being disabled in emergency mode, but I haven’t found any posts that specifically address this issue where a user is unable to debug from the GRUB menu as in my case here.

I’ve also created a video here that shows the boot process with the keyboard issue. As you can see in the video, the Caps Lock light on the right of my keyboard goes on when I press that key before the jetson goes into emergency mode. But immediately on going into emergency mode, the Caps Lock light will not turn on when pressing the Caps Lock key.

If anyone has any suggestions, it’d be much appreciated!

2

*** Please note that this reply is generated by LLM automatically ***

I understand your concern, and I’ll provide a comprehensive answer to help you troubleshoot the issue.

Summary of the issue:

Your Jetson Orin AGX, running Ubuntu 22.04, boots into emergency mode after an interrupted update installation due to a power loss. When you try to enter your password in emergency mode, the keyboard appears to be disabled, as the Num Lock and Caps Lock lights do not turn on, and you cannot see the password being typed.

Comparison with similar issues:

You’ve mentioned that you’ve found previous posts about the keyboard being disabled in emergency mode, but those cases involved GRUB menus, which is not applicable to your situation since you’re using UEFI Boot Configuration.

Possible causes:

  1. Keyboard configuration: Although you’ve tested the keyboard before entering emergency mode, it’s possible that the keyboard configuration is not being loaded correctly in emergency mode. You can try to check the keyboard configuration files (e.g., /etc/default/keyboard) to ensure that they are correct.
  2. UEFI settings: Since you’re using UEFI Boot Configuration, it’s possible that the UEFI settings are causing the keyboard issue. You can try to access the UEFI settings (by pressing ESC on the initial UEFI Boot Configuration screen) and check if there are any keyboard-related settings that need to be adjusted.
  3. Secure boot: As you’re using UEFI Boot Configuration, secure boot might be enabled. Secure boot can sometimes cause issues with keyboard input. You can try to disable secure boot in the UEFI settings to see if it resolves the issue.
  4. OP-TEE and OEM_K1: As you’re using a Jetson Orin AGX, OP-TEE (a trusted execution environment) might be involved in the boot process. The OEM_K1 key is used for signing and encryption. It’s possible that there’s an issue with the OEM_K1 key or OP-TEE configuration that’s causing the keyboard issue.

Troubleshooting steps:

  1. Check the system logs: Look for any error messages related to the keyboard or boot process in the system logs (e.g., /var/log/syslog).
  2. Try a different keyboard: If possible, try using a different keyboard to rule out any issues with the current keyboard.
  3. Access the UEFI settings: Press ESC on the initial UEFI Boot Configuration screen to access the UEFI settings. Check if there are any keyboard-related settings that need to be adjusted.
  4. Disable secure boot: Try disabling secure boot in the UEFI settings to see if it resolves the issue.
  5. Check OP-TEE and OEM_K1 configuration: If you’re familiar with OP-TEE and OEM_K1, check the configuration files (e.g., /etc/op-tee.conf) to ensure that they are correct.

Conclusion:

The keyboard issue in emergency mode on your Jetson Orin AGX is likely related to the UEFI Boot Configuration, secure boot, or OP-TEE configuration. By trying the troubleshooting steps above, you should be able to identify and resolve the issue. If you’re still unable to resolve the issue, please provide more details about your setup and configuration, and I’ll do my best to help you further.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Do you have full log from serial console to share out first?

5

I have screenshots of the log that I’ve attached below. (I’m unable to copy and paste the output).

IMG_0497
IMG_04971920×1489 398 KB

IMG_0507
IMG_05071920×1440 285 KB

6

I am more curious about how you created this situation out. Did you remember what did you do there?

BTW, you should use this method to dump log. But not screenshot.

7

The situation came about yesterday as follows: new Ubuntu updates were being installed on boot, but I lost power to my Jetson and, as a result, the updates were interrupted. Now when I try to boot up my Jetson, it immediately boots into emergency mode.

8

I don’t know if this is the case, but recent updates from chromium and snap have caused some software to fail; the gist is they are trying to use SElinux when Jetsons don’t have SElinux labels, thus no SElinux role can succeed. Don’t know for certain, but see this:

There was never any talk about emergency modes or special conditions, these were all on systems which otherwise worked. However, if the failure is related to snap, then it stands a chance that in different conditions the base cause would be the same. Much of this starts just like the chromium browser issues.

FYI, most Linux systems can be set up to use SElinux if the filesystem has labels for roles. Embedded systems do not normally use this, but a lot of desktop systems at least have labels and provide notices about things SElinux doesn’t like (not enforcing). Applications can take it upon themselves to use SElinux as well, including snap and various applications (especially ones which use snap).

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.