Messages

Hello,

I had this same problem recently and solved it by replacing the mSATA SSD.

From the look of your SSD brand and model, I suspect you have a QOTOM device? Hoodisk SSD SBFM61.3 is a common SSD in these devices. The SSD is dying, I suggest backing up your config, replacing the SSD, and restoring the config.

@Stephen maybe you want to upgrade to 22.1.1 first and try again.

This has fixed my issue with not being able to input my username in ddclient. Working now. Thanks Franco.

Been trying to test the new os-ddclient. I use Google as my dynamic DNS. When I went to use the new client I could not setup using my provided Username and Password. For some reason the new plugin says the Username google provided me had "invalid characters" and prevent me from saving the settings. Works fine with the old plugin and I have reverted.

Is there some kind of bug with character limitation for username in the new os-ddclient? I'm using the valid username provided by Google for my DNS. The Username that Google provides for their DNS is just 16 alpha numeric characters.

Hi

First things first: which hardware is this?

And does it have a VGA port?

It's a Qotom q500g6.

It has a HDMI and Serial port.

So for the boot config to set -D, I have to configure "Primary Console: VGA" and "Secondary Console: Serial" and now it works for me (i.e. the /boot.config is set with -D flag).

If I try to do "Primary Console: Serial" it will fail for me. Not sure why.

If you suspect it was the above change, I'd do a quick test and change the /boot.config to the way it was before (-D rather than -h).

Wow that worked for me. I had to change /boot.config back to -D for some reason and now my serial console is working again... -h does not work for me.

Found the change:

https://github.com/opnsense/core/commit/84a241c30a093fd30334843819946b2dd2832340

Thanks eponymous it was around this patch when my serial console died. Wonder if we should log a github issue.

I have tried to set primary console to serial and secondary console to serial and still have same problem.

I have serial console set as primary, and secondary console set to none.

Looks like 0x3f8 is my correct comconsole_port, when I try 0x2f8 I get no output instead of some output with 0x3f8.

So far I have tried the following tunable but my console still stops at the same point.

Code Select Expand

hint.uart.0.flags=0x0
hint.uart.1.flags=0x10
comconsole_speed=115200
comconsole_port=0x3F8
console=comconsole

Hi Waxhead, another solution, which is outside the system, is to turn on notifications when new posts are put into the "Announcement" section of the forums. New firmware are posted in that forum section, along with other important news.

Thanks eponymous. I'll give it a try and report back.

I was able to capture the serial console output at boot. After this point the console no longer responds.

From SSH "desgm | grep uart" responds with the following:

Code Select Expand


uart0: <16950 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (115200,n,8,1)
uart1: <16950 or compatible> port 0x2f8-0x2ff irq 3 on acpi0


Below are my settings for OPNsense System>Settings>Administration>Console

I have serial console set as my primary console in settings and it's no longer working.

I've checked the device, cable, and serial port are all fine. When I restart I can see output from the serial port (OPNsense splashscreen and and device loading lines on boot up) but after OPNsense loads the serial console stops responding. No console menu for login and no response to keyboard commands.

The serial console used to work fine, but some recent update changed that. I see in the change log some mention of "system: better logic for serial console options -h and -D" is there something I need set to restore the serial console functionality?