OpenWrt Support for Asus RT-AC88U

arinc9 · November 21, 2021, 11:39am

Did you reset NVRAM from CFE recovery then flash OpenWrt image? I had an issue similar to yours which resetting NVRAM fixed.

dsouza · November 21, 2021, 5:47pm

Yep, I did reset NVRAM. Rolled back to stock firmware, reset NVRAM again, 5Ghz is still dead. Stock firmware bootlooped once, reset NVRAM, back to stock firmware again, 5Ghz radio still dead.

This is what happed to me 2 years ago (with Merlin) when I shelved this router.

I had the intention to install OpenWRT and use it again as my main router, but I need the 5Ghz working. This way this router is back to the shelf again...

dsouza · December 12, 2021, 10:31pm

Well, I decided to try again, and some really strange things are happening. The 5Ghz radio is still not detected, and now there are two 2.4 radios listed (one OK and the other does not work).

I've tried multiple NVRAM resets, went back to stock firmware, reinstalled OpenWRT and nothing (neither OpenWRT nor stock firmware are able to see the 5Ghz radio).

I still suspect that it might be a hardware issue, but @arinc9, if you have any other suggestion in terms of resetting or restoring this device I am willing to try.

I suspect the dmesg errors below can be related to this issue:

77pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.asus,rt-ac88u.txt failed with error -2
brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2
brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available

Detailed DMESG

[   12.256880] pci_generic_config_write32: 50 callbacks suppressed
[   12.256891] pci_bus 0000:01: 1-byte config write to 0000:01:00.0 offset 0x3c may corrupt adjacent RW1C bits
[   12.272618] pci 0000:00:00.0: enabling device (0140 -> 0142)
[   12.278296] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   12.287975] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   12.297647] brcmfmac 0000:01:00.0: enabling device (0140 -> 0142)
[   12.303760] pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   12.313442] pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   12.487787] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[   12.709919] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.asus,rt-ac88u.txt failed with error -2
[   12.721056] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2
[   13.060406] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[   13.069243] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   13.080516] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43664/4 wl0: Nov  5 2018 03:19:56 version 10.28.2 (r769115) FWID 01-d2cbb8fd
[   13.120358] pci_bus 0001:01: 1-byte config write to 0001:01:00.0 offset 0x3c may corrupt adjacent RW1C bits
[   13.130199] pci 0001:00:00.0: enabling device (0140 -> 0142)
[   13.135894] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   13.145611] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   13.155316] brcmfmac 0001:01:00.0: enabling device (0140 -> 0142)
[   13.161461] pci_bus 0001:01: 2-byte config write to 0001:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   13.171167] pci_bus 0001:01: 2-byte config write to 0001:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[   13.347795] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[   13.359479] brcmfmac 0001:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.asus,rt-ac88u.txt failed with error -2
[   13.370605] brcmfmac 0001:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2
[   18.370522] kmodloader: done loading kernel modules from /etc/modules.d/*
[   20.270874] bgmac_bcma bcma0:4 eth1: Link is Up - 1Gbps/Full - flow control off

Thanks!

arinc9 · December 13, 2021, 8:51am

Nope, that's all I had in mind. If Wi-Fi won't work on the stock firmware, I highly doubt that it will work on OpenWrt.

These appear on mine as well, they shouldn't matter. I don't see anything unusual on your dmesg.

skyline · December 15, 2021, 6:21am

Hi there,

first of all thank you for your great work!!!!!!
I tested the image and it works fine.

Wifi works for me, although the 5GHz range is a bit worse than with the HGG firmware, which I want to replace.
However, the transmission speed is better.

When installing wireguard, however, I ran into a problem that the kernel is not compatible.

Another problem arises after the update of the hostapd-common package.
After this, the wifi no longer works.

arinc9 · December 15, 2021, 8:35am

Cheers!
I don't know about hostapd-common but for wireguard, try to force install it with --force-depends opkg option.

skyline · December 19, 2021, 4:54am

Installation works!
Thank you.

But I haven't it config at the moment.

I have a problem to connect from a lan-device (FHEM-Server) to wlan-devices.

The problem is only at IoT devices with esp8266.

francisuk1989 · December 23, 2021, 3:33pm

What happens when you set the country code under Edit > Advanced Settings to see if that's the issue also?

skyline · December 23, 2021, 6:31pm

I've already changed the country code, deactivated wmm, changed encryption and much more. Nothing works
I also changed the " option ldpc '0' " from this post:

github.com/kaloz/mwlwifi

ESP8266/Embedded devices unable to connect to 2.4Ghz Radio

opened 09:21AM - 03 Mar 18 UTC

iganeshk

I am trying to setup the wireless camera over 2.4ghz access point on 3200ACM run…ning openwrt r6302/r6365 using the latest driver on 3200ACM with all the possible encryption and channels but it just fails after authentication and hence dhcp is unable to detect and allocate an IP to it. Here are the logs that I observed on various settings. ``` Fri Mar 2 14:07:05 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 4) Fri Mar 2 14:07:06 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX Fri Mar 2 14:07:06 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (RSN) Fri Mar 2 14:07:17 2018 daemon.info hostapd: wlan1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated Fri Mar 2 14:07:51 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX Fri Mar 2 14:07:51 2018 kern.debug kernel: [43300.431211] ieee80211 phy1: staid 4 deleted ``` ``` Sat Mar 3 02:53:37 2018 kern.debug kernel: [43405.708782] ieee80211 phy1: staid 4 deleted Sat Mar 3 02:53:40 2018 daemon.info hostapd: wlan1: STA 88:83:5d:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request Sat Mar 3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found Sat Mar 3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found Sat Mar 3 02:53:41 2018 daemon.notice hostapd: handle_auth_cb: STA 88:83:5d:xx:xx:xx not found Sat Mar 3 02:53:43 2018 daemon.info hostapd: wlan1: STA 88:83:5d:xx:xx:xx IEEE 802.11: associated (aid 4) Sat Mar 3 02:53:43 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx Sat Mar 3 02:53:44 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx Sat Mar 3 02:53:45 2018 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 88:83:5d:xx:xx:xx ``` After allocating static ip: ``` Fri Mar 2 14:10:22 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: associated (aid 1) Fri Mar 2 14:10:23 2018 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 88:83:5d:XX:XX:XX Fri Mar 2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: pairwise key handshake completed (WPA) Fri Mar 2 14:10:23 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX WPA: group key handshake completed (WPA) Fri Mar 2 14:10:27 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:30 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:33 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:37 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:40 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:43 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:43 2018 daemon.info hostapd: wlan1-1: STA 88:83:5d:XX:XX:XX IEEE 802.11: authenticated Fri Mar 2 14:10:48 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:51 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:54 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:10:59 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:11:02 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:11:05 2018 daemon.warn dnsmasq-dhcp[3775]: DHCP packet received on wlan1-1 which has no address Fri Mar 2 14:11:08 2018 daemon.notice hostapd: wlan1-1: AP-STA-DISCONNECTED 88:83:5d:XX:XX:XX ``` At first I though it was an issue with dnsmasq, but then I was able to connect the camera with radio2 over 2.4ghz.

Also without luck.

Some router with openwrt have problems to connect to the esp8266.

github.com/kaloz/mwlwifi

IOT can't connect to 2,4Ghz

opened 07:15PM - 28 May 18 UTC

closed 09:16AM - 24 Aug 18 UTC

daloki83

Other Router with default settings = OK WRT3200 with Linksys OS = OK WRT3200 O…penWrt SNAPSHOT r6865-419238fdb3 / LuCI Master (git-18.148.50949-a013967) =NOK Device is a Gosund Smart Plug (https://www.amazon.de/gp/product/B07B911Y6V/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1) I tried all different kinds of Encription/Cipher/Key/WifiName/Channel etc...but no way. The only working way is without encryption. If you need anything else, just let me know. **SYSLOG** Mon May 28 21:03:02 2018 user.notice root: testLog #################################### CUT ################################################# Mon May 28 21:04:14 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:04:14 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:04:14 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:04:14 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated Mon May 28 21:04:27 2018 kern.debug kernel: [13130.714789] ieee80211 phy1: staid 3 deleted Mon May 28 21:04:27 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:04:27 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:04:27 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:04:29 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated Mon May 28 21:04:33 2018 daemon.warn odhcpd[1729]: DHCPV6 SOLICIT IA_NA from 00030001f8461c81370d on br-lan: ok fd7d:4600:2d4e::763/128 Mon May 28 21:04:43 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:04:43 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: disassociated Mon May 28 21:04:43 2018 kern.debug kernel: [13146.623454] ieee80211 phy1: staid 3 deleted Mon May 28 21:04:44 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Mon May 28 21:04:46 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:04:46 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:04:46 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:04:46 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated Mon May 28 21:05:10 2018 kern.debug kernel: [13173.807477] ieee80211 phy1: staid 3 deleted Mon May 28 21:05:10 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:05:11 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:05:11 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:05:11 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated Mon May 28 21:05:39 2018 kern.debug kernel: [13202.914951] ieee80211 phy1: staid 3 deleted Mon May 28 21:05:39 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:05:40 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:05:40 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:05:40 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated Mon May 28 21:06:13 2018 kern.debug kernel: [13236.917407] ieee80211 phy1: staid 3 deleted Mon May 28 21:06:13 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: associated (aid 3) Mon May 28 21:06:14 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED ec:fa:bc:93:57:c5 Mon May 28 21:06:14 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 WPA: pairwise key handshake completed (RSN) Mon May 28 21:06:15 2018 daemon.info hostapd: wlan1: STA ec:fa:bc:93:57:c5 IEEE 802.11: authenticated **WIRELESS_CONF** `config wifi-device 'radio0' option type 'mac80211' option country 'FR' option channel '48' option hwmode '11a' option htmode 'VHT160' option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0' config wifi-iface 'default_radio0' option device 'radio0' option network 'lan' option mode 'ap' option ssid 'CR4P_2_5G' option encryption 'psk2' option key '14digits' config wifi-device 'radio1' option type 'mac80211' option country 'FR' option channel '8' option hwmode '11g' option htmode 'HT40' option noscan '1' option txpower '20' option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0' config wifi-iface 'default_radio1' option device 'radio1' option network 'lan' option mode 'ap' option ssid 'CR4P_2_24G' option encryption 'psk2' option key '14digits' config wifi-device 'radio2' option type 'mac80211' option channel '36' option hwmode '11a' option path 'platform/soc/soc:internal-regs/f10d8000.sdhci/mmc_host/mmc0/mmc0:0001/mmc0:0001:1' option htmode 'VHT80' config wifi-iface 'default_radio2' option device 'radio2' option network 'lan' option mode 'ap' option ssid 'LEDE' option encryption 'none' option disabled '1' ` **MWFWIFI** driver name: mwlwifi chip type: 88W8964 hw version: 7 driver version: 10.3.4.0-20180330 firmware version: 0x09030206 power table loaded from dts: no firmware region code: 0x30 mac address: 60:38:e0:bd:94:b9 2g: enable 5g: disable antenna: 4 4 irq number: 50 ap macid support: 0000ffff sta macid support: 00010000 macid used: 00000001 radio: enable iobase0: e1200000 iobase1: e1480000 tx limit: 1024 rx limit: 16384

With the asuswrt firmware was everything fine.

meth · January 6, 2022, 3:29pm

Hello, I would like to know how complete support is for this model. From reading the latest posts, it's not clear to me if the router works correctly or not.

I would also like to know how easy (or hard) it is to revert to the stock firmware.

arinc9 · January 6, 2022, 7:29pm

The 21.02 image I maintain works completely fine. Reverting to stock firmware is very easy as you just need to do it with CFE Recovery Mode.

skyline · January 6, 2022, 7:51pm

The firmware works really great!
I only have problems with some wireless client that cannot connect to another device, but they can connect to the internet.

I have problems with esp8266-devices and with mobil phone Umidigi S3 Pro.

meth · January 8, 2022, 3:05pm

I installed. Seems to be running okay by now. I'm running into this issue when installing a package:

-> https://openwrt.org/faq/cannot_satisfy_dependencies

The installed version of package kernel is not compatible, require 5.4.154-1-7992aa48… while 5.4.154-1-3927b629… is installed.

Is this something you need to solve at your end?

Thanks

arinc9 · January 8, 2022, 3:20pm

I changed the kernel a bit, to use DSA, for example. Therefore the kernel hash on the versioning is different than the prebuilt packages depend on. You can force opkg to install the package anyway with --force-depends option.

meth · January 8, 2022, 3:25pm

Thank you, that is great.

Any plans to have openwrt add this device to the supported devices list?

arinc9 · January 8, 2022, 8:13pm

I mailed a patch adding support of this device. We had a little conversation on the details with @rmilecki who's supposed to be the maintainer of the bcm53xx target. However, I did not get a response from them afterwards so support for this device is sort of in a limbo right now. The devicetree of this device is still not complete on Linux upstream anyway so I'm not being pushy.

meth · January 8, 2022, 8:35pm

Thanks.

One of the things that are broken in the asuswrt firmware is 6in4 tunnels. I was hoping they'd work here. I was following this guide, but I happened upon a problem:

Sat Jan  8 20:10:08 2022 daemon.notice netifd: Interface 'wan6' is setting up now
Sat Jan  8 20:10:09 2022 kern.warn kernel: [19425.437086] sit: Unknown symbol __xfrm_policy_check (err -2)
Sat Jan  8 20:10:09 2022 daemon.err modprobe: 1 module could not be probed
Sat Jan  8 20:10:09 2022 daemon.err modprobe: - sit
Sat Jan  8 20:10:09 2022 daemon.notice netifd: wan6 (6320): Command failed: Unknown error

Would you mind enabling the CONFIG_XFRM option in next builds of the firmware? I'm confused as to why that option is disabled since it is enabled in openwrt by default. Thanks!

arinc9 · January 9, 2022, 11:00am

That option is enabled on the repository my build is based off of as well. I'm not sure where you got the idea that it was disabled.

github.com

arinc9/openwrt/blob/21.02-asus_rt-ac88u/target/linux/generic/config-5.4#L6499

    
      
          # CONFIG_WW_MUTEX_SELFTEST is not set
          # CONFIG_X25 is not set
          # CONFIG_X509_CERTIFICATE_PARSER is not set
          # CONFIG_X86_PKG_TEMP_THERMAL is not set
          CONFIG_X86_SYSFB=y
          # CONFIG_XDP_SOCKETS is not set
          # CONFIG_XEN is not set
          # CONFIG_XEN_GRANT_DMA_ALLOC is not set
          # CONFIG_XEN_PVCALLS_FRONTEND is not set
          CONFIG_XEN_SCRUB_PAGES_DEFAULT=y
          CONFIG_XFRM=y
          # CONFIG_XFRM_INTERFACE is not set
          # CONFIG_XFRM_IPCOMP is not set
          # CONFIG_XFRM_MIGRATE is not set
          # CONFIG_XFRM_STATISTICS is not set
          # CONFIG_XFRM_SUB_POLICY is not set
          # CONFIG_XFRM_USER is not set
          # CONFIG_XFS_DEBUG is not set
          # CONFIG_XFS_FS is not set
          # CONFIG_XFS_ONLINE_SCRUB is not set
          # CONFIG_XFS_POSIX_ACL is not set

Looks like kmod-sit which is a dependent of 6in4 is having trouble finding symbols. You should build your own image from my 21.02-asus_rt-ac88u branch with 6in4 enabled.

OpenWrt Wiki page for the build system:

meth · January 9, 2022, 11:45am

sit is as you say an external module, and it fails to load because it can't find the symbol "__xfrm_policy_check" in the kernel, which is guarded with CONFIG_XFRM:

-> https://github.com/torvalds/linux/blob/4634129ad9fdc89d10b597fc6f8f4336fb61e105/include/net/xfrm.h#L1077-L1095

Hence my natural assumption was that the kernel is not built with that configuration option on.

I will look into building the firmware myself.

arinc9 · January 9, 2022, 11:52am

I see. It's a bit messy to use prebuilt kernel modules on a custom build which might produce weird errors like you stumbled upon. So it's a better idea to compile the image with the packages (especially kernel modules) you want.

The steps to compiling the build is not as long as the wiki page makes it to be, as it tries to be thorough.