Quote:
Originally Posted by NiLuJe
I tend not to respond when I have no idea  .
Random somewhat related comments:
* Patching diags to get SSH in there and make it stick is kind of the RescuePack's sole purpose in life .
* I don't think anyone ever attempted anything related to USBSerial (I'm not even sure the kernels support that gadget). So, yeah, monitoring would be far more reliable over serial.
If it does boot, the kernel logs are somewhat sanely archived by the logging system, although this sometimes goes a bit wonky. |
Ah, good for making that known! I thought you gave up on this
I did know that there was something "called" a Rescue Pack (specifically, it's when I noticed this in your Snapshots thread), but I thought it was for bricked Kindles, and didn't read the thread. And I wish I had read this, because it would have saved me a whole load of effort (half of which has been head-scratching because
ENABLE_DIAGS did nothing on a Kindle w/o Rescue Pack
So, do you think I should jump right in?
I'm going to
dd if=rootfs.img of=/dev/mmcblk0p4 bs=4096 via a SSH session from diags, then copy
/opt/amazon/low_level_screens/* from the Touch
rootfs and reboot.
If that doesn't work, I'm going to throw in the contents of
/lib/modules/* as well [1]
Anything I should know?
P.S.
[1]: I thought about this because of this quote by @knc1:
Quote:
The Linux kernel (as used in the Kindles) is not a monolithic, self-contained, kernel image.
Some of its services are provided by dynamically loaded "kernel modules" (things like the e-ink display drivers).
"kernel modules" live inside of the file system image.
Translation: You must use "matched pairs" of a file system image (the loadable modules ++ other stuff) and a kernel image.
|