operating-system
operating-system copied to clipboard
Published
20 hours ago •
home-assistant
home-assistant
wlan0 disabled or not detected on Khadas VIM3
trafficstars
Describe the issue you are experiencing
I tried to use the onboard wifi on the Khadas Vim3, but wlan0 isn't visible in the network parameters or in the ssh terminal. I installed official haos version for khadas vim3 (7.6) with the OOWOW tool from Khadas (note : in OOWOW wlan is enabled and functional). After successful installation of HAOS 7.6, wlan0 isn't present I upgraded then to the latest version of HAOS wlan0 don't appears in network menu
What operating system image do you use?
khadas-vim3 (Khadas VIM3)
What version of Home Assistant Operating System is installed?
10.1
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
- etch a sd card with Khadas OOWOW tool
- write HAOS 7.6 image on the eMMC
- start Home Assistant onboarding and installation
- update to latest version ...
Anything in the Supervisor logs that might be useful for us?
23-05-11 09:23:04 INFO (MainThread) [supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1
23-05-11 09:23:04 INFO (MainThread) [supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1
23-05-11 09:23:04 INFO (MainThread) [supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1
23-05-11 09:23:05 INFO (MainThread) [supervisor.host.services] Updating service information
23-05-11 09:23:05 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-05-11 09:23:05 WARNING (MainThread) [supervisor.host.network] Requested to update interface eth0 which does not exist or is disabled.
23-05-11 09:23:05 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
23-05-11 09:23:05 INFO (MainThread) [supervisor.docker.monitor] Started docker events monitor
23-05-11 09:23:05 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-cli with version 2022.11.0
23-05-11 09:23:05 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
23-05-11 09:23:06 INFO (SyncWorker_1) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/aarch64-hassio-cli with version 2022.11.0 - 172.30.32.5
23-05-11 09:23:06 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-dns with version 2022.04.1
23-05-11 09:23:06 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-05-11 09:23:06 INFO (SyncWorker_0) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/aarch64-hassio-dns with version 2022.04.1 - 172.30.32.3
23-05-11 09:23:06 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
23-05-11 09:23:06 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-audio with version 2023.04.1
23-05-11 09:23:06 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
23-05-11 09:23:07 INFO (SyncWorker_1) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/aarch64-hassio-audio with version 2023.04.1 - 172.30.32.4
23-05-11 09:23:07 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-observer with version 2021.10.0
23-05-11 09:23:07 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-multicast with version 2022.02.0
23-05-11 09:23:07 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
23-05-11 09:23:08 INFO (SyncWorker_0) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/aarch64-hassio-multicast with version 2022.02.0 - Host
23-05-11 09:23:08 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-05-11 09:23:08 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
23-05-11 09:23:08 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/khadas-vim3-homeassistant with version 2023.5.2
23-05-11 09:23:08 INFO (MainThread) [supervisor.os.manager] Detect Home Assistant Operating System 10.1 / BootSlot B
23-05-11 09:23:09 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/45df7312 repository
23-05-11 09:23:09 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/5c53de3b repository
23-05-11 09:23:09 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
23-05-11 09:23:09 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
23-05-11 09:23:09 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/30e576d0 repository
23-05-11 09:23:10 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 75 new - 0 remove
23-05-11 09:23:10 INFO (MainThread) [supervisor.addons] Found 7 installed add-ons
23-05-11 09:23:10 INFO (SyncWorker_4) [supervisor.docker.interface] Attaching to 30e576d0/aarch64-addon-hassio-access-point with version 0.4.6
23-05-11 09:23:10 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/vscode/aarch64 with version 5.5.7
23-05-11 09:23:10 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-mosquitto with version 6.2.1
23-05-11 09:23:10 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-letsencrypt with version 4.12.8
23-05-11 09:23:10 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-configurator with version 5.6.0
23-05-11 09:23:10 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-ssh with version 9.7.0
23-05-11 09:23:10 INFO (SyncWorker_6) [supervisor.docker.interface] Attaching to ghcr.io/esphome/esphome-hassio with version 2023.4.4
23-05-11 09:23:10 INFO (MainThread) [supervisor.backups.manager] Found 18 backup files
23-05-11 09:23:10 INFO (MainThread) [supervisor.discovery] Loaded 2 messages
23-05-11 09:23:10 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-05-11 09:23:10 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
23-05-11 09:23:10 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-05-11 09:23:10 INFO (MainThread) [__main__] Running Supervisor
23-05-11 09:23:10 INFO (MainThread) [supervisor.os.manager] Rauc: B - marked slot kernel.1 as good
23-05-11 09:23:10 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
23-05-11 09:23:10 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 1 add-ons
23-05-11 09:23:11 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-mosquitto with version 6.2.1
23-05-11 09:23:15 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
23-05-11 09:23:16 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 1 add-ons
23-05-11 09:23:16 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-ssh with version 9.7.0
23-05-11 09:23:22 INFO (MainThread) [supervisor.core] Start Home Assistant Core
23-05-11 09:23:22 INFO (SyncWorker_6) [supervisor.docker.interface] Starting homeassistant
23-05-11 09:23:22 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
23-05-11 09:23:29 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
23-05-11 09:23:29 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-05-11 09:23:30 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-05-11 09:23:30 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-05-11 09:23:30 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-05-11 09:23:30 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/mattlongman/Hassio-Access-Point repository
23-05-11 09:23:30 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
23-05-11 09:23:32 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-05-11 09:23:32 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
23-05-11 09:23:32 INFO (MainThread) [supervisor.store] Loading add-ons from store: 75 all - 0 new - 0 remove
23-05-11 09:23:58 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
23-05-11 09:23:58 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 2 add-ons
23-05-11 09:23:58 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/esphome/esphome-hassio with version 2023.4.4
23-05-11 09:23:59 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-configurator with version 5.6.0
23-05-11 09:24:04 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
23-05-11 09:24:04 INFO (MainThread) [supervisor.core] Supervisor is up and running
23-05-11 09:24:04 INFO (MainThread) [supervisor.host.info] Updating local host information
23-05-11 09:24:04 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.MULTIPLE_DATA_DISKS/ContextType.SYSTEM
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
23-05-11 09:24:04 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.IPV4_CONNECTION_PROBLEM/ContextType.SYSTEM
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.NO_CURRENT_BACKUP/ContextType.SYSTEM
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.CREATE_FULL_BACKUP - ContextType.SYSTEM / None
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.NO_CURRENT_BACKUP - ContextType.SYSTEM / None
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
23-05-11 09:24:05 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-05-11 09:24:05 INFO (MainThread) [supervisor.host.services] Updating service information
23-05-11 09:24:05 INFO (MainThread) [supervisor.host.network] Updating local network information
23-05-11 09:24:05 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-05-11 09:24:05 INFO (MainThread) [supervisor.host.manager] Host information reload completed
Anything in the Host logs that might be useful for us?
May 11 07:23:11 homeassistant kernel: eth0: renamed from veth2cd70dc
May 11 07:23:11 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethebc17bd: link becomes ready
May 11 07:23:11 homeassistant kernel: hassio: port 6(vethebc17bd) entered blocking state
May 11 07:23:11 homeassistant kernel: hassio: port 6(vethebc17bd) entered forwarding state
May 11 07:23:11 homeassistant NetworkManager[444]: <info> [1683789791.1579] device (vethebc17bd): carrier: link connected
May 11 07:23:11 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 11 07:23:16 homeassistant systemd[1]: var-lib-docker-overlay2-67ef060d7f1c097e93e82b11c2478eea4b431f97f0e3c79ad2c95cb5b3547cb7\x2dinit-merged.mount: Deactivated successfully.
May 11 07:23:16 homeassistant systemd[1]: mnt-data-docker-overlay2-67ef060d7f1c097e93e82b11c2478eea4b431f97f0e3c79ad2c95cb5b3547cb7\x2dinit-merged.mount: Deactivated successfully.
May 11 07:23:16 homeassistant kernel: hassio: port 7(vethfe2cf7f) entered blocking state
May 11 07:23:16 homeassistant kernel: hassio: port 7(vethfe2cf7f) entered disabled state
May 11 07:23:16 homeassistant kernel: device vethfe2cf7f entered promiscuous mode
May 11 07:23:16 homeassistant kernel: kauditd_printk_skb: 65 callbacks suppressed
May 11 07:23:16 homeassistant kernel: audit: type=1700 audit(1683789796.398:196): dev=vethfe2cf7f prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
May 11 07:23:16 homeassistant kernel: audit: type=1300 audit(1683789796.398:196): arch=c00000b7 syscall=206 success=yes exit=40 a0=c a1=4001024e70 a2=28 a3=0 items=0 ppid=1 pid=511 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
May 11 07:23:16 homeassistant kernel: audit: type=1327 audit(1683789796.398:196): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
May 11 07:23:16 homeassistant NetworkManager[444]: <info> [1683789796.4051] manager: (vetha56440a): new Veth device (/org/freedesktop/NetworkManager/Devices/19)
May 11 07:23:16 homeassistant NetworkManager[444]: <info> [1683789796.4101] manager: (vethfe2cf7f): new Veth device (/org/freedesktop/NetworkManager/Devices/20)
May 11 07:23:16 homeassistant dockerd[511]: time="2023-05-11T07:23:16.425859500Z" level=warning msg="Failed to delete conntrack state for 172.30.33.1: invalid argument"
May 11 07:23:16 homeassistant systemd[1]: Started libcontainer container 297baa583ccd27d7f49fdea249aa741bf4e7d4bc5b6b9eb7cf902887e0a0de96.
May 11 07:23:16 homeassistant kernel: audit: type=1334 audit(1683789796.563:197): prog-id=46 op=LOAD
May 11 07:23:16 homeassistant kernel: audit: type=1334 audit(1683789796.565:198): prog-id=47 op=LOAD
May 11 07:23:16 homeassistant kernel: audit: type=1300 audit(1683789796.565:198): arch=c00000b7 syscall=280 success=yes exit=15 a0=5 a1=4000135700 a2=78 a3=0 items=0 ppid=2912 pid=2923 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:16 homeassistant kernel: audit: type=1327 audit(1683789796.565:198): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F32393762616135383363636432376437663439666465613234
May 11 07:23:16 homeassistant kernel: audit: type=1334 audit(1683789796.565:199): prog-id=48 op=LOAD
May 11 07:23:16 homeassistant kernel: audit: type=1300 audit(1683789796.565:199): arch=c00000b7 syscall=280 success=yes exit=17 a0=5 a1=4000135490 a2=78 a3=0 items=0 ppid=2912 pid=2923 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:16 homeassistant kernel: audit: type=1327 audit(1683789796.565:199): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F32393762616135383363636432376437663439666465613234
May 11 07:23:16 homeassistant kernel: eth0: renamed from vetha56440a
May 11 07:23:16 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfe2cf7f: link becomes ready
May 11 07:23:16 homeassistant kernel: hassio: port 7(vethfe2cf7f) entered blocking state
May 11 07:23:16 homeassistant kernel: hassio: port 7(vethfe2cf7f) entered forwarding state
May 11 07:23:16 homeassistant NetworkManager[444]: <info> [1683789796.9411] device (vethfe2cf7f): carrier: link connected
May 11 07:23:22 homeassistant systemd[1]: Started libcontainer container c7e8aa0e304fddcec5c2625d932b56418eb5b83a6ea5c7f5df7df51ba2baa6a0.
May 11 07:23:22 homeassistant kernel: kauditd_printk_skb: 29 callbacks suppressed
May 11 07:23:22 homeassistant kernel: audit: type=1334 audit(1683789802.249:211): prog-id=50 op=LOAD
May 11 07:23:22 homeassistant kernel: audit: type=1300 audit(1683789802.249:211): arch=c00000b7 syscall=280 success=yes exit=14 a0=5 a1=4000137700 a2=78 a3=0 items=0 ppid=3160 pid=3171 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:22 homeassistant kernel: audit: type=1327 audit(1683789802.249:211): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F63376538616130653330346664646365633563323632356439
May 11 07:23:22 homeassistant kernel: audit: type=1334 audit(1683789802.249:212): prog-id=51 op=LOAD
May 11 07:23:22 homeassistant kernel: audit: type=1300 audit(1683789802.249:212): arch=c00000b7 syscall=280 success=yes exit=16 a0=5 a1=4000137490 a2=78 a3=0 items=0 ppid=3160 pid=3171 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:22 homeassistant kernel: audit: type=1327 audit(1683789802.249:212): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F63376538616130653330346664646365633563323632356439
May 11 07:23:22 homeassistant kernel: audit: type=1334 audit(1683789802.249:213): prog-id=51 op=UNLOAD
May 11 07:23:22 homeassistant kernel: audit: type=1334 audit(1683789802.250:214): prog-id=50 op=UNLOAD
May 11 07:23:22 homeassistant kernel: audit: type=1334 audit(1683789802.250:215): prog-id=52 op=LOAD
May 11 07:23:22 homeassistant kernel: audit: type=1300 audit(1683789802.250:215): arch=c00000b7 syscall=280 success=yes exit=14 a0=5 a1=4000137960 a2=78 a3=0 items=0 ppid=3160 pid=3171 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:34 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 11 07:23:35 homeassistant kernel: kauditd_printk_skb: 1 callbacks suppressed
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789814.999:216): prog-id=14 op=UNLOAD
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789814.999:217): prog-id=13 op=UNLOAD
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789814.999:218): prog-id=12 op=UNLOAD
May 11 07:23:35 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789815.288:219): prog-id=25 op=UNLOAD
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789815.288:220): prog-id=24 op=UNLOAD
May 11 07:23:35 homeassistant kernel: audit: type=1334 audit(1683789815.288:221): prog-id=23 op=UNLOAD
May 11 07:23:58 homeassistant systemd[1]: var-lib-docker-overlay2-8e272f71dcfcf953f861454d5af57b85aba603fcc4409e45443dc3e785f71cc7\x2dinit-merged.mount: Deactivated successfully.
May 11 07:23:58 homeassistant systemd[1]: mnt-data-docker-overlay2-8e272f71dcfcf953f861454d5af57b85aba603fcc4409e45443dc3e785f71cc7\x2dinit-merged.mount: Deactivated successfully.
May 11 07:23:58 homeassistant systemd[1]: Started libcontainer container 963ed6a9ef76cc80af54b1bbe692470ebc0baca3adb01c3df87fb9887488239a.
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.519:222): prog-id=53 op=LOAD
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.520:223): prog-id=54 op=LOAD
May 11 07:23:58 homeassistant kernel: audit: type=1300 audit(1683789838.520:223): arch=c00000b7 syscall=280 success=yes exit=15 a0=5 a1=400018d700 a2=78 a3=0 items=0 ppid=3649 pid=3660 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:58 homeassistant kernel: audit: type=1327 audit(1683789838.520:223): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F39363365643661396566373663633830616635346231626265
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.520:224): prog-id=55 op=LOAD
May 11 07:23:58 homeassistant kernel: audit: type=1300 audit(1683789838.520:224): arch=c00000b7 syscall=280 success=yes exit=17 a0=5 a1=400018d490 a2=78 a3=0 items=0 ppid=3649 pid=3660 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
May 11 07:23:58 homeassistant kernel: audit: type=1327 audit(1683789838.520:224): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F39363365643661396566373663633830616635346231626265
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.521:225): prog-id=55 op=UNLOAD
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.521:226): prog-id=54 op=UNLOAD
May 11 07:23:58 homeassistant kernel: audit: type=1334 audit(1683789838.521:227): prog-id=56 op=LOAD
May 11 07:23:58 homeassistant kernel: hassio: port 8(vethd827133) entered blocking state
May 11 07:23:58 homeassistant kernel: hassio: port 8(vethd827133) entered disabled state
May 11 07:23:58 homeassistant kernel: device vethd827133 entered promiscuous mode
May 11 07:23:58 homeassistant NetworkManager[444]: <info> [1683789838.8549] manager: (veth09335f5): new Veth device (/org/freedesktop/NetworkManager/Devices/21)
May 11 07:23:58 homeassistant NetworkManager[444]: <info> [1683789838.8592] manager: (vethd827133): new Veth device (/org/freedesktop/NetworkManager/Devices/22)
May 11 07:23:58 homeassistant dockerd[511]: time="2023-05-11T07:23:58.899520425Z" level=warning msg="Failed to delete conntrack state for 172.30.33.2: invalid argument"
May 11 07:23:59 homeassistant systemd[1]: Started libcontainer container 7c20180f6de08db4da5e5b11becff2479f070603642fe605e158df31d3ef201c.
May 11 07:23:59 homeassistant kernel: eth0: renamed from veth09335f5
May 11 07:23:59 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd827133: link becomes ready
May 11 07:23:59 homeassistant kernel: hassio: port 8(vethd827133) entered blocking state
May 11 07:23:59 homeassistant kernel: hassio: port 8(vethd827133) entered forwarding state
May 11 07:23:59 homeassistant NetworkManager[444]: <info> [1683789839.5432] device (vethd827133): carrier: link connected
May 11 07:24:04 homeassistant kernel: kauditd_printk_skb: 41 callbacks suppressed
May 11 07:24:04 homeassistant kernel: audit: type=1334 audit(1683789844.965:243): prog-id=61 op=LOAD
May 11 07:24:04 homeassistant kernel: audit: type=1334 audit(1683789844.966:244): prog-id=62 op=LOAD
May 11 07:24:04 homeassistant kernel: audit: type=1334 audit(1683789844.966:245): prog-id=63 op=LOAD
May 11 07:24:04 homeassistant systemd[1]: Starting Hostname Service...
May 11 07:24:05 homeassistant systemd[1]: Started Hostname Service.
May 11 07:24:05 homeassistant kernel: audit: type=1334 audit(1683789845.341:246): prog-id=64 op=LOAD
May 11 07:24:05 homeassistant kernel: audit: type=1334 audit(1683789845.341:247): prog-id=65 op=LOAD
May 11 07:24:05 homeassistant kernel: audit: type=1334 audit(1683789845.342:248): prog-id=66 op=LOAD
May 11 07:24:05 homeassistant systemd[1]: Starting Time & Date Service...
May 11 07:24:05 homeassistant systemd[1]: Started Time & Date Service.
May 11 07:24:35 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.363:249): prog-id=63 op=UNLOAD
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.363:250): prog-id=62 op=UNLOAD
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.363:251): prog-id=61 op=UNLOAD
May 11 07:24:35 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.683:252): prog-id=66 op=UNLOAD
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.683:253): prog-id=65 op=UNLOAD
May 11 07:24:35 homeassistant kernel: audit: type=1334 audit(1683789875.683:254): prog-id=64 op=UNLOAD
May 11 07:25:55 homeassistant kernel: audit: type=1334 audit(1683789955.337:255): prog-id=67 op=LOAD
May 11 07:25:55 homeassistant systemd-timesyncd[503]: Network configuration changed, trying to establish connection.
May 11 07:25:55 homeassistant systemd[1]: Started Journal Gateway Service.
May 11 07:25:55 homeassistant systemd-timesyncd[503]: Contacted time server [2606:4700:f1::123]:123 (time.cloudflare.com).
May 11 07:25:55 homeassistant systemd-journal-gatewayd[4261]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
System information
System Information
| version | core-2023.5.2 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.11 |
| os_name | Linux |
| os_version | 6.1.25 |
| arch | aarch64 |
| timezone | Europe/Paris |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 4972 |
| Installed Version | 1.32.1 |
| Stage | running |
| Available Repositories | 1283 |
| Downloaded Repositories | 3 |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 10.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.04.1 |
| agent_version | 1.5.1 |
| docker_version | 23.0.3 |
| disk_total | 27.9 GB |
| disk_used | 8.3 GB |
| healthy | true |
| supported | true |
| board | khadas-vim3 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Mosquitto broker (6.2.1), ESPHome (2023.4.4), Terminal & SSH (9.7.0), File editor (5.6.0), Let's Encrypt (4.12.8), Studio Code Server (5.5.7), Hass.io Access Point (0.4.6) |
Dashboards
| dashboards | 2 |
|---|---|
| resources | 2 |
| views | 1 |
| mode | storage |
Recorder
| oldest_recorder_run | 8 mai 2023 à 07:23 |
|---|---|
| current_recorder_run | 11 mai 2023 à 09:23 |
| estimated_db_size | 78.23 MiB |
| database_engine | sqlite |
| database_version | 3.40.1 |
Additional information
Log from Hass.io Access Point
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started Starting Hass.io Access Point Addon Error: Device 'wlan0' not found. ip: ioctl 0x8913 failed: No such device ip: ioctl 0x8913 failed: No such device ifconfig: SIOCSIFADDR: No such device Could not read interface wlan0 flags: No such device nl80211: Driver does not support authentication/association or connect commands nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Could not read interface wlan0 flags: No such device nl80211 driver initialization failed. wlan0: interface state UNINITIALIZED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped
I had the same problem with directly install 10.3 on VIM3 via oowow and also with installing 7.6 via oowow internet source and doing the updating steps. No WLAN and also no NVME SSD (port mode was set to "PCIe" and worked with Khadas Ubuntu-Server 22.04/6.1 image).
It's a pitty that NVME- and WLAN-support is not available even with the actual version (10.3), so 2 month and one major update later. At the end it's called "officially supported", but even the basics (WLAN and PCIe) don't work at all.
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
The issue is a driver problem as described here .
I still wonder that this problem exists at all. There was no HW-change for VIM3 until now. So the WLAN-problem should exist still from beginning of integrating this board to the HA board list.
At the end the board is too less used for priorized issue fixing. And the board is not working properly because there is no issue fixing. And nobody is using this board (maybe) because it is not fixed in basic issues like WLAN or PCIe-SSD, because there is no issue fixing, because of not priorized.
So there is no way out. This board is slowly dying within HA board list.
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I saw on the last update of HAOS, that some things have been done for Khadas, but after installation my wlan really don't want to exist.
I saw on the last update of HAOS, that some things have been done for Khadas, but after installation my wlan really don't want to exist.
This is standard ARM- and HA-stuff. Khadas specific support is dead. It would be good to communicate that. So, that everything is clear and everybody knows that and don't walk into that "trap".
Personally I tested a lot of boards for HA. And at the end an x86-64 Intel N100 board is actually in 2023/2024 the best solution (in my opinion).
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.