![]() |
Re: Update for Enhanced kernel for power users just released
I can't in good conscience vote on 42 when I went almost instantly to 46.
|
Re: Update for Enhanced kernel for power users just released
What is ur dev revision ? 2204 ? PR 1.2 ? Has anyone had trouble playing SDLMame or Mame with CPU at 1 Ghz and dualshock connected?
|
Re: Update for Enhanced kernel for power users just released
@ Geneven. What is ur device revision? PR 1.2 or PR 1.3 ? Do you play psx4all or mame with 1 Ghz overclocked?
|
Re: Update for Enhanced kernel for power users just released
Quote:
ten characters |
Re: Update for Enhanced kernel for power users just released
Quote:
Uboot is great, in principle, of course. But not every uboot build play that well in real situations. Just my 2 cents. |
Re: Update for Enhanced kernel for power users just released
Quote:
|
Re: Update for Enhanced kernel for power users just released
Quote:
The fact of the matter is that U-boot did not play well with a pre-installed multiboot and folks could not load a kernel, and yes most of the people I discussed this with tried pretty much everything including your suggestion to get the battery charged, all of them had to get it charged externaly. From my observations, I believe that some part of the kernel must be loaded before the device can charge - try it yourself, turn off the phone, plug it in and watch as the 5 dots appear before it starts charging. |
Re: Update for Enhanced kernel for power users just released
Quote:
Quote:
The problem that was with power44 was that the combination of NOLO and u-boot on HW revision 2204 leaves the system in a state that causes the kernel to hang at start. Quote:
How do you know when it starts charging? |
Re: Update for Enhanced kernel for power users just released
Just want to ask again: could it be some conflict between uboot and HW versions? If so then would it be good the mention the HW versions that have tested the kernel and uboot?
|
Re: Update for Enhanced kernel for power users just released
Matan, on your first point its really a matter of interpretation, from wiki:
"When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my MP3 player when I tried to modify its firmware."[1] In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement. However, it is common to use the term for a problem which can be rectified but only by a complex and difficult procedure, often requiring additional software." I wasn't aware that it was a conflict of the HW revision and V44 , it was an assuption that I had made regarding multi-boot. Anyway - on the battery issue, I can confirm you are right. I am running V45 and have just left my device at the U-boot screen when plugged into the wall for the last few minutes (I have had to cancel loading by pressing a keyboard key periodically as it will only sit at the Tux screen for a little while before reloading). I then booted and opened BatteryGraph - it now has more capacity than when I first turned it off, so hardware is charging the battery. However it don't understand why some people were claiming to have left their device plugged in for some time and were unable to flash, I doubt that they are lying. Perhaps the error, or reboot loop was in some way draining more power than was being supplied, the only way to check for sure would be to revert to V44 for testing. |
| All times are GMT. The time now is 13:58. |
vBulletin® Version 3.8.8