View Single Post
Old 06-04-2012, 11:28 AM   #12
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
So what you are saying is that the output is the same for the working unit you refer in this (#11) post and the broken unit you refer to in the OP (#1)? Or are you referring to the same unit?

If so: The working unit should show more output, I think.

The "Hit any key to stop autoboot" indeed indicates that at that point, you could make appear a menu or similar means within uboot. Did you hit a key at that point and looked what happens? Of course I mean for the blocked unit you refer to in #1.

As a side note: That this looks the same on the bricked kindle and working kindles still does not prove that the kernel of the bricked unit is OK. It's just a hint that it might be.

Ownership of the tty device on the host machine certainly isn't the culprit here. You wouldn't see anything if that were the case, and facing a permission error instead.
hawhill is offline   Reply With Quote