Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (6)
to General by Kalatti - 5 days, 4 hrs ago - more...
|
2010-08-04
, 04:49
|
|
Posts: 58 |
Thanked: 10 times |
Joined on Jan 2010
|
#32
|
@petur : I dont think all devices would be lucky to be stable for the ideal profile. I used to get reboots after every 10 minutes. Currently am using LV profile and its been stable till now.
@brandl: If you type kernel-config show you will see that 125 and 250 are included in the avoid frequencies, this is the default for the ideal profile , this is not a bug but intended to make the device more snappy.
@brandl: If you type kernel-config show you will see that 125 and 250 are included in the avoid frequencies, this is the default for the ideal profile , this is not a bug but intended to make the device more snappy.
 |
|
2010-08-04
, 07:55
|
|
Posts: 34 |
Thanked: 12 times |
Joined on Nov 2009
@ Girona, Spain
|
#33
|
Originally Posted by tzsm98
I found the changelog in garage information but with no information of build 39. I assume that are technical and internal updates with not big features.
I see an update to the enhanced linux kernel is available. Anyone had an issue with it? I ask only because of the instabilities that cropped up in one of the versions between v24 and about v29.
edit: it loaded and runs fine for me. No sign of instability. Saw v39 was in the works but it was not in "one stop shopping" form whenI looked.
__________________
Yesterday is history
Tomorrow is unknown
Today is a gift
Tomorrow is unknown
Today is a gift
|
|
2010-08-04
, 16:15
|
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#34
|
i'm also very interested in the changelog
|
|
2010-08-04
, 18:46
|
|
Posts: 52 |
Thanked: 55 times |
Joined on Dec 2009
|
#35
|
Best I can figure build 39 incorporates the patch to work arround Errata 4530973:
I have very little understanding on what that could possibly mean.
This option enables the workaround for the 430973 Cortex-A8
(r1p0..r1p2) erratum. If a code sequence containing an ARM/Thumb
interworking branch is replaced with another code sequence at the
same virtual address, whether due to self-modifying code or virtual
to physical address re-mapping, Cortex-A8 does not recover from the
stale interworking branch prediction. This results in Cortex-A8
executing the new code sequence in the incorrect ARM or Thumb state.
The workaround enables the BTB/BTAC operations by setting ACTLR.IBE
and also flushes the branch target cache at every context switch.
Note that setting specific bits in the ACTLR register may not be
available in non-secure mode.
|
|
2010-08-05
, 14:23
|
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#36
|
Indeed, interesting but somewhat cryptic.
Originally Posted by coreyoconnor
Best I can figure build 39 incorporates the patch to work arround Errata 4530973:
I have very little understanding on what that could possibly mean.
|
|
2010-08-05
, 15:31
|
|
Posts: 221 |
Thanked: 51 times |
Joined on Nov 2009
@ Germany
|
#37
|
...in extras catalouge ("stable software") you have only v37; v39 is in extras-devel ("unstable").
Titans comment on v39:
"v39 merely adds a kernel-power-bootimg package which could be useful for multiboot.
users should just stick with v37"
Source: http://talk.maemo.org/showpost.php?p...&postcount=109
Edit: btw - on my device v39 runs just fine - no problem.
Last edited by HugoSon; 2010-08-05 at 15:33. Reason: Edit:
Titans comment on v39:
"v39 merely adds a kernel-power-bootimg package which could be useful for multiboot.
users should just stick with v37"
Source: http://talk.maemo.org/showpost.php?p...&postcount=109
Edit: btw - on my device v39 runs just fine - no problem.
Last edited by HugoSon; 2010-08-05 at 15:33. Reason: Edit:
|
|
2010-08-06
, 11:34
|
|
Posts: 62 |
Thanked: 6 times |
Joined on Jun 2010
@ Poland
|
#38
|
On my device, kernel power39 works fine too.
__________________
Maemo Meego Maego!
Maemo Meego Maego!
|
|
2010-08-07
, 07:37
|
|
Posts: 92 |
Thanked: 17 times |
Joined on Feb 2010
|
#39
|
I've updated yesterday. No visible change either.
|
|
2010-08-09
, 17:08
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#40
|
I used the power kernel in the past but suddenly I got battery drain problems and went back to the stock kernel. Battery drain was not over yet and then found I had the hildon-desktop cpu usage problem. After removing the mymenu/catorize functionality I got reasonable battery lifetime again.
A couple of days ago I decided to go for the power kernel again. v39 was just released.
The first thing I noticed was a constant battery drain again. Even while doing nothing, and going completely offline during the night.
Then I saw the "dspbridge: timed out waiting for mailbox" messages in syslog/dmesg. I removed the dspbridge module. But still I get the same battery drain.
I also noticed problems with the camera/videorecorder. I can only take pictures in the automatic picture mode. Switching to for example night mode or video mode gives an "unexpected error occured".
So today I went back to the default kernel.
- battery drain is gone
- camera works fine in any mode again.
A couple of days ago I decided to go for the power kernel again. v39 was just released.
The first thing I noticed was a constant battery drain again. Even while doing nothing, and going completely offline during the night.
Then I saw the "dspbridge: timed out waiting for mailbox" messages in syslog/dmesg. I removed the dspbridge module. But still I get the same battery drain.
I also noticed problems with the camera/videorecorder. I can only take pictures in the automatic picture mode. Switching to for example night mode or video mode gives an "unexpected error occured".
So today I went back to the default kernel.
- battery drain is gone
- camera works fine in any mode again.
| The Following 2 Users Say Thank You to mirakels For This Useful Post: | ||
edit: it loaded and runs fine for me. No sign of instability. Saw v39 was in the works but it was not in "one stop shopping" form whenI looked.
A Thing of Beauty Is a Joy Forever
Last edited by tzsm98; 2010-08-03 at 22:43. Reason: update