Re: Introducing ubiboot N9 (multiboot OS loader)
 

Download it from http://tablets-dev.nokia.com/maemo-d...12.1_amd64.deb and install it first ;)

@juiceme I happy you can get a Jolla
ubiboot ready for it?
LOL

Re: Introducing ubiboot N9 (multiboot OS loader)
 

root@garp-Lenovo-B590:/home/garp# dpkg -i flasher_3.12.1_amd64.deb
dpkg-deb: error: `flasher_3.12.1_amd64.deb' is not a debian format archive
dpkg: error processing flasher_3.12.1_amd64.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
flasher_3.12.1_amd64.deb
root@garp-Lenovo-B590:/home/garp#

and trying Nautilus: Internal error the file “/flasher_3.12.1_amd64.deb” couldn't open

And looked here! http://213.128.137.28/showpost.php?p...postcount=1087
:confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

click on deb file to install it

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yeah know! but only message= Internal error can't open file
no matter where I try in/out of Nautilus:confused:

Edit: downloaded file three times too!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

File broken I think (only 17kb)
http://213.128.137.28/showpost.php?p...postcount=1087

This work and is 66kb
http://tablets-dev.nokia.com/maemo-d...-downloads.php

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Can anyone tell the meaning of below code which don't work:

'numeric-owner' which numbers?
'nemo-handset' + half a file name 'armv7hl-n950-*.tar.bz2' ?

sudo tar --numeric-owner -xf nemo-handset-armv7hl-n950-*.tar.bz2 -C /media/Alt_OS/

ref Nemo: http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Nemo Mobile support thread: http://talk.maemo.org/showthread.php?t=80361

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Maybe nice charging percentage indicator in maintenance mode? :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This is one of the problems not solved yet; charging does not work in ubiboot. What it would need is fairly lot of stuff from the device management framework to enable BME to work correctly.

(So, when in ubiboot maintanance mode you CAN actually run the device dry if you keep it up for hours...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yep, confirmed :(
Down to the state you need flasher...

OT (wish): would be nice to get that sorted out (or get usb plug-in event always recognized correctly, so charging only works)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The N9/50 has a BQ24153A, which can be made to charge the battery or supply power for USB host ;)

Presumably something like the N900 bq27x00 driver could be made to control it sans BME.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That's worth looking into, thanks.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Need Help!
Don't know if it's right thread here or it should be Nemo, try here first?

Two days ago I was running Ubiboot, correct booting Harmattan, Firefox, Nitdroid and had partition Alt_OS ready for Nemo following this instruction:
http://wiki.maemo.org/Ubiboot

Only thing missing was unpack/install Nemo to Alt_Co.:
Couldn't get this code working in Ubuntu:
sudo tar --numeric-owner -xf nemo-handset-armv7hl-n950-*.tar.bz2 -C /media/Alt_OS/

Tried unpack in Ubuntu (also Nautilus), get message: you are not owner to Alt_OS no permission to unpack
Then made great mistake by using unzip in Windows (?) AND do it wrongly ending up with mess and Fatal error in partitions, which seems solved now (?)

Before starting again install Ubiboot need to know how to run above sudo tar ...code:
Should the code be written in terminal Ubuntu exactly as it stands or should something be substituted (filled in) ex. as with this code:
flasher -F firmware.bin -F emmc.bin --no-preserve -f -R

And/or how to get permission to unpack to device Alt_Os in Ubuntu?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@garp
Please stop 'polluting' all threads about ubiboot/sailfish/nemo/... with the same question(s) over and over.
They all are not really related to the topic but to low-level IT questions. I would encourage you to open up your own thread and ask there again.

To your question: the * (star) stands for some characters distinguishing different releases, thats all. So yes replace with characters of the image file you downloaded.
For the rights I just may guess that partition was created as root and user does not have write access (how to overcome use google or another thread please); or maybe just created partition and gave no file system?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK thanks for answer anyway - * have of course tried with full name of file - not totally idiot:cool:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okay, but you wrote misunderstandable.
Then I assume the partition of N9 is just not mounted on ubuntu as /media/Alt_OS but under /media/something
(last answer here in this thread)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks - and I know, that's because I'm total new on Ubuntu - have always used Windows - and maybe not so easy to learn in age near 70!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Respect for your age, sir. I have still few tens of years to get there :)

Regarding your problem, what I find easier to do when extracting filesystem images to device (whether it be android, firefox, nemo or sailfish) is to copy the TAR file ro the device, to MyDocs for example, and then untar it when running in ubiboot maintanance console.
That way it works all the time and you need not use any partition export thingies.

How to get the tarred image to device, then? There are several ways;

• 1.) you can copy it to your MyDocs when running Harmattan
• 2.) you can configure the private/public keys to your ubiboot and use SFTP to transfer it
• 3.) you can export the mmcblk0p1 in ubiboot, copy it there, unexport it and remount under ubiboot

When you have the image in the device, just mount the partition you want to extract it to, and then "tar -xvf <filename.tar> -C /mnt/x/"

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme Thanks - I will try again also because I did see before chrash Ubiboot is really great!:)

And respect to you too maybe not yet for age but for your work here!;)

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

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@garp
Is this full output?
Then you are missing the preinit_harmattan file/link.
Furthermore your preinit is just a link to init (an executable). It should be a shell script. So something went awry.
permissions should be -rwxr-xr-x
Kernel will not start this way (idk if loading via kexec also fails already at this stage).
What you need for sure is the original preinit and the preinit_harmattan from juiceme (other repository preinits.tar.gz)).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK thanks, only thing strange 'the original preinit' haven't changed that and where to get a new one?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

From where you got also the kernel and cpio, but other folder
http://www.swagman.org/juice/ubiboot/other/
preinits.tar

Load to device and untar to rootfs
tar -xvf preinits.tar -C /

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yeah thought so have just tried with this code via ssh with preinits.tar in device MYDocs but message can't find directory etc?

garp@garp-Lenovo-B590:~$ sudo su
[sudo] password for garp:
root@garp-Lenovo-B590:/home/garp# ssh -i my_n9_identity root@192.168.2.15
************************************************** ******
* Welcome to RM-696 ubiboot-02 maintanance console *
************************************************** ******

Enter passphrase for key 'my_n9_identity':
~ # tar -xvf preinits.tar -C /
tar: can't open 'preinits.tar': No such file or directory
~ #

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Of course.
As MyDocs is not mounted and preinits.tar not in that directory.
You could mount MyDocs (see commands in my post about device backup) or more easy copy it directly to '/'.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

But MyDocs is mounted and also the 3 other partitions both looking to Home map and Nautilus is'n it enough?:confused:

Just doing this:"Once the device reboots, keep the USB cable plugged in to enter “maintenance mode”. You will notice that the File Manager of your Linux Distribution will open and will mount/show all the partitions:"
http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root

By the way I have also unpacked preinits.tar to rootfs '/' by archive isn't it enough?

Just doing this

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Move the file from MyDocs to '/' (rootfs, p2) from PC and try again. [You also use scp when in ssh session.]

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks but 'ruhig' now you know I'm not an expert!:D:
What's scp??

Sorry same result!:(:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So I had ubiboot running for a while, an older version that I installed in July.
I tried to update ubiboot to the latest version using the installation instructions here (basically flashing ubiboot kernel, copying over cpio etc and extracting preinits.tar. Now whenever I try to boot, no matter what I select (or even if I select nothing), I get the same issue as Garp: I can still access the filesystem if I connect to USB. Any ideas? Also, where is the log file stored?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Log file: /home/user/MyDocs/boot