-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve autochannel selection #266
Comments
hi, you can set rt-n56u/trunk/proprietary/rt_wifi/rtpci/5.0.3.0/mt7615/embedded/common/cmm_profile.c Line 3506 in 97bb560
rt-n56u/trunk/proprietary/rt_wifi/rtpci/4.4.2.1/mt7615/embedded/common/cmm_profile.c Line 4237 in 97bb560
|
hi @hanwckf, i will hardcode in '3' to see what happens. i have a few more questions. i noticed in 4.4.2.1, that the radios would do calibration before finishing initialisation, like this for 2ghz:
and for 5ghz:
but i do not se that in 5.x. is this because the code did not force autochannelsel mode = 3? i will test this mode today and report back if calibration happens. i just wanted to know why in 5.x it is not there. i have COC enabled so i wanted to know. also: is there any way to improve performance? right now i am using 2012 mac pro and wireless performance seems to be stuck around 200 MBps on 5ghz, and much less for 2ghz. i was hoping you could provide some insight. here is my 2ghz config file:
and my 5ghz config file:
|
one more thing @hanwckf: is there any way to improve iw priv interface for txpower? it seems very difficult to increase txpower for radios using simple command. i know iwpriv set TxPower= is only percentage. i was hoping for good instruction on how to increase txpower for entire radio instead of picking OFDM,HT, etc using SetTxPwrManual. |
hi @hanwckf, i tried setting mode to 3 but now i'm getting an "out of range" because i guess it sets channel=0 when doing autochannelselect mode. not sure why this would confuse driver
|
oh another thing @hanwckf, sometimes i get this error reported by the AP when a client tries to connect:
sometimes it happens, not often. i usually have to restart the client or something to fix itl, just wondering how i can minimise this problem. |
Are you using ddwrt instead of Padavan mantained by me or Yonsm? The AutoChannelSelection works well in Padavan with 4.4.2.1 and 5.0.x.0 drivers. Also, the performance of MT7615 is similar to stock firmware, it was tested by many users, you can re-flash to stock firmware and compare it, or try more devices to test performance. As for the error message about PMF, I never seen that message in Padavan. It seems like something about WPA3? |
hi @hanwckf, mysteriously, it is no longer there! i hope @Yonsm can chime in. i do remember his commit message being "adding latest driver' and it said 5.0.4.0. what i will say is, the code does not seem much different from your 5.0.3.0 after the changes. so i know for sure it's the latest driver. regarding what firmware: yesi 'm using dd-wrt but i'm the builder of this fw. dd-wrt has switched over to mt76 which still has many problems. you can find my firmware here: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1095476#1095476 i do not think padavan supports teh DIR-882/878. the only change i made to the coe for the driver is removing L1 profile support, because i just don't like it. i agree performance should be better. i have checked out your driver and i will try it out, but given that chips/mt7615.c is not different from each version, i doubt performance will be better. are there some settings in the dat file that i am missing? and regarding autochannel selection, did you see my paste above showing that setting the Alg to 3 does not work? it is strange. i will try your version and hope for much better results. |
@hanwckf the reason i removed l1profile integration is because mt_wifi tries to open it when the driver first starts, and if it fails, it won't try to open the files again. in DD-wrt, we make custom dat files during init process of OS. so the driver needs to 'wait' before bringing radios up for first time. i will spend more time in next few days trying to integrate l1profile. maybe that is the problem. i believe you when you say rated speeds should be achievable with this fw. |
hey buddies (@hanwckf and @Yonsm), turns out l1profile was the reason autochannel select was not working! weird! i did manage to integrate it properly this time. i didn't like l1profile introduction when mt_wifi 5.x came out so i worked around it. i guess that was reason autochannel select was not working. i am hoping performance may be better now, but i am not sure. also: is it possible mixing ram codes was problem? i mixed ramcodes of latest openwrt mt76 driver and proprietary driver, because i wanted dates to be "new" (lol). is it possible mixing these ramcodes caused problems? here's full boot log with same DAT file as before. i expect high performance now, friends! no excuse! you know this, it's chinese way!1
|
ok with full log i have one more question @hanwckf @Yonsm: is ATE_SUPPORT important? in config file you call it 'testing', but it seems more important than that. it is 'fat'. it adds 20 blocks to image. please explain what it does. i disable it because it's fat, and RealTek's business, 'fat' gets you fired. it's unacceptable. think of struggles of putting integrated sound on motherboard in late 90s. driver only does so much. answer appreciated, ty. /signed ATE_MODE sCeptic |
i will close this issue as the main topic at hand has been resolved, however i would encourage further discussion even with this status. |
* Delete AdGuardHome * adguard home bump to v0.102.0
* Delete AdGuardHome * adguard home bump to v0.102.0
hello @hanwckf,
firstly, as i wrote to @Yonsm on QQ, i am praying for all chinese to be in good health and spirits during these times. we would not have this great mt7615 driver if not for your hard work, and that requires you to be healthy. keep your spirits up!
now, back to business.
auto channel selection for 5 GHz is not very good. it always chooses channel 36.
i think in previous commits somewhere, you did make change to autochannel selection. i can't find this commit right now, but i know this change was intended to improve auto channel selection. it still has not improved much.
maybe i am missing something? config file has AUTOCHANNELSELECT=1 or 2, same result.
thx
The text was updated successfully, but these errors were encountered: