Re: Introducing ubiboot N9 (multiboot OS loader)
 

This could propably be around the start of installer (package manager):

Code:

---

Nov 17 18:13:10 (2013) pkgmgrd[8477]: GLIB MESSAGE default - ASSUME NETWORK 0

---

This sounds like it could have something to do with the phenomenon:

Code:

---

Nov 17 18:13:59 (2013) applauncherd[5028]: Daemon: State file not on aegis protected file system, exiting.

---

If that is related, then the problms are indeed caused by some aegis mismatch.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, that's interesting. Google brings up some seemingly-relevant code.

It looks to me (note: I don't know C++) that after an installation is complete, applauncherd attempts to reload its previous state.

/var/run/applauncherd (which contains the state file, /var/run/applauncherd/saved-state) is checked as to whether it's an aegisfs mountpoint first. Somehow/somewhere, this fails, causing applauncherd to exit.

Well, that would explain why there's only a problem in openmode. What I don't understand is why this problem doesn't happen all the time, and not for all openmode users.

Also possibly useful: aegis_system_mode_t, aegis_crypto_verify_aegisfs

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Good catch that :D

Now as I check that, it is indeed in the non-closed part of harmattan, distributed as applauncherd_3.0.3+0m8.tar.gz on the PR1.3 cdrom.
What this means, is that it can be fixed :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme i think we need to make ubibootctl cli-tool with
--add-kernel=/path/to
--remove-kernel=/path/to
--type=harmattan|nemo|android|sailfish
--refresh
options. this tool should automatically add kernel path to active .conf file and set init options to it or remove kernel from config. then we can easily pack kernels to deb archive and use ubibootctl in postinst and prerm scripts =)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Allright, I recompiled "/usr/lib/applauncherd/libapplauncherd.so" with the slightest possible modification, just set the debug flags on so that it will not die on the aegis conflict.

Please try the new library (md5sum=238b47681749eb2bf78a819ac6bb42f7) and see if it makes any difference for you :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks. Well, no crashes yet. However, there also hasn't been any note of the conflict in the syslog, so I can't tell if the bug just hasn't happened yet - stupid unreliable bugs ;)

Will keep checking after installs etc. Anyone else having this problem, now is probably the time to test! :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

just overwrite original one?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That's what I did. Or actually, to make it safe I first copied the old library off just in case it would not work with the new one.

Code:

---

~ $ devel-su
Password:

BusyBox v1.20.0.git (MeeGo 3:1.20-0.2+0m8) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ #
~ # cp /usr/lib/applauncherd/libapplauncherd.so /root/libapplauncherd.so.backup
~ # cp /root/libapplauncherd.so /usr/lib/applauncherd/libapplauncherd.so
~ #

---

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Awesome!
And I thought this was a legit Harmattan bug - it was getting annoying!

I wonder how deep Aegis is embedded into the system, and whether we can just stub it out/remove it completely from libs?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, it is fairly deep AFAIK. Unfortunately not all the components are open source, if it only was so life would be all daisies :)

For example, the SMS-extended-character handling bug in "/usr/lib/libsms.so.0.0.0", which causes device to trash the received SMS message without a trace even when it had correctly acknowledged the receiving to RAN.
(A bug that I call absolutely critical as it breaks the (un-)deniability of messaging...)

Now install and uninstall wont close all apps!

Thanks, you solve this major bugs

@juiceme, i think you should open a new thread for this bugs fix

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If you decide it's necessary, can you plz share the link here, TIA.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I made a new thread about it; http://talk.maemo.org/showthread.php?t=91825

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme
"Back-to-back flashing is performed by first flashing the device like in "normal closed mode flashing", both emmc and rootfs. Then, immediately flashing the device again, now with an Open Mode kernel, without letting the device to boot up between the two flashing rounds."

I use Windows:
Will the device automatically boot up after first normal mode flashing? Meaning does I need to do something to avoid this?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You must not give thr '-R' parameter.
And you must not unplug USB.
And you must not wait too long between those two flasher commands (else the device leaves flashing mode on itself and reboots).

That's all.

--
for point 3 you may prepare the command oflline (device not plugged), press Enter and use command repetition (up and down arrows) afterwards ...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=peterleinchen;1387511]You must not give thr '-R' parameter.
And you must not unplug USB.
And you must not wait too long between those two flasher commands (else the device leaves flashing mode on itself and reboots).

That's all.
--
for point 3 you may prepare the command oflline (device not plugged), press Enter and use command repetition (up and down arrows) afterwards ...[/QUOTE

Does this look OK?
accli -I says = open
uname -r says however 2.6.32.54-dfl61-20121301:confused:

C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage_2.6.32.54-openmode_l2fix
--flash-only=kernel --suppress-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan

Picked ape-algo from a FIASCO file
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 95 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2051 kB/s]
Updating SW release
Success

C:\Programmer\nokia\Flasher>

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If you used the "standard" L2fixed kernel or any minimally modified open mode kernel that is OK.
The reason the kernel id string is same is because the kernel module interface has been kept same as the original. (so you do not need to install new modules with the kernel)

if you are in doubt, do a "dmesg | head" and look for the kernel compile stamp. If you see my name there it is OK :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks! (juice@alaspin) behind version - correct?:)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That's correct :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

:confused:HELP!
Installed Ubiboot but the 'idiot' (that's me) forgot to create the /boot and put in these before installing:
zImage_2.6.32.54-openmode_l2fix
zImage.pr13
zImage (which by now, has been renamed to “zImage_e-yes_nitdroid+l2fix”, without the quotes)
zImage-2.6.32.54-dfl61-20121301 (Optional)

Now the Ubiboot screen shows up can choose everything but after moment message turns up:
Boot OS/kernel selection failed!
Please run a maintanance boot

How to do that?:confused:

EDIT: maybe can handle it by the Paragon ExtFS for Windows which by USB gives access to all it seemes by windows explorer!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@Garp Try plug USB cable and power on N9, if it can run into maintanance mode you can copy kernel to Harmattan rootfs

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi all,
I use v0.3.5, try new Nemo with Wayland/Qt5 image from here
I can boot to Harmattan but cannot with Nemo, there're log files:
ubiboot.dmesg
ubiboot.log
ubiboot.conf

Anyone can help.
Thks.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

just flash back to any openmode kernel, boot up and fix it!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Help!:confused:
Ok now everything seems to be ok but can't boot:
Start= open up Ubiboot screen choose nothing or Harmattan 2.6.32.54-openmode_l2fix, the N9 just close in black screen? To start need to push start button 6 second and then push one more to get started again.
Taking another OS ex. Nitdroid it comes with the message mentioned : Boot failed Please run a maintanance boot? (There is however no maintanance boot/mode avaiable?)

USB ok through Paragon I can mount all partitions:
N9 (MyDocs) 49,82GB FAT-32
Alt_OS 3,91GB ExtFS =Nemo
rootfs 4GB ExtFS =Harmattan
() 2GB ExtFS= Nitdroid

Device screen says:
Welcome to Ubiboot ver. 0.3.5 (Boot loadere is based on Moslo ver. 0.0.13.1)

Try 1 (0)
Partitons exported successifully via USB
Configured 192.168.2.15 on USB
Starting DHCP server, offering 192.168.2.100

Starting Telnet server
Starting SSH server

Re: Introducing ubiboot N9 (multiboot OS loader)
 

From the log I can see that only kernel that is found is the zImage_2.6.32.54-openmode_l2fix.

However, if even that does not boot, are you sure you have the preinit file correct? (for Harmattan it is /sbin/preinit_harmattan)
If preinit file is missing or does not have execute permission then the result is just as you described, black screen with nothing happening.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

From the ubiboot.log I can see that your kernel vmlinuz-2.6.32.20130129.1-n950 is correctly loaded, so the failure to boot comes after that. Your ubiboot.conf looks OK to me also.

Usually there are 2 reasons that can cause the failure; either the init/preinit file is missing or has wrong permissions, or the modules of kernel are missing or incorrectly configured.

As you can boot to Harmattan, you can do that and mount your Nemo partition somewhere (for example mount /dev/mmcblk0p4 /mnt) and then check if you have some problem with either /mnt/sbin/init or /mnt/lib/modules/

Have you been able to boot to Nemo before?
If not, and if this is a new installation, it is possible that something went awry when you extracted the Nemo rootFS to ALT_OS partition. You can try to wipe it clean and extract again.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks and you were right both Harmatta, Firefox and Nitdroid missing in /sbin/.
However it didn't help now it says Please run maintanance boot with openmode_I2fix?:confused:
How to see if execute permission without terminal?

Edit: Now worse "But menu script not found"

Thank juiceme, this is first time i try nemo, i ll check it later :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

In the log you have "Cannot load Harmattan kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix"
This means that maybe you moded/renamed the kernel image, check that it is correct.

If you extract the preinits.tar file in the device the permissions will be correct. What you should not do is extract the files in windows and then transfer to the device, as that will break the permission bits.

If you do "ls -l /sbin/preinit*" on the device console, you see the permissions:
The "x" bits in the permission string mark that the file is executable.
If you do not see this string "-rwxr-xr-x" in the front of each filename, then you have a permission problem.

To correct it you can give command "chmod a+rx /sbin/preinit*"

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=juiceme;1388405]In the log you have "Cannot load Harmattan kernel /boot/Harmattan/boot/zImage_2.6.32.54-openmode_l2fix"
This means that maybe you moded/renamed the kernel image, check that it is correct.

If you extract the preinits.tar file in the device the permissions will be correct. What you should not do is extract the files in windows and then transfer to the device, as that will break the permission bits.

If you do "ls -l /sbin/preinit*" on the device console, you see the permissions:

/QUOTE]

Thanks but how to get access to the device in this situation - only way as I see it is USB = to Mount via Windows Paragon etc.?

It seems very odd now, the kernels return to disappear from /root the Menu script seems failed etc.:confused::confused:

So can I just start again with Back-to-back flashing from now on?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=Garp;1388409]When you start the device with USB cable connected, you will get to the maintanance mode where you can telnet or ssh into the device.

It's easy to fix all the boot related problems from maintanance mode, as well as make backups etc...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

just flash openmode kernel to device and boot to harmattan ;)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=juiceme;1388411]OK but how to use this telnet/ssh? Normally I use putty:
http://www.chiark.greenend.org.uk/~s.../download.html
but it seems not to work here?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=Garp;1388415]With windows you need some NDIS drivers, or else it does not recognize the USB0 as ethernet device.

You might find some info by searching TMO.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=juiceme;1388420]OK thanks, tomorrow think follow coderus above and start all over again!

Or now Menu script work again but boot failure and when connect USB an Mount then again, again in /boot no zImage at all - it disappear!(map empty) after trying to boot from Ubiboot menu:confused::confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Can't boot after flash openmode kernel (showing Nokia short the device close) and can't do firmware flash! See attached:confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@Garp seems you removed original /sbin/preinit. yes, you need a Linux machine to fix it, or make rootfs reflash.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

how to make rootfs reflash?

don't understand preinit problem but it was a mess on rootfs when mount via USB ex. /boot was empty and couldn't copy zImages to map!