I think you have broken it I'm afraid. I have had that but can't remember what I did to cause it. Only way I could fix it was a re-flash though.
Think you're right and I knew it soon as it happened. I had the same event occur before messing with it but was still able to access multiboot's menu to recover. Seems this happened because selected a menu option that looped back into the menu. Had I stopped there and power cycled I may have been ok but I selected another menu item. So I'm guessing I told it to boot from a faulty space where multiboot was not living. Thanks anyway. This was my first real fubar that required a flash and I expected it to happen sooner hehe
so you installed -kernel-power_2.6.28-maemo39_armel.deb and
-kernel-power-modules_2.6.28-maemo39_armel.deb
but not the -kernel-power-flasher_2.6.28-maemo39_armel.deb right ? probablly because i installed the flasher ? and cause the problem.
How can you install that ''most advanced module''? I'm having problems with NITDroid rebooting because of empty battery (while in fast it's not empty).
Led flashes red then my phone shuts down!!!
To the user who is having the Nokia splash screen, and immediate device halting - simply reflash the kernel from your FIACSO image, and it will boot properly.
alright...incase to prove that i didnt do anything, i format everything include eMMC..did a nice clean install...so i went to install NITDroid with multiboot and boot NITDroid fine and kernel v37...so then i installed
/kernel-power-bootimg_2.6.28-maemo39_armel.deb
/kernel-power-modules_2.6.28-maemo39_armel.deb
dpkg -i each file. Then i went make sure to see /lib/modules/ have:
2.6.28.10power37
2.6.28.10power39
2.6.28.NIT.05
then i went to /boot/ rename the current zImage-2.6.28-maemo39 to vmlinuz-2.6.28.10power39 then move to boot/multiboot/ then make sure i went there and see:
vmlinuz-2.6.28-omap1
vmlinuz-2.6.28.10power37
vmlinuz-2.6.28.10power39
vmlinuz-2.6.28.NIT.05
then i went to /etc/multiboot.d/ create a new Maemo-2.6.28.10power39.item and in it with:
ITEM_NAME="Maemo 2.6.28.10power39"
ITEM_KERNEL=2.6.28.10power39
ITEM_MODULES=ext3
.Double check everything and then reboot.. 1st time reboot , the menu option comes up so then i choose Maemo 2.6.28.10power39..Nokia Screen appears for seconds then shutdown, reboot 2nd time...no menu option instead just Nokia screen then shut down and keep looping like that if turn on device....no menu option and no booting into v39. So i have to use command flash-only=kernel to boot again into default kernel. Then i reboot from default kernel to choose powerv.37 then it boot into power.v37 fine...
so any sugesstion why v37 work but not v39?
So then i tar the file early installed from NITDROID (multiboot-power37.tar.gz) to see what in there...all i see was boot,etc,lib folder and i did make sure all the v39 files are silmulate with v37.tar but still no luck to boot into v39, perhaps It is v39 ?
If I read correctly, this module allows you to check battery temp? How do you actually check it and I have a play around and see if I can work anything out.
E: nope, that didn't work. Will contact jay-c and see what he says.
Well after booting power37 i can load the battery module with:
Code:
modprobe bq27x00_battery
The problem is autoloading that module but as Jay-C posted:
alright...incase to prove that i didnt do anything, i format everything include eMMC..did a nice clean install...so i went to install NITDroid with multiboot and boot NITDroid fine and kernel v37...so then i installed
/kernel-power-bootimg_2.6.28-maemo39_armel.deb
/kernel-power-modules_2.6.28-maemo39_armel.deb
dpkg -i each file. Then i went make sure to see /lib/modules/ have:
2.6.28.10power37
2.6.28.10power39
2.6.28.NIT.05
then i went to /boot/ rename the current zImage-2.6.28-maemo39 to vmlinuz-2.6.28.10power39 then move to boot/multiboot/ then make sure i went there and see:
vmlinuz-2.6.28-omap1
vmlinuz-2.6.28.10power37
vmlinuz-2.6.28.10power39
vmlinuz-2.6.28.NIT.05
then i went to /etc/multiboot.d/ create a new Maemo-2.6.28.10power39.item and in it with:
ITEM_NAME="Maemo 2.6.28.10power39"
ITEM_KERNEL=2.6.28.10power39
ITEM_MODULES=ext3
.Double check everything and then reboot.. 1st time reboot , the menu option comes up so then i choose Maemo 2.6.28.10power39..Nokia Screen appears for seconds then shutdown, reboot 2nd time...no menu option instead just Nokia screen then shut down and keep looping like that if turn on device....no menu option and no booting into v39. So i have to use command flash-only=kernel to boot again into default kernel. Then i reboot from default kernel to choose powerv.37 then it boot into power.v37 fine...
so any sugesstion why v37 work but not v39?
So then i tar the file early installed from NITDROID (multiboot-power37.tar.gz) to see what in there...all i see was boot,etc,lib folder and i did make sure all the v39 files are silmulate with v37.tar but still no luck to boot into v39, perhaps It is v39 ?
I can confirm everything is working perfectly here.
I installed kernel-power-bootimg and kernel-power-modules,
renamed the zImage and modified the .item file.
Booted fine with the first attempt.
If you have problems, it's highly likely there is a typo somewhere.
Cheers
Jay-C
Should I have power 37 installed (flashed) before this?
edited:
No need for v 37. Just make sure that name of bootimage is exactly correct. In my case I was (after dozen of rechecks) missing .10 from name. I had xxxxxpower39 instead of xxxxx.10power39. Did not realize I had to use exactly the same name as instructed Stupid, stupid, stupid....
To the user who is having the Nokia splash screen, and immediate device halting - simply reflash the kernel from your FIACSO image, and it will boot properly.
''
I wanted to openly thank you also, seems my occurred because I did not have the modules installed at least the 2nd time I had the occurrence after reflash. Thanks because that step saved me the second time. Cheers!
Is there an issue with users having 2.6.21 vs 2.6.28 in their .item file, half the the posts have one and have the other, this may be causing some issues.
Stupid, stupid, stupid....