Replies: 3 comments 3 replies
-
The "Init network" part of the startup simply initializes ("turns on") the network adaptor, it does not include connection/Wi-Fi association or DHCP - that all happens much later, in the background. That's why it appears to be fast. You will see an IP address pop up on the LCD, usually less than ~1 minute after booting if the network is successfully connected. If you want to view logs in real-time and ensure that Wi-Fi is connecting and that DHCP is being attempted, follow the "Reading mt32-pi's logs" from the troubleshooting section of the wiki. You will need an HDMI monitor. |
Beta Was this translation helpful? Give feedback.
-
Thank you - that helped finding my problem. Unsurprisingly, it was in front of the screen 😉 |
Beta Was this translation helpful? Give feedback.
-
I'm on mt32-pi 0.12.1 @RPI 3A+ . Wifi didn't work so I used hdmi debug kernels and found out: 00:00:02.81 wpa: Line 1: unknown global field 'ctrl_interface=/run/wpa_supplicant'. I removed line ctrl_interface=/run/wpa_supplicant from wpa_supplicant.conf and now wifi seems to be working but I guess this needs to be fixed in a proper way. |
Beta Was this translation helpful? Give feedback.
-
Just tried to enable Wi-Fi on my 3A+ (mt32-pi.cfg and wpa_supplicant.conf). Pretty sure the changes are correct.
When booting w/ verbose on, starting network is amazingly quick (dhcp!) and I don't have network.
how can i further debug that? apparently something goes wrong but i have no idea what it could be.
Beta Was this translation helpful? Give feedback.
All reactions