[Alpha] Kobo-UNCaGED - Calibre wireless connection - Page 2

NiLuJe · 02-20-2020, 01:47 PM

Calibre being down (or the Wireless thingy not being started) should trigger an obvious message saying so (in the center white popup region, IIRC).

It might not stay on screen for very long, but it should be visible.

church mouse · 02-20-2020, 02:02 PM

Quote:

Originally Posted by NiLuJe

Calibre being down (or the Wireless thingy not being started) should trigger an obvious message saying so (in the center white popup region, IIRC).

It might not stay on screen for very long, but it should be visible.

In my case, Calibre is working and I can access it using Calibre Companion on my phone.

KU just seems to start the ''Running Kobo-Uncaged'' process then immediately begins the closing process.

NiLuJe · 02-20-2020, 03:05 PM

@church mouse: Does it ever actually enter the "Connected" screen (i.e., black background)?

What's the *exact* final error message (specifically, the error codes at the end). (Because it can't be BS:61, as that one's supposed to be negative ;p)

sherman · 02-20-2020, 03:31 PM

It might also help to see what logs were written to syslog, if any. To get access to this log, on your kobo, search for 'devmodeon' (it will appear to do nothing). To check this worked, go to menu > settings > Device Information. There should be 'Developer options' at the bottom.

Plug in your Kobo to your computer, open the '.kobo' directory, and there should be one or more files with syslog in the name. Open the latest file. You can paste the log here, or search for any lines that contain 'uncaged' or 'kobo-uncaged'.

church mouse · 02-20-2020, 03:47 PM

Quote:

Originally Posted by NiLuJe

@church mouse: Does it ever actually enter the "Connected" screen (i.e., black background)?

What's the *exact* final error message (specifically, the error codes at the end). (Because it can't be BS:61, as that one's supposed to be negative ;p)

It never connects to Calibre - it never has time. Looking at the run-ku.sh, it seems to get as far as KU_BIN to start /bin/kobo-uncaged before immediately (and I mean immediately) beginning the leaving process.

Apologies, I see the message has a - sign before 61 i.e BS: -61.

Does that help at all?

sherman · 02-20-2020, 03:56 PM

Ignore the BS error, it's a symptom of the fact that Kobo-UNCaGED exited in an unexpected state. I probably need to rework the shell script a little to make this a bit clearer.

I'm hoping there sill be something useful in the syslog.

church mouse · 02-20-2020, 03:58 PM

Quote:

Originally Posted by sherman

It might also help to see what logs were written to syslog, if any. To get access to this log, on your kobo, search for 'devmodeon' (it will appear to do nothing). To check this worked, go to menu > settings > Device Information. There should be 'Developer options' at the bottom.

Plug in your Kobo to your computer, open the '.kobo' directory, and there should be one or more files with syslog in the name. Open the latest file. You can paste the log here, or search for any lines that contain 'uncaged' or 'kobo-uncaged'.

Does this extract of the log help?

19:37:00 UNCaGED: USBMS mode entered . . .
Feb 20 19:37:00 UNCaGED: Running Kobo-UNCaGED
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Started Kobo-UNCaGED
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Reading options
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Creating KU object
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Opening NickelDB
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Getting Kobo Info
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Getting Device Info
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Reading Metadata
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Reading metadata.calibre
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Gathering metadata
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Book not in cache: file:///mnt/onboard/.kobo/guide/userguide.pdf
Feb 20 19:37:01 KoboUNCaGED[7584]: 2020/02/20 19:37:01 Book not in cache: file:///mnt/onboard/legacygetkepub2417book_librarya divided spy - charles cumming_2417.kepub.epub
Feb 20 19:37:01 UNCaGED: Leaving USBMS . . .
Feb 20 19:37:01 UNCaGED: Disabling WiFi
Feb 20 19:37:01 wpa_supplicant[7476]: ioctl[SIOCSIWAP]: Operation not permitted
Feb 20 19:37:01 wpa_supplicant[7476]: eth0: CTRL-EVENT-DISCONNECTED bssid=f4:f2:6d:9f:72:cb reason=3 locally_generated=1
Feb 20 19:37:01 wpa_supplicant[7476]: ioctl[SIOCSIWAP]: Operation not permitted
Feb 20 19:37:01 wpa_supplicant[7476]: eth0: CTRL-EVENT-TERMINATING
Feb 20 19:37:02 UNCaGED: WiFi disabled (0) . . .
Feb 20 19:37:02 UNCaGED: Unmounting onboard
Feb 20 19:37:03 UNCaGED: Onboard unmounted (0) . . .
Feb 20 19:37:03 UNCaGED: Unmounting SD card
Feb 20 19:37:03 UNCaGED: SD card unmounted (0) . . .
Feb 20 19:37:03 UNCaGED: Waiting for content processing

sherman · 02-20-2020, 04:13 PM

Oh dear. I was hoping for an exit error in there, and I didn't find one. Which makes me suspect a Panic occurred.

Are you able to modify the run-ku.sh script to redirect stderr to a file? Unfortunately, that's where Go outputs it's Panic messages. eg:
$KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" 2> error.log

church mouse · 02-20-2020, 04:33 PM

Quote:

Originally Posted by sherman

Oh dear. I was hoping for an exit error in there, and I didn't find one. Which makes me suspect a Panic occurred.

Are you able to modify the run-ku.sh script to redirect stderr to a file? Unfortunately, that's where Go outputs it's Panic messages. eg:
$KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" 2> error.log

Getting above my pay scale here. Are you saying you simply want me to amend the run-ku.sh by replacing the current $KU_BIN etc with the new line? If so, yes.

If you need me to do more than that, I can give it a go with some Noddy instructions from you.

sherman · 02-20-2020, 04:40 PM

Yep, just edit line 79 from

Code:

$KU_BIN -onboardmount="${MNT_ONBOARD_NEW}"

to

Code:

$KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" 2> "${MNT_ONBOARD_NEW}/.adds/kobo-uncaged/error.log"

Then run again. Hopefully, there will then be an 'error.log' file in the kobo-uncaged directory afterwards.

church mouse · 02-20-2020, 04:50 PM

@sherman

Error log attached

sherman · 02-20-2020, 05:03 PM

Thanks.

Yep, it's a panic alright. It also did it in the area I was expecting it to, which is... nice.

I've had this horrible suspicion I've forgotten to deal with DRM'd books, and/or malformed books. The underlying epub library I'm using seems a bit prone to panics

church mouse · 02-20-2020, 05:08 PM

Quote:

Originally Posted by sherman

Thanks.

Yep, it's a panic alright. It also did it in the area I was expecting it to, which is... nice.

I've had this horrible suspicion I've forgotten to deal with DRM'd books, and/or malformed books. The underlying epub library I'm using seems a bit prone to panics

OK.

I don't usually have any drm books on the Kobo, but occasionally, when away from home, I am tempted to buy and download immediately (there is also the issue of Kobo sometimes going into an unwanted sync mode).

I leave you to scratch your head.

Many thanks for your help.

sherman · 02-20-2020, 05:24 PM

Thanks for helping me track this down. I don't like unexplained crashes!

church mouse · 02-20-2020, 05:27 PM

@sherman

One additional thing before I go: I have just removed all books from my Clara, rebooted, then added two non-drm books from my Calibre Server using the Kobo browser (no issues). However, trying to use KU and Calibre wireless causes the same panic and error as before.

I don't know if that is as you would suspect.

02-20-2020, 03:05 PM	#18
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@church mouse: Does it ever actually enter the "Connected" screen (i.e., black background)? What's the exact final error message (specifically, the error codes at the end). (Because it can't be BS:61, as that one's supposed to be negative ;p) Last edited by NiLuJe; 02-20-2020 at 03:07 PM.

02-20-2020, 04:40 PM	#25
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Yep, just edit line 79 from Code: $KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" to Code: $KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" 2> "${MNT_ONBOARD_NEW}/.adds/kobo-uncaged/error.log" Then run again. Hopefully, there will then be an 'error.log' file in the kobo-uncaged directory afterwards.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PDF compressed when sent with Calibre Wireless Connection	zorrodee666	KOReader	1	03-23-2019 11:50 PM
connecting Calibre to Calibre without wireless connection	TomSpot	Calibre Companion	1	07-10-2018 07:07 AM
Wireless connection to calibre.	sorg	Kindle Developer's Corner	33	07-16-2015 12:49 PM
Calibre Companion and wireless connection	taratears	Calibre Companion	13	03-28-2015 06:32 PM
Nook Touch/Calibre wireless connection?	tigersfan	Devices	8	01-10-2012 03:51 PM

02-20-2020, 01:47 PM	#16
NiLuJe BLAM! Posts: 13,497 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Calibre being down (or the Wireless thingy not being started) should trigger an obvious message saying so (in the center white popup region, IIRC). It might not stay on screen for very long, but it should be visible.

02-20-2020, 03:31 PM	#19
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	It might also help to see what logs were written to syslog, if any. To get access to this log, on your kobo, search for 'devmodeon' (it will appear to do nothing). To check this worked, go to menu > settings > Device Information. There should be 'Developer options' at the bottom. Plug in your Kobo to your computer, open the '.kobo' directory, and there should be one or more files with syslog in the name. Open the latest file. You can paste the log here, or search for any lines that contain 'uncaged' or 'kobo-uncaged'.

02-20-2020, 03:56 PM	#21
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Ignore the BS error, it's a symptom of the fact that Kobo-UNCaGED exited in an unexpected state. I probably need to rework the shell script a little to make this a bit clearer. I'm hoping there sill be something useful in the syslog.

02-20-2020, 04:13 PM	#23
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Oh dear. I was hoping for an exit error in there, and I didn't find one. Which makes me suspect a Panic occurred. Are you able to modify the run-ku.sh script to redirect stderr to a file? Unfortunately, that's where Go outputs it's Panic messages. eg: $KU_BIN -onboardmount="${MNT_ONBOARD_NEW}" 2> error.log

02-20-2020, 05:03 PM	#27
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Thanks. Yep, it's a panic alright. It also did it in the area I was expecting it to, which is... nice. I've had this horrible suspicion I've forgotten to deal with DRM'd books, and/or malformed books. The underlying epub library I'm using seems a bit prone to panics

02-20-2020, 05:24 PM	#29
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Thanks for helping me track this down. I don't like unexplained crashes!

02-20-2020, 05:27 PM	#30
church mouse Evangelist Posts: 484 Karma: 5277078 Join Date: Oct 2009 Location: UK Device: Kobo Clara HD, Boox Poke 2, PocketBook Verse Pro (634)	@sherman One additional thing before I go: I have just removed all books from my Clara, rebooted, then added two non-drm books from my Calibre Server using the Kobo browser (no issues). However, trying to use KU and Calibre wireless causes the same panic and error as before. I don't know if that is as you would suspect.

Advert

Advert