Multiboot 0.2.5 released - Page 19 - maemo.org

sacal | # 181 | 2010-08-04, 19:28 | Report

Originally Posted by mornage View Post

OK, if I understand how this works, as you have your module specified in /etc/modules.boot you just need to tell multiboot to run it. modify your item file to

Code:

ITEM_NAME="Maemo 2.6.28.10power37"
ITEM_KERNEL=2.6.28.10power37
ITEM_MODULES=ext3 bq27x00_battery

Thanks again mornage

I followed your tip but unfortunately i wasn't able to autoload the module.

I have tried 3 different ways:

1 - i changed /etc/multiboot.d/Maemo-2.6.28.10power37.item as in your last post with no changes in /etc/modules and with no /etc/modules.boot file.
The system booted but the module wasn't loaded.

2 - Then i create a /etc/modules.boot file with:

Code:

#
# modules.boot
#
# List of modules the bootloader (multiboot) shall load.
# 
bq27x00_battery

After rebooting and choosing power37 the system just fails the boot process and i have to reboot omap1.

3 - Then i deleted /etc/modules.boot and changed /etc/modules with:

Code:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
bq27x00_battery

The system booted power37 normally but the module bq27x00_battery wasn't autoloaded.

I'm don't know how to use modules.boot.examples and i couldn't find any help about it. I wonder if the file name should have item id like modules.Maemo-2.6.28.10power37.item

Perhaps the developer Jay-C may help on this.

mornage | # 182 | 2010-08-04, 19:44 | Report

Originally Posted by sacal View Post

Thanks again mornage

I followed your tip but unfortunately i wasn't able to autoload the module.

I have tried 3 different ways:

1 - i changed /etc/multiboot.d/Maemo-2.6.28.10power37.item as in your last post with no changes in /etc/modules and with no /etc/modules.boot file.
The system booted but the module wasn't loaded.

2 - Then i create a /etc/modules.boot file with:

Code:

#
# modules.boot
#
# List of modules the bootloader (multiboot) shall load.
# 
bq27x00_battery

After rebooting and choosing power37 the system just fails the boot process and i have to reboot omap1.

3 - Then i deleted /etc/modules.boot and changed /etc/modules with:

Code:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
bq27x00_battery

The system booted power37 normally but the module bq27x00_battery wasn't autoloaded.

I'm don't know how to use modules.boot.examples and i couldn't find any help about it. I wonder if the file name should have item id like modules.Maemo-2.6.28.10power37.item

Perhaps the developer Jay-C may help on this.

One more thing you can try, try adding the module into modules.boot.example. It is the only place that I see the modules listed that the item files refer to.

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.

Last edited by mornage; 2010-08-04 at 20:18.

The Following User Says Thank You to mornage For This Useful Post:
sacal

xopher | # 183 | 2010-08-04, 20:28 | Report

Think I may have borked things a bit. I was playing with different item configs and now I have a solid white light when booting with the Nokia splash until the unit powers down abruptly. The multimenu does not appear when the keyboard is exposed. Any suggestions before I get home and perform a reflash? It also just hits a bootloop if I just plug it into a charger no flashy yellow to indicate charging.

Last edited by xopher; 2010-08-04 at 20:34.

mornage | # 184 | 2010-08-04, 20:53 | Report

Originally Posted by xopher View Post

Think I may have borked things a bit. I was playing with different item configs and now I have a solid white light when booting with the Nokia splash until the unit powers down abruptly. The multimenu does not appear when the keyboard is exposed. Any suggestions before I get home and perform a reflash? It also just hits a bootloop if I just plug it into a charger no flashy yellow to indicate charging.

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.

Jay-C | # 185 | 2010-08-04, 21:24 | Report

Originally Posted by mornage View Post

Ok, I'm now booted into power-kernel V39!! Here is what I did.

Boot maemo using power kernel.
Update power kernel to V39 via appman.
download this file to MyDocs
open xterm

Code:

sudo gainroot
cd MyDocs
mkdir Kernel
dpkg-deb -x kernel-power_2.6.28-maemo39_armel.deb /home/user/MyDocs/Kernel

This should extract all files from the deb file into the newly created Kernel folder. Now we move and rename the kernel into multiboot.

Code:

cd Kernel/boot
mv zImage-2.6.28-maemo39.fiasco /boot/multiboot/vmlinuz-2.6.28.10power39

You should now have the correct kernel in the correct place, with the correct name. All that is left now is to adjust the item file.

Code:

cd /etc/multiboot.d
nano Maemo-2.6.28.10power37.item

Change the following lines

Code:

ITEM_NAME="Maemo 2.6.28.10power37" to ITEM_NAME="Maemo 2.6.28.10power39"
ITEM_KERNEL=2.6.21.10power37 to ITEM_KERNEL=2.6.21.10power39

Reboot and you should now see the new kernel where the old one was.

Please bear in mind that I am in work and get regularly interrupted by people calling. Although I have tried my best to ensure everything is spelled correctly, there may be a few typos so I recommend using tab to complete paths and file names.

Edit, to quote titan:

So you really do not need to do this. The guide is only really for people that already have. (i.e 1st steps have been done and you have had to boot back into default maemo)

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

The Following User Says Thank You to Jay-C For This Useful Post:
jurgel

Jay-C | # 186 | 2010-08-04, 21:28 | Report

Originally Posted by sacal View Post

Thanks again mornage

I followed your tip but unfortunately i wasn't able to autoload the module.

I have tried 3 different ways:

1 - i changed /etc/multiboot.d/Maemo-2.6.28.10power37.item as in your last post with no changes in /etc/modules and with no /etc/modules.boot file.
The system booted but the module wasn't loaded.

2 - Then i create a /etc/modules.boot file with:

Code:

#
# modules.boot
#
# List of modules the bootloader (multiboot) shall load.
# 
bq27x00_battery

After rebooting and choosing power37 the system just fails the boot process and i have to reboot omap1.

3 - Then i deleted /etc/modules.boot and changed /etc/modules with:

Code:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
bq27x00_battery

The system booted power37 normally but the module bq27x00_battery wasn't autoloaded.

I'm don't know how to use modules.boot.examples and i couldn't find any help about it. I wonder if the file name should have item id like modules.Maemo-2.6.28.10power37.item

Perhaps the developer Jay-C may help on this.

AFAIK bq27x00 is conflicting with BME. If you load the module in bootup, BME won't start most of the time, and the system reboots.

We had this problem with Nitdroid, but it is solved now with a more advanced bq27x00 module.

However, it is safe to load the module once the system is up and running (!?!)

Cheers
Jay-C

The Following 2 Users Say Thank You to Jay-C For This Useful Post:
mornage, sacal

ryanl33x1511 | # 187 | 2010-08-04, 21:34 | Report

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.

ryanl33x1511 | # 188 | 2010-08-04, 21:42 | Report

still not working, probally it conflict with mobilehotspot kernel ?

Coffee | # 189 | 2010-08-04, 22:00 | Report

Did Jay-C make Multiboot or have my wires crossed?

gtessier00 | # 190 | 2010-08-04, 22:07 | Report

Originally Posted by Jay-C View Post

AFAIK bq27x00 is conflicting with BME. If you load the module in bootup, BME won't start most of the time, and the system reboots.

We had this problem with Nitdroid, but it is solved now with a more advanced bq27x00 module.

However, it is safe to load the module once the system is up and running (!?!)

Cheers
Jay-C

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!!!