OPNsense Forum
English Forums => 24.1 Production Series => Topic started by: Layer8 on February 25, 2024, 05:23:00 pm
-
Hi,
have the exact same issue with 24.1.2 like described here: https://forum.opnsense.org/index.php?topic=23412.0
Its an APU 1d4 (AMD G-T40E Processorm 4GB Ram and a 32GB SSD)
In my case, I reinstalled with the 24.1 iso because I switched to ZFS based installation some weeks ago. I uploaded the config backup and everything worked fine first, including the console menu.
Today, I noticed that the console menu is not displayed anymore. I have no clue whats the reason for this issue.
How to fix this?
No other issues detected at the moment. Restart does not help.
-
Try this as root to put the shell back:
chsh -s /usr/local/sbin/opnsense-shell root
-
I cant see the menu over the rs232-console and there is no prompt at all. So I cant type anything over rs232. Last output/lines are the SHA256keys. Below this keys, I can see a blinking cursor, but I cant enter anything.
Console output over VGA is not available, because the APU 1D4 does not have a video output.
When I login over SSH, I can see the menu. I tried your command over SSH but this did not solve the problem.
-
Com port changed, driver issue or serial settings from the machine you're connecting from
-
I dont think so.
I can see the entire boot process over the rs232 console connection in Terra Term. I can see the BIOS intialisation, the opnsense boot loader, how configs get loaded.
The only thing whats missing is the bold part:
HTTPS: SHA256 37 BF 97 F4 FD 3B D9 5D 88 03 E2 9A 15 E5 26 B9
SSH: SHA256 key (ECDSA)
SSH: SHA256 key (ED25519)
SSH: SHA256 key (RSA)
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option:
But the curser is blinking a line under "SSH: SHA256 key (RSA)"
A blinking curser means, that the rs232 connection is alive.
-
Is System > Settings > Administration ... all the Console settings really configured as it should be?
Because on a system without any VGA and serial console only the FreeBSD kernel will default to serial output. But once the booted OS and the services take over you still need an explicit configuration to activate e.g. login or in the case of OPNsense the menu on the serial console ...
-
System - Settings - Administration - Console: do NOT check the "USB-based serial" checkbox.
-
Is System > Settings > Administration ... all the Console settings really configured as it should be?
Because on a system without any VGA and serial console only the FreeBSD kernel will default to serial output. But once the booted OS and the services take over you still need an explicit configuration to activate e.g. login or in the case of OPNsense the menu on the serial console ...
I thought so, because it looks like default (which is working on all other installations):
Console driver checked
Primary Console Serial Console
Secondary Console None
Serial Speed 115200
USB-based serial checked
Console menu checked
System - Settings - Administration - Console: do NOT check the "USB-based serial" checkbox.
Disabling the USB-based serial solved the issue. Thanks!
I am just wondering why it worked after I reinstalled opnsense and stopped working now.
Could the issue be, because I am using an Android mobile phone over USB for WAN connectivity?
-
Could the issue be, because I am using an Android mobile phone over USB for WAN connectivity?
Definitely. Your OPNsense was displaying the console to the phone.
-
Makes sense. Thanks.
Just a little improvement... Could it be possible to activate the console permanently over rs232 and usb in default settings?
-
There can be only one serial console so the system needs to be set to either traditional COM port or USB serial device.