Serial console not interactive anymore after upgrade to 25.1

Started by kingfisher77, February 02, 2025, 10:52:11 AM

Previous topic - Next topic
Quote from: estebang on February 07, 2025, 03:00:06 PMAlso seeing this on Protectli V1410. Will try the tunables, thanks

I wouldn't think you'd see this here...that uses the FT232RQ-QFN32 UART.

I'm running the old FW2B and have no serial console issues.

Ok, interesting. I'll check if makes any difference over the weekend if I can get to the site

Just heard from Protectli support that they have been able to reproduce the issue and it's a different one all together, though similar effect. Essentially related to the coreboot bios. The workaround they suggested is to flash back to AMI bios for the time being

Quote from: estebang on February 07, 2025, 07:09:43 PMJust heard from Protectli support that they have been able to reproduce the issue and it's a different one all together, though similar effect. Essentially related to the coreboot bios. The workaround they suggested is to flash back to AMI bios for the time being

I have the V1410 also.  Thanks for posting- I'll follow for updates.  Hopefully they issue a coreboot update soon because that's one of the main selling points of these units.

Prior to seeing this thread I tried to upgrade to 25.1 from a USB flashed with Rufus, using the OPNsense 'serial' image.  I was not able to get the USB drive listed in the boot menu at all, whereas I did not have that issue with 24.7.  I guess there must also be something new with 25.1 boot images that coreboot doesn't like (?)  Did you have to do anything special to boot the installer?

Edit: I was finally able to get the USB drive seen in the boot menu of coreboot.  Don't know what the issue was, but it worked after several attempts.  I do also now get stuck on the "lo=: link state changed to UP" line as the OP, so indeed this affects the N5105 Vaults as well.

I successfully upgraded my ancient APU2D4 (with serial port console) on my home network.

THANK YOU for the fix provided in this discussion thread! Otherwise, the upgrade would have caused some panic for me when the console would have stopped working.

In Tunables, I simply added hint.uart.0.at = isa (and hint.uart.1.at = isa). This added the settings to /boot/loader.conf and superceded the values in /boot/device.hints. Just for completeness, I updated the values in /boot/device.hints after the upgrade.

The upgrade from 24.7.12_4 to 25.1 was smooth. THANK YOU, Franco!

On a side note, I will start investigating new hardware for my firewall. That's a discussion for the Hardware and Performance forum.

Good evening,
I have the same problem with the "Protectl FW6Bi"....
If I enter the commands hint.uart.0.at="isa" and hint.uart.1.at="isa" in Tunables, I see the complete start but then I have no access to the selection menu with the keyboard.
I can neither get into the "boot menu" with "F11" nor into the BIOS with "delet" when starting. Does anyone have any other ideas?
Many thanks

By chance, did you verify that hint.uart.0.at="isa" (& hint.uart.1.at="isa") were in /boot/device.hints before upgrade? To verify that "isa" is the correct value?
Also, was hint.uart.0.at="isa" (& hint.uart.1.at="isa") in /boot/loader.conf after you added the values in Tunables and saved?

If the upgrade worked correctly, there is the possibility that the web interface is working. Did you try to connect to web interface?
For me, watching the console simply confirmed that the upgrade worked.

IF the web interface is working, you could possibly go to System:Settings:Administration and enable Secure Shell.
Login with Secure Shell and you should be able to manually edit/boot/device.hints and check that hint.uart.0.at="isa" is in /boot/loader.conf

Good Luck!