05-26-2020, 02:48 PM | #106 | |
Grand Sorcerer
Posts: 6,216
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
ETA: Posts #2 and #63 updated with the new info about overwriting system fonts. Last edited by jackie_w; 05-26-2020 at 04:55 PM. Reason: ETA |
|
05-26-2020, 03:44 PM | #107 |
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
|
Nothing should actually *write* to the rootfs at runtime, so the most plausible source of potential issue would be running out of free space *during* an update.
|
Advert | |
|
05-26-2020, 06:05 PM | #108 |
Bibliophagist
Posts: 40,363
Karma: 156982136
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
AFAIR, the update is unpacked on the FAT32 partition and then copied to the root partition. Keep less than 100MB free on the FAT32 partition and updates will happily fail with an error message.
Last edited by DNSB; 05-26-2020 at 06:09 PM. |
05-26-2020, 11:55 PM | #109 |
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
|
@DNSB: That's... not actually clear to me.
That there'd be a free space check during the update's *download* OTA, sure, why not. But I'm concerned with storage issues in the rootfs, not the USB partition . And there, the actual installation is basically an unchecked tar call. There's an integrity check *before* the unpack, but that would have no bearing on a storage space issue arising *during* the unpack. The only thing that would flag such a failure is the lack of an updated revinfo entry in the install log (/usr/local/Kobo/install.log). It'll happily keep on trucking and try to install the kernel, bootloader & co, even if the unpack screwed up first. (Which, granted, would probably not be *that* problematic, because those don't live in the rootfs). ---- That said, we currently have quite a bit of leeway in terms of free space there, so I wouldn't worry too much about it, especially given the fact that the only people actually putting stuff in the rootfs ought to know what they're doing in the first place . Last edited by NiLuJe; 05-27-2020 at 12:00 AM. |
05-27-2020, 07:26 AM | #110 |
Guru
Posts: 884
Karma: 270656
Join Date: Jun 2016
Device: Kobo
|
@NiLuJe
Delete these fonts Code:
8472 -rw-r--r-- 1 root root 8.3M May 14 14:15 KBJ-TsukuMinPr6N-RB.ttf 3811 -rw-r--r-- 1 root root 3.7M May 14 14:15 KBJ-UDKakugoPr6N-M.ttf 4523 -rw-r--r-- 1 root root 4.4M May 14 14:15 ub_arudjingxihei.ttf |
Advert | |
|
05-27-2020, 08:49 AM | #111 | |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
|
|
05-27-2020, 03:57 PM | #112 | |
Bibliophagist
Posts: 40,363
Karma: 156982136
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
|
|
05-27-2020, 04:03 PM | #113 |
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
|
@DNSB: There's *never* an unpack to the FAT32 partition? There's no "copy" to the rootfs either.
There's a "copy" (i.e., a download by Nickel, OTA; or a manual copy by the user, via USBMS) of the KoboRoot tarball + upgrade folder to the FAT32 partition, then there's an unpack from there to the rootfs during the update process. (Semantics, true, but that needed clarification not to confuse my point, which was solely about the actual unpack process to the rootfs, during which the state of the FAT32 partition is irrelevant, as nothing gets written to it ). EDIT: Okay, I was indeed glossing over a step in case of an OTA, assuming Nickel downloads the kobo-update ZIP first, actually stores it on disk, and then unpacks it, there's indeed an extra unpack to the FAT32 partition there, my bad . I'm not familiar with the actual implementation, but it could just as well be "streaming" the unpack straight from memory, without needing the ZIP data to ever make it to disk. Worth mentioning, but not the step I was concerned with . Last edited by NiLuJe; 05-27-2020 at 04:13 PM. |
05-27-2020, 05:37 PM | #114 | |
Bibliophagist
Posts: 40,363
Karma: 156982136
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
Code:
nickel: ( 334.153 @ 0x179fa08 / ui.warning) void Unzipper::startWork() "/mnt/onboard/.kobo/updatefilename.zip" failed verify |
|
05-27-2020, 07:07 PM | #115 |
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
|
@DNSB: Well, that's not terribly efficient, but, oh, well. .
In any case, that's definitely not the step I'm concerned with (which is partly why it completely skipped my mind ^^), but thanks for the details . AFAIK, nickel itself never deals with the KoboRoot (by which I mean unpacking it), that's left entirely to the init script, so I'm mightily confused by you two final sentences. The naively sane approach to the zip unpack failing would be to clean up and forget about it (or retry a fresh and/or delta download), not continue to attempt an update from half-broken assets? |
05-28-2020, 01:21 AM | #116 | |
Bibliophagist
Posts: 40,363
Karma: 156982136
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
Looking at the rcS, upgrade-wifi.sh and upgrade-generic.sh, it would appear that if /mnt/onboard/.kobo/KoboRoot.tgz exists, the first step is to set the boot to the recovery partition. Code:
dd if=$UBOOT_RECOVERY of=/dev/mmcblk0 bs=128k count=1 seek=6 A few oddities. If a Kobo.tgz file is found, it seems to be treated the same as KoboRoot.tgz but is unpacked into /usr/local/Kobo. No check for the upgrade directory is made and the two upgrade-*.sh scripts are not run and no reboot is done. I will admit I haven't played much with Kobo's startup scripts since I stopped trying to use advboot for playing with KOReader 5 or 6 years ago. |
|
05-28-2020, 01:31 AM | #117 |
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
|
@DNSB: Yep, that's it. I got the impression you were saying that *nickel* was handling part of that after the download, which is what was confusing me .
(That and the use of "file copy" to describe what tar's doing when unpacking. But I get what you were trying to say now ^^ (i.e., unlink() -> sendfile() [well, a pair of read() + write() because the (un)compressor filter writes to a pipe]). The Kobo vs. KoboRoot thing might be related to how a factory reset reinstall is handled (or not, I'm possibly getting my wires crossed with Kindles, there ). Last edited by NiLuJe; 05-28-2020 at 02:07 AM. |
05-28-2020, 01:57 AM | #118 | |
Bibliophagist
Posts: 40,363
Karma: 156982136
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
I don't think Kobo vs. KoboRoot is related to a factory reset. In theory, nothing should write to the recovery partition so Kobo would not make it that easy. When I was playing with updating the recovery image for a Glo, I had the uSD card mounted on my laptop and still have rather copious notes on how many ways I found to not create a valid recovery image. |
|
04-30-2024, 11:48 AM | #119 |
Junior Member
Posts: 4
Karma: 10
Join Date: Jun 2023
Device: Kindle Paperwhite (11th Gen)
|
Looks like the new colour Kobos no longer ship with Avenir and Georgia, so the old trick doesn't work. Can anyone help me figure out which default fonts are used for the interface?
Thanks. |
04-30-2024, 01:39 PM | #120 | |
Resident Curmudgeon
Posts: 76,310
Karma: 136006010
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
https://en.fontsloader.com/types/avenir Georgia https://en.fontsloader.com/types/georgia After looking at some of the user photos posted on MR, I like the sans-serif font better then the Avenir and the serif font is similar enough to Georgia that it makes no real difference. Last edited by JSWolf; 04-30-2024 at 01:43 PM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PRS-T1 Support for FB2 format, folders & non-Latin languages? | boren | Sony Reader | 8 | 08-08-2023 12:43 PM |
Oddball writing systems & Non-ISO 639-2 Languages | Fiat_Lux | Library Management | 0 | 10-31-2014 01:35 PM |
Fonts supported by K4 & KT | ElMiko | Amazon Kindle | 28 | 09-05-2012 03:19 PM |
Touch Ad-supported Kobo Touch? | FJames | Kobo Reader | 6 | 11-25-2011 08:26 PM |
TOPAZ & Other Languages | molochei | Kindle Developer's Corner | 1 | 06-06-2008 06:57 AM |