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

[koboje]

Originally Posted by NiLuJe

Does it behave when toggling it manually?

I don't recall having tested auto-connect, but I also don't recall anything hardware-specific about it off the top of my head.

The Wi-Fi scripts are one of the last thing I tested/fixed in the PR, so, double-check you're actually running the latest code in case you did a custom setup?

EDIT: Yup, #worksforme (startup via KFMon + NM).

Not sure why. I just replaced the nightly koreader folder to your one-click zip and installed with your script method. When i touch "connect" from the calibre menu while wifi is off, the error message pops up after I touched wifi turn on.
Even "network" - "wi-fi connection" menu also returns the same error message. Well, again, not a big deal at all as I can exit from koreader and turn on wifi from kobo stock menu. Thank you always and I love elipsa's big screen (i know resolution sucks but still i like it!)

[NiLuJe]

@koboje: That's the error we get when we fail to load the Wi-Fi chip's driver (granted, possibly among other things ^^), which one of the last thing I fixed, hence the questions .

On the off-chance something changed, on which FW version is this happening?

(Otherwise, investigating this would require shell access over USBNet, and while I have it running fine, I haven't updated KoboStuff with the final round of fixes, and I won't be able to do so until next week ).

[NiLuJe]

Err, actually, the crash.log would be a good start ^^.

[koboje]

Originally Posted by NiLuJe

Err, actually, the crash.log would be a good start ^^.

Device: Kobo Elipsa FW: 4.28.17925 (latest)


Log:

07/23/21-20:42:56 INFO Kobo Wi-Fi: enabling Wi-Fi
ifconfig: SIOCGIFFLAGS: No such device
07/23/21-20:43:13 INFO quitting uimanager


Hope this is the right log. Oh btw, wifi works very well on my libra running the latest stable release. It could be something to do with naming of elipsa wifi chip?

[koboje]

Duplicated post. Sorry!!

[NiLuJe]

Ideally, I'd need the full file .

[Zac Ereader]

Can't get KOReader to launch on a Mini. Clicking on the icon does nothing.

Using a Kobo Mini with stock firmware:
FW 3.19.5761

Tried the one click installations:
OCP-KOReader-v2021.06.zip
OCP-Plato-0.9.17_KOReader-v2021.06.zip

Installs OK but neither seems to launch KOReader. Log file is empty.

Ideas? How to launch KOReader on a Mini?

[NiLuJe]

NickelMenu doesn't support FW 3.19, so, clarify what you mean by "icon".

(KFMon *might* support it, but it's admittedly only been tested on FW >= 4.8).

TL;DR: Update to the current FW release first (you'll have to do so manually, because the Mini is strangely locked from OTA updates).

[vintodrimmer]

Originally Posted by koboje

That's good enough if we can highlight with the pen! Can't wait!!!!!! Is https://build.koreader.rocks/download/nightly/ the link for nightly download?

Thanks for the link!
I was having troubles building it myself, but the nightlies work perfectly on my Elipsa.

On a general note, I have a couple of questions, that I failed to quickly find an answer to. If there is an answer, please point me to the corresponding thread.
1. Is there a way to tweak the interface? Everything is frighteningly large right now. I don't think I've seen a corresponding option in the advanced menu, but I'd be glad if there is a possibility to change the fond size for the GUI. I think I had similar experience some 5 years ago with Kindle.
2. Is there no way to read the books that were sent to Kobo using Calibre Web? It's not a large issue, since I'm planning on running a syncthing instead, but would be nice to transfer my current reading progress.

[NiLuJe]

1. There's a DPI setting in [Gear] > Screen (or somewhere around there ;p).

2. If they're sent somewhere in the .kobo folder, see the previous answers about that in this very thread ;p (they're about the native Dropbox folder, but the principle is the same).

[vintodrimmer]

Originally Posted by NiLuJe

1. There's a DPI setting in [Gear] > Screen (or somewhere around there ;p).

2. If they're sent somewhere in the .kobo folder, see the previous answers about that in this very thread ;p (they're about the native Dropbox folder, but the principle is the same).

Thanks!

Does anyone use SSH-key authorization? I might need some assistance.

I created a new RSA key-pair and cat it into into `/mnt/onboard/.adds/koreader/settings/SSH/authorized_keys`. When trying to connect I get a password prompt.
I tried using a directory instead and dropping the .pub files inside, setting common file permissions, using the "-i" flag instead of `keychain` and so on to no avail.
I'm pretty sure I'm missing something obvious, but can't quite put my finger on it.
Should I create a key from root user?

Additionally, when I press on "SSH public key", it shows me where to put my public SSH keys. I assume it doesn't recognize the keys and would have otherwise changed to the list of added keys?

[NiLuJe]

I've never set this up because reasons. (i.e., I hate this plugin in KOReader with a fiery passion, because it's a giant PITA to maintain the pile of hacks necessary to make it somewhat user-friendly, which, case in point: it isn't ).

I assume I did quickly check that the patch worked at one point, though ;D (EDIT: Yup, I've got an old authorized_keys in there, so, at least, that looks right. I can't vouch for your kchain alias, but I don't have any issues with a pam_ssh and/or keychain @ login workflow over here. Double-check that you actually have an ssh-agent running with the right key loaded? (ssh-add -l)).

As usual in this situation, try running your client session with -vvvv, as well as checking the server logs (via logread), that may shed some light on the issue.

EDIT²: And, no, AFAICT, the "SSH public key" field/button/whatever being visible has no bearing on your actual setup, it's always there.

[vintodrimmer]

Originally Posted by NiLuJe

I've never set this up because reasons.

As usual in this situation, try running your client session with -vvvv, as well as checking the server logs (via logread), that may shed some light on the issue.

Thanks for the `-vvv`. Apparently, Fedora silently disabled RSA and I was getting "debug1: send_pubkey_test: no mutual signature algorithm".

In the end I switched to your tools, since they "just work" with my existing ed25519 keys and have a config I can find/modify.

Spoiler:

I was looking for a reason to ditch Fedora on my desktop for a while, after it messed up containers on my server.

[VeronikaMD]

Originally Posted by NiLuJe

I actually never checked how far the pen buttons get picked up, but that's an interesting idea if it works from a reasonable distance .

I won't have time to look into it until the end of *next* week, though .

@Frenzie: In Nickel, the bottom button is a highlighter (free and converted to actual highlights when it crosses word boxes) and the top one an eraser.

----

As promised, I've just updated the OCP with today's nightly .

Hi !

A big thank you for this new OCP (I use Koreader especially for the contrast change in PdFs) : It works so well now on Kobo Elipsa !!

[embryo]

3333 ;o)