Messages

1

20.7 Legacy Series / Re: can't install 20.7

« on: October 24, 2020, 09:12:05 pm »

Thanks, pimpex, for your response.

I have been trying to install from the dvd iso, and could not figure out how to get any file on that without jumping through some flaming hoops. But it did get me thinking in a different direction.

I had tried to install on older hardware from the vga img, and failed miserably. However, I gave it a fresh try today on my new hardware, and it actually installed!

Question for someone who knows more than I do: is the code in the dvd install different from the the code in the vga install? Or is this from some quirk that I'm completely ignorant of?

Anyway, I went on to upgrade to the latest-and-greatest version from the console. I had a bit of trouble with syslog-ng, and found plenty of posts about that. I got it straightened out (re-ran upgrade to finish it, and let it reboot after that).

I am off-and-configuring and should have this upgraded firewall in place shortly.

2

20.7 Legacy Series / can't install 20.7

« on: September 27, 2020, 09:26:25 pm »

Trying to install 20.7 on new hardware. The DVD boots fine. If I log in with installer <password>, I get dumped into a GUI, where I can move the arrow-mouse-cursor, but clicks are not recognized. I can move with arrow keys on the keyboard, and make selections. After just a couple of screens, it totally hangs (can't get selection to move or be recognized).

I can Ctrl-Alt-Delete and reboot. Next time in, I log in with root <password>, select 8 (shell), enter opnsense-installer, and get dumped back to that same GUI, where I can work with a couple of screens and then it becomes unresponsive.

Is there some sort of option I can use somewhere somehow to get a good-old-text-only installation?

Any idea why it seems to be so unhappy with my built-in graphics?

Edit: add hardware details
Motherboard: Gigabyte B450M DS3H
CPU: AMD Ryzen 3 3200G with Radeon Vega 8 Graphics
Memory: Crucial 8GBDDR4-3200 UDIMM


Thanks.

3

General Discussion / Re: Bootloop, BSD11.1 vs. 11.2, uefi

« on: August 24, 2020, 05:41:11 pm »

Hi again, all -

Believe it or not, I'm still futzing around with this. It is my HOME firewall, and is not my full-time job. It gets attention sporadically, usually on the rare occasion it bites us in the tush. We had one of those occasions recently.

I did a search in these forums, and stumbled across a (more recent than mine) relevant post from @thesohogeek: https://forum.opnsense.org/index.php?topic=17351.0. Thanks so much! I enjoyed your humor (humour?) 

Since none of the devs here for OPNsense appears to be addressing this issue, I will be visiting the FreeBSD forums to see what is going on over there. This issue is keeping me stuck at 18.7, which is making me more uncomfortable as time moves on. We normally run the firewall on old hardware trickled-down from desktops as those get upgraded for various reasons. There is currently nothing wrong with this hardware, and barely breaks a sweat with our level of traffic. We don't need to spend $500US-plus to buy a new motherboard/CPU/memory. We just need firewall software that is happy to run without UEFI.

Any comments or work-arounds are welcome.

4

General Discussion / Bootloop, BSD11.1 vs. 11.2, uefi

« on: September 03, 2019, 01:57:31 pm »

Hi Folks, was not certain where to put this so trying General.

I'm in the process of catching up some backlogged updates. When going from OPNSense 18.7 to 19.1, which I believe involves an underlying upgrade from BSD11.1 to BSD11.2, I get in a boot loop, the only way to get out of is by manually selecting the old kernel from the console.

Yes, I found this post: https://forum.opnsense.org/index.php?topic=11674.msg52864#msg52864. Yes, I tried creating the file in /boot. It did not help. There is NO uefi option in the BIOS to change (we tend to run on old hardware).

Here is the question: is there some requirement for UEFI in BSD11.2? Anyone out there running OPNSense 19.1+ without it? Also, I did notice that my hard drive is formatted in the GPT style, rather than the MBR style; is it possible that the kernel sees that and ASSUMES there is a UEFI capability that is not there and freaks out? :-)

Thanks for your time.