![]() |
#826 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 10,259
Karma: 50100907
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Forma, Clara HD, Nexus 7 HD, iPad Pro, Tolino epos
|
Quote:
|
|
![]() |
![]() |
![]() |
#827 |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 10,259
Karma: 50100907
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Forma, Clara HD, Nexus 7 HD, iPad Pro, Tolino epos
|
I had a couple of hours to kill today so continued playing with my Mini and KSM. I factory reset the Mini, updated to 3.19.5671-s, installed KSM 09 & KOReader and all seemed to work happily. Installed 4.25.15875 from KSM's controlled install. Rebooted and went to Nickel. Tried the restore.zip after updating the rcS file to the test version posted by @rtiangha and still booted into Nickel.
The good news is that it did not brick my Mini. The bad news is it looks as if KSM 09 is not working with 4.25 firmware. |
![]() |
![]() |
![]() |
#828 | |
Member
![]() Posts: 24
Karma: 10
Join Date: Jun 2018
Device: Tobo Touch 2.0; Kobo Aura One
|
Quote:
Anyhow, it rebooted into nickel, and the "Action books" ("Exit nickel" and so on) no longer worked. Then I downloaded KSM09_plus_update_001_and_nightmode.zip, replaced the kbmenupngs just to be sure, and dropped KoboRoot.tgz in the .kobo folder. After rebooted I kept a blank screen and a blinking blue light. I waited for several hours, but no changes. Switching off and on didn't bring any changes, so eventually I did a hard factory reboot. That is where I am now, trying to figure out how to get KSM working again. It is so much better than the FMON family - which, as I understand, keep nickel in charge. Also, I really like the "rescue connection" KSM makes the first minute - even though this time it didn't save me. If @tshering no longer wants to support it - isn't there anyone else who might? My current version of Kobo is given as N7097AL044956,3.0.35+,4.25.15875,3.0.35+,3.0.35+,0 0000000-0000-0000-0000-000000000373 [Update]: I finally installed KFMon (with KOReader and Plato). That allows me to use KOReader, at least. Would there be an easy way to add a "book" for Frotz? Last edited by Biep; 11-22-2020 at 04:51 PM. Reason: And eventually.. |
|
![]() |
![]() |
![]() |
#829 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,278
Karma: 19703052
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O & Forma
|
Someone might have (spoiler alert: not volunteering, just venting), if the full sources were actually available somewhere and the builds actually reproducible... ;o).
The fact that they've never been has probably helped slowly drive a stake through its heart over the years... Last edited by NiLuJe; 11-22-2020 at 01:36 PM. |
![]() |
![]() |
![]() |
#830 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,139
Karma: 429212
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
I think the drivers are the same ones as vlasovsoft (the sources of which are available). Besides that it's plain text scripts and a few generic tools. So I think one should probably be able to come Close Enough™ within a few hours if you want to recompile the binary parts. And a motivated person would do well to simply ask nicely first.
![]() |
![]() |
![]() |
![]() |
#831 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,278
Karma: 19703052
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O & Forma
|
That still leaves the Qt GUI and an actual buildsystem, which has been a black box from the start
![]() Besides, I like kicking over anthills ^^. |
![]() |
![]() |
![]() |
#832 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 268
Karma: 61195
Join Date: Jul 2016
Device: Kobo Glo HD
|
Quote:
If it's a touch driver problem (doubtful, but who knows??), I noticed that the most recent vlasovsoft package was released earlier in March of this year. I don't know if the drivers are any newer than the last release (although they're probably newer than what shipped with KSM), but maybe replacing those might help. However, when I tried to do an update roll up of KSM a while ago, I had problems with the recent version of the Glo HD driver where it wouldn't work; I had to revert to using the previous version from an older vlasovsoft version to get touch back. I don't know if that's an issue with the Glo HD or all Mark 6 devices, though. The updated driver for the Mark 7 devices still worked though. That said, I can boot into the vlasovsoft stuff via NickelMenu, so I'm 95% certain it isn't a touch driver issue that prevents KSM from booting. |
|
![]() |
![]() |
![]() |
#833 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 268
Karma: 61195
Join Date: Jul 2016
Device: Kobo Glo HD
|
Quote:
|
|
![]() |
![]() |
![]() |
#834 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,278
Karma: 19703052
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O & Forma
|
Getting a custom QPA to behave is usually simply a few env vars away, see UMR for inspiration, where I think we had the very same kind of discussion ^^.
(Not familiar with how Frotz is built, though, is it even Qt? ![]() |
![]() |
![]() |
![]() |
#835 |
Member
![]() Posts: 24
Karma: 10
Join Date: Jun 2018
Device: Tobo Touch 2.0; Kobo Aura One
|
@tshering:
Are you listening? I think you could make a lot of people happy by releasing the source code. Not necessarily open source, if you don't want that - you could still retain a final say over the product. |
![]() |
![]() |
![]() |
#836 |
Member
![]() Posts: 24
Karma: 10
Join Date: Jun 2018
Device: Tobo Touch 2.0; Kobo Aura One
|
KOReader has a much better environment (e.g. file browser, keyboard, ..). It would be wonderful if the IF formats would simply be recognised as document types in KOReader, and start the appropriate interpreter.
|
![]() |
![]() |
![]() |
#837 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,278
Karma: 19703052
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O & Forma
|
@Biep: KOReader isn't really built to have anything taking over its screen/input (for any meaningful period of time), though, so it's a tad more problematic that just running ash or Python
![]() |
![]() |
![]() |
![]() |
#838 | |
Member
![]() Posts: 24
Karma: 10
Join Date: Jun 2018
Device: Tobo Touch 2.0; Kobo Aura One
|
Quote:
Likewise, I hope that nickel is started from something like a .loginrc. If so, then a script run from a computer could rename that script, and install another .loginrc that would give a simple start menu, and start nickel, KOReader, Frotz, .. depending on what the user chooses. But I realise my model of how things work is probably way too simple. |
|
![]() |
![]() |
![]() |
#839 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,278
Karma: 19703052
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O & Forma
|
Well it is and it does: it defers to tightly-coupled rendering *engines*. But the UI & event loop is all KO.
--- As far as the Kobo init system goes: nope, it's basically back to System V: one rcS to rule them all ![]() Which, quite frankly, despite the limitations, is mildly refreshing after the depgraph hellscape that is upstart on the Kindle ![]() If you want systemd, get a reMarkable ![]() Last edited by NiLuJe; 11-24-2020 at 08:49 PM. |
![]() |
![]() |
![]() |
#840 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 268
Karma: 61195
Join Date: Jul 2016
Device: Kobo Glo HD
|
Full disclosure: I run the bouncer script so that I can have a password prompt on boot up (this was before the Nickel PIN but I kept it anyways later on) so that might have messed things up, but for fun, I decided to boot into koreader and use its terminal emulator to manually launch /adds/kbmenu/onstart/ksmhome.sh, and it seemed to work (well, it booted me to the KSM password prompt anyway), but it appeared that I didn't have touch (or at least, nothing on screen was updating).
I figured it might have had to do without setting some of the environment variables first (like the touch driver), so I tried to do the same using Konsole in vlasovsoft's launcher, and it got me to the password screen but it looked like it booted back to Konsole right away albeit the screen didn't refresh entirely as I could see Konsole output in some places on the display and tapping on where the keyboard was approximately put chars on the screen too. I'm not quite sure what that says, although it's making me think that it's something really stupid preventing KSM from starting properly and the fix (whatever it ends up being) might be trivial. Ideas welcome. Last edited by rtiangha; 11-25-2020 at 01:01 PM. |
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo Start Menu 08 | tshering | Kobo Developer's Corner | 1021 | 06-29-2020 05:59 PM |
Kobo-Adding alternative readers using Kobo Start Menu | Ken Maltby | KOReader | 75 | 01-10-2020 02:35 PM |
Kobo Start Menu | tshering | Kobo Developer's Corner | 918 | 10-12-2017 03:32 PM |
Start KOReader automatically with Kobo Start Menu | checcousero | KOReader | 2 | 03-07-2017 12:42 PM |
Kobo Start Menu 07 | tshering | Kobo Developer's Corner | 644 | 03-02-2017 07:40 AM |