26.7.1_1 -> 26.7.2 Boot loop

Started by axsdenied, August 12, 2026, 05:01:38 PM

Previous topic - Next topic
I just updated an intel nic only device w/o any problem too. And yes: services widget looks nice now :D

Quote from: franco on August 12, 2026, 07:57:21 PMThis is only true for the main mirror at the moment: if you want to force a reinstall use this:

# opnsense-update -fbkr 26.7.2

The realtek plugin should work again afterwards.  But still curious there was a second panic unrelated to realtek...


Cheers,
Franco

hi,

i did that and enabled the realtek plugin. box is booting but no ip adresses are given to the 2 realtek nics. even after adding new ip adresses via shell, they still remain empty and box is unreachable. any hints?

regards
ralf

August 12, 2026, 09:20:10 PM #17 Last Edit: August 12, 2026, 09:35:35 PM by oldRaven
I too had the boot loop and was able to disable an onboard Realtek (it was enabled but not in use).  I had removed the Realtek plugin before this attempt and still had the boot loop.  I've been using a dual Intel NIC as my primary card.  This did allow a successful boot; however, the interface names had changed and the IP changed.  A quick reconfiguration by adding the IP I had originally and deleting/reconfiguring the DHCP which had the wrong interface name got everything going.  Reviewing everything now to see if all else is OK...
Edit - Using Intel(R) PRO/1000 82576 Dual NIC

August 12, 2026, 09:34:46 PM #18 Last Edit: August 12, 2026, 09:40:35 PM by lmoore
There is no spin lock message in @axsdenied panic - probably because 'ifconfig' wasn't trying to bring up the interface.

Quote from: franco on August 12, 2026, 07:57:21 PMopnsense-update -fbkr 26.7.2

Performed this update - it took quite a while to download.

Rebooted and then installed the os-realtek plugin and then rebooted again.

There is no kernel panic and nor does the Realtek plugin driver work.

Some observations with the Realtek plugin:

- During initialisation the Realtek interface (re0) link state change is not reported

Initializing..........done.
igb0: link state changed to UP
igb1: link state changed to UP
igb2: link state changed to UP
igb3: link state changed to UP
em0: link state changed to UP
Starting device manager...acpi_wmi0: <ACPI-WMI mapping> on acpi0

- I don't know what [egress only] really means.

setup igb3
setup igb1
setup re0 [egress only]
Network UPS Tools upsdrvctl - UPS driver controller 2.8.5 release

[Update] The Realtek plugin driver doesn't support 'Promiscuous' mode;
tcpdump -ni re0
tcpdump: WARNING: re0: That device doesn't support promiscuous mode
(BIOCPROMISC: Unknown error: 166225792)


For now, the os-realtek plugin is unusable.

Does it work when doing the following?

# opnsense-revert -r 26.7.1 realtek-re-kmod


Cheers,
Franco

Quote from: franco on August 12, 2026, 09:42:25 PM# opnsense-revert -r 26.7.1 realtek-re-kmod

It appears for this to work the Realtek driver needs to already be installed. This is the NIC which connects me to the Internet, which means I won't have connectivity to the internet to revert the driver.

Can I perform an off-line installation of the driver?


% sudo opnsense-revert -r 26.7.1 realtek-re-kmod
Package 'realtek-re-kmod' is not installed

I can't establish an Internet connection using the plugin. The command above was issued after removing the plugin and establishing a connection to the Internet using the FreeBSD version of the Realtek driver.


Quote from: franco on August 12, 2026, 09:42:25 PMDoes it work when doing the following?

# opnsense-revert -r 26.7.1 realtek-re-kmod


Thanks Franco.

I've managed to revert the driver and I'm back up and running.

Just one other observation when I power off my system, I am getting this EFI related message on the serial console.

EFI RT fault general protection fault


Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0x1
stack pointer           = 0:0xfffffe00d34febc0
frame pointer           = 0:0xfffffe00d34fec30
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 16656 (halt)
rdi: 0000000000000000 rsi: 0000000000000000 rdx: 000000000000000f
rcx: 0000000000000000  r8: 0000000000000000  r9: 0000000000000000
rax: 00000000cbd4bb13 rbx: 0000000000000000 rbp: fffffe00d34fec30
r10: 0000000000000000 r11: 000000005f42535f r12: 0000000000000000
r13: 0000000000000002 r14: 0000000000004008 r15: fffff800011114a8
trap number             = 9
acpi0: Powering system off

Cheers,
Larry.