[tshering]

Originally Posted by klaasvaak42

Hi there and thanks tshering for developing for Kobo.

I'm new to this forum, and this is my first post. I am using a Kobo touch wifi 3rd generation.

I've been trying to install koreader (which works) and have it communicate with Calibre via wifi. When I toggle Wifi I get the error message

failed to initialize network control client: failed to connect to wpa_supplicant control socket: /var/run/wpa_supplicant/eth0

As koreader is started by KMS9 i'm asking for help here.

I am interested in solving the problem for KSM. But you have to be aware that this will have no influence on how Koreader handles the stuff.

Originally Posted by klaasvaak42

I've tried to run via the cmdline

sh -x ${ksmroot}/scripts_intern/wifi/wifi_enable_dhcp.sh

tells me there is no such file.

Since you mention cmdline, how did you do this? By the terminal emulator of Koreader? It should find the file, and it does (I just tried it. But it does not show any output. I do not know how exactly the emulator works. Maybe one would have to redirect stdout and stderr.)
If you executed your commands via telnet, chances are that the variable ksmroot, and those used by wifi_enable_dhcp.sh were not known.

Originally Posted by klaasvaak42

I've tried running the scripts and I've tried to run the

#wifi_variables_test.sh
logfile=${ksmuser}/txt/wifi_variables_test.txt
echo "WIFI_MODULE: ${WIFI_MODULE}" > "${logfile}"
echo "PLATFORM: ${PLATFORM}" >> "${logfile}"
echo "INTERFACE: ${ INTERFACE}" >> "${logfile}"

and the

# debug_enable_wifi.sh
logfile=${ksmuser}/txt/enable_wifi_log.txt
sh -x ${ksmroot}/scripts_intern/wifi/wifi_enable_dhcp.sh &> ${logfile}

but neither provide any information for me or were able to create logfiles (might be i'm not looking in the right direction.

Here I have the same question: How did you call these scripts? Since I tested them before I posted them, they should work when you call them from within KSM, as I described it.
As for the variables WIFI_MODULE and so on, you could query them from the Koreader terminal emulator individually, or by "printenv" and then searching through the output list. You could also use the KSM webinterface for the same purpose.