Reply
Thread Tools Search this Thread
Posts: 1,378 | Thanked: 1,910 times | Joined on Apr 2010 @ St. Helens, England
#121
Your walls of text are very awkward to read...

If you post these maybe it will help.

Code:
uname -r
Code:
sudo kernel-config show
Code:
sudo gainroot
cd /home/user/MyDocs
gzip -c /dev/mtd2 > mtd2.gz
__________________
The stable-beast currently runs...
21.2011.38-1Smaemo6 (CSSU Stable)
2.6.28.10power52 (125-600Mhz SR VDD1&2)

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap -


Before posting in a thread please try this.
Before starting a new thread please try this.
 

The Following 4 Users Say Thank You to sixwheeledbeast For This Useful Post:
Estel's Avatar
Posts: 3,840 | Thanked: 5,613 times | Joined on Mar 2011
#122
I've noticed, that - when charging via bq2415 module - leaving device "on cable" when fully charged for many hours, lead to crash 100% times. It happens, despite fact, that charging is terminated properly (no yellow light, no charging when checking current flowing).

I can't tell when it happens exactly, but it's happening 100% of times, when I leave N900 for overnight charging with bq2415. Strangely, after such crash, device remains in state, when I can see static framebuffer output *without* backlight.

After using external light to allow reading from out transreflective screen, I was able to see that it reported DSME state as DSME_MALF (instead of "USER" or "SHUTDOWN". Which, probably, mean "malfunction".

It's worth to mention, that even disconnecting from charger and long-press of power button doesn't turn device off - it's necessary to remove battery (and put it back again), to recover from this state.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 2 Users Say Thank You to Estel For This Useful Post:
Posts: 15 | Thanked: 3 times | Joined on Jul 2012
#123
Originally Posted by Estel View Post
I've noticed, that - when charging via bq2415 module - leaving device "on cable" when fully charged for many hours, lead to crash 100% times. It happens, despite fact, that charging is terminated properly (no yellow light, no charging when checking current flowing).

I can't tell when it happens exactly, but it's happening 100% of times, when I leave N900 for overnight charging with bq2415. Strangely, after such crash, device remains in state, when I can see static framebuffer output *without* backlight.

After using external light to allow reading from out transreflective screen, I was able to see that it reported DSME state as DSME_MALF (instead of "USER" or "SHUTDOWN". Which, probably, mean "malfunction".

It's worth to mention, that even disconnecting from charger and long-press of power button doesn't turn device off - it's necessary to remove battery (and put it back again), to recover from this state.

/Estel
As far as i know it does not crash completely. SSH should still work so you can still reboot.
I noticed that this error only occurs if the screen is off, so
I leave my screen on with simple brightness widget.
 

The Following User Says Thank You to projekt For This Useful Post:
Estel's Avatar
Posts: 3,840 | Thanked: 5,613 times | Joined on Mar 2011
#124
Are You sure, that, when leaving screen ON, bq2415 concludes charging, instead of charging indefinitely? It seems to me, that power draw, when screen is on, may be bigger than treeshold set for termination_current.

Thanks for confirming this bug, BTW! I had no idea, that it's in some kind of "working" state, despite no X (just framebuffer, if one have it enabled) 0_o.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 
Posts: 54 | Thanked: 23 times | Joined on Jun 2012 @ Hungary
#125
Hello guys, I have a problem with the included injection drivers.
With the first post linked .sh I got nothing like StefanL, so I decided to use his corrected version instead of Pali's.
the corrected .sh
But I think that this also fails to work.
Images showing the issue: terminal, failed to load modules
packet injection is still not active
If you can mention a power46wl1 and kernel 51 dual boot, it's an option, but I can't use u-boot, because I repartitioned the flash, and it cannot find bootmenu.scr.
What can I do with those modules to load? Please help.
 
Posts: 1 | Thanked: 0 times | Joined on Sep 2012
#126
Hi guys, i am still learning how to on my n900, and now i face this problem, i tryed search but no accured found, i made upgrade to KP51, as usual, all went well, but after few hours i found out, that when i recieve SMS there is no alert light and tone, unles i keep conversation window open on background, so i made clean flash, again install KP51, and i am using CSSU testing, and same problem. Is there anyone who hase same problem?? or somebody who can give me help how to fix this think
 
Posts: 15 | Thanked: 2 times | Joined on Jan 2012
#127
Hy guys ,
Sorry if my question is dumb , bear with me ...
I have 2.6.28-10power51 ,
I typed "sudo kernel-config show" but the "current kernel configuration" line is empty . however with "uname -r" command I see that I have the above version
My question is : is this the latest version ?
Fapman does not show me any updates available
 
Posts: 128 | Thanked: 170 times | Joined on Mar 2010
#128
Yes, that's the latest one. I don't think that line is supposed to contain anything else. It looks like it's just the 'introductory' text for the following.
 
Posts: 259 | Thanked: 200 times | Joined on May 2010
#129
guys i had some errors ?
Attached Images
 
__________________
- Building MMORPG game for N900 :
Progress :
- Game Engine :100%
- Buildings : 70%
- Next : Fleet management and ships factory , complete the map and scouts to explore the map .
 
Posts: 4 | Thanked: 0 times | Joined on Sep 2012
#130
On http://wiki.debian.org/ArmEabiHowto
i read that to keep compatibilty with old eabi and eabi
kernel should be compiled with

CONFIG_ARM_THUMB=y
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
______________________

On p51 i see only

# CONFIG_AEABI is not set
CONFIG_ARM_THUMB=y


Doesnt this break compatibility with old arm chroots? I cant chroot into an older arm etch for istance.
 
Reply

Tags
bq2415x_charger, bq27200, kernel-power

Thread Tools Search this Thread
Search this Thread:

Advanced Search

 
Forum Jump


All times are GMT -4. The time now is 12:06 AM.