Actually I am using voyage (shrinked down debian) on my APU1, which is running very fine. voyage is distributed as a basic image, to be cloned to SD-card, and booted from there.
I am also using openwrt/LEDE on various devices, all to be flashed to integrated flash of the dvices.
But how is LEDEs APU2-image to be applied ?
You dd it to your storage, just like you probably did with the Debian image.
If you'd like an image with the web interface included (development snapshots lack it), you can grab images from the 17.01 branch (pre-release) here .
So, by APU2-image, you refer to the generic x86_64 image, which for version 17.01.2 is located here?
I just ask as I have spendt some time now reading through various forums, and there are quite some manuals for compiling special images for the APU2. Mentioned issues include special requirements in order to boot LEDE from SD, to enable all three LAN ports (as by default, according to various descriptions, only one LAN port is enabled by default), as well as mulitcore, push-button and LED-support (although I would suppose the patches for the latter ones are already included it LEDE version 17.01.2).
So my question is: If I have a APU.2C4 with WLE200NX WIFI module, the installation of version 17.01.2 of LEDE is as simple as to download the generic combined image, dd it to my SD-card, boot the device, and do the rest (switch on WIFI, enable the other LAN ports and configure one of them as WAN port) via the LUCI web interface?
Sorry for the newbie-type of question, but I want to buy a both reliable and easy to maintain hardware this time....
Just for reference:
The latest firmware image downloads can be found via the Table of Hardware:
https://lede-project.org/toh/views/toh_fwdownload?dataflt[Model*~]=apu2
For installation instructions see:
https://wiki.openwrt.org/toh/pcengines/apu2
If the installation instructions are outdated / incomplete / whatever: Update them. It's a wiki that lives from the input of its users.
- The APU2 will boot from SD if there is no internal HD/SSD installed.
- A default (and sensible) x86 setup is just configuring one port; most x86 platforms only have one interface. You can reconfigure easily (SSH or web UI). If you're using an APU, that shouldn't be a problem I suppose?
- Multicore is enabled by default. My APU2 shows 4 cores.
- LED support has made it into 17.01.2 as well.
Thanks a lot for the response.
Any experience with WIFI? Do WIFI modules (e.g., WLE200NX, which is basically recommended by the APU2 vendor) work out of the box as well?
For reasons of completeness: I have got myself a APU.2C4 with WLE200NX WIFI module now. Unfortunately, the generic X86_64 LEDE image does not show any pre-configured WIFI-interface, nor does it list the WIFI-device itself, thus making it impossible to configure a WIFI access point / client by means of the web GUI (at least I did not find a way). In summary: WIFI does NOT work out of the box at the moment.
The image will not include any wireless device drivers. Not sure about other packages for wireless. This may help ID the wireless driver you need.
https://wikidevi.com/wiki/Compex_WLE200NX
Some months ago already I succeeded to build a working image from sources, incl. WLE200NX. In case of interest I can share (old) .config
1 Like
Can u please share?
My WLE200NX is not working although I installed all necessary drivers. It even shows that it loaded the ath9k driver. But I can not see this card under iw phy. Strange: It pops up using iwinfo...
Oh, I was missing ath9k-htc-firmware. Now it works. 
https://teklager.se/en/knowledge-base/openwrt-wifi-configuration-instructions/
1 Like