![]() |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
|
Re: Introducing ubiboot N9 (multiboot OS loader)
boot menu script not found...n9 got sailfish & harmattan working properly...until i rebooted in harmattan to switch over to sailfish......i faced this issue
"boot menu script not found" plz run a maintenance boot"..help me guys |
Re: Introducing ubiboot N9 (multiboot OS loader)
I've edited ubiboot.conf and now I've got a "Trap! Booting in 2 seconds" message. How to cope with that without a full reflash?
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Usually that means that you have managed to put in incompatible CPIO or corrupted the one you are loading.... What is your ubiboot version number? If you cannot boot any OS now, what you should do is connect the USB cable to a computer and go to the ubiboot maintanance mode. Then you can telnet to the device and check what is the state of the FS, and why the menuscript is not found. As a temporary measure you can just flash a normal Harmattan Open Mode kernel (like the L2-fixed kenel, for example...) If you do so, and manage to boot up Harmattan, please could you post your ubiboot.log file so I can check what is the cause of the problem? On versions older than 0.3.5 the loaction is /var/log/ubiboot.log and on newer versions /home/user/MyDocs/ubiboot.log |
Re: Introducing ubiboot N9 (multiboot OS loader)
Quote:
Are you able to go to maintanance mode (connect USB cable to a computer) or does the trap occur before maintanance console activation? If you cannot activate maintanance mode, then you are in a bit trickier situation, since you propably need to boot a different kernel (not ubiboot since it always tries to read ubiboot.conf) However, full flash is not required, not at all :)
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Now this problem that @marmistrz got had me thinking a bit of a design problem in ubiboot that need addressing.
If indeed it is possible to get init to trap with an ill-formatted ubiboot.conf file there needs to be a way to get out of this situation gracefully, for example by marking the ubiboot.conf file tainted and not use it on the subsequent boots. Scenario could be something like this;
Basically what happens is if you soup up your ubiboot.conf badly, the device renames it to ubiboot.conf.bad for example and so on the 3rd attempt no configuration file is found and the device goes to maintanance mode. Actually there is a possibility of using an automatic backup configuration with this kind of setup! :D
|
Re: Introducing ubiboot N9 (multiboot OS loader)
Nice idea.
But wouldn't it be easier to create a safe copy like 'ubiboot.conf.sav' in the same folder (which gets loaded after marking current conf as bad)? This way we could still have configs on mtd 4/5 and p1. If marked as bad and not found '*.sav' then jump to next partition. |
Re: Introducing ubiboot N9 (multiboot OS loader)
Excellent idea :)
There's just one minor thing, what if the .sav is also corrupt? I suppose there needs to be logic to decide that, too and in case it proves to be so then proceed to the next partition and finally to drop to unfiltered maintanance mode if nothing starts up correctly :D |
All times are GMT. The time now is 15:23. |
vBulletin® Version 3.8.8