New Alix board for 2013
-
That is the one sold by PC Engines
http://www.pcengines.ch/msata16a.htm
I read a review of the APU and this SSD and the guy at ipfire,org got the same bad results. He also states, that it is a cheap SSD and would buy another. http://planet.ipfire.org/post/pc-engines-apu1c-a-review
Greets, Jud3x
-
Yeah that's just down the the SSD itself rather than the board then, and it's pretty much what I'd expect for an SSD in that price range.
Read speed is far better than write speed though, and TBH I'm not sure what you'd want to be constantly writing at high speed to a small SSD like this for anyway, not least because of the limited write cycles of NAND.
-
Anyone else having issues bridging the LAN interfaces? I get intermittent connectivity when I try and I can see the physical connection dropping. It should be noted that as soon as I remove the bridge I no longer get connection drops.
LAN: bridge0
MGMT: re1
WIFI: ath0
WIRED: re2BRIDGE0 Members: WIFI, WIRED
System Log:
Mar 30 19:13:03 syslogd: kernel boot file is /boot/kernel/kernel Mar 30 19:13:05 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:05 check_reload_status: rc.newwanip starting re2 Mar 30 19:13:08 php: rc.newwanip: rc.newwanip: Informational is starting re2. Mar 30 19:13:08 php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: opt3) (real interface: re2). Mar 30 19:13:08 php: rc.newwanip: rc.newwanip: Failed to update opt3 IP, restarting... Mar 30 19:13:08 check_reload_status: Configuring interface opt3 Mar 30 19:13:11 php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 're2' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Mar 30 19:13:11 check_reload_status: Linkup starting re2 Mar 30 19:13:11 kernel: re2: link state changed to DOWN Mar 30 19:13:13 check_reload_status: Linkup starting re2 Mar 30 19:13:13 kernel: re2: link state changed to UP Mar 30 19:13:14 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:16 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:16 check_reload_status: rc.newwanip starting re2 Mar 30 19:13:18 php: rc.newwanip: rc.newwanip: Informational is starting re2. Mar 30 19:13:18 php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: opt3) (real interface: re2). Mar 30 19:13:18 php: rc.newwanip: rc.newwanip: Failed to update opt3 IP, restarting... Mar 30 19:13:24 php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 're2' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Mar 30 19:13:24 check_reload_status: Linkup starting re2 Mar 30 19:13:24 kernel: re2: link state changed to DOWN Mar 30 19:13:26 check_reload_status: Linkup starting re2 Mar 30 19:13:26 kernel: re2: link state changed to UP Mar 30 19:13:26 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:29 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:29 check_reload_status: rc.newwanip starting re2 Mar 30 19:13:32 php: rc.newwanip: rc.newwanip: Informational is starting re2. Mar 30 19:13:32 php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: opt3) (real interface: re2). Mar 30 19:13:32 php: rc.newwanip: rc.newwanip: Failed to update opt3 IP, restarting... Mar 30 19:13:32 check_reload_status: Configuring interface opt3 Mar 30 19:13:34 php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 're2' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Mar 30 19:13:35 check_reload_status: Linkup starting re2 Mar 30 19:13:35 kernel: re2: link state changed to DOWN Mar 30 19:13:37 kernel: re2: link state changed to UP Mar 30 19:13:37 check_reload_status: Linkup starting re2 Mar 30 19:13:37 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:39 php: rc.linkup: Hotplug event detected for WIRED(opt3) but ignoring since interface is configured with static IP ( ) Mar 30 19:13:39 check_reload_status: rc.newwanip starting re2 Mar 30 19:13:42 php: rc.newwanip: rc.newwanip: Informational is starting re2. Mar 30 19:13:42 php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: opt3) (real interface: re2). Mar 30 19:13:42 php: rc.newwanip: rc.newwanip: Failed to update opt3 IP, restarting... Mar 30 19:13:47 php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 're2' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Mar 30 19:13:47 check_reload_status: Linkup starting re2 Mar 30 19:13:47 kernel: re2: link state changed to DOWN -
SpankIt, are you using 2.1?
This has been fixed in 2.1.1. There is a long thread about it somewhere.Steve
-
Hi there!
I have an issue with APU1C and pfsense 2.1, the LiveCD is not booting. Here are more details:
Booting stops after "Starting the BTX loader" message.http://pcengines.info/forums/?page=post&id=2ADF62BD-420D-447D-A387-A9B047776417&fid=40251191-FF24-48A8-BB0E-995B04812ADE
Anyone has an idea what's wrong?
Bye
-
Marama,
I didn't try to install from CD, instead I'd recommend to install via USB-Stick. Choose the amd64 memstick-image and follow the instructions to write the image to the stick. Mount it with a running freebsd and append 'console="comconsole" to /boot/loader.conf (don't forget to mount the stick and change the filepath - this is not copy & paste):
$ echo 'console="comconsole"' >> /$USB_MOUNT_POINT/boot/loader.confNow you're good to go. Boot from the USB- Stick and pass the following line to the kernel during startup:
$ set kern.cam.boot_delay=10000Now you can follow the install-scripts as described in various How-To's.
If you want to use an SD-Card, it's even simpler - just follow the instructions from the CF-Card install to the letter, but during first boot pass the
$ set kern.cam.boot_delay=10000line to the kernel, and everything works as expected. Once booted it's best to add the "kern.cam.boot_delay" statement to /boot/loader.conf. Don't forget to remount the partition before editing, it's readonly per default.
Have fun!
-
Interrupt the boot loader.
type-
set kern.cam.boot_delay=10000
boot
After booting add kern.cam.boot_delay=1000 to /boot/loader.conf.local via edit or from console.sir could you please explain this further? how to do it etc..thanks
-
Marama,
I didn't try to install from CD, instead I'd recommend to install via USB-Stick. Choose the amd64 memstick-image and follow the instructions to write the image to the stick. Mount it with a running freebsd and append 'console="comconsole" to /boot/loader.conf (don't forget to mount the stick and change the filepath - this is not copy & paste):
…Keychain, thanx for helping me out, but reseting from 115200 to 9600 seemed to have helped.
BTW, should I go for symmetric or embedded kernel? -
Interrupt the boot loader.
type-
set kern.cam.boot_delay=10000
boot
After booting add kern.cam.boot_delay=1000 to /boot/loader.conf.local via edit or from console.sir could you please explain this further? how to do it etc..thanks
It's been covered several times, most recently by keychain, but to make the process clear:
Write the nano image to the SD card using a card reader and physdiskwrite.
Connect a null modem cable to the serial port and use putty or similar to connect at 9600.
Power the unit up. You will see a bunch of garbage due to the console being at the wrong speed.
Eventually, you will see pfSense booting. When you see a message about 'Booting [/boot/kernel/kernel]' press CTRL-C until it drops to an 'OK' prompt. If you miss it, shut down and try again.
At the prompt type:set kern.cam.boot_delay=10000Then press enter. It should return to the OK prompt. Then type:
bootand press enter. The unit should now boot. Assign interfaces. Remember re2 is the one marked 'LAN'
Log in to the webgui and go to diagnostics, edit file.
Enter:/boot/loader.conf.localin the save/load path. Then enter:
kern.cam.boot_delay=10000below and click the save button.
-
SpankIt, are you using 2.1?
This has been fixed in 2.1.1. There is a long thread about it somewhere.Steve
I am using 2.1, thanks for the heads up I will give that a shot.
-
should i use memstick or memstickserial image?
from the APU specs
Storage: Boot from SD card (connected through USB), external USB or m-SATA SSD. 1 SATA data + power connector.does this mean i have to still use a card reader and plug to the APU USB even there is a SD slot on board?
FYI ive used memstick image but ive never get to boot to pfsense at all
-
@dotdash
should i use memstick or memstickserial image?I've been using the nano-2.11-pre-i386 image, writing it via a card reader, then putting it in the apu.
You could boot from USB memstick and install to the SD card if you want, but I haven't tried it.
Edit- If you choose to install from memstick, use the -serial version… -
Serial memstick (choose the Embedded kernel when installing) is the best bet for an mSATA.
For SD, you'll probably want NanoBSD but you'll need to make the kern.cam.boot_delay adjustment since the SD reader appears to the OS as a USB device even though it's internal.
You may also want these changes if you're on NanoBSD: https://doc.pfsense.org/index.php/Boot_Troubleshooting#NanoBSD_on_Newer_Hardware
It may be time to lock this thread and start new ones for individual issues/suggestions. This has been going for a long time and has meandered through many distinct topics.
-
does this mean i have to still use a card reader and plug to the APU USB even there is a SD slot on board?
No, this just means the built-in SD card reader is attached to the USB bus internally.
Edit: jimp beat me to it.
-
It may be time to lock this thread and start new ones for individual issues/suggestions. This has been going for a long time and has meandered through many distinct topics.
Yes, I agree. A new board has come (in 2014 not 2013) and so the original point of this topic is fulfilled. It would be easier if people post specific issues or help/doc with installing and using it in different threads. Feel free to lock it.
-
Locking the topic, thanks for all the information everyone!
If you wish to add something unique then start a new thread about a specific topic regarding the APU.
