Thread: Introducing ubiboot N9 (multiboot OS loader)
View Single Post
juiceme is offline juiceme
2013-06-20 , 22:57
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#340
Allright, I have been off-line for a longish time, sorry for that. I was off on a trip to Far North, and after some incident with shovel&wheelbarrows called physical work I hurt my back. I have been on sick leave for few days...

Here's some combination of answers I can dream up at the spur of the moment. Later to follow...

Originally Posted by peterleinchen View Post
First one is just "cosmetic". Would you mind taking out partition 8 and 9 from configuration and init? Our standard compiled kernels only support up to 8 devices (7 partitions).
Yes, no problem in that. Will do it in the next release.

Originally Posted by peterleinchen View Post
Second one is I would like to give my device(s) a unique IP address. Even for telnet usage. I know x.x.x.15 is kind of standard, but would like to have my own.
A reasonable request, can do that in the next release.
Also might add something on the DHCP side, currently it gives 192.168.0.100 as the address of the USB device on the PC, should maybe set that also as configurable...

Originally Posted by peterleinchen View Post
Third one is a bug (probably). Did you or anyone else was successful with version -02 and using mtd5?
Yes, I did test it on my device, but of course it might be that I made a typo or missed a line in the version I actually released... silly things like that happen all the time.
I'll have to test that, and if found guilty, it'll be corrected.

Originally Posted by peterleinchen View Post
I wanted to boot nit from p5:
I copied my full p2 to p5 (of course together with all kernels in boot), moved nit folder to p5, changed nitdroid partition number to 5 in config. And here comes my problem. Nitdroid does not want to start. It always shuts down with black screen: selection in ubi works, selecting nit kernel works (ubi log kexec load success), but then I have dim-lighted black screen for about a few (30?) seconds and device is off. Power button for 3 s jsust boots up again. I have nfc what is biting me here? Maybe watchdog, as it seems not to be started by default. Maybe we can discuss this on irc next days?
This I have to confess I have not tested. I have NIT only on the default loction, and did not try to place it on a different partition.
It sure sounds like a WD problem, and those are a bitch to debug...

Originally Posted by peterleinchen View Post
Ah and maybe one more (to be confirmed tomorrow morning).
Charging an empty device with wall charger works in act-dead mode. But this morning it was still connected to charger and an alarm fired up: no light on display, no UI at all, no possibility to stop the alarm ...
Hmm, never tested that, true. I'll have to see what's with the selection logic but it should actually work, as it detects the mode first and then launches the kernel with the appropriate mode.
Actually when it's in the charging/ACT_DEAD mode, when the alarm later triggers it should not restart ubiboot as it is already running a Harmattan instance, just without user input functionality.

Originally Posted by peterleinchen View Post
Furthermore I experienced that the act#ead charging mode worked only 1 out of 3 times. I had device off, plugged charger, then it booted, shut down (steady LED) and rebooted to telnet console. I pulled charger, pushed power button for 8s and tried again. Same. Only af the third time I saw the charging symbol.
Logs do not tell any suspicious (to me ).
Well, there is some starngeness going on when the device is in ACT_DEAD mode, I have myself noticed that it can start Harmattan more or less spontaniously without going down to ubiboot, when the charger is disconnected and the power button is pressed. I assume tht's a shortcut that has been created to make it boot a bit quicker.

Originally Posted by death_jax View Post
Also for me charging a powered off phone (obviously with a wall charger) didn't work; instead of charging was activated only maintenance mode.. In fact I used the flasher trick to do it...
So, your device always wakes up to ubiboot when you plug in the wall charger in a powered-down mode?
That should not happen, do you have the setting "G_OVERRIDE_USB_CHARGER_BOOT=1" in your ubiboot.conf?
Also you do need to have G_DEFAULT_OS and G_DEFAULT_KERNEL set up to start a Harmattan kernel.

Originally Posted by ncik View Post
I feel really stupid posting it. But I seem to have hit a roadblock. Where do I place the kernels?
No need to feel stupid, I have found out that quite a few people have trouble figuring out that. The problem is that when you are running Harmattan you have a different view of the mounted filesystem than when you are running ubiboot. The README document evidently does not make that clear enough.
I hope you managed to do that with the good advice people gave you here...

Originally Posted by thedead1440 View Post
Regarding the alarms, maybe death_jax is referring to unrestricted sys-ui as its known to cause the same issue on non-ubiboot phones too. However although the symptoms are the same here, your case seems to be caused by ubiboot while his problem is a common unrestricted sys-ui issue...
Indeed, I am fairly sure these problems are not caused by the same thing, even as the symptoms are same.
More testing is obviously required.

Some additional random things; I still have not had time to fix the ssh server to ubiboot. I hope to get to that sometime soonish... Also I thought of adding WLAN configuration to ubiboot, enabling telnet to the device without having the USB connection present.
 

The Following 4 Users Say Thank You to juiceme For This Useful Post: