Trouble installing PFSense on Soekris 6501-70
-
Hmm, well I'm pretty sure 2.1.5 should boot from that hardware with no problem. I've never tried 2.2 directly but I know there are people who have upgraded to it.
Are you running the latest BIOS?
Have you tried using a different USB drive? Some hardware is really fussy about USB flash drives.Steve
-
Yeah, 2.1.5 is up and running now. Trying to get it into a position where I can upgrade it.
I tried another SanDisk Fit 32GB USB drive. I don't think that was the issue. There just seems to be something funkey with trying to do a fresh install of 2.2.2.
-
I noticed the 2.1.5 build was built on FreeBSD 8.3. Let the system upgrade itself to 2.2.2 and that build was being reported as 8.3. Thought that was weird. Checked my install on VMWare and it was FreeBSD 10.1.
So I grabbed the PFSense 2.2.2 upgrade tarball and manually upgraded and the system is now on FreeBSD 10.1.
Crazy upgrade process but everything is working. Here's how it went:
PFSense 2.1.5 on a USB key -> System self upgrades to 2.2.2. Then manually upgrade with the 2.2.2 tarball and BAM. 2.2.2 on FreeBSD 10.1.
Off to configure!
-
There is an issue currently with some systems not rebooting correctly after an upgrade from 2.1.X to 2.2.X. Likely if you had just rebooted it it would have come back up running the correct kernel.
Anyway glad you got to 2.2.2 in the end. :)Steve
-
My problem wasn't with an upgrade.
It was with a fresh, clean install of 2.2.2. It refused to reboot after the install had finished.
-
Oh, OK. Nevermind then.
I was just reffering to this:
@tom-28:Let the system upgrade itself to 2.2.2 and that build was being reported as 8.3.
Failing to reboot is usually the cause when you see that.
Steve
-
I have the same problem on Soekris
1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. F1 pfSense F6 PXE Boot: F1
Then it reboots. Release 2.2.2 too.
Additionally at installation I see a crippled boot menu.
First I see this
nsSeconds to automatic boot. Press Ctrl-P for entering Monitor. onboooott//ccoonnffiigg:: --SS111155220000 --DD
Then the cursor jumps around untill it finally draws something like a boot menu but it's unreadable
+ e + W | | | | . ] | B | . r | B | . t | [ | . t | R | | | | : | O | . ) | [ | . . | C | | | | | | | | | + + + \ H- \ey24:0 8086 8185 06040000 0107 0010 08 00 01 3FFF2000 A2FFA100 11 ke25:0 8086 8180 06040000 0107 0010 08 00 01 5FFF4000 A4FFA300 05 /k26:0 8086 8181 06040000 0107 0010 08 00 01 0FFF1000 00FFA000 09 [/code] The numbers are remains of the soekris bios output the rest has been drawn by the boot menu I set the soekris console speed to 115200 and after boot from install USB I see normal output, just the menu is totally crippled and I have to use trial and error to select the right option. Once on harddisk however it does not boot anymore, I tried easy and advanced install and standard or modified kernel, nothing works. This is not my first pfsense I installed on soekris but the first one that does not boot after install on harddisk.
-
I'm having the same difficulty on a 6501-30.
I installed just fine, but can't boot afterward.
-
So, I was able to install 2.1.5, and then upgrade to 2.2.2.
That's strange. Anyone able to venture a guess as to why? -
Hmm, the boot loader in 2.2 somehow incompatible? Seems odd though.
Steve
-
Hope it helps: I am running a net6501-70 with pfSense 2.2.2 i386 nanoBSD on a compact flash card.
I marched the whole upgrade path: 2.1.5 -> 2.2 -> 2.2.1 -> 2.2.2, no experience so far with a fresh installation. Luckily I never had a reboot issue.
Peter
-
Adding another data point, I see the same issue only with a fresh 2.2 install on my net6501. I installed 2.1.x and then upgraded and it runs fine that way, probably not worth the effort tracking it down further at the moment. There are some installer changes happening for 2.3 that might make for an interesting test once they materialize in full.
-
May want to add an installation note somewhere in the official documentation at doc.pfsense.org for the Soekris installs out there.
We know it affects the 6501-30 and 70 whatever jimp has.
-
Has anyone tried a NanoBSD install to see if that works? Or if it's just a full install?
-
I've got a net6501-50 running 2.2.2-nano-i386 off USB.
As far as I remember, I just wrote nano to the stick and popped it in. The x64 build did not work.edit-the issue with x64 is the missing mptable support in the kernel (see http://wiki.soekris.info/Net6501_freebsd)
Should work with these additions-
device atpic # Optional legacy pic support
device mptable # Optional MPSPEC mptable support -
I just started having the same issue with a clean install on a Soerkis6501 using pfSense-CE-memstick-serial-2.3.1-RELEASE-i386.img from a USB to install pfSense 2.3.1 on a CF….
Any ideas? ??? -
I've loaded 2.3-i386 nano on a usb stick and just popped it in, works fine. Haven't tried 2.3.1, or an msata yet. (Hardware is 6501-50)
-
I've loaded 2.3-i386 nano on a usb stick and just popped it in, works fine. Haven't tried 2.3.1, or an msata yet. (Hardware is 6501-50)
Yes, mine works too with USB stick however I want to use my CF since it I have it and it was working fine before…
-
I had a net6501 back in for a little polishing up, so I did a few tests-
2.3.1-nano-i386 on a USB works fine.
Installing 2.3.1 to msata is still broken and won't boot.
2.1.5 appears to be the last version that would boot properly from msata on a net6501. You may be able to load 2.1.5 and upgrade- untested.
Others have reported success by installing the msata in a laptop, installing, then changing fstab and installing in the net6501- untested.
As this appears to be a quirk will Soekris hardware, I don't see this getting fixed unless someone figures it out and submits a reasonable patch.
I'm just going to run nano on mine. -
What I actually did and solved the problem was to install 2.1.5 from memstick to my CF, then use the web UI to upgrade directly to 2.3.1 and restored my config! :)