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

[enotar]

What I did few days ago to install koreader is to copy the folder structure complete of koreader in .kobo directory.
I use kobo start menu and last 3.20 firmware.
I rebooted and koreader appears in menu below sart nickel.
when I press koreader nothing happened.
What I don't understand is that in the installation of koreader it state to install file structure complete and the KoboRoot.tgz file but I don't find anywhere this file in the file posted in post#1? I think I don't need it as I use kobo menu.
Today I just replace the file in directories by your files.
I think the launch script is not run so it is maybe in the wrong place?

[Ken Maltby]

The KoboRoot.tgz file in the KOreader download zip, is only there to install the fmon and launching scripts that allow you to launch the program within the Nickel/Kobo user interface. It is not used to "install" the actual KOreader program software.

You need to have the koreader folder there before you merge xping's folder with the existing one. With the merge process you are replacing the files with the same name, in the original koreader folder with the ones that xping is providing.

If the problem is as xping is describing, and it sounds very likely, then the frontlight lines that need commenting out are in script files of the same names but in the /.kobo/kbmenu/onstart. Or, if none of those are changed then it would be some in the koreader folder. So, if xping's changes do not seem to work you should check to see if he is trying to change a script that the Kobo Start Menu reads from the onstart folder.

Luck;
Ken

[tshering]

Originally Posted by Ken Maltby

If the problem is as xping is describing, and it sounds very likely, then the frontlight lines that need commenting out are in script files of the same names but in the /.kobo/kbmenu/onstart. Or, if none of those are changed then it would be some in the koreader folder. So, if xping's changes do not seem to work you should check to see if he is trying to change a script that the Kobo Start Menu reads from the onstart folder.

In start menu, the only file directly concerned with koreader is .kobo\kbmenu\onstart\koreader_kobo.sh; and it is not affected by Xping's replacements.
I don't have my Touch at hand. I will try the newst koreader build tomorrow.

[enotar]

Originally Posted by tshering

In start menu, the only file directly concerned with koreader is .kobo\kbmenu\onstart\koreader_kobo.sh; and it is not affected by Xping's replacements.
I don't have my Touch at hand. I will try the newst koreader build tomorrow.

I have this but that does not launch and doesnt créate crash log.....

#!/bin/sh
export LC_ALL="en_US.UTF-8"

# we're always starting from our working directory
cd /mnt/onboard/.kobo/koreader/

# export trained OCR data directory
export TESSDATA_PREFIX="data"

# export dict directory
export STARDICT_DATA_DIR="data/dict"
# finally call reader
./reader.lua /mnt/onboard 2> crash.log

[tshering]

Originally Posted by enotar

I have this but that does not launch and doesnt créate crash log.....

#!/bin/sh
export LC_ALL="en_US.UTF-8"

# we're always starting from our working directory
cd /mnt/onboard/.kobo/koreader/

# export trained OCR data directory
export TESSDATA_PREFIX="data"

# export dict directory
export STARDICT_DATA_DIR="data/dict"
# finally call reader
./reader.lua /mnt/onboard 2> crash.log

I would expect it to work. From post #1018 I take that crash.log is created, but is empty. I think, that would imply that koreader is launched and exits for some reason without having any error. From your recent post I would understand that no crash.log at all is created. This would rather suggest that the script (or at least the last line) is not executed at all.

To check whether the script is executed at all, you could replace the last line with

echo "before koreader" >> /mnt/onboard/.kobo/koreadertest.log
./reader.lua /mnt/onboard 2> crash.log
echo "after koreader" >> /mnt/onboard/.kobo/koreadertest.log

[enotar]

no, the screen just blink
It looks problema is in reader.lua?
koreadertest.log

before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader
before koreader
after koreader

[tshering]

Originally Posted by enotar

no, the screen just blink

I meant to say that I expect the script to be executed and koreader to be launched. And this is actually happening, as your test shows. What then happens, I don't know.
I wonder whether there is anybody running the latest build of koreader successfully on a Touch (on any Kobo?) under FW 3.2.0.

[enotar]

Originally Posted by tshering

I meant to say that I expect the script to be executed and koreader to be launched. And this is actually happening, as your test shows. What then happens, I don't know.
I wonder whether there is anybody running the latest build of koreader successfully on a Touch (on any Kobo?) under FW 3.2.0.

Not only problem with the latest but with koreader_old too nothing work.
I wonder if koreader work at all?

[tshering]

Originally Posted by enotar

Not only problem with the latest but with koreader_old too nothing work.
I wonder if koreader work at all?

I would like to confirm that the latest build (koreader-kobo-arm-linux-gnueabihf-v2013.03-971-g7e26047.zip) is running on my Touch (mark 4) under FW 3.2.0. The only change I had to do is this. But this concerns only the touch input, the FileManager shows already without this modification.

Edit 1: The last but one build (koreader-kobo-arm-linux-gnueabihf-v2013.03-967-gb17b780.zip) works too.

Edit 2: In the first test, I called the koreader from the start menu, but in the meanwhile I tried launching from nickel and this works as well.

[xping]

Originally Posted by Kudalufi

I've grabbed and installed the latest koreader and installed it on my Touch w/ 3.2.0. From the comments on the nightly builds, it seemed like it was supposed to have been fixed for Kobo, but I cannot get it to launch. From the looks of the crash it looks like it might have to do with the changes added for the latest nightly, as they made changes for the frontlight:

NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
./luajit: ./ffi/kobolight.lua:51: cannot change brightess value
stack traceback:
	[C]: in function 'assert'
	./ffi/kobolight.lua:51: in function 'setBrightness'
	./frontend/ui/device/kobopowerd.lua:27: in function 'setIntensityHW'
	./frontend/ui/device/basepowerd.lua:39: in function 'setIntensity'
	./reader.lua:186: in main chunk
	[C]: in function 'dofile'
	./koreader-base:37: in main chunk
	[C]: at 0x0000c5a4

Does anyone else have this running on a Touch with 3.2.0 right now?

@kudalufi. Did U try my patch? Any news about issue on kobo touch?

[enotar]

Originally Posted by tshering

I would like to confirm that the latest build (koreader-kobo-arm-linux-gnueabihf-v2013.03-971-g7e26047.zip) is running on my Touch (mark 4) under FW 3.2.0. The only change I had to do is this. But this concerns only the touch input, the FileManager shows already without this modification.

Edit 1: The last but one build (koreader-kobo-arm-linux-gnueabihf-v2013.03-967-gb17b780.zip) works too.

Edit 2: In the first test, I called the koreader from the start menu, but in the meanwhile I tried launching from nickel and this works as well.

That is strange, install is pretty straight forward, just extract and copy to ./kobo but it doesn't work for me.
I am out of ideas....

[Ken Maltby]

I am not sure anyone has the original N905 version of the Touch working with any version of the FW 3.2.0. Check the firmware thread first post and be sure you are using a download for your version of Touch.

Luck;
Ken

[tshering]

Originally Posted by enotar

That is strange, install is pretty straight forward, just extract and copy to ./kobo but it doesn't work for me.
I am out of ideas....

Really strange! Maybe you could try putting this script into kbmenu/scripts/test and start it from there.
testkoreader.sh

#!/bin/sh
kbmenudir=/mnt/onboard/.kobo/kbmenu
sh $kbmenudir/onstart/koreader_kobo.sh 2> $kbmenudir/koreadertest.log

Maybe it gives us some information what is happening in the line ./reader.lua /mnt/onboard 2> crash.log.

If this doesn't give us meaningful information, we could try starting the koreader with strace. You can find strace in kbmenu/tools.

[enotar]

Originally Posted by tshering

Really strange! Maybe you could try putting this script into kbmenu/scripts/test and start it from there.
testkoreader.sh

#!/bin/sh
kbmenudir=/mnt/onboard/.kobo/kbmenu
sh $kbmenudir/onstart/koreader_kobo.sh 2> $kbmenudir/koreadertest.log

Maybe it gives us some information what is happening in the line ./reader.lua /mnt/onboard 2> crash.log.

If this doesn't give us meaningful information, we could try starting the koreader with strace. You can find strace in kbmenu/tools.

Hey Tkz...
I am at work now but test it later (in 3 hours). I hope we can get to the bottom of this.

[enotar]

Originally Posted by tshering

Really strange! Maybe you could try putting this script into kbmenu/scripts/test and start it from there.
testkoreader.sh

#!/bin/sh
kbmenudir=/mnt/onboard/.kobo/kbmenu
sh $kbmenudir/onstart/koreader_kobo.sh 2> $kbmenudir/koreadertest.log

Maybe it gives us some information what is happening in the line ./reader.lua /mnt/onboard 2> crash.log.

If this doesn't give us meaningful information, we could try starting the koreader with strace. You can find strace in kbmenu/tools.

Blank log
How do I run strace with koreader?
thank you

Edit
redo all install but without menú
Now when I launch koreader.png it launch kobo reader not koreader, this is insane....
Re install menú, same thing; I begin to think that the versións I have dont work
Any idea?