Messages

I have another system that refuses to upgrade to 22.7, as per @Franco request I am ELI5 (hopefully) solution :

Currently running 22.1.x with FreeBSD 13.1-RELEASE, as per previous instructions by @Franco to allow 13.1-RELEASE over 22.1.x installs as per https://forum.opnsense.org/index.php?topic=28505.0 and locked base and kernel packages in System:Firmware:Packages and clicked the little unlocked icon (to lock) at the end of base and kernel package lines (on the righthand side), as such preventing downgrades to 13.0-release while still allowing to upgrade 22.1.x all the way t 22.1.10_4 without overwriting 13.1-RELEASE.

Once at 22.1.10_4 and 13.1-RELEASE (locked), there is no way to upgrade to 22.7, as system insist that is up to date, except for usual base and kernel 13.0-RELEASE package downgrade availability (which of course are locked, therefore won't downgrade regardless).

The only way for system to detect 22.7 availability is to unlock base and kernel packages in Sytem:Firmware:Packages and hit the lock icon (to unlock) at the end of base and kernel package lines (on the righthand side) and downgrade to 13.0-RELEASE.

Once base and kernel are unlocked and downgraded to 13.0-RELEASE, the system proceeds to detect 22.7 upgrade and allows to proceed to 22.7.

Hope this helps.

@Franco
The locked 13.1 base & kernel prevented the detection of availability of 22.7 from 22.1.10_4, that's why I made my comments about unlocking manually.

If 22.7 is supposed to unlock and upgrade automatically, that didn't happen for me, I was forced to unlock and downgrade to 13.0 in order for my install to detect 22.7 availability.

I was scratching my head prior and even changing download mirror, thinking mirroring had not down streamed completely at that point.

I had FreeBSD 13.1 installed on top of 22.1 ever since it was allowed and had base and kernel packages locked in order to avoid being downgraded to 13.0 upon each 22.1.x update.

That actually prevented detecting the 22.7 upgrade, it kept telling me up to date (except for available 13.0 downgrade) I actually had to unlock base and kernel, update/downgrade to 13.0/22.1.10_4

And then hit Check for Updates and finally the 22.7 upgrade showed up...

What do you mean by running, did you perform any usual installation steps ?

If you look under System:Firmware:Plugins and type "rule" without quotes in the search box, you will find several rulesets including os-intrusion-detection-content-snort-vrt which is activated with an Oinkcode.

Once installed, just go to Services: Intrusion Detection: Administration:Rules and paste you Oinkcode then save, then enable selected, then download.

If you solved it, would you be so kind to share your resolution ?

[built-in dual Realtek NICs]

Works fine on Beelink GK55 mini PC, Intel J4125, 8GB RAM (also works fine replacing with 16GB sodimm), 128GB SSD, built-in dual Realtek NICs, purchased brand new on sale for CAD $215 Amazon.ca :

OPNsense 22.1.8_1-amd64
FreeBSD 13.1-RELEASE
OpenSSL 1.1.1o 3 May 2022

- unbound : all blocklists enabled except WindowsSpyBlocker(Update & Extra)
- Suricata IDS/IPS
- Zenarmour/Sensei : Free Edition

Great many thanks to the Developers ensuring latest most secure OS version !

I use vga image, it boots, installs via installer login, goes through the process of installing and never boot properly thereafter.

I am forced to use 21.7 vga image, install and upgrade...

I have same issue, cannot boot 22.X release once installed.  I ended up booting/installing with 21.7.1 release and let system go through several upgrades, 21.7.8, 22.1 then 22.1.7, a little longer than I would like, but it works...
Download 21.7.1 here :
https://pkg.opnsense.org/releases/

The old release is here :
https://pkg.opnsense.org/releases/

Did you try to change the mirror in the Settings ?

Looks like your wan port doesn't have proper access to Internet or is not setup properly.
Try connecting your wan port as DHCP client to a working network with internet access or make sure your wan port uses proper authentication if PPoE or other than DHCP.

I had same issue, fixed with 22.1.3 update

Ordered new Beelink GK55, reinstalled using leftmost USB3 port (the one opposite the power switch on the front faceplate) and problem never occurred, tried reinstall from scratch a couple of time and never re-cooured.

I was using the other USB3 port on the other GK55, either defective port or unit.

Case closed.

Hi,

Installed 21.7 on Beelink GK55, dual Realtek 1Gb, upgraded to 21.7.7, everything is fine using Logitech USB Keyboard K400+.

Upgraded to 21.7.8, final release, still OK

Upgraded to 22.1 and this keeps appearing on boot regardless of Logitech USB dongle is plugged or not, if plugged or later plugging Keyboard still works fine.  Goes through several cycles of USB errors/warnings and eventually stops as if nothing happened and GK55 seems to work fine.

Although non-fatal error/warning, it's quite annoying and a bit unsettling considering never happened with 21.7.x

Has anyone else experienced this and is there a fix.

Boot log:

uhub0: 16 ports with 16 removable, self powered
Root mount waiting for: usbus0
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
Root mount waiting for: usbus0
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
ugen0.2: <Unknown > at usbus0 (disconnected)

End log segment.

Any thought on hoe to fix ?