Reply
Thread Tools
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#2151
Originally Posted by ade View Post
I'm having the problem that disabling HEN usb mode makes my phone reboot. I did not experience that a few weeks ago when I last used this.

Some last moment messages I see in syslog:
Code:
ov 20 13:11:18 Nokia-N900 BME: pre-start
Nov 20 13:11:18 Nokia-N900 BME: starting battery precharge
Nov 20 13:11:18 Nokia-N900 BME: precharge -> failure
Nov 20 13:11:18 Nokia-N900 BME: start
Nov 20 13:11:18 Nokia-N900 init: bme main process (2296) terminated with status 1
Nov 20 13:11:18 Nokia-N900 BME: post-stop
Nov 20 13:11:19 Nokia-N900 init: console main process (2302) terminated with status 2
Nov 20 13:11:19 Nokia-N900 BME: crash detected -> rebooting
Nov 20 13:11:19 Nokia-N900 DSME: reboot request received from pid 2306: (no such process)
Nov 20 13:11:19 Nokia-N900 DSME: Reboot
Nov 20 13:11:19 Nokia-N900 DSME: state change request: DSME_STATE_USER -> DSME_STATE_REBOOT
Nov 20 13:11:19 Nokia-N900 DSME: new state: DSME_STATE_REBOOT
Nov 20 13:11:19 Nokia-N900 DSME: Shutdown in 2 seconds
It looks like the BME re-enabling fails...

Could it be related with the lastest kernel v49 version? I would be happy if someone could test hen-usb mode for me.
Most, likely, this is caused by bq27x00_battery.ko module loaded during boot - it loads first, then open path for bme. Ho ever, after stopping bme, starting it again result in reboot (to protect device from possible harm, by 2 thing accessing same i2c bus simultaneously. In KP's up to 47, there was a "path" that allowed them to co-exist together, but it was considered possibly harmful for the device. Real risk is disputable, and it depends how things are "protected" - in best case, during such risky situation bq27x00_battery just got "confused", in worst case, it may result in random, dangerous things related to hardware. So, with no doubts, disabling this "path" is improvement (trust me, I was very skeptic about removing it, and dig deep to get info why it's necessary).

First of all, you should check '/etc/modprobe.d/blacklist' - it should contain:
Code:
blacklist bq27x00_battery
If this is present, You should check '/etc/modules'. It's possible, that it contains bq27x00_battery entry there - mysteriously, it happened to me, while upgrading to kp49. Modules from this list, are loaded during boot regardless of blacklist entry (thanks to Pali for that info), so you should *remove* it from here.

After that, reboot, and Your issue should be fixed.

/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 3 Users Say Thank You to Estel For This Useful Post:
Alfred's Avatar
Posts: 855 | Thanked: 612 times | Joined on Oct 2010 @ Germany
#2152
@trisha
Use the appropriate thread 720p playing, and also read the first post over there.
__________________
Reps are just one click away: Extras | Extras-Testing | Extras-Devel | My-Maemo | CSSU |
Transform your lock screen into a weather forecast Thanks button ================>
 

The Following User Says Thank You to Alfred For This Useful Post:
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#2153
Originally Posted by Estel View Post
Most, likely, this is caused by bq27x00_battery.ko module loaded during boot - it loads first, then open path for bme. Ho ever, after stopping bme, starting it again result in reboot (to protect device from possible harm, by 2 thing accessing same i2c bus simultaneously. In KP's up to 47, there was a "path" that allowed them to co-exist together, but it was considered possibly harmful for the device. Real risk is disputable, and it depends how things are "protected" - in best case, during such risky situation bq27x00_battery just got "confused", in worst case, it may result in random, dangerous things related to hardware. So, with no doubts, disabling this "path" is improvement (trust me, I was very skeptic about removing it, and dig deep to get info why it's necessary).

First of all, you should check '/etc/modprobe.d/blacklist' - it should contain:
Code:
blacklist bq27x00_battery
If this is present, You should check '/etc/modules'. It's possible, that it contains bq27x00_battery entry there - mysteriously, it happened to me, while upgrading to kp49. Modules from this list, are loaded during boot regardless of blacklist entry (thanks to Pali for that info), so you should *remove* it from here.

After that, reboot, and Your issue should be fixed.

/Estel
kernel-power installs it own modproble blacklist file with blacklisted bq module too: /etc/modprobe.d/kernel-power.blacklist
 

The Following 5 Users Say Thank You to pali For This Useful Post:
Posts: 3 | Thanked: 1 time | Joined on Oct 2010 @ Philadelphia, PA
#2154
Originally Posted by TMavica View Post
nono, i know need to del this line, because without load bq2700, then delete this line, reboot loop will be happened

just want to know how to enable bq2700 at startup
just same as before? add a line to the modules file?
I mistakenly delete the line, do you know how to recover it?

Thanks.
 
Posts: 6 | Thanked: 1 time | Joined on Oct 2011
#2155
Originally Posted by left View Post
So, not sure if this is the right place to post this, but still. Been running kernel-power (downloaded via appdownloader) for like 2 months, no problems whatsoever. This afternoon, I discovered massive performance issues on my N900. Blacked out, reacting very slow. After a few reboots, found out it had to do with my online status on Skype. As this is one of the main functions of this phone I intend to keep using it

So, tried it all. Deleted last installed apps, everything. Nothing helped. Also tried de-installing kernel-power. Didn't work (used the menu shortcut). Then reflashed after 3 hours of trying things out (this phone is my only one), everything seemed to work fine, could login to Skype without problems. Then installed kernel-power (again via appdownloader) and the problem of hanging, slow reactions and such was there again! This time, I could remove kernel-power through the menu, and it looks like my N900 runs like before again. No troubles.

As you might have noticed, I'm far from an expert. Tried to look for general logfiles, but I cannot find them. I just don't have the knowledge. Just wanted to let you guys know what I experienced, it might not be related at all, but I don't have a clue.

Please let me know if I can be of any more help, and excuse me if this post doesn't belong here...
Guys, sorry for bringing this up again... Today I installed kp49, with hopes that the issue would be gone. Unfortunately, it's not. I would like to be able to use kp on my device, as well as cssu, so any help is appreciated! Problem occurs the moment I am actually signed in, during the signing-in process everything seems to be fine. Both on WiFi and 3G. It's making me headaces!

I reflashed, but didn't change anything to the emmc.
Any thoughts?
 
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#2156
Originally Posted by pali View Post
kernel-power installs it own modproble blacklist file with blacklisted bq module too: /etc/modprobe.d/kernel-power.blacklist
Estel,
Your suggestion was the right one. Thanks.

An "lsmod" gave me:
Code:
bq27x00_battery         6480  0 
power_supply            7108  1 bq27x00_battery
I removed the module using "rmmod", and indeed, no more reboots after closing hen-usb!

bq27x00_battery was blacklisted, but also mentioned in my /etc/modules, so it was loaded nevertheless. Removed it from /etc/modules and it is no longer loaded after a reboot.
 

The Following 2 Users Say Thank You to ade For This Useful Post:
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#2157
you can load bq27x00_battery only when bme is stopped.
and when you have enabled h-e-n bme is stopped.
 
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#2158
Originally Posted by pali View Post
you can load bq27x00_battery only when bme is stopped.
and when you have enabled h-e-n bme is stopped.
I am pretty sure that is not the case. bq27x00_battery was also loaded at boot time (next to BME). An lsmod just after boot showed me the module, and now that I have disabled bq27x00_battery, I have to read temperature values using i2cget and get different battery level indications (which is also an indication bq27x00_battery is no longer loaded). Estel also has the impression it is loaded at boot time. If you like you can test it by putting bq27x00_battery in /etc/modules.
 

The Following User Says Thank You to ade For This Useful Post:
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#2159
Do not add bq27x00_battery to /etc/modules !!! bq27x00_battery cannot live together with BME !!
 

The Following 2 Users Say Thank You to pali For This Useful Post:
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#2160
Originally Posted by pali View Post
Do not add bq27x00_battery to /etc/modules !!! bq27x00_battery cannot live together with BME !!
That turned out to be the cause my reboot problem as I described...
I was reffering to your remark that BME and bq27x00_battery cannot be loaded at the same time. They can, although it is not desirable as you rightly state.
 

The Following 2 Users Say Thank You to ade For This Useful Post:
Reply

Tags
battery-status, bq27x00_battery, kernel, kernel-power, misiak4king, noobs-cant-read, pali4president, patches, readdirections, revolverspinyou


 
Forum Jump


All times are GMT. The time now is 13:58.