maemo.org - Talk - Multiboot 0.2.5 released

maemo.org - Talk (https://talk.maemo.org/index.php)

- Android (https://talk.maemo.org/forumdisplay.php?f=54)

- - Multiboot 0.2.5 released (https://talk.maemo.org/showthread.php?t=58797)

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by zaoltryence (Post 775506)

is this correct when i put on the code
nano Maemo-2.6.28.10power37.item
iit says not found...
any advice?

I am presuming you have nano installed? if not use any editor (leafpad, vi, or what ever you feel comfortable with) or apt-get install nano

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by sacal (Post 775516)

Mornage

Thank you very much for taking your time looking into my problem.

The contents of my item file, located at /etc/multiboot.d/Maemo-2.6.28.10power37.item are:

Code:

ITEM_NAME="Maemo 2.6.28.10power37"

ITEM_KERNEL=2.6.28.10power37

ITEM_MODULES=ext3 bq27x00_battery

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

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by mornage (Post 775596)

I am presuming you have nano installed? if not use any editor (leafpad, vi, or what ever you feel comfortable with) or apt-get install nano

yup, i sorted it out, i just used leafpad instead, but thanks for the reply :)

Re: Multiboot 0.2.5 released

i could not get the v39 via appman...tried enable and disable and update but still, maybe because i already installed it early and flash back v.37..will it be problem if i install it manually via dpkg?

download
-kernel-power_2.6.28-maemo39_armel.deb (1st)
-kernel-power-modules_2.6.28-maemo39_armel.deb (2nd)
-kernel-power-flasher_2.6.28-maemo39_armel.deb (3rd)

then

-run xterm
-sudo gainroot
-dpkg -i location/of/file (intsall them the consecutively as shown above)

then follow the step below ? i think this is what i did last night...
and still facing NOKIA screen and shutdown, no multiboot option.

Quote:

Originally Posted by mornage (Post 775168)

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)

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by ryanl33x1511 (Post 775639)

1stly I am persuming you have extras-devel enabled?

when you flashed back, did you just follow the steps on nitdroid thread to install v37? If so, you are probably best off removing the kernel and reinstalling but you are welcome to try just manually installing. If it doesn't work you can always boot the default kernel with 0 or b.

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by mornage (Post 775587)

Please post nitdroid issues in the nitdroid help thread in future(stickied at the top of this forum). you are more likely to get a response and it leaves this thread to deal with multiboot issues.

you have to partition your SD memory card.

oh yeah im on a wrong thread. i truly apologize. i have this thread and the nitdroid thread open in different tabs, got confused.....

Re: Multiboot 0.2.5 released

still not work, after choose kernel power v.39 at reboot first time. NOKIA SCREEN COME UP then SHUTDOWN....
THEN after that Cant get through NOKIA Screen to Multiboot option ,no matter how many reboot...so there is no option for B or 0, only solution to use flash-only=kernel -f -R to get to default kernel.

This is the problem occur, at least to me... Did you manage to boot to v39 and check the kernel version if it is v39 ?

Re: Multiboot 0.2.5 released

the problem is that the device boot to v39 fine, that is it couldnt get through Nokia Screen, it load the kernel and some how the kernel conflict with multiboot or something wrong that is why i keep getting stuck at Nokia Screen and shutdown. is it because i manually install 39 and not via appman ? i dont think it matter

but after boot into default kernel, i then apply the kernel v37 multiboot again ,this time it work with v37 and reboot choose 1st option for v.37 then it boots fine.

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by ryanl33x1511 (Post 775688)

I the way you manually installed 39 conflicted with the way you had manually installed 37 when you had previously installed 39. The files were probably all mixed up.

If 0 or B wont boot (bear in mind you may have to boot twice and the charger cannot be plugged in) then I'm afraid you will have to reboot. You might as well just stick to power kernel 37 though as 39 offers no advantage unless you are developing. If you must install 39, do so as in my guide.

Re: Multiboot 0.2.5 released

Quote:

Originally Posted by gabby131 (Post 775661)

oh yeah im on a wrong thread. i truly apologize. i have this thread and the nitdroid thread open in different tabs, got confused.....

No problem, we all it at times. :D