Kobo Glo: Cannot get WiFi working

[rectagonal]

I had the wierd partition structure mentioned here: #12 and here #14.

Any attempt to create a new ext4 filesystem in partition 1 resulted in no boot. So I opted to resize the existing ext4 partition 1, leaving the 9.5mb of free space at the beginning intact, and just deleted the contents of the existing rootfs with a rm -rf *. I then extracted the rootfs.tar.gz into partition 1.

uBoot uImage rootfs taken from the provided a9bf918_build.

USB, backlight and etc all seem to be working fine except for WiFi.

Any attempts to enable wifi at the GUI result in "Failed to connect to wpa_supplicant control socket: /var/run/wpa_supplicant/eth0"

/var/run/wpa_supplicant does not exist.

lsmod does list brcmfmac

I've extracted the firmware and modules .debs from a9bf918_build release and their contents do appear to be on the sdcard.

uname -a reports a kernel version that matches the /lib/modules folder.

EDIT:

Output of enable-wifi.sh

rfkill: Cannot open RFKILL control device
Could not read interface wlan0 flags: No such device
WEXT: Could not set interface 'wlan0' UP
wlan0: Failed to initialize driver interface

[lgeek]

Is sdio_wifi_pwr also loaded? Could you post the output of dmesg?

[rectagonal]

sdio_wifi_pwr does load, after you attempt to enable wifi. (I got that wrong a sec ago.) will follow up with dmesg.

[rectagonal]

dmesg.txt

Possible relevant bits here:

brcmfmac: brcmf_sdio_get_fw: Unknown chipid 43362 [0]
brcmfmac: brcmf_bus_start: brcmf_sdbrcm_bus_init failed -2
brcmfmac: brcmf_sdio_probe: dongle is not responding
brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
TPS65185 temprature data = 0x18,24

[lgeek]

brcmfmac: brcmf_sdio_get_fw: Unknown chipid 43362 [0]

That's the WiFi driver complaining that it doesn't support the WiFi chipset. However, I'm pretty sure my devices have the same chipset and that it's supported by the brcmfmac driver distributed with okreader (compiled from linux-backports-3.14.22-1 and included in linux-okreader-modules). However, this being a backported driver, it requires the compat kernel module and I don't see any messages about that being loaded in your dmesg output. Can you confirm compat is loaded? I'm not quite sure what's going on at this point TBH. I've had a quick look at the rootfs from a9bf918_build and it seems to contain the right drivers (they're already installed, you don't need the standalone dpkgs).

[rectagonal]

Hrm.

So I confirmed compat.ko was in the /lib/modules/2.6.35.3.-850-gbc67621+ directory

I did a "modprobe compat" and "lsmod" ahead of enabling wifi, and confirmed it was loaded in memory.

Got the error message again. "Failed to connect to wpa_supplicant control socket: /var/run/wpa_supplicant/eth0"

[lgeek]

Sorry, bit of a misunderstanding there. What I was saying is that brcmfmac should require the compat module. So if brcmfmac loaded without automatically causing compat to load, something might be wrong there with the version of brcmfmac you have.

[rectagonal]

Gotcha.

I did a clean restart, enabled wifi through the GUI. Error message recurred.

lsmod reports compat was loaded after I tried to enable wifi. It was not loaded prior.

A list of all currently loaded modules after trying to enable wifi:

sdio_wifi_pwr
brcmfmac
cfg80211
compat
brcmutil
g_file_storage
arcotg_udc

[lgeek]

Hmm. Can you confirm the sha1sum for /lib/modules/2.6.35.3-850-gbc67621+/brcmfmac.ko? It Should be 19f74d084384001f05ec6bf81d5ce7ead61b2aef.

[rectagonal]

It matches freakishly enough.
I did a sha1sum of compat.ko too just to feel useful: 6acf2dff16a41ac3bcd6960913dbda94b9f3f093

[lgeek]

Alright, I'll need to get back to you on this. I'll try to see if any of my Kobos use the same WiFi chipset and check whether it works with that build of okreader. It might take me some time. Please remind me if I don't get back to you in a week or so.

[rectagonal]

Fair enough and thanks! Ill also try and do a complete reinstall tonight, on the offchance ive botched something non-obvious on my end.

[rectagonal]

This problem still persists over here. Were you able to reproduce @lgeek ?

[jdek]

Trying to build this for the Aura H2O.

load.sh:

#!/bin/sh

modprobe sdio_wifi_pwr
usleep 200000
modprobe -r brcmfmac
usleep 200000
modprobe brcmfmac
usleep 200000

DEVPATH="mmc1:0001:2"
echo -n 1 > "/sys/class/firmware/$DEVPATH/loading"
cat "/lib/firmware/brcm/brcmfmac43362-sdio.bin" > "/sys/class/firmware/$DEVPATH/data"
if [ "$?" = 0 ]; then
    echo -n  1 > "/sys/class/firmware/$DEVPATH/loading"
    echo -n -1 > "/sys/class/firmware/$DEVPATH/loading"
fi

Firmware exists:

# find / -name brcmfmac43362-sdio.bin
/lib/firmware/brcm/brcmfmac43362-sdio.bin

Loading fails with Error -2 (ENOENT?).

# ./load.sh
brcmfmac: brcmf_sdio_get_fw: fail to request firmware brcm/brcmfmac43362-sdio.bin (-2)
brcmfmac: brcmf_bus_start: brcmf_sdbrcm_bus_init failed -2
brcmfmac: brcmf_sdio_probe: dongle is not responding
brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...