Quote:
Originally Posted by knc1
But the kernel firmware is not limited to just the version.
You must have matching builds of all modules.
Some of those are in the initramfs (u-image) and some are in the usual /lib/modules/<version>/* (rootfs.img) file system path.
And when you are re-building the PW kernel&modules for the touch kernel&modules hardware (including e-ink differences) don't forget that you must get everything ABSOLUTELY correct.
(If the newly built kernel hangs, while booting the kindle ...)
|
Does that result in a permanent brick?
This is currently my biggest fear, as I don't have a serial cable, nor are my soldering skills any good.
Quote:
If you must insist on doing this -
You really should set-up the touch hardware to load the new, test u-image&rootfs.img combination over the network rather than committing to the flash drive hardware.
(Yes, the 5.x series hardware support includes loading over the network.)
|
I think I'm pursuing 5.4.x for now, and if that works out, I'd move up. At least, I'd be targeting the original Paperwhite. The SoC is the same, so the kernel version is hopefully the same!
Quote:
Originally Posted by NiLuJe
@WaseemAlkurdi: 2.6.31 on the Touch (at least originally. Might have been updated later, although I doubt it).
|
You're right, it is 2.6.31 indeed. But is a x.x.01 difference significant when it comes to making or breaking libc, especially when that difference is likely to be minor patches?
But anyhow, it's going to be 5.4.x first, as no kernel work is required (if the versions turn out to be identical).