PfSense with Axiomtek NA341 Board
-
sorry, I was in a hurry
pfSense-2.1.1-RELEASE-4g-i386-nanobsd.img
pfSense-2.1.1-RELEASE-4g-i386-nanobsd_vga.imgI followed this tutorial too : https://doc.pfsense.org/index.php/HOWTO_Install_pfSense
I replaced config file ( .xml ) but nothing, same results -
Hmm, I'm missing something. You were able to replace the config.xml file? How did you do that? The box had booted pfSense or you mounted the card in a BSD machine?
If you are getting to the end of the POST messages from the BIOS and then you see nothing from either image on either the VGA or console port then the most likely cause is that the images are not writing to the card correctly. Do you see any errors when writing the image? You could try using the 2GB images instead to ensure they are fitting on the card.Steve
-
Shows me the boot menu F1, F2, and then the message: "/".
Should be fine if I follow the documentation -
https://doc.pfsense.org/index.php/Installing_pfSense
"If everything is configured correctly you should see the kernel beginning to load. At systems with VGA the output will stop displaying a "/" at the screen. From that point on all output is at COM1. Please check the bootup process there by using a null modemcable and a terminal program."This is the last message I have seen on both monitor and serial ( HyperTerminal, Putty )
On writeing the img to CF i had no error messages
-
Ok. Have you ever seen anything on the serial console? Have you proved the connection on some other hardware? Like it says in the doc the standard Nano image switches it's console output to the serial port at that point so your serial terminal setup not working correctly matches those symptoms. That doesn't explain the nano+vga images though.
You are seeing the FreeBSD bootloader though so it looks at though the images are writing to the card correctly and the bios is correctly booting it though so that's good. ;)
Steve
-
Since it's hanging at the 'spinner' you could try these HD mode suggestions:
https://doc.pfsense.org/index.php/Boot_Troubleshooting#BIOS.2FDisk_ErrorsSteve
-
Not helped :(
I tried with the 2Gb img and same results
Is any way to start instalation from a bootable usb ? I tried with usb stick and usb dvd but won't boot, hiren's cd also boots
Please give me other suggests, thank you -
If it will boot from USB then you can write the Nano images straight to the USB stick and boot from that.
To boot anything via USB you probably have to interrupt the boot loader and set a delay. See:
https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USBSurprised it wouldn't boot from CF though. :-\ As a test you could try booting an alternative image from the CF. For example you could use this FreeDOS image:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios2.img.gz
That boots to a console at 9600bps on com1.Steve
-
I tried with FreeDOS, is booting even if it stops asking me for mouse, at COM1, but this is another work :)
what I do with pfSense ?
I tried to boot over the SATA port with a DVD RW, loader stop on console at:
CD Loader 1.2Building the boot loader arguments
Looking up /BOOT/LOADER… Found
Relocating the loader and the BTX
Starting the BTX loader
_ -
Was that via VGA or serial?
That's odd. It boots the FreeDOS image fine but hangs booting pfSense. :-\ Hmm, must be something it doesn't like about the disk controller or some other piece of hardware. Nothing on that board looks too exotic though and you tried the various HD modes in the BIOS?.Steve
-
I tried FreeBSD 9.1 amd64, i386, memstick and FreeBSD 10 too
On Monitor ( via vga )
On Terminal ( via serial console )
With pfSense Embeded 4GB ( or 2GB ) CF VGA or Serial img:
Monitor: same as FreeBSD
Terminal:
No any good results with IDE or AHCI setting in BIOS
Also I tried installing Windows 7 Ultimate 32bit, everything worked OK
-
Hmm, that's….. interesting.
Some time ago there was an issue with the graphics drivers for the newer (at that time) Atoms such as the D2500. The driver was eventually fixed upstream and is now included in pfSense. I never saw the problem first hand but descriptions of it sound a lot like what you're seeing. There were work-arounds at the time I seem to recall.You could try, just as a test, booting a 1.2.3 image. They didn't suffer from that problem. If that works you can probably upgrade in place to 2.1.1.
Steve
