Quote:
Originally Posted by ryt
Hello!
I installed KSM 8 and the patch KSM08_ext_aura_one_etc_04c you proposed on top of it.
Note that when I installed the patch, I took the KSM 8 archive (delivered with this thread), patched it with the archive delivered on the patch thread on my laptop and then moved the whole archive to my device.
I did again the operation a second time, but taking only the KoboRoot.tgz from the patch (without patching the KoboRoot directory delivered with this thread) which is what you expect us to do.
I assume both operation end up with the same result.
|
This is my assumption too. When you installed the patch-KoboRoot.tgz, you did select "install update" (and not "install partial update"). Right? (But this should not make a difference anyway, if the patching on the laptop was successful.)
Quote:
Originally Posted by ryt
I have an issue with the wifi.
Even, when I connect directly to Nickel without logging first to KSM, it keeps searching for a network without finding any whereas the wifi is said to be activated.
It does basically the same in KSM, no wifi network is found.
My device is new, so I'm wondering whether it comes from the device or from the fact that I installed KSM 8.
So here is my question:
Can KSM affect anyhow the wifi module of Nickel when logged directly to Nickel without passing through KSM?
|
A potential point of error is that the variable WIFI_MODULE does not have the correct value (on the Aura One the value should be "8189fs"). This would happen if the rcS file was not replaced by the patched version.
In order to see which rcS is on your device, you can select "tools" > "backup and restore" > "restore rcS.sh." You can than find a copy of the rcS on the user partition (.adds/kbmenu_user/backups/rcS_someDateAndTime).
Some users have observed that sometimes the configuration file /etc/wpa_supplicant/wpa_supplicant.conf becomes somehow obstinate (cf.
this threat). I am not sure whether this might also produce the effect you are describing. But you can select "wifi > xdel wpa supplicant.conf.sh." This will delete this configuration file. The file will be newly created, when you "start nickel," or "wifi > wifi ap scan.sh" or "wifi > wifi_manage_networks.sh."
Note: If these two things do not solve your problem, I will upload a file that disables temporarily KSM, so that you can easily try how nickel connects to the network (without possibly being influenced by KSM). But first I have to get to my computer.