Odroid C4 wlan interface not recognized

Creating a bug report/issue

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=8
  • Distro version | bullseye
  • Kernel version | Linux DietPi 5.10.123-meson64 #22.05.3 SMP PREEMPT Wed Jun 22 07:23:04 UTC 2022 aarch64 GNU/Linux
  • SBC model | Odroid C4/HC4 (aarch64)
  • Power supply used | 12V/2A AC power plug
  • SD card used | SanDisk ultra 32GB Class 10

Additional Information (if applicable)

#- Software title | (EG: Nextcloud)
#- Was the software title installed freshly or updated/migrated?
#- Can this issue be replicated on a fresh installation of DietPi?
#<-- If you sent a “dietpi-bugreport”, please paste the ID here →

  • Bug report ID | bf51140a-dfcd-4c78-81ab-5db7f276902d

Steps to reproduce

  1. Fresh install of DietPi downloaded from the official DietPi website (DietPi - Lightweight justice for your SBC!) and using Etcher to flash the SD card.
  2. Plug in an external USB Wi-Fi adapter (Alfa AWUS036ACS 802.11ac AC600 / RTL8812au) and then plug in a keyboard, mouse, Ethernet cable, and then power.
  3. Go through the initial setup configuration and dietpi-config and attempt to scan for Wi-Fi networks. This fails so move to next step.
  4. Manually configure an SSID and WPA PSK in the network adapter configuration (Ethernet and Wi-Fi are different subnets) and the config fails to locate the adapter.
  5. Move on to the rest of the initial configuration.
  6. Using the command ‘ip a’ identifies the Ethernet and loopback interface, but no wlan interface.

Expected behaviour

  • In previous versions of DietPi running on an Odroid C2, the wlan interface can be seen without any additional work.

Actual behaviour

  • The OS can’t identify the wlan adapter, even when configured in the ‘dietpi-config’ menu for slot0

Extra details

  • To verify the adapter and board is working, loaded Ubuntu 20.04 from HardKernel on the Odroid C4 board and it recognized the adapter. The command ‘iw wlan0 info’ when run on Ubuntu shows the information about the interface. I also loaded and updated the latest DietPi OS on a NanoPi NEO3 and it was able to recognize the adapter without any problems. As mentioned, the same adapter also works on an Odroid C2 running DietPi version 3.14.79.

'iw wlan0 info" returns the help screen with no information.
‘lsmod’ shows the following:
Module Size Used by
88XXau 2248704 0
snd_soc_hdmi_codec 20480 1
cfg80211 397312 1 88XXau
rfkill 36864 2 cfg80211
ir_nec_decoder 20480 0
meson_vdec 77824 0
v4l2_mem2mem 40960 1 meson_vdec
videobuf2_dma_contig 24576 1 meson_vdec
videobuf2_memops 20480 1 videobuf2_dma_contig
rc_odroid 16384 0
meson_ir 16384 0
meson_saradc 24576 0
rc_core 57344 4 ir_nec_decoder,meson_ir,rc_odroid
videobuf2_v4l2 32768 2 meson_vdec,v4l2_mem2mem
snd_soc_meson_g12a_tohdmitx 20480 1
meson_gxbb_wdt 20480 0
dw_hdmi_i2s_audio 16384 0
snd_soc_meson_codec_glue 16384 1 snd_soc_meson_g12a_tohdmitx
videobuf2_common 57344 3 meson_vdec,videobuf2_v4l2,v4l2_mem2mem
snd_soc_meson_axg_frddr 36864 3
snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr
snd_soc_meson_axg_tdmout 24576 1
meson_rng 16384 0
videodev 278528 4 meson_vdec,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
snd_soc_meson_axg_sound_card 16384 0
panfrost 65536 0
mc 61440 4 videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
gpu_sched 32768 1 panfrost
snd_soc_meson_card_utils 16384 1 snd_soc_meson_axg_sound_card
snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card
snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout
snd_soc_core 221184 10 snd_soc_meson_axg_tdm_formatter,snd_soc_meson_axg_sound_card,snd_soc_hdmi_codec,snd_soc_meson_g12a_tohdmitx,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_fifo,snd_soc_meson_axg_tdmout,snd_soc_meson_axg_frddr,snd_soc_meson_card_utils,snd_soc_meson_codec_glue
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 20480 1 snd_soc_core
snd_pcm 126976 6 snd_soc_hdmi_codec,snd_soc_meson_axg_tdm_interface,snd_soc_core,snd_soc_meson_axg_fifo,snd_soc_meson_codec_glue,snd_pcm_dmaengine
snd_timer 40960 1 snd_pcm
snd 90112 4 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm
soundcore 16384 1 snd
display_connector 20480 0
ip_tables 32768 0
x_tables 45056 1 ip_tables
autofs4 45056 2
meson_gxl 20480 0
spidev 24576 0
rtc_meson_vrtc 20480 1
realtek 24576 1
axg_audio 77824 13
reset_meson_audio_arb 16384 3
sclk_div 16384 1 axg_audio
clk_phase 16384 1 axg_audio
dwmac_generic 16384 0
dwmac_meson8b 16384 0

‘lsusb’ shows the following information:
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:0811 Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz]
Bus 001 Device 004: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard
Bus 001 Device 003: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse]
Bus 001 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

‘journalctl -u ifup*’ doesn’t show that the wlan interface is even attempted to be brought up.

‘ifup wlan0’ returns the following:
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ifup: failed to bring up wlan0

Many of the posts surrounding this are at least 12 months old, if not older, and everything I have read during all of my troubleshooting has said to not follow threads that are years old with outdated links. I’ve read so many different forums and GitHub pages I have lost track of everything else I have tried. I would just like to have this board recognize this particular adapter. I need this adapter becasue it has a single RPSMA antenna connector and I use it for a class I teach on Wi-Fi antennas. Thanks!

Edit: I have been going through this open issue on GitHub WIFI Realtek RTL8811AU seen by OS, not configurable in dietpi-config · Issue #4387 · MichaIng/DietPi · GitHub but when I get to the workaround that was posted on 3 June 2021 it doesn’t work for me. I know this issue is still listed as open, but I was hoping there had been some updates since the last post 19 Aug 2021.