Re: Introducing ubiboot N9 (multiboot OS loader)
 

Can you build and send me .conf file please?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Did something I should have done ages past, prompted by @wicket actually :D
Branched https://github.com/juiceme/kernel-ad...t_v037_patched so that there'd be no trouble to find what is the correct repository to build ubiboot kernel :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I see readme file but little complicated for me.
can you explain me how to build kernel and other files like .conf etc...?
Or please can you do it and upload new file here please?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I'll release 0.3.8 soon, maybe today.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Released new version of ubiboot, 4 years and some after the previous one :D

http://swagman.org/juice/ubiboot/ubi...3.8_060318.tar

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have ubiboot small (tiny) installed on my N9.
if i flash kernel with this new version it will cause problem or not? like upgrade...
Or do i need to install with fresh PR1.3?

thanks for your work :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You need to change 3 things,
1.) Update the new ubiboot.conf to your configuration partition
2.) Update the new ubiboot-02.menus.cpio to same place
3.) Flash the new kernel zImage_2.6.32.54-ubiboot-02_06032018

The new ubiboot is not compatible with the previous one, as internal interface version has changed.

However; you do not need to change any other partitions (OS installations), just make sure you copy to the new ubiboot.conf the same configuration you have now.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

How to pass this error on 64GB device?

Thanks

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Ah, so it happens that your kernel partition is not large enough to hold the image. (so could be there is so much worn areas that the usable size has shrunken too much?)

Or is he device N9 or N950? I am not sure if the partition is smaller on N950 device?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It's N9.
How can i do now? to flash new ubiboot kernel.
nb. i try with n9 16GB it's the same error :(
perhaps your ubiboot is for N950 kernel...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Works for me;

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I've upgraded to 0.3.8 (copied over new cpio, updated conf and flashed kernel) and I'm experiencing an issue with g_multi.ko kernel module:
Because of that maintenance mode doesn't export partitions via USB (other stuff seem to be working). Can anyone confirm an issue or maybe even offer a solution?

I'm in need of initrmafs support so I can boot postmarketOS w/o using command line, but I'm facing an issue due to a fact that pmOS uses 2 partitions - one for kernel + initramfs, and another for rootfs. If I specify ubiboot to use the partition with kernel + initramfs ubiboot fails while checking for existatnce of /sbin/init script since that partition doesn't contain init (Checking 2nd stage kernel init file:...). Is there any way around that?
Using command line I'm able to load pmOS with:
In any case thanks for keeping ubiboot alive!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

What's the HW revision of your device?


Yes, that is also solvable of course.
When ubiboot first was designed there was no need for using separate partitions for system and kernel & initramfs, however implementing that is not too difficult.
I think it ought to be done so that widest possible set of configurations is easy to handle, I'll have to think about it a bit.


hehe, I had ignored it for a long time; only now as these new alternate OS'es start appearing it's worth continuing work on it :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

1601. Previous version worked fine, and I'd say that it's and build/install issue rather than something HW related - but I guess you have something in mind :)


I was thinking of skipping the check (and passing and empty value to kernel) when G_OSX_INITSCRIPT is not set.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Sounds to me like a mismatch between the kernel and the module. I couldn't find any kernel modules within the cpio archive or ubifs so my guess is that these are coming from the rootfs of Harmattan (is that right juiceme?). If this is the case, the new kernel probably differs sufficiently that it would cause the problem. One possible solution could be to bundle the newly built modules with ubiboot and mount them over the top the rootfs.

juiceme, what's the reason for the new ubiboot kernel? Has anything changed there? I never bothered to flash the new ubiboot kernel as the changes I submitted didn't require them so I'm still on the previous kernel (0.3.6 tiny) and have no problems with loading g_multi.

EDIT:
P.S. I haven't been able to get any recent (patched) mainline kernel to boot at all via ubiboot, not even by entering the kexec command manually via telnet. It's very difficult to debug without a serial console and can't find any info on how to build a cable for the N950 (I don't have an N9). One option I was hoping for was to build a ubiboot kernel with the serial USB gadget but as juiceme knows, it's broken and doesn't build right now.

My only (semi) success with booting patched mainline has been with Pali's 0xFFFF with the default (NULL?) kernel cmdline. With that I'm able to bring up initrd and the display comes up. The strange thing is that if I try to specify a cmdline, it breaks it.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have to admit I did not test that so extensively, just that it launched harmattan correctly on my device. Indeed something mus have gone amiss when I built and packaged it.

Yes, modules are built in the initramfs, if you check the ubifs.list file you see how it populates the filesystem when kernel is built


Technically there was no forced reason to update the kernel but I wanted to do that, to check that my toolchain still works :D
Also as there was new functional interface to kexec I pushed up the internal version number which needs to match between the kernel, the cpio and the configuration file.

I'll have to recheck what went wrong with the build.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

There is something here that I am not seeing now; I build the modules in the same kernel tree as the kernel itself, and install them correctly. Nothing has changed since the last time I built these, and the version strings and everytihing match, yet I still get the "g_multi: no symbol version for module_layout" error...

juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$
juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$ grep g_multi ubifs/ubifs_list
file /lib/modules/2.6.32.54-ubiboot-02-b/g_multi.ko drivers/usb/gadget/g_multi.ko 744 0 0
juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$
juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$
juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$ strings ./drivers/usb/gadget/g_multi.ko | grep ubiboot
vermagic=2.6.32.54-ubiboot-02-b preempt mod_unload modversions ARMv7
juice@ahma:~/kernel_dev/new_work/kernel-adaptation-n950-n9$

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK search me, just how stupid can one be... :)

I realized the reason my modules were incompatible, and now I remembered I actually knew this 4 years ago but had forgotten it. Woot, me growing old or what???

So; this is the problem/solution; I'll note it down here so when in another 4 years I forget it again someone can point me to this and call me a bloody feather-head... :eek:

When building a kernel with modules that are to be included in the built-in-initramfs there is a slight inconsistancy in the build mechanics; the initramfs image is built in "make" phase but the modules are built in "make modules"; this means that you have to build modules before zImage, else your make will of course fail due to the missing modules.
Now, when you do "make modules" before "make", you get the modules but there are some dependencies missing and the build system will not warn you about it....

The correct procedure to do it is this;

• make clean; make mrprop
• ARCH=arm make ubiboot-02_defconfig
• [edit your ubifs/ubifs.list so that you comment out all modules-to-be-included]
• ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make
• ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make modules
• rm -rf ./usr/built-in.o usr/initramfs_data.cpio ./usr/initramfs_data.o ./arch/arm/boot/zImage ./arch/arm/boot/Image
• [edit your ubifs/ubifs.list so that you re-enable all modules-to-be-included]
• ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make

And now Bob's your uncle and you will have a new shiny working combined kernel image in ./arch/arm/boot/zImage

Note to self; I need to write a sedscript to do the comment/uncomment thingy...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

He he,
it feels good not to be the only one! :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Released ubiboot-02 (integrated) version, rev. 0.3.9

New features:

N/A

Bug fixes:

Fix login to device in repair mode

General enhancements:

N/A

Work in progress:

N/A

Get it fresh from HERE
See the README file
See the Changelog file

Installation notes:

This version uses internal interface version 5 which was introduced in version 0.3.8. If you have 0.3.8 it is enough to just flash the kernel. If you are updating from older version you need to update the kernel, config file and cpio to be of the new version.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OMG,cant believe it comes back again!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hello all,
I'm having some trouble getting into openmode.
I must have tried a dozen different ways, incl. the version in the wiki and the version in the README.
I use this flasher version, the firmware.bin and emmc.bin from here, and this openmode kernel.
Do all these files fit together?
I am not getting any errors.
The last command's full output:
It looks OK.
But no matter what and how I try, I keep getting a yellow warning triangle when I boot.

At some point I managed to ssh into the phone and executed this command:
I also tried the same command as user and got the same error.

Did the open kernel even flash properly? the uname command suggests otherwise?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Your device is in openmode after that, no problems there.
However this does not get rid of the "ugly-triangle-and-warning" screen in the startup.

The problem is that to remove the openmode-warning with disclaimer-cal you need to do that before booting into openmode, because it is stored in a memory location hat is no longer accessible in openmode :eek:

So, the correct procedure is;

• 1. Flash the device clean in closed mode
• 2. remove the ugly warning
• 3. Flash the device back-to-back to openmode

Yes, most likely the openmode flashing went quite OK.

The reason the kernel string in uname looks exactly like in the closed-mode kernel is because I made it so :p:p:p
If the kernel version string had changed, then you'd have to copy in new modules too. Now as it is the openmode kernel works as a drop-in and uses the same modules under /lib/modules/

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I forgot to say, just if you don't believe that check the few first lines in dmesg to see the kernel build and version... :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I actually figured it out while I was waiting for my post to be published! Sorry for the noise.

I must say it's a bit of a treasure hunt wild web adventure with half the files referenced in the tutorials gone... But your (swagman.org yours?) website has everything I need now - I hope.

I figured that much, but it didn't stop me from slightly panicking at the time... :o

Re: Introducing ubiboot N9 (multiboot OS loader)
 

For the next poor soul that tries (is described elsewhere as well),
with back-to-back is meant to do;
3.a flash device (firmware) in closed mode
do NOT boot up
3.b flash open-mode-kernel
Have fun! :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

This still eludes me, after doing 'disclaimer-cal remove View-openmode', how could i flash the device again without it restoring the warning message. Because that's what happend.

Finally, after removing the warning with 'disclaimer-cal remove View-openmode', i settled to not doing a full flash but just this:
Then afterwards, just in case, because i didn't know any better:
Still now i get crashes after installing an app using dpkg or apt-get. I mean, terminal window and open apps closing after final phase of an install process - 'updating desktop entries'. So i have to run some n9qtweaks multiple times to get everything installed.

Can somebody hint what could be wrong. Or what are the correct flashing commands, after disabling the warning message.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It's exactly like you described; first do the 'disclaimer-cal remove View-openmode', then flash back to back.

However I cannot remember exactly what was the command line so that the device gets flashed so that the openmode warning is still off. (I should dig up one of my old N9's and check it...)

About the other problem, crashing of applications when installing stuff; I remember that was a problem which was patched and the patch/explanation should be somewhere on TMO too.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Skimming through the README and the thread I just found (after 7y) that juiceme has a small quirk in his description :eek: which I never noticed as I was doing it on my own way.

See here
https://talk.maemo.org/show.hreadt.p...&postcount=698
and here (kne post earlier)
https://talk.maemo.org/showthread.ph...&postcount=697

afair you do not need to flash emmc for back-to-back, firmware is enough. It does not hurt either.
BUT what you must not give is the parameter '-R' for the firmware flash after disclaimer removal and before kernel flash.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks @peterleinchen; Indeed it has been quite a few years since I last played with those that I was not sure any longer what was the exact flasher command to get the desired result :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Has anyone been able to install postmarketos successfully? I can't find a guide and i didn't know where else to ask :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It should not be that difficult if only the userland works with the fairly dated range of kernels supported by n9.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

https://wiki.postmarketos.org/wiki/Nokia_N9_(nokia-n9)

That said, you may want to also consider Maemo Leste ... they haven't updated N9 support in a bit, but can definitely help you with it. With postmarketOS you'll likely be stuck to something like XFCE4 only due to non-working 3d acceleration. Leste has the acceleration working on N900 and Droid 4, and it's very likely they could help you get it up and running on N9 too

EDIT: Looks like 3d has worked on pmOS after all, at some point, https://twitter.com/fi1ippz/status/9...194349056?s=09.
Leaving the previous text intact though, since you'll likely still get better accel support on Leste than anywhere else.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

i estimate the chances of still getting help here near zero, nevertheless i try it. so i want to put ubiboot on my two recently received n950s. on both when i try to flash the ubiboot kernel the flasher says the image is too big for the partition. i even tried the small image. maybe it is because both n950 are the 512MB ram version? funny thing is that one of them is black with 16GB storage, the other one is silver with 64GB storage.