libreELEC 8.2.2 rpi3 and NO wifi channel 13

  • Away from home with rpi3 and Librelec 8.2.2 installed and unable to either see and connect to router with wifi channel set to 13

    (not my router so no access to change channel even for short period)

    I have temp connected to rpi3 in order to check and modify settings that thought would allow/enable channel 13 access on rpi3 but I still have blank "System - LibreELEC - Settings - Connections" window.

    Used following method posted by chewitt but unfortuantely does not seem to work in 8.2.2?

    WiFi Channel 13 not possible on RasPi 3, regional settings doesn't help

    Any ideas/help greatly appreciated.

  • You might need to replace "DE" with the appropriate regdom for wherever you are, i.e. FR for France. Also, don't forget that RPi3 wireless has terrible range. You need to find a way to send us "dmesg" log so we can see what's happening.

  • Yes creating a backup then trying with clean install is an idea.

    Additional Notes just for information.

    I moved rpi3 closer too Wifi Router but this made no improvement to visibity of specific routers 2.4ghz WiFi signal to rpi3.

    Other possible weak Wifi connections in area appeared/dissappeared; but never closest router of interest/need so that why I believed its broadcasting on channel 13 to be main issue. (Checked with wifi anlysyzer app on motog phone)

    I could connect rpi3 to my motog phone acting as wireless mobile hot spot (thats how I connected from another device to get dmesg log) and have/had no problems connecting to router wirelessly at home. (Actually this is when I updated rpi3 manually to 8.2.2 before travelling to visit family etc)

  • chewitt

    With further testing hopefully additional useful information. Essentially I ssh'd into rpi3 when rpi3 & PC both connected to hotspot provided by motog phone. Following is image of networks visible in kodi (along with confirmation of connected to motog hotspot)

    Xx3gq5q.png

    Then running connman commands in ssh and specifically "connmanctl scan wifi" which immediataly updated kodi's view of avaiable networks.

    TSJAIY4.png

    Unfortunately any attempts to complete connection to Freebox-63910C (selecting and entering phass-phrase in kodi) failed and after long wait would drop back and automatically reconnect to kodi (updated view with only motog hotspot visible again?)

    kodi.log and dmesg, Where I can see within kodi.log, failed attempts to connect to Freebox-6391C

    (where I know I was entering wifi password correctly)

    Code
    ERROR: ## LibreELEC Addon ## connman::dbus_error_handler ## ERROR: (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

    Edited once, last by MikeKL (December 27, 2017 at 10:35 PM).

  • I have had the same problem with my raspberry pi zero w.

    After adding country code (Sweden)


    echo "options cfg80211 ieee80211_regdom=SE" > /storage/.config/modprobe.d/cfg80211.conf

    I got after reboot:

    LE821:~ # modprobe -D cfg80211

    insmod /lib/modules/4.9.59/kernel/net/rfkill/rfkill.ko

    insmod /lib/modules/4.9.59/kernel/net/wireless/cfg80211.ko ieee80211_regdom=SE

    LE821:~ #

    Now I am able to connect both to channels 12 and 13

    I guess that you may use any eurpean contry code except "EU"

    Hope this will help.

  • He already tried "FR" which is a valid regdom. It appears to be something else .. but debugging wireless connectivity issues requires rather specialist knowledge of radio properties and without some nice error messages to Google progress will be non-existent.

    MikeKL sprunge.us is offline (and may not return) so can you repost the files to ix.io or pastebin.com?

  • Sprunge.es is up atm, but as it seems to keep going offline, grabbed copies of previous files, here they are on pastebin.com

    kodi.log

    dmesg

    Please Note: I am leaving location where I have been having problems to connect in a few hrs so will not have an opportunity to gather more information or try anything else to achieve a connection at currnet location. (So if I am only one with problem don't worry etc)

    Thought I was getting somewhere with ssh, connman and wifi.config file in /storage/.cache/connman but that may have been something to do with file having incorrect parameters or similar. (did not really know what I was doing, just challenging myself to learn a little more)

    Freebox-63910C.config file contents (Note Name = switched to SSID = <in hex>)

    Code
    [global]
    Name = Freebox-63910C
    Description = Freebox-63910C Wifi service config file
    [service_wifi_Freebox-63910C]
    Type = wifi
    SSID = 46726565626f782d363339313043
    Passphrase = <correct passphrase was inserted here>

    *A in front of Freebox-63910C (connection I wanted to achieve) indicating connman aware of what to do, but with a connection failure result when trying to switch connection via ssh

  • chewitt

    cfg80211.conf must be placed in modprobe.d directory. Check my post again.

    Ask him to send output from "modprobe -D cfg80211" command.

    That will show if value of iee80211_regdom is correctly passed to the kernel module.

  • raspi0w & chewitt , For info this current situation in modprobe.d folder etc

    (not currently in situation/location where I can try again with cfg80211.conf copied to modprobe.d folder)

  • MikeKL, chewitt

    Your output shows that you are missing file cfg80211.conf in directory /storage/.config/modprobe.d/ .

    The consequence is that country code is not passed to kernel and you are using US as a default country code.

    US country code allows only channels 1-11.

    I advise you,

    ssh login in your computer

    Copy and paste following line:

    echo -e "options cfg80211 ieee80211_regdom=DE" > /storage/.config/modprobe.d/cfg80211.conf

    then type

    cat /storage/.config/modprobe.d/cfg80211.conf

    the output should be: options cfg80211 ieee80211_regdom=DE

    reboot your computer

    type modprobe -D cfg80211 

    the output shoud be

    insmod /lib/modules/4.9.59/kernel/net/rfkill/rfkill.ko

    insmod /lib/modules/4.9.59/kernel/net/wireless/cfg80211.ko ieee80211_regdom=DE

    If you are able to see ieee80211_regdom=DE in the second output line, try to connect to your router using GUI