View Single Post
Old 09-04-2015, 09:23 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
The problem I pointed out was with the kernel. The upgrade script generates a file name the includes the PCB. But, the mark4 firmware package doesn't include a kernel that matches the name generated for either the Glo or the N905C Touch. There is a version for the other devices in their packages.

I think I agree with the analysis here, but my shell scripting in rubbish and I need to actually test it before agreeing completely.

As to how much it matters, it really depends on how often the image and uboot are changed. From comparing the upgrades, it doesn't happen that often. But it does happen. And not upgrading these might explain some different behaviour that people see. And, from memory, the version of this in the recovery firmware for the Glo gets the names right. Which means the uboot and kernel are installed for next first update. And that probably explains why a factory reset fixes some of the unusual problems.
davidfor is offline   Reply With Quote