Re: Introducing ubiboot N9 (multiboot OS loader)
 

This driver is not working on windows 8. For those you who had a same problem as I did, I found a workaround for Win8.;)

-------

Apologise for duplex post, I didn't see the first one...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Why leave the forum when all this info is already availabe? :)

--
as we already at this question again. Anybody knows about the CDC serial driver questioned when ubiboot in maintenance mode?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Need help!
I should be up running Ubiboot, created Alt_OS for Nemo etc, have checked everything - I think!
Booting to Ubiboot screen OK, then select but receive message:
"Boot OS/kernel selection failed! Please run a maintanance boot."

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Do you guys have nitdroid running with acceptable performance with ubiboot? To me graphics was slow and jerky, compared to nitdroid/meego dualboot mode. But i don't know where the culprit is, i've had my n9 motherboard replaced, maybe that changed something.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

When I look into your ubiboot log, I can see that you are trying to load 2 kernels, zImage_2.6.32.54-openmode_l2fix and zImage_e-yes_nitdroid+l2fix.
What I find strange is that you actually have managed to boot Harmattan correctly once:

Dec 2 11:46:11 (none) user.notice root: Loading kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Dec 2 11:46:11 (none) user.notice root: kexec_load() successful

But then again, after this it fails every time:

Dec 2 11:51:28 (none) user.notice root: Selecting Nitdroid OS, running kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
Dec 2 11:51:29 (none) user.notice root: Cannot load Nitdroid kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
--
Dec 2 12:24:59 (none) user.notice root: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Dec 2 12:25:01 (none) user.notice root: Cannot load Harmattan kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
--
Dec 2 13:03:32 (none) user.notice root: Selecting Nitdroid OS, running kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
Dec 2 13:03:33 (none) user.notice root: Cannot load Nitdroid kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
--
Dec 2 13:06:29 (none) user.notice root: Selecting Nitdroid OS, running kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
Dec 2 13:06:30 (none) user.notice root: Cannot load Nitdroid kernel /boot/Nitdroid/boot/zImage_e-yes_nitdroid+l2fix
--
Dec 2 13:27:48 (none) user.notice root: Selecting defaults due to timeout in main menu
Dec 2 13:27:48 (none) user.notice root: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Dec 2 13:27:50 (none) user.notice root: Cannot load Harmattan kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
--
Dec 2 13:29:14 (none) user.notice root: Selecting defaults due to timeout in main menu
Dec 2 13:29:14 (none) user.notice root: Selecting Harmattan OS, running kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix
Dec 2 13:29:15 (none) user.notice root: Cannot load Harmattan kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix

So what has happened between the instants 11:46:10 and 11:51:28, for the kernel to be not found any longer?

So, can you boot to the maintanance console, and check that you really truly have the kernels in Harmattan root partition's boot directory?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

There should be no reason for that really, but you can easily check the feeling yourself; Since ubiboot uses it's own preinit files, you propably still have the sillyboot-modified oribinal preinit on your system? (or if you do not have that any longer, it is easy to install to the device as it does not affect ubiboot.

Then, just flash the Nitdroid kernel to your device, boot it up and see if it looks/feels different.
To go back to ubiboot you just need to reflash with ubiboot kernel.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I can see the kernel and others too correct in /boot using Ubuntu!

Edit: Only time in stallation proces device booted correct was after installing Nemo and that was before installing Ubiboot!:confused:
using this :http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just to make sure, there are several different "/boot" directories on your device;

• The ubiboot configuration directory, mmcblk0p1:/boot (which is /home/user/MyDocs/boot/ inside Harmattan)
  This is where your ubiboot.conf and ubiboot-02.menus.cpio go
• The Harmattan root partition boot directory, mmcblk0p2:/boot (which is /boot/ inside Harmattan)
  This is where your Harmattan, Nitdroid, Firefox, etc. kernels are located
• The Nemo root partition boot directory, mmcblk0p4:/boot (which is normally not visible inside Harmattan)
  This is where your Nemo kernels live

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Is it normal that my root fs is not mounted in Ubuntu during maintenance? also Alt_OS partition does not mount.

I've installed Ubiboot successfully and managed to run custom kernels also. It was easy :)

EDIT: Attached log

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks but how to search via ssh through mmcblk0p1 etc. fdisk only gives info partitions etc. Can't find it by google?

Disk /dev/mmcblk0: 64.1 GB, 64130908160 bytes
4 heads, 16 sectors/track, 1957120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 17 1632512 52239872 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/mmcblk0p2 1632513 1760512 4096000 83 Linux
Partition 2 does not end on cylinder boundary
/dev/mmcblk0p3 1760513 1891584 4194304 83 Linux
/dev/mmcblk0p4 1891585 1957120 2097152 83 Linux

Have seen this: http://talk.maemo.org/showpost.php?p...&postcount=671 but afraid to do serious mistakes:confused

Loking into MyDocs/boot and /boot it seems correct! - can even see Nemo files in /Alt_OS/boot

Edit: Is this execute OK? (have run chmod a+rx /sbin/preinit*)
~ # ls -l /sbin/preinit*
lrwxrwxrwx 1 root root 5 Oct 29 22:51 /sbin/preinit -> /init