Thread: Introducing ubiboot N9 (multiboot OS loader)
View Single Post
juiceme is offline juiceme
2013-03-14 , 21:43
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#132
Originally Posted by peterleinchen View Post
Hey juiceme,

I thought I had already summarized above
But once again (maybe more precise).
Nit is working
Harmattan (all kernels) working
Ah, I am sorry, it's just that lately I've been doing quite a lot of support for people with ubiboot and once in a while I get mixed up about different problems

But yes, now that I read the thread back a bit I find all the information there.

Originally Posted by peterleinchen View Post
Nemo:
I got it (this morning)
I had a wrong link (mnt/7 instead of /mnt/7). Please do NOT kill me (even remotely) ...
BUT: that was not enough. The return value of kexec -l was 255. So we never ever got to execute the kernel or return to console. Nice idea would here be to go back to menu?
So i just added a few lines to return a "0" in case the result was not "0". Then Nemo booted fine !? What the heck? I did not find meaning of "kexec -l" returning 255. But kexec -e worked.
in shell scripts the return value is just u_char, so 255 means -1. That would translate to -EPERM, which is really strange since you should only get that when attempting kexec_load as non-root user...?

Originally Posted by peterleinchen View Post
So no problems at all with partitions or logical disks or my mods (just the wrong link).

Thank you

--edit
OK, got a dead battery. And put it to charger. Checked again and now return value is "0", so everything okay!
This time bootreason=usb. When I got the 255 the bootreason was sw_rst. Maybe this caused the 255? IDK.
But I am happy
bootreason is a flag that comes off the NOLO as the indicator on how the system should behave on startup, so for example "usb" means system was started because USB was plugged on when device was OFF, "rtc" means system has powered up because a calendar/clock event was triggered etc...
I find it highly unlikely that this has something to do with the kexec_load return value.
Actually, this is just the indicator I need to watch for, as the bug correction mentioned earlier

Originally Posted by peterleinchen View Post
--Remarks
- I still have sometimes weird restart behavior, i.e. after decoupling battery (nemo did not start) it needed a few attempts. It seems bootreason=pwr_off? Maybe change the bootreason in command_line also?
- Charging does not take place when connected charger to powered off phone. it goes to ubi console and does not charge.
Maybe wait for 60s and when there was no telnet connection established (do not know how to detect) then boot to Harmattan (bootreason=act_dead) and let it charge?
Yes, this is because for the charging to work correctly BME should be enabled with g_nokia but the device mistakenly thinks that it's not connected to charger but rather to a PC, and hence loads g_multi to export directories and wait for telnet connection.
To be fixed in near future

Originally Posted by peterleinchen View Post
- A recovery shell from ubi console! After rethinking and recognizing that this (n)9 is a touch-only device, it would be hard to achieve, or?
Well, ever heard of sillykbd?
I already made my own virtual keyboard for N9 preinit environment, it's usable for things like encfs passphrase entry. There's just four lines of text visible on screen at the same time but that's better than nothing. it's actually fairly nice hack, done just with bash scripting
It would not be too difficult to implement a small shell interface with something like it...
See https://toosa.swgman.org/svn/sillykbd/TRUNK/sillykbd

Originally Posted by peterleinchen View Post
- Possibly add /mnt/5, /mnt/6, /mnt/7 dirs in file system and code (maily unmounting in init). And if somehow easy configurable Nemo partition (7 instead of 4). Not for me, as I already have and know now what to do.
Yes, can be done and will be added to backlog.

Originally Posted by peterleinchen View Post
In this context again my question regarding the possible number of devices on mmcblk0? Anybody here knows about that?
(maybe thedead? , thanks for the drivers)
 

The Following User Says Thank You to juiceme For This Useful Post: