Kobo Start Menu 08

[Ken Maltby]

Just curious, what happens if you go to "Network" in KOReader and turn on the WiFi there?

Luck;
Ken

[gaurav_singh_md]

Originally Posted by Ken Maltby

Just curious, what happens if you go to "Network" in KOReader and turn on the WiFi there?

Luck;
Ken

this appears:
Failed to initialize network control client: Failed to connect to wpa_supplicant control socket: /var/run/wpa_supplicant/eth0.

[Ken Maltby]

If you go into the Kobo Nickel settings and "Edit network connections", do you see your network? Is it selected? Once it has been selected there it should be in the "supplicant" list.

Luck;
Ken

[tshering]

Originally Posted by gaurav_singh_md

This is what it says in KSM:
sdio wifi pwr.ko: not loaded
dhd.ko: not loaded

In nickel no wifi networks are detected (there are at least 10 detected on other devices) and if i try to add my network manually it says "wrong password".

I hope you find a solution.

I am not sure if a corrupt wpa_supplicant.conf can cause your problem. But this is something that can easily be tried.
If you select "wifi" > "xdel wpa supplicant.conf.sh" the file wpa_supplicant.conf will be deleted. When you then start nickel, a clean wpa_supplicant.conf is created. You would then have to select the network again and put in the password (if networks are found).

Edit: In case your wpa_supplicant.conf is not corrupt, you might back up your old wpa_supplicant.conf, before you delete it, especially if there are a lot of known networks registered.
select: "tools" > "back up and restore" > "back up" > "back up wpa supplicant conf.sh"
you can later restore the file by: "tools" > "back up and restore" > "restore" > "restore wpa supplicant conf.msh" > ... (there will be a list of backed up wpa_supplicant.conf files with time stamp).

[gaurav_singh_md]

Originally Posted by tshering

I am not sure if a corrupt wpa_supplicant.conf can cause your problem. But this is something that can easily be tried.
If you select "wifi" > "xdel wpa supplicant.conf.sh" the file wpa_supplicant.conf. When you then start nickel,a clean wpa_supplicant.conf
is created. You would then have to select the network again and put in the password (if networks are found).

In Nickel:
"No wi-fi networks found"

Same as before.

[gaurav_singh_md]

Originally Posted by Ken Maltby

If you go into the Kobo Nickel settings and "Edit network connections", do you see your network? Is it selected? Once it has been selected there it should be in the "supplicant" list.

Luck;
Ken

"Your kobo ereader has no known networks"

and it doesn't detect any on rescan. I count 17 on my laptop (including mine and 3 free - without passwords).

[tshering]

Originally Posted by gaurav_singh_md

In Nickel:
"No wi-fi networks found"

Same as before.

Only idea I have at the moment is trying to connect to a wifi network manually by telnet via usbnet. Do you think you can prepare your pc for this, and are ready to do it. Then we could see the exact error message of wpa_supplicant. If you run windows, see the notes in the first post of this thread under "enable USBNet" (in the spoiler).

[gaurav_singh_md]

Originally Posted by tshering

Only idea I have at the moment is trying to connect to a wifi network manually by telnet via usbnet. Do you think you can prepare your pc for this, and are ready to do it. Then we could see the exact error message of wpa_supplicant. If you run windows, see the notes in the first post of this thread under "enable USBNet" (in the spoiler).

Enabling Telnet looks simple. I deleted the vlasovsoft folder yesterday. So i put it back for the usbnet? In ksm usbnet is disabled.

[tshering]

Originally Posted by gaurav_singh_md

Enabling Telnet looks simple. I deleted the vlasovsoft folder yesterday. So i put it back for the usbnet? In ksm usbnet is disabled.

if you select "usb" > "usb toggle.sh", it should change to "USBNet support: enabled." If it does not, we are out of luck with this approach. I had the suspicion that recent firmwares of mark 6 devices have dropped the necessary module. I even asked in this thread owners of such devices, but did not get any response. (vlasovsoft is not necessary)
If it turns out that usbnet does not work, we have to find another way.

[gaurav_singh_md]

Originally Posted by tshering

if you select "usb" > "usb toggle.sh", it should change to "USBNet support: enabled." If it does not, we are out of luck with this approach. I had the suspicion that recent firmwares of mark 6 devices have dropped the necessary module. I even asked in this thread owners of such devices, but did not get any response. (vlasovsoft is not necessary)
If it turns out that usbnet does not work, we have to find another way.

It says USBNEt support : enabled. I have enabled the telnet client as well.

[tshering]

Originally Posted by gaurav_singh_md

It says USBNEt support : enabled. I have enabled the telnet client as well.

Do you have already a usbnet connection between your pc and the kobo?

[gaurav_singh_md]

Originally Posted by tshering

Do you have already a usbnet connection between your pc and the kobo?

Do you mean if the kobo is connected to the laptop via cable? it is connected.

[tshering]

Originally Posted by gaurav_singh_md

Do you mean if the kobo is connected to the laptop via cable? it is connected.

You need to install a virtual network card (I hope this is the correct name) on your pc. If you are running windows 10, follow these instructions (starting with: Download & Unzip attachment kindle_rndis.inf_amd64-v1.0.0.1.zip), but set the IP address to 192.168.2.100 (not to 192.168.15.1 or similar, since this is for Kindle).
(BTW, in between, I figured out an approach without usbnet. If you do not want to continue the usbnet approach, just tell it.)

If anybody has a suggestion, what the problem might be, or a simple way to find it, please tell it.

I describe the other approach:
select: "tools" > "start kbterminal.sh"
press on "direct mode" so that it changes to "file mode"
type into the input field: sh -x $ksmroot/scripts_intern/wifi/wifi_enable_dhcp.sh (typing is even more laggy than selecting a menu entry)
press "Enter"
when you are presented with the output view you can page by pressing on the left or right border of the text area, you can zoom in and out by pressing the top or bottom are of the text area. I hope, there will be an error message that is helpful.
You can save the output by selecting "history" > "kbt:save"; and then ""keyboard" > "Enter".
You return to the menu by pressing "Exit" (in the "keyboard" view).

[gaurav_singh_md]

Originally Posted by tshering

You need to install a virtual network card (I hope this is the correct name) on your pc. If you are running windows 10, follow these instructions (starting with: Download & Unzip attachment kindle_rndis.inf_amd64-v1.0.0.1.zip), but set the IP address to 192.168.2.100 (not to 192.168.15.1 or similar, since this is for Kindle).
(BTW, in between, I figured out an approach without usbnet. If you do not want to continue the usbnet approach, just tell it.)

If anybody has a suggestion, what the problem might be, or a simple way to find it, please tell it.

I describe the other approach:
select: "tools" > "start kbterminal.sh"
press on "direct mode" so that it changes to "file mode"
type into the input field: sh -x $ksmroot/scripts_intern/wifi/wifi_enable_dhcp.sh (typing is even more laggy than selecting a menu entry)
press "Enter"
when you are presented with the output view you can page by pressing on the left or right border of the text area, you can zoom in and out by pressing the top or bottom are of the text area. I hope, there will be an error message that is helpful.
You can save the output by selecting "history" > "kbt:save"; and then ""keyboard" > "Enter".
You return to the menu by pressing "Exit" (in the "keyboard" view).

kbt>sh -x $ksmroot/scripts_intern/wifi/wifi_enable_dhcp.sh

stderr:
sh: illegal option -/

finished

This is the result (output).

[tshering]

Originally Posted by gaurav_singh_md

kbt>sh -x $ksmroot/scripts_intern/wifi/wifi_enable_dhcp.sh

stderr:
sh: illegal option -/

finished

This is the result (output).

This does not seem to be helpful.
If you search the Kobo forum, you will find a lot of complaints concerning wifi (on devices with and without modifications). Since we are in the current situation unable to find the specific source of the problem, I would recommend that you re-install the firmware (see here). When installing it, select "install partial update" (not "install update"). If wifi still does not work, install the firmware that you had before the last update.