Re: Introducing ubiboot N9 (multiboot OS loader)
 

Might be something to do with configuring the device on powerup, as I see at least on some occasions "Power Management for TI OMAP3" before the crash.
Maybe it's related to the fact that the device boots first to ubiboot and then to the default kernel which takes longer than booting straight to the default kernel from powerup... Could be some watchdog gets in a wrong state during that phase?

Does it do this often?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

G'd morning. Sorry, just fell asleep (laying in bed :)).

Yes, it does it almost always, when I plug in the wall charger in powered off state. But sometimes it also works and it boots ubiboot and then harmattan lwfix kernel and correctly charges.

The reason why you see different log reports may be that it behaves differently when booted from powered off state and after crash it boots with another boot reason (sw_rst)?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You are correct, if the device goes into kernel panic for some reason I think the bootreason is not trusted, it can have correct value or it can be "32wd_to" or something else..

Hm i just thought of something, have you tried disabling watchdogs, with "sudo flasher --set-rd-flags=no-omap-wd,no-ext-wd,no-lifeguard-reset"

It would be intresting to hear if that makes any difference in either the cold-powerup crashing or the problem to starts kernel-plus.


PS: I do recommend you to fix yourself a serial-console cable... Just this morning, when I debugged a problem in my new-hopefully-soon-to-be-released ubiboot kernel I had to hook up console to find out why going to repair console did not work... and yes, it turned to be the case I had wrong g_multi.ko in my buildscripts... :D:D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Going to set those rd flags and report back later...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

So, needed some time to get my available HW ready for flashing :(
I disabled the watchdogs. And the first two tests were absolutely successful and I thought thats it. But the third time was unsuccessful: the screen stayed black after loading ubi kernel and no charging happened. Tried a few more times and 50/50 was okay/not charging. This time I needed to push power button for 8s, as no reset is done. Pulling/plugging USB did not help, a real power cut was needed. I think due to no-lifeguard-reset?
So in general no change, but the symptoms are different!

Same to the plus_nat kernel. No change here: screen stays black and needs power cut.


Some else info I could provide?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK, I thought that it might help in the charging startup situation but alas, seems it's not the watchdoggies this time.

About the boot to kernel plus, that really bugs me... Just few hours ago TMavica reported that booting from ubiboot to kernel-plus-extfat works without problems, so unless there is something wrong with your setup this is again some HWREV related thingy :mad:

And the strange thing here's that TMavica's got a 1603 device and you have 1601, and up to now it has always been 1603 that are the most troublesome devices?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

What should I say? :(

I also removed kernel and modules and started all over, no change.

I tried many times without booting problem until now

Re: Introducing ubiboot N9 (multiboot OS loader)
 

^Are you saying you have a problem now?
Or that you still don't have any problems?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thats nothing to do with open mode, it happens on secure mode too. System kills background applications if it decides that its low on RAM. Its a feature and not a bug.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just found many people got a problem after install apps from store or deb, all running apps closed after installation, but this is not everytimes.

Maybe this is because of the hw rev problem also? same as ubiboot booting previously?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

System has this process called Out of Memory handler which issues "kill -9" to the applications that are not whitelisted when memory tresshold limit is reached. And installing applications eats usually quite much memory, which causes OOM process to start the killing spree.

If the treshold limit is not reached then nothing is killed.

Ubiboot rebooting issue was more because of watchdogs not beeing triggered.

But this happens only in open mode for me... It closes even one app, usually i don't keep much apps open...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

YA
it only happened in open mode, but not in normal mode

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme
Just as a reminder (due to TMavicas note above and this

I already noted before, that loading from mtd5 does not work yet (at least for me), due to not 'unmounting' mtd4 or numbering ubi devive mtd5 as #2.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, and that is already fixed in the 0.3.3-alpha. The problem was a typo in initscript:

juice@osiris:~/kernel_dev$ diff 2.6.32.54-ubiboot-02_may/usr/ubifs/init 2.6.32.54-ubiboot-02_sep/usr/ubifs/init | grep /mnt/u5
< mount -t /mnt/u5
> mount /mnt/u5

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hey guys, I have a question! Some days ago I installed Ubiboot without installing Nemo (only Harmattan and NitDroid) but now I'd like to try it, what's the way to follow? Can I just follow the nemo-related steps in the wiki or I have to flash ubiboot again? :confused: Thanks :)

@juiceme i will test later when i free

Re: Introducing ubiboot N9 (multiboot OS loader)
 

No need to reflash it, just boot with the MOSLO kernel&rootfs to repartition your mmcblk0. (remember you need to have enough free space on partition 1 for this tu succeed... and of course take backup of everything...)

When the partitioning is done and you boot the device, your ubiboot environment works just like before.

When you have repartitioned the device, you can extract the Nemo rootFS to your mmcblk0p4 either via the MOSLO export or ubiboot maintanance console. (or you can do it in the device console, whatever...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thank you, and let me know if/when it works.
As I do not have windows I have not tested creating extfat partion and mounting it myself. (altough I guess it would not be too difficult to just port mkfs.exfat to the device)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I'm not sure about what to do, isn't it ok if i do (in ubuntu)
wget -r -l1 -nd --no-parent -Amoslo-0.*.rpm http://releases.nemomobile.org/snaps...mv7hl/armv7hl/
rpm2cpio moslo-*.armv7hl.rpm | cpio -vidu
sudo flasher -k usr/share/moslo/zImage-moslo -n usr/share/moslo/initrd-moslo -l -b

and then when finished:

sudo tar --numeric-owner -xf nemo-handset-armv7hl-n950-*.tar.bz2 -C /media/Alt_OS/
which are steps in the wiki? :confused:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That is more or less correct as I remember it :)

In the wiki the steps are under the section "Install Nemo Mobile OS" before you hit the section "Flash the Device with Ubiboot-02"

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme ok thanks :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme I tried, but boot script still said not found

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I'll need to get one of my partitions formatted to exfat and try it myself, then.
Can you show me your /var/log/ubiboot.log, what does it say about mounting partitions?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Same one...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

****
forget mark it..

Re: Introducing ubiboot N9 (multiboot OS loader)
 

It should be still available, as it is on your root partition /var/log directory....

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I figured out how to easily do this without windows :D

• installed exfat-utils to my Easy Debian sandbox
• formatted a partition to exfat and verified it's mountable
• booted to ubiboot console and mounted it as exfat

-> everything works OK for me.

So, Tmavica, there must be some glitch in the ubiboot-02_230913 alpha that causes this to not behave correctly for you.

Can you try the following:

• go to ubiboot maintanance console
• unmount all exported filesystems (if any) from your PC (this is important or the next command does not work)
• remove the exports on N9 by command "echo "" > /sys/devices/platform/musb_hdrc/gadget/lun0/file"
• check that there are no mounts of mmcblk0 by command "mount"
• try to mount the partition with command "mount -t exfat /dev/mmcblk0p1 /mnt/1" (assuming that it is your partition 1 that is exfat)
• check with command "mount" that the partition is mounted correctly

and you should see something like this:

/ #
/ # mount -t exfat /dev/mmcblk0p1 /mnt/1
/ # mount
rootfs on / type rootfs (rw)
none on /dev type devtmpfs (rw,relatime,size=498796k,nr_inodes=124699,mode=75 5)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /tmp type tmpfs (rw,relatime,size=10240k)
/proc/sys/debug on /proc/sys/debug type debugfs (rw,relatime)
none on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mmcblk0p1 on /mnt/1 type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8, namecase=0,errors=remount-ro)
/ #

Re: Introducing ubiboot N9 (multiboot OS loader)
 

ubiboot-02_230913 alpha? Any link?

O dear
I just return to vfat this morning..

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well it's alpha :D
For some (not all though) upcoming features see http://www.swagman.org/juice/ubiboot/TODO
If you have some specific need and are willing to act as a tester contact me in PM

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Of course, let me test it with my exfat :rolleyes:

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okaaay, I see ubiboot menu, but kernels doesn't starts, think it is my conf mistake.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Allright, and you have your /MyDocs/ formatted for extfat?
If that is so, then it works up to the point it can access the partition to load fonf file & cpio.
Can you post your ubiboot log file?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, MyDocs exfat. I'll post log later :)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Aaah, it was my conf fault! Successfully loaded exfat kernel from ubiboot-menu!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Okaaay, nitroid loaded... Seems good!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme
do you still need ubiboot.log?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well I'd like to see it goes OK on your device.
(and to compare to TMacica's log, when I get it, to see why it fails there)