06-19-2020, 11:55 AM | #16 |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
|
06-19-2020, 12:09 PM | #17 |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
|
Advert | |
|
06-19-2020, 12:49 PM | #18 |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
One more thing
I started KoReader with NM and tried to update to 2020.06-3. As expected this failed as described in #9. I then deleted all the files in the ota folder and started KoReader with KFMon. Again the update failed. I am given the same two options - retry with a full download or abort. I retried the full download. After a restart KOReader updated properly. I have no idea what's going on. |
06-19-2020, 03:05 PM | #19 |
BLAM!
Posts: 13,478
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
That's because your NM entry was not quite right.
It's documented in the OCP configs, and in the wiki . ---- To expand on that: both cmd_spawn and cmd_output are *already* passed to sh -c internally, so that was useless. As was redirecting the output, because it's a cmd_spawn, not a cmd_output. Given the sh -c thing, I do recommend using cmd_spawn & exec to avoid one layer of shell wrapper (and get a mostly-useful PPID (1, because it's reparented to init) in the process, instead of a random sh process). But, most importantly, use absolute paths. That's what was breaking OTAs. In fact, I'm not quite sure why it wasn't breaking startup, period. Last edited by NiLuJe; 06-19-2020 at 03:11 PM. |
06-19-2020, 03:52 PM | #20 | |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
Quote:
|
|
Advert | |
|
06-19-2020, 04:34 PM | #21 |
BLAM!
Posts: 13,478
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Both of those were documented on May 13 (i.e., roughly as soon as the quiet flag was implemented, if I recall; and well before an actual KOReader release supporting NM hit stable).
|
06-19-2020, 05:07 PM | #22 |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
The post i mentioned was from May 2nd. @Carmelocotonto used this line in his config and noone seemed to object, so I used it too. Worked well with the then current nightly (unless you wanted to do an ota update )
But, you are absolutely right, people should read documentations more often and thorough. |
06-19-2020, 05:11 PM | #23 |
Connoisseur
Posts: 62
Karma: 3010
Join Date: Feb 2019
Device: kobo h2o
|
Yes¡ now is updating right!
I copy the command from the same thread. Thanks! Enviado desde mi SM-A705FN mediante Tapatalk |
06-20-2020, 06:07 AM | #24 |
Terraner
Posts: 522
Karma: 4207769
Join Date: Aug 2011
Device: Kobo Libra, Aura One, Kindle Oasis 1 & 2 ...
|
|
06-22-2020, 09:03 PM | #25 |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
I have known these past months some very slooow updates and some failures.
The June OTA update has been perfect. Fast and informative. I still have a Kindle PW3 (wifi) Congratulation for your tireless work |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Debian chroot won't upgrade without Kernel Upgrade | Avi Wadhwa | Kindle Developer's Corner | 2 | 12-26-2018 06:54 AM |
And Again: New minor Upgrade upgrade for Muse and Odyssey | Tosch | Bookeen | 13 | 04-22-2015 08:23 AM |
Why can’t I complete the Kobo Touch firmware upgrade or Desktop upgrade? | DarrellAtKobo | Kobo Reader | 31 | 08-31-2012 10:45 PM |
No matter how many times I upgrade to 1.4 it still asks me to upgrade | djorkboy | Kobo Reader | 6 | 09-06-2010 12:36 AM |
Don't upgrade your iPhone 3GS to iOS4, DO upgrade your iPad | Bookbee | Apple Devices | 19 | 07-30-2010 10:10 AM |