APU1C 2.2.2 Image
-
Is there a trick to installing 2.2.2 onto an APU1c? When I flash the pfSense-2.2.2-RELEASE-4g-amd64-nanobsd.img image onto an SD card, it doesn't boot. If I go back to the 2.1.4 image it boots up just fine. Am I using the wrong image?
-
I just tried pfSense-2.2.2-RELEASE-4g-i386-nanobsd-20150413-2010.img and it isn't booting, either.
-
I've loaded nano on a bunch of 1d's, I don't think there is much hw difference to the 1c.
When you say 'isn't booting' what exactly do you mean?
2.2x sets the serial to 115200, so set your console to that before you boot it. You should see the bios stuff.
You will need to assign interfaces via serial before it will fully boot, I expect you are not seeing the console and thusly not getting the interfaces assigned. -
I can connect in @ 115200 and I can see the file systems, so I guess it is booting.
Running top only shows:
php-fpm
sh
php-fpm
check_reload_status
devd
top
check_reload_status.I then ran /etc/rc.reload_all and now I see some extras such as:
unbound
filterlog
ntpd
radvd
lighttpd
inetd
sleepRunning ifconfig doesn't work. If I run /sbin/ifconfig I can see the network cards, but they don't have ipv4 addresses - only ipv6.
-
Should I be using the 64-bit or the 32-bit image?
The 64-bit on boot shows:
/boot/kernel/kernel text=0x121w2d8 data=0x881b58+0x357620 zf_read: unexpected EOF
readin failed
elf64_loadimage: read failed
can't load 'kernel'The 32-bit image seems to load fine.
-
Looks like I had a couple of issues.
1: Putty wasn't showing me the right stuff and even when it did it wouldn't let me type.
2: While the 64-bit archive downloaded for the Tx site ine and unpacked fine it appears to have been corrupt. I downloaded it from the Ky mirror and it loads fine.
3: I forgot about the whole assigning NICs thing before it would load. DOH! Using Hyperterminal I was able to get in and assign them.
