@mich0111 @Blenky @cardoc Like I already said, it does it on any network.
First board would get a very weak signal -90db and reconnect every 15 seconds
second board gets a strong signal to the wifi, and still reconnects every 15 seconds.
antenna replaced as well, new emmc flashed as well.
The Sovol OS is the problem. I’m not the only one having this issue either.
See other people with the same problem here, Where to file issues regarding the operating system?
Not only that, but its hard to read logs on sv08 max because its being filled with garbage.
sovol linux config has hostapd enabled but incorrectly configured so it’s constantly restarting, producing repeating logs like:
Mar 23 23:02:23 SPI-XI systemd[1]: Starting Access point and authentication server for Wi-Fi and Ethernet…
Mar 23 23:02:23 SPI-XI hostapd[11751]: Configuration file: /etc/hostapd/hostapd.conf
Mar 23 23:02:23 SPI-XI hostapd[11751]: Could not open configuration file ‘/etc/hostapd/hostapd.conf’ for reading.
Mar 23 23:02:23 SPI-XI hostapd[11751]: Failed to set up interface with /etc/hostapd/hostapd.conf
Mar 23 23:02:23 SPI-XI hostapd[11751]: Failed to initialize interface
Mar 23 23:02:23 SPI-XI systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
Mar 23 23:02:23 SPI-XI systemd[1]: hostapd.service: Failed with result ‘exit-code’.
Mar 23 23:02:23 SPI-XI systemd[1]: Failed to start Access point and authentication server for Wi-Fi and Ethernet.
Mar 23 23:02:25 SPI-XI systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 2950.
Mar 23 23:02:25 SPI-XI systemd[1]: Stopped Access point and authentication server for Wi-Fi and Ethernet.
/etc/hostapd/hostapd.conf indeed does not exist. It’s unclear if there’s any reason why hostapd should be enabled in the first place.
every 15 minutes it deletes all but the last 5MiB of journald logs via a cron job running armbian-truncate-logs, even though journald is already configured to retain only 20MiB of logs lmao
shame on sovol for shipping this garbage, wow.