Koreader running on Kobos (all of them, hopefully!) - Page 159

tshering · 09-04-2015, 02:10 PM

Quote:

Originally Posted by NiLuJe

@tshering: Huh, no idea why the hell would wpa-supplicant and its children would inherit/have a hold on these fonts... Does this happen with KOReader's builtin network-manager? If not, it might be a quirk of how this is done in KSM? But if it's done before KOReader is even started, why the hell is it even looking at KOReader stuff?

Although, given the PIDs in your last post, wpa-supplicant appears to have been started *after* KOReader, so I'm confused. [EDIT: Because that's what you did, I got confused with the spoiler blocks ;p]

EDIT: Okay, yeah, the Kobo only has busybox ps*. pstree might be more readable, although I personally kind of hate how it presents stuff, but, still, better than nothing ;p.

Please have a look at post #2362. The first spoiler shows what is happening when KSM turns the wifi connection on and then Koreader is started, and the second spoiler shows what is happening when Koreader is started and then wifi is turned on via the Koreader menu.

NiLuJe · 09-04-2015, 02:12 PM

@tshering: Yeah, I got confused with the spoiler blocks

.

See my edits, it makes perfect sense now

.

NiLuJe · 09-04-2015, 02:41 PM

See if it still happens with this KOReader build.

(Haven't had time to test it, sorry).

If it works properly, that's definitely a borked TC on the buildbot.

tshering · 09-04-2015, 03:08 PM

Quote:

Originally Posted by NiLuJe

See if it still happens with this KOReader build.

(Haven't had time to test it, sorry).

If it works properly, that's definitely a borked TC on the buildbot.

It does not seem to work properly.

Spoiler:

NiLuJe · 09-04-2015, 04:02 PM

@tshering: Yeah, something's going wonky with the FT buildsystem when cross-compiling, it's not building the tailored *nix src file with CLOEXEC support, looking into it.

tshering · 09-04-2015, 04:16 PM

Quote:

Originally Posted by NiLuJe

@tshering: Yeah, something's going wonky with the FT buildsystem when cross-compiling, it's not building the tailored *nix src file with CLOEXEC support, looking into it.

For the moment, I am running this after exiting Koreader:

Code:

#!/bin/sh

# since we have to kill wpa_supplicant anyway ...
[ $(ps | grep -c wlarm_le) -gt 0 ] && wlarm_le -i eth0 down
ifconfig eth0 down
[ $(lsmod | grep -c dhd) -gt 0 ] && /sbin/rmmod -r dhd
[ $(lsmod | grep -c sdio_wifi_pwr) -gt 0 ] && /sbin/rmmod -r sdio_wifi_pwr
killall wpa_supplicant

# try to kill all processes that keep koreader font files open
while :
do
  p=$( lsof | grep 'koreader.*/fonts' | awk 'NR==1 { print $1 }')
  [ "x$p" == "x" ] && break
  kill $p
  [ $? -gt 0 ] && break
done

NiLuJe · 09-04-2015, 04:22 PM

@tshering: Found what was confusing the FT buildsystem (autotools & cross-compiling... >_<").

I'm rebuilding everything, and I'll check if it helps.

The good news is that the fix is trivial, and *should* work with the buildbot, so I'll send a PR if that fixes it

.

tshering · 09-04-2015, 04:25 PM

Quote:

Originally Posted by NiLuJe

@tshering: Found what was confusing the FT buildsystem (autotools & cross-compiling... >_<").

I'm rebuilding everything, and I'll check if it helps.

The good news is that the fix is trivial, and *should* work with the buildbot, so I'll send a PR if that fixes it

.

Ok, thank you!

NiLuJe · 09-04-2015, 04:44 PM

Code:

/mnt/onboard/.niluje/usbnet/bin/lsof +c0 | grep koreader                                                                                                            
zsh                2777       root  cwd       DIR      179,3     4096 18985 /mnt/onboard/.custom/koreader
koreader.sh        2963       root  cwd       DIR      179,3     4096 18985 /mnt/onboard/.custom/koreader
koreader.sh        2963       root  rtd       DIR      179,1     1024     2 /
koreader.sh        2963       root  txt       REG      179,1   535840 34368 /bin/busybox
koreader.sh        2963       root  mem       REG      179,1    97580   934 /lib/ld-2.11.1.so
koreader.sh        2963       root  mem       REG      179,1   398928   947 /lib/libm-2.11.1.so
koreader.sh        2963       root  mem       REG      179,1   881932   752 /lib/libc-2.11.1.so
koreader.sh        2963       root    0u      CHR      136,0      0t0     3 /dev/pts/0
koreader.sh        2963       root    1u      CHR      136,0      0t0     3 /dev/pts/0
koreader.sh        2963       root    2w      REG      179,3        0 19640 /mnt/onboard/.custom/koreader/crash.log
koreader.sh        2963       root   10r      REG      179,3     3045 19440 /mnt/onboard/.custom/koreader/koreader.sh
koreader.sh        2963       root   11u      CHR      136,0      0t0     3 /dev/pts/0
reader.lua         2996       root  cwd       DIR      179,3     4096 18985 /mnt/onboard/.custom/koreader
reader.lua         2996       root  txt       REG      179,3   427528 19566 /mnt/onboard/.custom/koreader/luajit
reader.lua         2996       root  mem       REG      179,3    10616 19626 /mnt/onboard/.custom/koreader/libs/libkoreader-lfs.so
reader.lua         2996       root  mem       REG      179,3    11936 19634 /mnt/onboard/.custom/koreader/libs/libkoreader-input.so
reader.lua         2996       root  mem       REG      179,3   453688 19629 /mnt/onboard/.custom/koreader/libs/libfreetype.so.6
reader.lua         2996       root  mem       REG      179,3  3520284 19619 /mnt/onboard/.custom/koreader/libs/libmupdf.so
reader.lua         2996       root  mem       REG      179,3   245752 19633 /mnt/onboard/.custom/koreader/libs/libjpeg.so.8
reader.lua         2996       root  mem       REG      179,3     9296 19617 /mnt/onboard/.custom/koreader/libs/libwrap-mupdf.so
reader.lua         2996       root  mem       REG      179,3   305800 19603 /mnt/onboard/.custom/koreader/fonts/noto/NotoSans-Regular.ttf
reader.lua         2996       root  mem       REG      179,3   119380 19572 /mnt/onboard/.custom/koreader/fonts/droid/DroidSansMono.ttf
reader.lua         2996       root  mem       REG      179,3   310484 19600 /mnt/onboard/.custom/koreader/fonts/noto/NotoSans-Bold.ttf
reader.lua         2996       root  mem       REG      179,3    19704 19506 /mnt/onboard/.custom/koreader/common/serialize.so
reader.lua         2996       root  mem       REG      179,3    10284 19508 /mnt/onboard/.custom/koreader/common/libluacompat52.so
reader.lua         2996       root  mem       REG      179,3    27816 19513 /mnt/onboard/.custom/koreader/common/socket/score.so
reader.lua         2996       root    2w      REG      179,3        0 19640 /mnt/onboard/.custom/koreader/crash.log
wpa_supplicant     3046       root  mem       REG      179,3   290016 19623 /mnt/onboard/.custom/koreader/libs/libssl.so.1.0.0
wpa_supplicant     3046       root  mem       REG      179,3  1258480 19627 /mnt/onboard/.custom/koreader/libs/libcrypto.so.1.0.0
default.script     3052       root  cwd       DIR      179,3     4096 18985 /mnt/onboard/.custom/koreader
default.script     3057       root  cwd       DIR      179,3     4096 18985 /mnt/onboard/.custom/koreader

That's much better

.

That does leave our own OpenSSL lib being used instead of the system's though...
I'll check if that can be arrranged.

That, and the CWD.

NiLuJe · 09-04-2015, 05:00 PM

Okay, I think I got everything!
I updated the KOReader build, please check that I didn't miss anything

.

See PR #335 & #1620.

Note that wpa_supplicant & the dhcp client still won't get killed on exit if started without nickel running. Since that's not something I'm doing, I have no idea if that's a desirable behavior or not (see platform/kobo/nickel.sh for how it's done with nickel running).

tshering · 09-04-2015, 05:45 PM

NiLuJe,
the updated version works for me. Thank you.
I think I will kill wpa_supplicant & the dhcp in KSM 8 to prevent problems for people who run older versions of Koreader.

NiLuJe · 09-04-2015, 05:47 PM

@tshering: Great! Thanks for mentioning this, that made me discover a rather sneaky issue with my cross builds

.

ectoplasm · 09-06-2015, 05:06 PM

I have a lighttpd server, which can serve zsync. Any ideas if I can make Koreader clients recognize my server, so I can drop files there?

Ken Maltby · 09-06-2015, 05:26 PM

Quote:

Originally Posted by ectoplasm

I have a lighttpd server, which can serve zsync. Any ideas if I can make Koreader clients recognize my server, so I can drop files there?

The Koreader WiKi If you can recreate the "Publish" on your server. Have you tried turning on the "Subscriber" in the Koreader Zsync plug-in, and then see if your server is offering anything?

This is assuming the server is in the same network that your device accesses.

Luck;
Ken

Don't understand how these file operations keep being added to the "Reader Menu" instead of the "File Manager Menu"?

ectoplasm · 09-06-2015, 09:17 PM

Quote:

Originally Posted by Ken Maltby

The Koreader WiKi If you can recreate the "Publish" on your server. Have you tried turning on the "Subscriber" in the Koreader Zsync plug-in, and then see if your server is offering anything?

This is assuming the server is in the same network that your device accesses.
...

Zsync doesn't add involve adding code to the server, the code is client side and pulls from the server via http and byte ranges. There must be logic in the koreader implementation to seek out other clients. I looked at the code, but didn't feel inclined to undertake to work out a way to imitate a client (maybe simple, maybe not).

I found a fairly simple alternative (at least one I know how to implement), and that is serving up a bare-bones ODPS file from Lighttpd. I got the idea from Calibre's ODPS server. I can script a file change monitor, which generates the ODPS file list, without all the extraneous tags Calibre uses which I don't care about.

This gets me where I wanted, which is to drop epubs in a folder (step 1), and then pull them later from the reader (step 2). I do this now with nickel and kobo's browser (and could still do that from KSM if I load up nickel). I prefer this to the standard approach, where both steps must be done at the same time. Note that my "server" is always on, so this wouldn't work for folks without a server.

09-04-2015, 05:00 PM	#2380
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Okay, I think I got everything! I updated the KOReader build, please check that I didn't miss anything . See PR #335 & #1620. Note that wpa_supplicant & the dhcp client still won't get killed on exit if started without nickel running. Since that's not something I'm doing, I have no idea if that's a desirable behavior or not (see platform/kobo/nickel.sh for how it's done with nickel running). Last edited by NiLuJe; 09-04-2015 at 05:30 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)	hawhill	Kindle Developer's Corner	1289	04-07-2025 10:18 AM
Touch Using two Kobos	tkavan	Kobo Reader	4	06-23-2017 02:47 AM
2 kobos at once	tsarinaerika	Kobo Reader	14	06-03-2013 04:13 AM
Syncing between two Kobos	fx3000se	Kobo Reader	4	01-24-2013 02:10 PM
2 kobos 1 account	retired05	Kobo Reader	9	05-05-2012 08:25 AM

09-04-2015, 02:12 PM	#2372
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: Yeah, I got confused with the spoiler blocks . See my edits, it makes perfect sense now .

09-04-2015, 02:41 PM	#2373
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	See if it still happens with this KOReader build. (Haven't had time to test it, sorry). If it works properly, that's definitely a borked TC on the buildbot.

09-04-2015, 04:02 PM	#2375
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: Yeah, something's going wonky with the FT buildsystem when cross-compiling, it's not building the tailored *nix src file with CLOEXEC support, looking into it.

09-04-2015, 04:22 PM	#2377
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: Found what was confusing the FT buildsystem (autotools & cross-compiling... >_<"). I'm rebuilding everything, and I'll check if it helps. The good news is that the fix is trivial, and should work with the buildbot, so I'll send a PR if that fixes it .

09-04-2015, 05:45 PM	#2381
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	NiLuJe, the updated version works for me. Thank you. I think I will kill wpa_supplicant & the dhcp in KSM 8 to prevent problems for people who run older versions of Koreader.

09-04-2015, 05:47 PM	#2382
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: Great! Thanks for mentioning this, that made me discover a rather sneaky issue with my cross builds .

09-06-2015, 05:06 PM	#2383
ectoplasm Addict Posts: 255 Karma: 1151364 Join Date: Aug 2009 Device: Aura HD and H2O	I have a lighttpd server, which can serve zsync. Any ideas if I can make Koreader clients recognize my server, so I can drop files there?