Re: Introducing ubiboot N9 (multiboot OS loader)
 

Done, Now I have uploaded the archive ubiboot-02_0.3.4_081013.tar to both Swagman and Skeiron.
I'll have to edit tha announcement posts too.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juice
I did not want to disparage your (great and much appreciated) work, just did not see the new ubifs online and did not take snapshot of your svn (maybe I should have?).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

heh, it was just a joke :D

But of course you can do "svn co" on the repo, or browse via web using the link. I'll upload a new snapshot to Swagman&Skeiron at some point, but propably not yet, as I am still honing out smallish things on it... but the SVN repo is always up to date, feel free to comment on my code :)

And ideas/enhancements are always welcome!

Can i install nitroid to MyDocs partition instead of home/user/nitdroid??
I want to save home/user storage
If i install nitdroid to home/user/nitdroid, whenever i use nitdroid install apps and games, will all these install to home/user/nitdroid or in MyDocs??

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The problem with that is that Nitdroid itself wants to mount /dev/mmcblk0p1 as SDCARD. If you use it as the Nitdroid root directory it is going to cause few problems... :D

Possible solutions:
1. modify Nitdroid initialization so that it does not want to have a different partition for SDCARD. (you also lose ability to export partition via USB)
2. create partition 4 (or if you already have Nemo on partition 4, use that as /nitdroid or create a new partition 5) and install your Nitdroid to that partition.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Furthermore to mention MyDocs is most probably vfat and not extfs, so: NO.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, that's true. ( altough mine has been vfat, extfat, ext4 during varioust times... no need really to keep it vfat :D )

Ah, I have a little issue here but it's probably a nitdroid issue

so my MyDocs partition is ext4 and nitdroid keeps asking to format it (recognizes it as SD Card...)
Sd card fix doesn't work for me
I dont wanna do that because i fear it will erase a lot of stuff^^

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[OT]
Do you remember me crying that the touchscreen does not react after boot up (and being connected to charger?

Sorry for being very late with the solution! ;)
This post of Jonni reminded again to write it down here again.
I have a few chargers (all N900 ones) spread over my house. And it was/is really one specific charger (original Nokia N900!!!), that does this.
I came aware after waking up in the night seeing some ghostly usage of my N9. Touchscreens was lightened up and some random actions were executed. From reading a bit here I already knew that this was due to a bad shielded charger cable (or something like this), so I tested it with my other chargers and none of them had this behavior. Also this touchscreen blocking did not occur again.
Maybe it is due to some adapter UK-->EU (this problematic one is an original Nokia N900 charger from UK)?

Long story short, it was the charger. And it did not happen again!
[/OT]

Re: Introducing ubiboot N9 (multiboot OS loader)
 

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

New features:

• Support for SSHD & SFTPD in the maintanance mode
• Better chekcking for error conditions
• Strict version checks
• Better logging
• New kernel layout support larger initramfs
• New version of ubiboot.conf

Bug fixes:

• Fixed typos in template ubiboot.conf.

General enhancements:

• Rewrote the README document from scratch
• Handling of RSA certificates
• Added clearer GPLv2 licensing
• Reorganized the svn repository
• Changes in the kernel build environment

Work in progress:

• Ported wpa_supplicant for WLAN configuration
• Lot of work towards WLAN initialization, yet incomplete.

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

Installation notes:
Again, just as last time, this version is not compatible with any files from the previous versions. Hence you need to review your current ubiboot.conf and put your kernel configuration into the new ubiboot.conf file.

The files are also uploaded at Skeiron, for your convenience:
ubiboot-02_0.3.5_301013.tar

Re: Introducing ubiboot N9 (multiboot OS loader)
 

right now i have sillyboot on my device for NITDroid and its working, I wanted to transition over to ubiboot, is there an easy way to install this without any reflashing? I would like to try a few different kernels and the device I am used to in my N900 but i got this phone off ebay and have loved it ever since, any guidance would be very appreciated, I am just a bit confused. Thanks again for keeping this project going and giving all us N9 users fresh with all these great tools

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Install ubiboot as usual.
Ubiboot runs /sbin/preinit_harmattan or preinit_nitdroid, skipping over sillyboot (custom /sbin/preinit).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

so my device is ready? im sorry for bothering you I just dont want to make my device unbootable, how would i go upon removing sillyboot and swapping to ubiboot? thanks again, I will need to do lots of research on where to put kernels and what to edit to make it boot different kernels and OS's thanks for the patience and sorry again

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@plourde, you do not need to remove sillyboot at all, sillyboot and ubiboot operate at different boot phases.

How sillyboot works:

• boot loader starts up the flashed kernel just as usual
• last part of kernel startup is call to /sbin/preinit which does number of things before launching up /sbin/init
• sillyboot is a modification of /sbin/preinit which allows starting up different init, based on user selection

How ubiboot works:

• boot loader starts up the ubiboot kernel instead of device kernel
• ubiboot runs a self-contained linux minidistro which has many things, including the boot menu selection
• based on user selection, ubiboot loads up the next level kernel and set sup the correct boot environment.
  a) for Harmattan, it prepares kernel to run /sbin/preinit_harmattan from mmcblk0p2.
  b) for Nitdroid, it prepares kernel to run /sbin/preinit_nitdroid from mmcblk0p2.
  c) for Nemo, it prepares kernel to run /sbin/init from mmcblk0p4.
  d) for Firefox, it prepares kernel to run /sbin/preinit_firefox from mmcblk0p2.
  e) and so on...
• last thing what happens, is that ubiboot executes the loaded 2nd level kernel, which goes on and starts the prepared preinit/init file.

So, now you understand that when you use ubiboot, your sillyboot will never be run at all, the modified /sbin/preinit that is sillyboot is sidestepped totally.

To install ubiboot, this is the simple list of things what to do:
1.) copy the file ubiboot.conf to your /home/userMyDocs/boot/ directory
2.) copy the cpio archive to your /home/user/MyDocs/boot/ directory
3.) copy your kernels to /boot/ directory
4.) copy the preinits to /sbin/ directory
5.) flash the ubiboot kernel

That's it. And remember to check that ubiboot.conf has the correct list of kernels that you copied to /boot/

There are dozens of things you could do differently but this is the basic setup.

@juiceme before install ubiboot would't it be an idea or needed to establish ext4 (or 2,3) partition to avoid the limitation of 4GB for operating systems etc. and make effective use of space on a 16GB?
I have used 3GB before ubiboot with only one (Openmode) kernel?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Do you mean, to change your mmcblk0p1 from vfat to some better FS?
The 4G limitation is only for files on vfat, not filesystems. Or are you talking about a case where you have a loop-mounted filesystem on a file on your vfat partition, something like EasyDebian?
In that case, yes, it's better to change the vfat to something else, like exfat or ext4fs.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I'm thinking of doing this:
http://talk.maemo.org/showthread.php?t=86662

and this http://talk.maemo.org/showpost.php?p...3&postcount=28

I will wait for nitdroid support ext2 etc format, before formating MyDocs

but seem not much news

Re: Introducing ubiboot N9 (multiboot OS loader)
 

What about Nemo etc don't support ext 2 etc. either?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, that mostly concerns if you want to mount your MyDocs to some windows-computer.
If you only use Linux, or if you never export your USB drives you can just format your mmcblk0p1 as ext4fs, it will work like that, no problems.

This has no effect to ubiboot, of course, excepting the fact that people normally put ubiboot configuration files in MyDocs/boot/ directory as that is the default location.
(but as well you could put them in mmcblk0p2:/boot/, it does not matter :D)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Nemo should well support ext2fs, I have not tried it but I would be really surprised if it did not. That would be actually quite hilarious :D

What Nemo does not support out-of-the-box is exfat, but adding support to that in Nemo kernel is minimal work.
(after all Nemo kernel is pretty much same as ubiboot kernel and that supports exfat...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That should be solved due to
http://talk.maemo.org/showthread.php?t=86662

using Ext2fsd v0.51 or even better to Windows8 (perhaps?)
Paragon_ExtFS_for_Windows_2.41.exe

My concern is if in future be able to use Nemo, Sailfish and maybe even NITDroid, Firefox if call and camera issues should be solved. Then if not ext2,3,4 can be used both the 16GB and the 64GB version could bee too small, I think (same rootfs 4GB)?

Right now have 16GB but possible to buy a 64GB rather cheap, but without use of ext it doesn't matter - don't need all that MyDocs space for music and pictures etc!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

All of those should well understand ext4fs, no problem there. The only problems are with Nitdroid and that only as it stupidly assumes that the SDCARD mount (which is MyDocs) needs to be vfat.
(it's not that it would not understand ext4fs, it's just some silly setting/script that wants it to be vfat)

That should be easily corrected by somebody who knows android.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

But must be something e-yes has made because no problem using ext4 on Android - have done so since long at HTC Desire (only 512MB internal memory) with diff Android versions latest Jelly Bean 4.2.2.!?

edit: Best Android app https://play.google.com/store/apps/d....control&hl=da

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme would you like to make some pseudo-terminal in ubiboot? and maybe some self-configuration which searches for kernels in boot folders and enables it? or harmattan configuration gui?

about ext4 and nitdroid: https://www.google.ru/search?q=android+ext4+sd+card

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, I already have "sillykbd" which is a simple touchscreen keyboard utility. It souldn't be too difficult to tie that into a TTY for a simple console...


Yes, that'd also be possible. I'll have to look into that.


Thanks :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Dont know whats the problem, I got black screen when selecting kernel.
include openmode l2fix and kernel plus r2, havent this problem before

Log is here

Re: Introducing ubiboot N9 (multiboot OS loader)
 

According to the logs it looks pretty good, no warnings up to that point.
You tried loading zImage-2.6.32.61-plus_20131030, zImage_2.6.32.54-openmode_l2fixand zImage.
Were any of those successiful?
Did you make any other changes, to kernel locations etc. when you updated ubiboot version?

No
Kernel location in /boot/, just got black screen when select kernel

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, ubiboot could find & load the kernels OK, that's clear from the log. Next step is the kexec() after which it is the 2nd stage kernel that is in charge of things, not ubiboot any longer.

Usually when the kernel loads OK but fails to boot there are 2 possible easy faults (and some more difficult)
The easy ones are, either something wrong with modules, or something wrong with init.

Assuming you have booted the same kernels before with earlier version of ubiboot, then the modules must be correct.

Can you check from your ubibot.conf that the preinit for harmattan is correct? It should propably be:
G_OS2_INITSCRIPT="\/sbin\/preinit_harmattan"
And check that you have /sbin/preinit_harmattan there and that it is executable.
(BTW, did you change your preinit or are you using the same as before?)

I havent change any init, use as before
I think modules problem, already do depmod -a 2.6.32.61-plus

Maybe the log , i flash back l2fix and get the log for u

Before I in normal mode, i do all file arrangement before make it become open mode, is it ok to do that?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

when flashing the ubiboot kernel do i what firmware do I use when flashing kernel only, emmc bin or legecy bin? Thanks in advanced thats my last step.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I flashed it and i cant get the phone to boot, it just tries to boot and shuts off any ideas? ubiboot boots but no luck on booting the phone

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@TMavica, did you get any of the kernels to boot, any at all?
or was the problem only with 2.6.32.61-plus kernel?

The best way to enter Open Mode is the back-to-back flashing.
If you do it the simple way, just flash Open Mode and then delete the aegis directories, you are going to have problems :(
People have checked this and it is indeed so, the device is going to be somewhat unstable, especially at boot.

@plourde, when you flash with "--flash-only=kernel" parameter, the flasher needs to get the APE algorithm from a firmware FIASCO image. That is why you need to specify the "-a firmware.bin" flag on the flasher command line.

Does ubiboot give any error messages with green text when you select a kernel for booting?

Can you do the following; flash back to the "normal kernel", for example using command:
"sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R"
Then, get the ubiboot log files (ubiboot.log, ubiboot.dmesg) from the configuration directory (/home/user/MyDocs/boot/)
Post the logs here and I will look what's the problem.

Nil kernel work. So what i need do? My way is normal mode > flash to open mode > del aegis dir, and do all things again?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

According to Rainisto, the correct way to flash to open mode is to flash the device back-to-back, that way it should work best.

How to do it, You need to flash first to Closed mode, then to Open mode, without device booting between.

If you have Linux, you can give the flashing commands on the same command line, like this:
"sudo flasher -F firmware.bin -F emmc.bin -f -R ; sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R"

If you have Windows, you can copy-paste the commands from a notepad or something to the console, giving the second command after the first has executed. Or you can have 2 DOS consoles open with the command written there and first press enter on the first, and when it has finished, on the second.

O
The first command seem to first the whole device

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I am sorry? what do you mean?