Closed current02 closed 3 months ago
@current02 Could you try upgrade your firmware from recovery to latest global stable?
@barni2000 yes, but it's not works, At the same time, I tried my old router that was connected no problem, which made me feel like a driver worked incompatibility,.
@barni2000 yes, but it's not works, At the same time, I tried my old router that was connected no problem, which made me feel like a driver worked incompatibility,.
than i think problem is in wcn36xx i could try search for some workaround. Maybe you could try change some settings in your router until then.
Yes at first I suspected it was the router, I thought it was the encryption, but I used Android sharing and no-secret Settings, he still didn't work, just showing the connection, but ping and other tools didn't working, How can I know the details? I'm not very good at that. I noticed that the driver matches WCN3620 but actually it is WCN3615, I didn't find this information, incidentally, the original Android system is no problem, I check the official open source system they use a very old kernel, which is a little difficult for me
[ 1910.857032] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 1910.900750] wcn36xx: ERROR SMD_EVENT (312) not supported [ 1912.301049] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 1912.351653] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.387840] wlan0: authenticated [ 1912.391713] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.415758] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 1912.450316] wlan0: associated [ 2063.957619] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2064.038210] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2064.538367] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 2064.588417] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.624683] wlan0: authenticated [ 2064.629321] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.653581] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 2064.688110] wlan0: associated [ 2077.123948] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2077.170128] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2108.467347] wlan0: authenticate with 90:de:80:73:bb:46 [ 2108.467382] wlan0: No basic rates, using min rate instead [ 2108.516509] wlan0: send auth to 90:de:80:73:bb:46 (try 1/3) [ 2108.518806] wlan0: authenticated [ 2108.521590] wlan0: associate with 90:de:80:73:bb:46 (try 1/3) [ 2108.526251] wlan0: RX AssocResp from 90:de:80:73:bb:46 (capab=0x1431 status=0 aid=1) [ 2108.526274] wlan0: No basic rates, using min rate instead [ 2108.559832] wlan0: associated
Yes at first I suspected it was the router, I thought it was the encryption, but I used Android sharing and no-secret Settings, he still didn't work, just showing the connection, but ping and other tools didn't working, How can I know the details? I'm not very good at that. I noticed that the driver matches WCN3620 but actually it is WCN3615, I didn't find this information, incidentally, the original Android system is no problem, I check the official open source system they use a very old kernel, which is a little difficult for me
[ 1910.857032] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 1910.900750] wcn36xx: ERROR SMD_EVENT (312) not supported [ 1912.301049] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 1912.351653] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.387840] wlan0: authenticated [ 1912.391713] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.415758] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 1912.450316] wlan0: associated [ 2063.957619] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2064.038210] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2064.538367] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 2064.588417] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.624683] wlan0: authenticated [ 2064.629321] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.653581] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 2064.688110] wlan0: associated [ 2077.123948] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2077.170128] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2108.467347] wlan0: authenticate with 90:de:80:73:bb:46 [ 2108.467382] wlan0: No basic rates, using min rate instead [ 2108.516509] wlan0: send auth to 90:de:80:73:bb:46 (try 1/3) [ 2108.518806] wlan0: authenticated [ 2108.521590] wlan0: associate with 90:de:80:73:bb:46 (try 1/3) [ 2108.526251] wlan0: RX AssocResp from 90:de:80:73:bb:46 (capab=0x1431 status=0 aid=1) [ 2108.526274] wlan0: No basic rates, using min rate instead [ 2108.559832] wlan0: associated
WCN3620 and WCN3615 is almost the same i think the problem is in the mainline driver, i had similar issues sometimes with WCN3660b and WCN3680. You could try build 6.6.0/main branch
Ok, thanks for your advice, incidentally this system is cool, it would be exciting to be compatible with glibc, I have the latest news that will reply to you, near time busy with work may delay a while
Yes at first I suspected it was the router, I thought it was the encryption, but I used Android sharing and no-secret Settings, he still didn't work, just showing the connection, but ping and other tools didn't working, How can I know the details? I'm not very good at that. I noticed that the driver matches WCN3620 but actually it is WCN3615, I didn't find this information, incidentally, the original Android system is no problem, I check the official open source system they use a very old kernel, which is a little difficult for me
[ 1910.857032] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 1910.900750] wcn36xx: ERROR SMD_EVENT (312) not supported [ 1912.301049] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 1912.351653] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.387840] wlan0: authenticated [ 1912.391713] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 1912.415758] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 1912.450316] wlan0: associated [ 2063.957619] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2064.038210] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2064.538367] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 2064.588417] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.624683] wlan0: authenticated [ 2064.629321] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 2064.653581] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc01 status=0 aid=2) [ 2064.688110] wlan0: associated [ 2077.123948] wlan0: deauthenticating from 9c:9d:7e:64:0c:65 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2077.170128] wcn36xx: ERROR SMD_EVENT (312) not supported [ 2108.467347] wlan0: authenticate with 90:de:80:73:bb:46 [ 2108.467382] wlan0: No basic rates, using min rate instead [ 2108.516509] wlan0: send auth to 90:de:80:73:bb:46 (try 1/3) [ 2108.518806] wlan0: authenticated [ 2108.521590] wlan0: associate with 90:de:80:73:bb:46 (try 1/3) [ 2108.526251] wlan0: RX AssocResp from 90:de:80:73:bb:46 (capab=0x1431 status=0 aid=1) [ 2108.526274] wlan0: No basic rates, using min rate instead [ 2108.559832] wlan0: associated
WCN3620 and WCN3615 is almost the same i think the problem is in the mainline driver, i had similar issues sometimes with WCN3660b and WCN3680. You could try build 6.6.0/main branch
emm... it's seem not working...
[ 26.505988] cpu cpu0: Failed to set OPP config [ 31.230259] zram: Added device: zram0 [ 32.078401] pactl[4929]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set [ 32.248619] wlan0: deauthenticated from 9c:9d:7e:64:0c:65 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT) [ 32.328055] wcn36xx: ERROR SMD_EVENT (312) not supported [ 32.594164] q6asm-dai c200000.remoteproc:smd-edge:apr:service@7:dais: command[0x10dac] not expecting rsp [ 32.594197] q6asm-dai c200000.remoteproc:smd-edge:apr:service@7:dais: command[0x10dac] not expecting rsp [ 32.594207] q6asm-dai c200000.remoteproc:smd-edge:apr:service@7:dais: command[0x10dac] not expecting rsp [ 32.594326] q6asm-dai c200000.remoteproc:smd-edge:apr:service@7:dais: command[0x10dac] not expecting rsp [ 33.474075] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 33.523374] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 33.559662] wlan0: authenticated [ 33.563224] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 33.587560] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc11 status=0 aid=4) [ 33.622237] wlan0: associated [ 36.575845] cpu cpu0: Failed to set OPP config [ 36.575984] platform qcom-cpufreq-nvmem: deferred probe pending [ 37.718737] wlan0: deauthenticated from 9c:9d:7e:64:0c:65 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT) [ 37.797265] wcn36xx: ERROR SMD_EVENT (312) not supported [ 38.079761] q6asm-dai c200000.remoteproc:smd-edge:apr:service@7:dais: command[0x10bdb] not expecting rsp [ 38.821588] wlan0: authenticate with 9c:9d:7e:64:0c:65 [ 38.870503] wlan0: send auth to 9c:9d:7e:64:0c:65 (try 1/3) [ 38.906958] wlan0: authenticated [ 38.911635] wlan0: associate with 9c:9d:7e:64:0c:65 (try 1/3) [ 38.935991] wlan0: RX AssocResp from 9c:9d:7e:64:0c:65 (capab=0xc11 status=0 aid=4) [ 38.970691] wlan0: associated [ 45.058982] wlan0: deauthenticated from 9c:9d:7e:64:0c:65 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT) [ 45.096299] wcn36xx: ERROR SMD_EVENT (312) not supported xiaomi-ysl:~$ uname -a Linux xiaomi-ysl 6.6.0-postmarketos-qcom-msm8953 #1 SMP PREEMPT Sun Dec 3 14:58:24 UTC 2023 aarch64 Linux
I have the same or simillar issue too on xiaomi-markw. Sometimes I can't connect to wifi until I come very close to my router. If I remember correctly, it is a timeout error too. This bug can make the system unresponsive for some time while it tries to connect (I can't open new windows, terminal commands freeze with blinking cursor) and even crash wifi and bluetooth (wifi and bt disappear from settings and then appears again after a few seconds)
Hi @current02,
Is this still issue with 6.8.2?