Originally Posted by pali

Yes, but it is bad to tell that this is vmlinuz if in fact it is zImage. (As I wrote I do not like some stupid hacks this type). Why multiboot does not work if file has normal zImage name??

# vmlinuz searchlist
VMLINUZ_SEARCH="boot/multiboot/vmlinuz- boot/multiboot/zImage- boot/vmlinuz- boot/zImage-"

ITEM_NAME="Maemo kernel-power46-pali1"
ITEM_KERNEL="2.6.28.10pali1"
ITEM_MODULES=ext3

1.Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~

The configuration files are in /etc/multiboot.d/

Each file named <whatever>.item represents a bootable configuration,
which can be selected from the bootup menu.


1.1 Item file format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~

A line starting with # is a comment

All other lines must be like the following:-

ITEM_ID="..."
A short name for this configuration.
No spaces, no special characters, max 6 characters long.

ITEM_NAME="..."
A description string for this configuration.
Shown on the bootmenu screen.

ITEM_KERNEL="..."
Kernel version to run in this configuration.
If the running kernel is not correct, multiboot will reflash
the device and reboot automatically.

ITEM_MODULES="..."
A list of kernel modules required to boot this configuration.
E.g. "ext2 ext3 fat vfat"

ITEM_DEVICE="..."
Root partition device name.
Use ${EXT_CARD} to point to the external MMC,
and ${INT_CARD} for internal.
E.g. "${EXT_CARD}p2" for partition 2 in removable MMC.

ITEM_FSTYPE="..."
Filesystem type for the root fs.
Usually ext2 or ext3.
Also, you must have the fs module loaded.

ITEM_FSOPTIONS="..."
Filesystem options for root fs. Typically,
for ext2/ext3:
"rw,noatime,errors=remount-ro"

ITEM_INITRC="..."
Init program to execute when switching over to root.
Optional, default is to search the usual locations.

ITEM_INITFS="..."
Locations where the Maemo root fs is moved after pivot.
Typically "initrd" or "mnt/initfs"
Defaults to "mnt/initfs"

Originally Posted by leojab

misiak, I was trying the same method earlier, the same way u mentioned in the noob guide but to no avail. I cannot get 2.6.68.10pali1 to boot. I can boot only to Maemo PR1.3 and NIITDroid Vostok.

When selecting option to power kernel, the N900 does not seems to flash the kernel area with the power kernel and it just gets stuck in a black blank screen..
I really needs power kernel for hostmode and many other features..
The /lib/modules, /boot/multiboot and /etc/multiboot.d seems fine with same reference to kernel.

I do not know where i am doing wrong :-(

ITEM_MODULES=ext

ITEM_MODULES=ext3

Originally Posted by leojab

Thanks pali and misiak.. I was able to finally get the kernel-power-pali1 installed.
The additional part to be checked is as follows:
1. After installing pali kernel, make sure the owner of the /lib/modules/2.6.28.10pali1 is root. This can be done using chown root:root command
2. Make sure the zImage file is in the /boot folder as well and it is owned by root

Now, I am satisfied with the first step.. cannot wait for more enhancement such as moving to kernel 2.6.37 with libraries

Originally Posted by AgogData

pali, can you tell me whats wrong here :

/home/user # cd /home/user/MyDocs/kernel/
/home/user/MyDocs/kernel # dpkg -i *.deb
Selecting previously deselected package kernel-power-bootimg.
(Reading database ... 67595 files and directories currently installed.)
Unpacking kernel-power-bootimg (from kernel-power-bootimg_2.6.28-pali1_armel.deb) ...
dpkg: regarding kernel-power-flasher_2.6.28-pali1_armel.deb containing kernel-power-flasher, pre-dependency problem:
kernel-power-flasher pre-depends on kernel-power (= 2.6.28-pali1)
kernel-power is installed, but is version 2.6.28-maemo46.
dpkg: error processing kernel-power-flasher_2.6.28-pali1_armel.deb (--install):
pre-dependency problem - not installing kernel-power-flasher
Selecting previously deselected package kernel-power-headers.
Unpacking kernel-power-headers (from kernel-power-headers_2.6.28-pali1_armel.deb) ...
Preparing to replace kernel-power-modules 2.6.28-maemo46 (using kernel-power-modules_2.6.28-pali1_armel.deb) ...
Unpacking replacement kernel-power-modules ...
dpkg: error processing kernel-power-modules_2.6.28-pali1_armel.deb (--install):
failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.28.10pali1/omaplfb.ko': No space left on device
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace kernel-power 2.6.28-maemo46 (using kernel-power_2.6.28-pali1_armel.deb) ...
Unpacking replacement kernel-power ...
Selecting previously deselected package linux-kernel-power-headers.
Unpacking linux-kernel-power-headers (from linux-kernel-power-headers_2.6.28-pali1_armel.deb) ...
dpkg: error processing linux-kernel-power-headers_2.6.28-pali1_armel.deb (--install):
failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./usr/include/linux/virtio_console.h': No space left on device
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Setting up kernel-power-bootimg (2.6.28-pali1) ...
Setting up kernel-power-headers (2.6.28-pali1) ...
Setting up kernel-power (2.6.28-pali1) ...
dpkg: failed to write status record about `wormux' to `/var/lib/dpkg/status': No space left on device