Interesting. I’ve no idea what ‘correct’ is.
Hi,
Any ideas why /etc/default/crda isn’t working and seems to prevent 5ghz being seen even after running the iw commands? If set crda back to default, reboot and run the iw commands; It can see by network and connect.
@sam_nazarko whats the correct setting for: /lib/firmware/config_43455c0.txt
?
Thanks Tom.
Hi,
Yeah but I’m still trying to find an export for ConnMan
Thanks Tom.
Edit: Gets Even weirder now, despite setting gb in local, its actully set to Germany.
$ iw reg get
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
Its connected and working.
Thanks Tom.
I think that’s because the channels are standarised across the EU. Wikipedia says Germany set the rule and it was then adopted by other countries.
Hi,
Yeah just worked it out, bm AP is pushing DE. It’s an ASUS which uses EU, which doesn’t actual exist; so it uses DE instead. Its not easy to change on my AP and from looking online it can be forceed to GB, but cripples the range.
So REGDOMAIN=EU
in /etc/default/crda survives a reboot for me.
Anyone else having an issue, should either just use EU or look for line like this to work out reg code should be:
osmc4k kernel: CFG80211-ERROR) wl_cfg80211_reg_notifier : Set country code DE from 11d AP
Thanks Tom.
Sorry for bringing this up again, but this still does not work for me, still can’t see any channels above 100.
For a while I used channel 64, for being able to use my Vero4k+ but this is not optimal so i have to switch back to channel 112, but here my Vero won’t connect.
I thought maybe the November update made a difference, but sadly no.
I made a clean install and updated to the latest November build, and have REGDOMAIN=GB set in crda
Here is the output of iw re get
osmc@osmc:~$ sudo iw reg get
global
country GB: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
Edit:
Made some further progress, if REGDOMAIN is unset, i can get WIFI above channel 100 to show up, if i run the following commands after each other, if i run them separately it will not work, i have to run both.
sudo iw reg set EU
sudo iw reg set GB
And inspired by @Tom_Doyle, i tried to use rc.local to run these commands during startup, but it result in a sad face during startup, when i run both commands, so tried to add a pause between each command, and it seems to work.
My rc.local looks like this
sudo iw reg set EU
sleep 5
sudo iw reg set GB
It seems to work, but it is not very user friendly, and a very good “out of the box experience” so it would be nice to get this fixed in a future release.
I will look in to it next week. I didn’t have time for this update.
Sam
I will let you know when I’ve made the necessary changes for testing.
Thanks for your patience.
This has now been fixed and is in the staging repository. It will be included in the next update shortly.
Thanks to @thansen_dk for testing and verifying the changes.
Sam
Hi @sam_nazarko
Sorry to say, but the Christmas update broke Wifi channels above Channel 100 again.
Tried the following command I got from you, that fixed it last time.
sudo mv /lib/firmware/config_43455c0.txt /lib/firmware/config.txt
reboot
But it gives me this output.
mv: cannot stat ‘/lib/firmware/config_43455c0.txt’: No such file or directory
As soon as I set my WIFI to a channel under 100 it can see and connect to the WIFI, above 100 it cannot see the SSID.
I am not able to post logs at the moment. due to some addons.
I’ll set the channel below 100 for now, to be able to use my Vero.
Please post logs so I can verify that your system is fully up to date.
Your logs show you have the latest WiFi package
You should have a file called /lib/firmware/config.txt
and it should have these contents:
bcn_timeout=20
kso_enable=0
ccode=ALL
regrev=38
mimo_bw_cap=1
PM=0
Can you check if you have the issue with a fresh install?
Correct, the config.txt is there with the content
It is the same issue, no ssid is shown when wifi channel is set to 100 or above.
The config.txt is there with the correct content
I am connected to my 2,4Ghz wifi for uploading logs.
It’s possible renaming config.txt back to /lib/firmware/config_bcm43455c0_ag.txt is now needed.
Sam
Hi @sam_nazarko
Renaming config.txt to config_bcm43455c0_ag.txt seems to work.
Thank you for your patience
Cheers — I made some changes to the driver and didn’t fully sync these changes.
Should be fixed in the next update and is now fixed in staging.
Cheers
Sam