Playing with the KSM 09 webinterface

[tshering]

@0xDEADBEAF

following the suggestion by Frenzie, you could try Koreader (without changing frontend/device/kobo/device.lua) by starting it from the command line of the webinterface: after killing KSM, execute

export PRODUCT=snow; $ksmroot/onstart/start_koreader.sh

[0xDEADBEAF]

Thank you for the answers!

Got koreader started correctly (KMS and koreader start via webinterface).
In koreader the touch sometimes does something, but normally does nothing. So they have probably similar problems. I will post this on the koreader thread you mentioned.

In the forum for pbchess (touch also not working) i can't post something because the captcha is broken and i cant create an account there...

I also asked the guys of Kobo so they maybe give me a proper hardware documentation, or even some driver source code. Lets see what happens.

Btw: Google does not know a H2O Edition 2 Version 2 it just knows an H2O Edition 2. And so do I.

When i was discovering some files of the kobo device ive found /usr/local/Kobo/generic/libkevdevtouch.so. That could be the driver for the touchscreen device. But it probably wont help you because it's a binary...

I have to learn for my studies now, so i won't spend much more time for this issue. Maybe i just wait a year or so and hope there are solutions online then.

Best regards


Edit:
https://github.com/koreader/koreader/issues/3925
for those who are interested in the koreader h2o2 touchscreen discussion

[tshering]

Originally Posted by 0xDEADBEAF

I have to learn for my studies now, so i won't spend much more time for this issue. Maybe i just wait a year or so and hope there are solutions online then.

Best regards

Just in case you need at some point a break from learning, you can find the source code of the current pbchess drivers here.
All the best

[tshering]

Note: For KSM nightmode see this post ff.

• remain in daymode*

• kill KSM

• export ksmColorsDay="-bg red -fg white -btn green"; $ksmroot/kobomenu.sh "-showresourcefiles=png"

Select any one of the menu entries (it does not do anything but exit the menu) before you repeat the command export ksmColorsDay= etc., or before you click "start KSM"!


*If KSM is in nightmode you have to set and export ksmColorsDay instead of ksmColorsNight.

For available predefinded color names see here.

[boriar]

Very funny play with colours!
Thank you so much!

[tshering]

Originally Posted by boriar

Very funny play with colours!
Thank you so much!

I am glad you are having fun!

[The_Immortal]

tshering,

1. http://192.168.2.101:8087/rmc_test.html - is available for me. But when I'm trying to connect to 192.168.2.101 via Putty I get the error "Connection refused". Is there a way to fix it?

2. Is there a way to connecto to the device via Putty under Wi-Fi connection (non-usbNet)?

Thank you!

[tshering]

Originally Posted by The_Immortal

tshering,

1. http://192.168.2.101:8087/rmc_test.html - is available for me. But when I'm trying to connect to 192.168.2.101 via Putty I get the error "Connection refused". Is there a way to fix it?

2. Is there a way to connecto to the device via Putty under Wi-Fi connection (non-usbNet)?

Thank you!

The webinterface and Putty use different ways to access the device. In order to use Putty you can enable telnet access with this old package. It does not matter whether you use wifi or usbnet.

[The_Immortal]

Originally Posted by tshering

The webinterface and Putty use different ways to access the device. In order to use Putty you can enable telnet access with this old package. It does not matter whether you use wifi or usbnet.

I put KoboRoot.tgz into /.kobo folder but still no effect

[tshering]

Originally Posted by The_Immortal

I put KoboRoot.tgz into /.kobo folder but still no effect

Did you also install it (handle update ...)? You might also have to restart the device after the update.

[The_Immortal]

Originally Posted by tshering

Did you also install it (handle update ...)? You might also have to restart the device after the update.

Oh, it works now, thank you!

But it actually provides telnet access instead of ssh:23 port (SSH) doesn't work, 22 (telnet) is ok. Is there a way to get SSH-connect?

And also I tried to use SFTP-connect:

Originally Posted by clsdclsd

For file transfers I tried WinSCP (http://en.wikipedia.org/wiki/WinSCP), I had to set the protocol option: sftp server to /mnt/onboard/.kobo/usbnet/sftp-server, after that it worked.

But there is no /mnt/onboard/.kobo/usbnet/sftp-server such file on my device...

Or does that old package provide telnet and FTP only?

[tshering]

Originally Posted by The_Immortal

Oh, it works now, thank you!

But it actually provides telnet access instead of ssh:23 port (SSH) doesn't work, 22 (telnet) is ok. Is there a way to get SSH-connect?

And also I tried to use SFTP-connect:
But there is no /mnt/onboard/.kobo/usbnet/sftp-server such file on my device...

Or does that old package provide telnet and FTP only?

It provides telnet and ftp only.

[Biep]

Hi,
I have an Aura One, with KSM 09 (+ KOReader + Vlasovsoft), and it used to boot into KSM, from where I could then move on (normally to KOReader).
I decided to enable the webinterface, and followed the instructions in this thread, and followed the test instructions given somewhere (can't find the post right now), and clicked some more (starting Plato and the like).

Now, whenever I boot my Aura One, it comes up with KSM, but then after a minute Nickel starts - once even after I had chosen KOReader already. Once Nickel has started I can exit back into KSM with the "Exit Nickel" fake book, and then everything is normal.

Is there a way to get rid of this behaviour? I have tried the "Always" script (supposing it means "Always start in KSM"), but to no avail.
Thank you!

P.S.: That webinterface is great!

[tshering]

Originally Posted by Biep

Hi,
I have an Aura One, with KSM 09 (+ KOReader + Vlasovsoft), and it used to boot into KSM, from where I could then move on (normally to KOReader).
I decided to enable the webinterface, and followed the instructions in this thread, and followed the test instructions given somewhere (can't find the post right now), and clicked some more (starting Plato and the like).

Now, whenever I boot my Aura One, it comes up with KSM, but then after a minute Nickel starts - once even after I had chosen KOReader already. Once Nickel has started I can exit back into KSM with the "Exit Nickel" fake book, and then everything is normal.

Is there a way to get rid of this behaviour? I have tried the "Always" script (supposing it means "Always start in KSM"), but to no avail.
Thank you!

P.S.: That webinterface is great!

I am glad you like the webinterface.
Actually, I do not think that the behaviour you mention is caused by you playing with it. KSM starts by default nickel after about 20 seconds, when there was no user interaction.

[The_Immortal]

tshering, may I ask you why don't you build in KoboTelnet into KSM?