ALIX system boards are manufacturered and sold by PC Engines. They utilise the x86-based AMD Geode CPUs. The boards and other components (enclosures, power supplies, wireless cards, CompactFlash cards, etc) are sold separately, although some retailers sell pre-build kits. At the time of writing (August 2011), ALIX boards and associated accessories are readily available from many resellers across Europe and North America.

Model	OpenWrt Version Supported	Model Specific Notes
Alix 1c, 2c*, 3c*	Kamikaze 8.09 and above	-
Alix 1d, 2d*, 3d*	Kamikaze 8.09 and above	-
Alix 6*	Kamikaze 8.09 and above	Almost certainly works, but is untested

The Alix.1 series is significantly different to most other Alix system boards in that it includes VGA/PS2 ports, a PCI slot, has only 1 ethernet port, and has a different BIOS. In short, it is very much a x86-compatible PC rather than a headless appliance. This is an important distinction (see below).

There are many models of ALIX boards (all work with OpenWrt at present), with two different CPU/RAM configurations:

All models have a CompactFlash socket and some also have a 44-pin IDE header for 2.5“ IDE hard disks.

Many models have miniPCI sockets (ideal for WiFi cards), and some have miniPCI Express sockets (note that there is a warning on the PC Engines site stating that these cannot be used with WiFi cards though). The Alix.1 series includes a standard 3.3V PCI riser.

The device does not include an embedded Ethernet switch. Models with multiple Ethernet ports have multiple Ethernet controllers (Via VT6105M).

There are two distinct options for installing OpenWrt, using images that are either:

• pre-built nightly and available from http://downloads.openwrt.org/, or
• built by yourself (or a mate).

There are no pre-built images specifically for the Alix boards. However, the generic x86 images will work, although they do not include all of the Alix system board drivers by default (e.g. LED support, USB). This is not a major problem as (it appears that) all these packages can always be added via the opkg utilities once the system has booted.

Alternatively, you can build such images yourself (recommended, but obligates a significant learning curve). Note that the x86/alix2 image appears to include a Alix.2-specific kernel and that this image is not recommended for the Alix.1 series.

Note that the x86/Generic image is the best option for the Alix.1 series because, unlike the x86/Alix2 image, it includes drivers for the VGA/PS2 console. This is because it is easier to add Alix-specific drivers to the x86-generic image, rather than VGA/PS2 drivers to an alix-specific image (which you'd have to build yourself anyway).

The current release Backfire 10.03.1-RC5 openwrt-x86-generic-combined-ext2.img.gz includes ethernet drivers (at least for the Alix.1/Alix.2d3 boards). After flashing the OpenWrt image, follow these guides to install missing packages:

• opkg update
  opkg install ''kmod-leds-alix''

• basic
• usb-installing
• usb-drives
• LuCI

NOTE: If you have problem mounting external storage on boot apply this fix: sleep.before.startup.

Building your own image and specifying the build profile below will ensure the appropriate drivers are all included in the image. Follow:

• OpenWrt Buildroot – About
• OpenWrt Buildroot – Installation
• OpenWrt Buildroot – Usage

The build profile should be (exception: Alix.1-series boards, see notes above):

• Target System: x86
• Subtarget: PCEngines alix2

The easiest method of installation for ALIX boards is to use dd to write the image to the CompactFlash card on machine.

1. Attach a USB CompactFlash reader/writer to the flashing machine and insert the CompactFlash card
2. Watch the output from 'dmesg' to see what device ID it has picked up (it will be something like /dev/sdb)
3. Ensure that /dev/sdb (or whatever is determined in step #2) is not mounted through the use of the mount command. If it is, unmount it with umount.
4. Decide whether you want to use the squashfs (openwrt-x86-squashfs.image) or ext2 image (openwrt-x86-ext2.image). The ext2 one will take up considerably more space on the CompactFlash card, but will be faster to boot.
5. Uncompress your image file

   gunzip openwrt-x86-generic-combined-ext2.img.gz

6. Flash the desired image to the CompactFlash card with:

   dd if=openwrt-x86-ext2.image of=/dev/sdb

7. Depending on your CF card size the default install won´t full fill your CF card. You can use gparted or equivalent application to expand the root partition.
8. Removed the CompactFlash card, place it in the ALIX board and power on.
9. Once powered on and booted up the ALIX should be reachable on 192.168.1.1 on eth1. In default install eth0 is wan interface configured to obtain ip by dhcp and eth1 is br-lan interface with static ip 192.168.1.1 this does not apply for the Alix.1c/1d - see below.
10. If you have a serial cable it is recommended to do the first boot and initial network configuration with it attached (minicom configured for 38400-8N1)

If you selected the squashfs image it may take quite a few minutes for the device to power on.

1. Usually one just has to dd the combined image onto the CF card:

   wget http://downloads.openwrt.org/backfire/10.03.1-rc5/x86_generic/openwrt-x86-generic-combined-ext2.img.gz
   gunzip openwrt-x86-generic-combined-ext2.img.gz
   dd if=openwrt-x86-generic-combined-ext2.img of=/dev/cfcard

2. Afterwards you can use the usual utilities like fdisk, tune2fs, etc. to resize the system partition (its only around 40MiB by default) and maybe upgrade the filesystem.
3. Sometimes you need to change the root= parameter in the GRUB settings if the booting kernel does not find the root device. You'll find the menu.list within the first partition.

—-

As stated above, the Alix.1d series is significantly different to the other Alix system boards. For example, when using a generic x86 image (recommended), the system will not be able to connect to the Internet by default.

With this in mind, the following scripts have been tested on both

• trunk (aka Attitude Adjustment / bleeding edge) using: openwrt-x86-generic-combined-ext4.img, and
• Backfire using openwrt-x86-generic-combined-ext2.img.

To use the VGA/PS2 console, boot the Alix.1d with these devices attached. When the console has stopped scrolling, just press Enter, and you should be good to go. The serial port is not necessary, but will work, although you will require a null modem cable (38400 8N1).

If you wish to use SSH (via TCP/IP) later, you will need to set a password for the root account (here's how to do it in a script).

(echo "12345678"; sleep 1; echo "12345678") | passwd root

By default, the Alix.1d will not be able to access the Internet (and thereby download packages) with a generic x86 image.

This is because the Alix.1d has only one ethernet port, eth0, which is configured as a LAN interface by default on this image. To configure it as a WAN interface, the following has worked for me (see network interfaces for more details):

uci set network.lan.ifname=

The lan network is still required for the wireless AP to 'bridge' to, even though it has no physical interface.

uci set network.wan=interface
uci set network.wan.ifname=eth0
uci set network.wan.proto=dhcp

Finally, effect the changes.

uci commit network
/etc/init.d/network restart

You can confirm the result of this script by executing: ifconfig eth0 | grep inet and/or ping 8.8.8.8 -c 4.

This should work on other x86 models. First, install the wireless card drivers (this assumes an Atheros ath9k-compatible wifi card):

opkg update
opkg install kmod-ath9k

You can confirm the result of this script by executing ifconfig wlan0. Next, configure the radio:

wifi detect > /etc/config/wireless
uci set wireless.radio0.disabled=0
uci commit wireless

Finally, install and start the access point daemon:

opkg install wpad-mini
wifi

By Default, the SSID will be OpenWRT and there will be no WEP/WPA.

Tested with r38680, this picture is correct:

→generic.sysupgrade

Assuming you have the kmod-led-alix module present (check via lsmod), you should get three LED devices under /sys/class/leds/ - alix:1, alix:2 and alix:3 This should turn on one led:

echo 1 > /sys/class/leds/alix:1/brightness

And off:

echo 0 > /sys/class/leds/alix:1/brightness

And this should make it blink:

echo timer > /sys/class/leds/alix:1/trigger
echo 1000 > /sys/class/leds/alix:1/delay_off
echo 100 > /sys/class/leds/alix:1/delay_on

You can assign various triggers for LED activity using the instructions here.

After reading the previous link about leds functionality, the easiest way to configure the leds is from the web gui (LuCI) in “System” » “LED configuration”

Note: The below is taken from the Old Wiki, and its current correctness is unknown.

• The button does not seem to work
• Attach serial cable, speed is 38400
• Press Esc during or after the memory check (can be tricky to time right)
• Choose 'safe mode' in the grub menu

Note: The below is taken from the Old Wiki, and its current correctness is unknown.

The Geode LX CPUs have a hardware watchdog. It might be supported by the scx200_wdt kernel module that provides the same support for the GX series.

These commands might enable the watchdog with the GX series CPUs.

mknod -m 600 /dev/wd c 10 130
modprobe scx200_wdt margin=30

An example of the watchdog in action on ALIX boards can be found at twam.info

As of OpenWrt Backfire 10.03, cryptodev support can be enabled by installing the following packages (confirmed and tested on Alix 2d13):

From Kernel Modules, Cryptographic API modules:

• kmod-crypto-core
• kmod-crypto-aes
• kmod-crypto-hw-geode
• kmod-crypto-ocf

This was tested using openssl-util, which was installed from Utilities –> openssl-util. The command to test it is:

• ”openssl speed -evp aes-128-cbc -engine cryptodev“

The Alix Geode crypto engine supports only AES-128. Other ciphers are not supported. For more general crypto hardware info, see here:

• cryptographic.hardware.accelerators

Many of the below are written with Gentoo in mind, but will work equally well on OpenWrt (you should install relevant pages via 'opkg' rather than 'emerge' though).

• Watchdog usage on Gentoo
• Accessing temperature sensors
• Utilising hardware AES engine

How to add tags