Have not done much with tc,but imho there should be the qos classes and routing all to best-effort by default.
Regarding ap0,afair it was not suggested anywhere recreating the device or disable it…create it once and use…setting state multiple times by echo will lead to unstable/undefined behaviour. Why do you need it?
I don’t mean recreating device.
In my case i can’t restart hostapd, it restarts but doesn’t work. In general i don’t need to restart it, but looks like it’s a driver issue, as other wifi devices lets to restart hostapd and continue to work. In case of new setup it can be very useful: change password or channel.
Afair this was happening also in earlier versions of driver. But none had an idea why this happen. We have no support for the code which is large and dirty. a few users like lexa2 helped me to get it working in newer kernelversions or in better shape.
I had kind-a-fixed driver code to be able to build it as a module but if I recall correctly it wasn’t providing much in terms of stability or alike. Problem was that having driver loaded as a module was mostly a one way road: attempts to unload and reload it might end up in kernel panics or in kernel memory corruption manifesting in things like sudden in-memory file system structures corruption with a subsequent loss of the data on the drive as soon as kernel decides to write corrupted structures to the disk. I hadn’t had any chance to work on anything R2 related since Nov 2019 so can’t provide you with more info than this.
i hang here on converting mgmt_frame_register to update_mgmt_frame_registrations callbacks
i had already replaced the struct-entry and the function-headers, but i do not know how to get missing frame_type and reg resolved. Can i get the fields back out of the update-param? other drivers callbacks got completely rewritten, so i have no clue what to change
So we are still in the bits 4-7 (lower 4 bits zero which are shifted away in new version)…4=0100,D=1101, so it looks like it is a redefinition of the stypes (with combination)…if we shift back the stypes it can work…but because of combination of multiple registrations this can be wrong
And the new update-callback is called once and not like the old callback for each wdev->mgmt_registrations
I guess we need to loop again through all devs and regs
Ok this weekend I tested the 5.8-rc branch and have some preliminary results:
I am running ArchlinuxARM and I’ve built the kernel in qemu on the same filesystem as I am running on the board.
[root@alarm ~]# uname -a
Linux alarm 5.8.0-rc4-bpi-r2+ #1 SMP Sat Jul 18 01:46:19 CEST 2020 armv7l GNU/Linux
So I’ve managed to start the AP, connect and route my connection to the internet. Very nice! Stopping hostapd and restarting it is not enough to make the AP reappear, but I’ve read before this is a known issue. At least a reboot fixes it.
More worrying is that i get intermittent crashes on several systemd services with various stacktraces:
[ 319.167468] systemd[1]: systemd-logind.service: Killing process 378 (systemd-logind) with signal SIGABRT.
[ 319.204724] systemd[1]: systemd-networkd.service: Killing process 363 (systemd-network) with signal SIGABRT.
[ 319.268033] systemd[1]: systemd-udevd.service: Killing process 356 (systemd-udevd) with signal SIGABRT.
Take a look at my wifi.sh. i make a “echo 0 >wmtdevice” to reset the combo-chip.
For the crashes i have no idea yet…i had not seen them before.did you modified the config? How long had you your device running? Was that after the hostapd restart?
it looks like you don’t have the config-file…i did a basic patch that the kernel crashes not if this is missing, but maybe there is another access anywhere which affects your systemd. could you try adding the file in this location? it should not return with -2…the last message is ok, but before it looks wrong
Yes that works, after this hostapd can be restarted:
echo 0 > /dev/wmtWifi
echo A > /dev/wmtWifi
I didn’t have that file, after I added it that particular error disappeared and some new ones appear:
[ 37.094342] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6620.defAnt'.
[ 37.110249] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6628.defAnt'.
[ 37.117693] [WMT-CONF][E]wmt_conf_parse_pair(323):unknown field 'mt6630.defAnt'.
It doesn’t seem important as WiFi just works.
I didn’t have time yet to look into the systemd issues, however I am sure they are unrelated to WiFi. I frequently get crashes, for example after login, when running ip addr, doing CTRL+C, or just doing nothing. The system keeps running without further issues, but it doesn’t give a lot of confidence with important services are crashing all the time.
My kernel config is just your config: mt7623n_evb_fwu_defconfig, no changes. If you are interested you can try my built kernel + modules. I will investigate more myself later.
