View Single Post
Old 05-11-2013, 02:58 PM   #365
trex_daemon
Enthusiast
trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.trex_daemon is faster than slow light.
 
Posts: 25
Karma: 29826
Join Date: Oct 2012
Device: kindle 3 Wifi
Quote:
Originally Posted by knc1 View Post
1) Which is where it typically stops when it checks if the battery's storage capacity is enough to run it.
Buy it a new battery. -- The step your Uncle missed.
(It wasn't "drained" but it certainly had aged before you got it.)

2) That would be a good idea, the kernel's ring buffer will have the battery info in it.
And anything else that might be blocking the boot-up process.
Also, there is a chance it is waiting for input on the serial port to confirm that it should continue the boot process under whatever condition it is finding.

3) In "Debug mode" on a K3 - you are running the Linux kernel with only different init scripting. (K3 does not have "main" and "debug" systems - just different init scripting).
One of the differences - -
It does not check the battery storage capacity nor set-up the battery management hardware the same.

Thanks for the fast answer!
At first I was also suspecting the battery. However, I've tried the battery in a different Kindle, where it booted without problems, and I was able to charge it with both the broken and the working one.
Note: When I've charged it with the broken one, after it was fully chaged, the yellow light changed to green. I've noticed that when there was no kernel running on it, the light stayed always yellow. As i've seen in some documentation, the kindle is able to charge the battery only if the kernel is running. Also, after a fully charge, the battery has 4.1V. So definitely it's not dying.

I suspect the same thing that you have pointed out: that the boot process somwhere is waiting for some input. However, I cannot find an 1.8V FTDI converted, only 3.3V.
That's why I was thinking that if I could export some debug info to the SDCard, maybe with some custom kernel, i could find out what's wrong.

The debug menu shows up, I can access the internal SD card, that means that the kernel did not panic, right ?

So it must be something with the startup scripts.

What is exactly rewritten when writing "partition3" and kernel ?
Aren't also the init scripts rewritten ?

Otherwise I cannot explain why it gets stuck also after flashing everything from a working kindle and later flashing with the live cd...
trex_daemon is offline   Reply With Quote