Hi @Jacmo
Make sure you have the mwifiex.conf (you need to add that manually because of the mentioned issue):
colibri-imx8x-06494206:~$ cat /etc/modprobe.d/mwifiex.conf
options mwifiex driver_mode=0x3
The hostapd.conf can be added as explained in the article:
colibri-imx8x-06494206:~$ cat /etc/hostapd.conf
interface=uap0
ssid=test-access-point
hw_mode=g
channel=1
own_ip_addr=192.168.8.1
The hostapd.network can be added as explained in the article as well:
colibri-imx8x-06494206:~$ cat /etc/systemd/network/hostapd.network
[Match]
Name=uap0
[Network]
Address=192.168.8.1/24
DHCPServer=yes
To change the hostapd.service in ‘/lib/systemd/system/hostapd.service’ on the running Torizon instance as explained in the article you need to make a little hack and change the file in the deployed ostree. This should generally be avoided because this is not the intended workflow of ostree, but in this case you can quickly change a little configuration to check if your system would work with that: Instead of changing the hostapd.service direclty in ‘/lib/…’ (which is read-only), you can change it in ‘/ostree/deploy/torizon/deploy/.0/lib/systemd/system/hostapd.service’. After a reboot, it will be replicated to ‘/lib/systemd/system/hostapd.service’.
Now you should be able to run hostapd if the module started properly with the interface uap0 (which randomly happens or not, as described from @jeremias.tx). After booting the module, you can check if there is the required interface with iw dev. If there is no uap0 but an interface called mlan0 there is no other way than reboot and try again currently with the existing known issues TOR-980 and TOR-979.
If this all still doesn’t work, there is most probably a wrong configuration. Could you then send the output of sudo systemctl status hostapd.service and after executing sudo systemctl restart hostapd.service the output of sudo journalctl -xe?
Best regards
Diego