OPNsense Forum
Archive => 19.1 Legacy Series => Topic started by: opnsenseuser on January 21, 2019, 04:16:02 pm
-
console:
opnsense-update show:
Nothing to do.
The following package files will be deleted:
/var/cache/pkg/opnsense-devel-19.1.r_34-9b47390c38.txz
/var/cache/pkg/opnsense-devel-19.1.r_34.txz
The cleanup will free 4 MiB
Deleting files: 100%
All done
prod gui update shows:
base 19.1.b 18.7.10
kernel 19.1.b 18.7.10 upgrade
dev gui update shows:
e2fsprogs-libuuid N/A 1.44.5 new
opnsense-devel N/A 19.1.r_34 new
syslog-ng N/A 3.19.1 new
but no rc1?
did i forget something? :-(
thx
-
While images are released and can be installed updates go through the last hoops of verification before being generally available. We do not want anyone to upgrade into something that hasn't been vetted...
30 minutes tops.
Cheers,
Franco
-
I was just about to ask the same question - the suspense is killing me :-)
-
It's up and running now. Have fun.
Make sure that either console option 12 asks you to type "19.1.r1" or the GUI wants to unlock it.... if now you're on 18.7.10, not the development branch (firmware settings).
Cheers,
Franco
-
so issued update from console using option 12
typed 19.1.r1 when asked
But GUI is still showing
OPNsense 19.1.r_33-amd64
FreeBSD 11.2-RELEASE-p7-HBSD
LibreSSL 2.7.5
What did I miss ?
-
That's correct. If you want you can switch to "production" which is the "real" 19.1.r1.
Cheers,
Franco
-
GUI says I am on production
Should I use the console to switch from dev to prod - looks like I'm stuck
-
Hmm, no, r_33 and 11.2-RELEASE-p7-HBSD both belong to 19.1. Check for updates, take the blue upgrade... should take you back.
# opnsense-version -n
Should currently show "opnsense-devel".
Afterwards it should show "opnsense".
-
Clean install and import gives me 19.1.r1
Thanks Franco, appears to be working nicely on my dev unit.
-
Hmm, no, r_33 and 11.2-RELEASE-p7-HBSD both belong to 19.1. Check for updates, take the blue upgrade... should take you back.
# opnsense-version -n
Should currently show "opnsense-devel".
Afterwards it should show "opnsense".
Sorry Franco. This isn’t working for me.
-
> Sorry Franco. This isn’t working for me.
It's integral that you are more specific in this regard. Debugging with no hints is impossible.
-
Or even imperative... :P
-
I changed it, sorry ;)
-
Franco the blue button update worked for me thank you
GUI now shows
OPNsense 19.1.r1-amd64
FreeBSD 11.2-RELEASE-p7-HBSD
LibreSSL 2.7.5
A bit like the Matrix take the Blue pill !!!
-
integral?
Whatever...
Let's re-phrase it.
"It's extremely important that you give as much information as you can to help with debugging the issue, I am not psychic". 8)
-
Franco the blue button update worked for me thank you
GUI now shows
OPNsense 19.1.r1-amd64
FreeBSD 11.2-RELEASE-p7-HBSD
LibreSSL 2.7.5
A bit like the Matrix take the Blue pill !!!
What's Viagra got to do with it?
-
> Sorry Franco. This isn’t working for me.
It's integral that you are more specific in this regard. Debugging with no hints is impossible.
ok.
1. had to switch to dev then search for updates.
install updates
2. had to switch back to prod and search for update
install updates
3. system reboots several times by itself.
4. after login firewall was on release r33
5. searched for updates!
install updates
6 now i´m on 19.1 rc1 :-)
-
You guys are killing me ;D
-
but monit widget doesn´t show anything
-
im on 18.7.10 but gui dont show updates
-
but monit widget doesn´t show anything
but status of monit says its working! :o
-
but monit widget doesn´t show anything
but status of monit says its working! :o
even after restart and reinstalling the monit tool and re-adding the widget to the dashboard no more information on the monit widget (see screenshot above)
-
im on 18.7.10 but gui dont show updates
Same here (amd64 PC); I got the 18.7.10_3 update, but it never shows 19.1-RC1. Tried GUI and SSH, different servers, and rebooting. The GUI only responds with, "There are no updates available on the selected mirror." There is no unlock option.
According to @opnsenseuser it appears one must first switch to and install the development branch, then go back to production, for RC1 to show up. Is that the intention?
-
im on 18.7.10 but gui dont show updates
Same here (amd64 PC); I got the 18.7.10_3 update, but it never shows 19.1-RC1. Tried GUI and SSH, different servers, and rebooting. The GUI only responds with, "There are no updates available on the selected mirror." There is no unlock option.
According to @opnsenseuser it appears one must first switch to and install the development branch, then go back to production, for RC1 to show up. Is that the intention?
yes, for me this was the way it works!
-
Monit widget doesn´t show any content anymore
can anyone confirm that?
i made an incident record!
https://github.com/opnsense/core/issues/3142 (https://github.com/opnsense/core/issues/3142)
-
Anyone know if the shci controller timeout will be fixed? After every update I have to go and edit boot file.
Sent from my Pixel 2 XL using Tapatalk
-
> After every update I have to go and edit boot file.
While file are you editing?!
-
> After every update I have to go and edit boot file.
While file are you editing?!
I created /boot/loader.conf.local
However after upgrade it was deleted.
-
We haven't been touching /boot/loader.conf.local in a long time. Since 18.1.x you can add your settings under system: settings: tunables too. Nice thing is it exports to config.xml and automatically populates /boot/loader.conf.
Cheers,
Franco
-
im on 18.7.10 but gui dont show updates
Same here (amd64 PC); I got the 18.7.10_3 update, but it never shows 19.1-RC1. Tried GUI and SSH, different servers, and rebooting. The GUI only responds with, "There are no updates available on the selected mirror." There is no unlock option.
According to @opnsenseuser it appears one must first switch to and install the development branch, then go back to production, for RC1 to show up. Is that the intention?
yes, for me this was the way it works!
@franco Is a Production "Release Type" to RC1 supposed to be possible? I'd like to test the Production upgrade path, but it isn't working, unless one first switches to a Development upgrade. Thanks!
-
We haven't been touching /boot/loader.conf.local in a long time. Since 18.1.x you can add your settings under system: settings: tunables too. Nice thing is it exports to config.xml and automatically populates /boot/loader.conf.
Cheers,
Franco
Ah I didnt know that,
So I can add following as tuneables?
hw.sdhci.enable_msi=0
hint.sdhci_pci.0.disabled=1
hint.sdhci_pci.1.disabled=1
-
Yes, but check /boot/loader.conf before reload to be sure.
It's important to note that this is deep inside the drivers and that's best reported and coordinated here:
https://bugs.freebsd.org/bugzilla/
Thanks,
Franco
-
Yes, but check /boot/loader.conf before reload to be sure.
It's important to note that this is deep inside the drivers and that's best reported and coordinated here:
https://bugs.freebsd.org/bugzilla/
Thanks,
Franco
thanks