maemo.org - Talk
Page 4 of 35 « First 23 4 5614 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Introducing ubiboot N9 (multiboot OS loader) (https://talk.maemo.org/showthread.php?t=89345)

rainisto 2013-03-12 13:00
Re: Introducing ubiboot N9 (multiboot OS loader)
 
At least I have some device where mtd4 is totally locked due memory errors and which are always inialized as readonly. Thats why it might be nice to have initramfs or mmcblk based version of ubiboot... Some people ofcourse are lucky and have working still mtd4 :)

juiceme 2013-03-12 13:10
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1328535)
Any ideas regarding my p7 problem? (Will post the complete error log tonight, hopefully.)
I have been trying to look up any references to problems booting extended partitions, or possible special naming needed for it but with no success really.
There were some mentioning that the partition order would matter, that in some cases the partition naming would not be consistent.

I still think the problem is mainly this: When in ubiboot environment, whether it be menu or console, your partition is accessible when you mount it as otherwice the kexec_load would not succeed, not finding the kernel.
However, when you boot it the new bootin kernel cannot find it, due to some namespace conflict, maybe ?

A easy case to solve if you only had serial console on your device :D

juiceme 2013-03-12 13:44
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by rainisto (Post 1328541)
At least I have some device where mtd4 is totally locked due memory errors and which are always inialized as readonly. Thats why it might be nice to have initramfs or mmcblk based version of ubiboot... Some people ofcourse are lucky and have working still mtd4 :)
Yes, I have found out that NAND gives you varying mileage. There are quite a few that either cannot use it at all or have it broken partially.
I am developing the alternate implementations, and at same time collecting info on bugs of the current implementation.

peterleinchen 2013-03-12 15:14
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by rainisto (Post 1328541)
At least I have some device where mtd4 is totally locked due memory errors and which are always inialized as readonly. Thats why it might be nice to have initramfs or mmcblk based version of ubiboot... Some people ofcourse are lucky and have working still mtd4 :)
During flash_erasing, I also had some bad blocks/sectors marked as read-only. But in general I seem to be lucky.

Quote:
Originally Posted by juiceme (Post 1328544)
I have been trying to look up any references to problems booting extended partitions, or possible special naming needed for it but with no success really.
Thanks.

Quote:
Originally Posted by juiceme (Post 1328544)
A easy case to solve if you only had serial console on your device :D
Har har ;)

peterleinchen 2013-03-12 16:34
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1328535)
Any ideas regarding my p7 problem? (Will post the complete error log tonight, hopefully.)
Here is the full output:
Quote:
~ # OCMD=$(cat /proc/cmdline); TMP1=$(echo "$OCMD" | sed -e "s/root\=\/dev\/mmcb
lk0p2/root\=\/dev\/mmcblk0p7/") ; TMP2=$(echo "$TMP1" | sed -e "s/ init\=\/sbin\
/preinit/init\=\/sbin\/init/") ; FCMD="\"$TMP2\"" ; eval "/mnt/usr/sbin/kexec -l
--type=zImage --command-line=$FCMD /mnt/mnt/7/boot/bzImage" ; echo $?
Cannot open /proc/atags: No such file or directory
kexec_load failed: Function not implemented
entry = 0x80008000 flags = 280000
nr_segments = 2
segment[0].buf = 0x2b008
segment[0].bufsz = 31c
segment[0].mem = 0x80001000
segment[0].memsz = 1000
segment[1].buf = 0x3aabe008
segment[1].bufsz = 2b17b0
segment[1].mem = 0x80008000
segment[1].memsz = 2b2000
255
where FCMD is:
Quote:
"init=/sbin/preinit_harmattan root=/dev/mmcblk0p7 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),1638 4k@3840k(kernel),2048k@20224k(log),469248k@22272k( var),32768k@491520k(moslo) bootreason=sw_rst bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=01234xxxxxxxxxxxxxxx imei=35xxxxxxxxxxxxx g_nokia.iSerialNumber=35xxxxxxxxxxxxx serialnumber=CTKxxxxxx omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfsutput,cmt_en:23:sysfs:i nit_activeutput,cmt_rst_rq:88:sysfs:init_active: output,sleep_ind:92:sysfsutput omapdss.def_disp_enabled=1 vhash=xxxx93xxxxxded180a3xxxxx42c0d09b0dxxxxx product_model=N9 hwid=1601"
I have searched for atags in stock harmattan /proc and in ubifs /proc and in Nemo /proc, but there is no such file. I remember that from N900 and u-boot, but here in Harmattan?
Do I have the wrong Nemo image (nemo-handset-armv7hl-n950-0.20130218.0.1.NEMO.2013-02-15.1.tar)? I do not think so, but when then :facepalm:
Or what?

I have done above from harmattan, mounted ubifs on /mnt and Nemo partition on /mnt/mnt/7

juiceme 2013-03-13 08:25
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1328589)
Here is the full output:
Quote:
~ # OCMD=$(cat /proc/cmdline); TMP1=$(echo "$OCMD" | sed -e "s/root\=\/dev\/mmcb
lk0p2/root\=\/dev\/mmcblk0p7/") ; TMP2=$(echo "$TMP1" | sed -e "s/ init\=\/sbin\
/preinit/init\=\/sbin\/init/") ; FCMD="\"$TMP2\"" ; eval "/mnt/usr/sbin/kexec -l
--type=zImage --command-line=$FCMD /mnt/mnt/7/boot/bzImage" ; echo $?
Cannot open /proc/atags: No such file or directory
kexec_load failed: Function not implemented
entry = 0x80008000 flags = 280000
nr_segments = 2
segment[0].buf = 0x2b008
segment[0].bufsz = 31c
segment[0].mem = 0x80001000
segment[0].memsz = 1000
segment[1].buf = 0x3aabe008
segment[1].bufsz = 2b17b0
segment[1].mem = 0x80008000
segment[1].memsz = 2b2000
255

Harmattan kernel does not implement kexec(), or at least it is not done correctly, hence the load of errors given to you when you try to load the kernel image to memory. I actually made one Harmattan-vanilla kernel that implements kexec() but have not used it since I adopted the MOSLO kernel (Nemo variant) to ubiboot.

Tou only get /proc/atags on kernels compiled with kexec() support.

You need to do that in ubiboot console or Nemo (Nemo should be able to kexec() if the needed tools and modules are in place)


Quote:
Originally Posted by peterleinchen (Post 1328589)
where FCMD is:
Quote:
"init=/sbin/preinit_harmattan root=/dev/mmcblk0p7 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),1638 4k@3840k(kernel),2048k@20224k(log),469248k@22272k( var),32768k@491520k(moslo) bootreason=sw_rst bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=01234xxxxxxxxxxxxxxx imei=35xxxxxxxxxxxxx g_nokia.iSerialNumber=35xxxxxxxxxxxxx serialnumber=CTKxxxxxx omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfsutput,cmt_en:23:sysfs:i nit_activeutput,cmt_rst_rq:88:sysfs:init_active: output,sleep_ind:92:sysfsutput omapdss.def_disp_enabled=1 vhash=xxxx93xxxxxded180a3xxxxx42c0d09b0dxxxxx product_model=N9 hwid=1601"
I have searched for atags in stock harmattan /proc and in ubifs /proc and in Nemo /proc, but there is no such file. I remember that from N900 and u-boot, but here in Harmattan?
Do I have the wrong Nemo image (nemo-handset-armv7hl-n950-0.20130218.0.1.NEMO.2013-02-15.1.tar)? I do not think so, but when then :facepalm:
Or what?

I have done above from harmattan, mounted ubifs on /mnt and Nemo partition on /mnt/mnt/7
Also, noticed that you have "init=/sbin/preinit_harmattan", it should be changed to "init=/sbin/init" for Nemo

peterleinchen 2013-03-13 14:32
Re: Introducing ubiboot N9 (multiboot OS loader)
 
HOLY SH..

I have struggled the whole day with my computers USB networking capabilities or lets say the Nokia f...ing non-ability to provide correct driver for Win7 64.

You will not believe (or at least i didn't):
The kernel could be loaded, so this command
Quote:
OCMD=$(cat /proc/original_cmdline); TMP1=$(echo "$OCMD" | sed -e "s/root\=\/dev\/mmcblk0p2/root\=\/dev\/mmcblk0p7/") ; TMP2=$(echo "$TMP1" | sed -e "s/ init\=\/sbin\/preinit/init\=\/sbin\/init/") ; FCMD="\"$TMP2\"" ; eval "kexec -l --type=zImage --command-line=$FCMD /mnt/7/boot/bzImage" ; echo $?
returned with zero/OK.
Then the excution of
Quote:
/usr/bin/disable_pm ; kexec -e ; echo $? ; sleep 10
immediately dropped the telnet session.
And the screen did stay black :(

BUT: I did see the LED blinking. AND my computer detected the Linux/RNDIS gadget (the correct name of USB network driver). So I thought what's going on here?
I disconnected USB, connected again. And fired up another telnet session on newly configured USB network.
And voila:
I could log in to Nemo as root :D

And now ??? ;)
How to enable the screen? And/or X, or whatever it is called in Nemo.


--UPDATE--
Now i disconnected USB immediately after executing kernel. Lost again telnet session.
But now i do see a nice snow crystal :D
To be continued ...

thedead1440 2013-03-13 14:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
peterleinchen,

Slightly off-topic; if you mean Win7 not being able to find/install SDK mode drivers for N9; get them from here and install them ;)

peterleinchen 2013-03-13 22:47
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Continued:
Unfortunately this was the only time I could touch the Nemo (when loaded and kexec the kernel from ubi command line and immediately disconnect USB).
When selected the Nemo via ubiboot menu nothing happens (screen stays black). I need to decouple battery.
When selected via ubi console and leave USB connected then screen stays black, but I can SSH into Nemo.
I did not test (yet) the black scrren from ubiboot selection for possibility of SSH login.

So I am stuck now...

juiceme 2013-03-14 07:47
Re: Introducing ubiboot N9 (multiboot OS loader)
 
So, can you sum up what is working currenty?
Boot to Nemo is failing but can you boot normally to Harmattan and Nitdroid?
From experience I have had myself and from other users boot to Harmattan is the trickiest, everybody that has installed ubiboot is able to boot to Nitdroid, and all that have Nemo in mmcblk0p4 can boot to Nemo.

peterleinchen 2013-03-14 11:48
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Hey juiceme,

I thought I had already summarized above ;)
But once again (maybe more precise).
Nit is working
Harmattan (all kernels) working

Nemo:
I got it (this morning) :D
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.

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 :)


--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?
- 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?
- 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.
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)

juiceme 2013-03-14 21:43
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1328949)
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.

Quote:
Originally Posted by peterleinchen (Post 1328949)
Nemo:
I got it (this morning) :D
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...?

Quote:
Originally Posted by peterleinchen (Post 1328949)
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 :D

Quote:
Originally Posted by peterleinchen (Post 1328949)
--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 :)

Quote:
Originally Posted by peterleinchen (Post 1328949)
- 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? :D
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 :D
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

Quote:
Originally Posted by peterleinchen (Post 1328949)
- 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.

Quote:
Originally Posted by peterleinchen (Post 1328949)
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)

peterleinchen 2013-03-14 22:35
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by juiceme (Post 1329050)
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 :)
No need to be sorry, not at all.

Quote:
Originally Posted by juiceme (Post 1329050)
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...?
u_char I knew, but where to find info about return values?
Seems I need to educate myself a bit more ...

Quote:
Originally Posted by juiceme (Post 1329050)
bootreason is a flag that comes off the NOLO as the indicator on how the system should behave on startup,
...
I find it highly unlikely that this has something to do with the kexec_load return value.
Me tto, as it is only a string passed to kernel, right? But ...

Quote:
Originally Posted by juiceme (Post 1329050)
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 :)
THX. But that would mean also connected via USB to PC will not load? But on wall carger yes? Fair deal.


Quote:
Originally Posted by juiceme (Post 1329050)
Well, ever heard of sillykbd? :D
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 :D
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
Yes, can be done and will be added to backlog.
Wow, that would be cool. Never heard of, only sillyboot.
toosa.swagman.org is down?

Thanks to your work I start to like the N9, even I still need a PC alongside :D

juiceme 2013-03-14 22:48
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by peterleinchen (Post 1329056)
No need to be sorry, not at all.

u_char I knew, but where to find info about return values?
Seems I need to educate myself a bit more ...

Me too, as it is only a string passed to kernel, right? But ...

THX. But that would mean also connected via USB to PC will not load? But on wall carger yes? Fair deal.

Wow, that would be cool. Never heard of, only sillyboot.
toosa.swagman.org is down?

Thanks to your work I start to like the N9, even I still need a PC alongside :D
Return values I just looked from the kernel sources, where the call is handled.

The charging/connection seems to be a tradeoff at the moment. It could be possible to hack up a module that does both, maybe. I really just took what was already there and did not look that deeply into it.

Re: toosa being down, no, it's up, but there's some DNS trickery going on, maybe?
Try the IP address: https://88.115.90.185/svn/sillykbd/TRUNK/sillykbd

juiceme 2013-03-18 21:56
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Updated ubiboot to use alternate installation FS. Now it is possible to use either mtd4 or mtd5 partition.
See changes of installation the README file

TMavica 2013-03-20 07:28
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I dont understand the part, where kernel file put to

coderus 2013-03-20 08:09
Re: Introducing ubiboot N9 (multiboot OS loader)
 
anywhere to mmcbk0p2
for example in readme: /boot

coderus 2013-03-20 08:11
Re: Introducing ubiboot N9 (multiboot OS loader)
 
@juiceme instructions 3. ends with umount. 4. starts with configuring boot.conf. but partition was unmounted :)

TMavica 2013-03-20 08:22
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by coderus (Post 1330226)
anywhere to mmcbk0p2
for example in readme: /boot
I have in 3 zimage in /boot, after bootup harmattan Nokia Logo appear but then shutdown.

Confirm the kernel not put in /mnt/boot/Harmattan/boot?
make the directory self?

coderus 2013-03-20 08:31
Re: Introducing ubiboot N9 (multiboot OS loader)
 
/boot/Harmattan in ubifs is symlink to / in meego :)

TMavica 2013-03-20 08:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
oic
let me try again

TMavica 2013-03-20 10:29
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I just success booting into nitdroid and Harmattan but with only 1 kernel work, I only can boot with zImage-2.6.32.54-dfl61-20121301, the nitdroid and l2fix kernel I cant boot up, it shutdown when booting.

Hurrian 2013-03-20 10:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Just keep trying to boot.

Kexec is hit and miss on Harmattan.

TMavica 2013-03-20 10:50
Re: Introducing ubiboot N9 (multiboot OS loader)
 
keep booting until it can boot in harmattan you mean...??

peterleinchen 2013-03-20 15:03
Re: Introducing ubiboot N9 (multiboot OS loader)
 
And make sure you have exactly the same spelling in boot.conf for the file name of kernels (was one of my mistakes at early stage: put a "_" instead of a "-".

TMavica 2013-03-20 15:38
Re: Introducing ubiboot N9 (multiboot OS loader)
 
A firm no mistake

TMavica 2013-03-20 15:47
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I find in the boot.conf preset
G_HARMATTAN_INITSCRIPT="\/sbin\/preinit_harmattan"
G_NITDROID_INITSCRIPT="\/sbin\/preinit_nitdroid"
G_NEMO_INITSCRIPT="\/sbin\/init"

there is \/ between, is it the format is wrong?

thedead1440 2013-03-20 15:51
Re: Introducing ubiboot N9 (multiboot OS loader)
 
TMavica,

That's right; what you should do is simply give the paste of all the steps you did and the contents of /boot/ in Harmattan as well as your ubifs/etc/boot.conf paste

That would make things easier instead of just guessing what you may have done wrong :)

TMavica 2013-03-20 15:58
Re: Introducing ubiboot N9 (multiboot OS loader)
 
I think the problem is here...should be change to

G_HARMATTAN_INITSCRIPT="/sbin/preinit_harmattan"
G_NITDROID_INITSCRIPT="/sbin/preinit_nitdroid"
G_NEMO_INITSCRIPT="/sbin/init"

thedead1440 2013-03-20 16:01
Re: Introducing ubiboot N9 (multiboot OS loader)
 
TMavica,

I mentioned to you above that format isn't wrong. If you want to solve issues its best you paste like mentioned instead of trying to "fix" what isn't broken ;)

Also before you do the above try to replace your preinit_harmattan with nitdroid's preinit by renaming nitdroid's preinit to preinit_harmattan

coderus 2013-03-20 16:06
Re: Introducing ubiboot N9 (multiboot OS loader)
 
@TMavica i think there are no type mistakes in scrips and configs :D

TMavica 2013-03-20 16:32
Re: Introducing ubiboot N9 (multiboot OS loader)
 
leave it
I gave up, the device keep booting

coderus 2013-03-20 16:38
Re: Introducing ubiboot N9 (multiboot OS loader)
 
sure. no need in ubiboot, if you can't just install it, set up and use ;)

TMavica 2013-03-20 16:41
Re: Introducing ubiboot N9 (multiboot OS loader)
 
but I can sure all step is no wrong and no error..

rainisto 2013-03-20 16:43
Re: Introducing ubiboot N9 (multiboot OS loader)
 
attaching serial cable to console rx tx pins will ofcourse tell you whats wrong, but thats beyond that most people are willing to do.

rainisto 2013-03-20 20:07
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Just tested this with one of my N950's. but unfortunately that one had ecc memory errors even on mtd5, so no way to make a volume for it.

Would be great to see initramfs or mmcblk version someday.

explit 2013-03-20 22:12
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Cool Thing. After a mtd-5 update I'm able to boot NITDROID with zImage.pr13 and Harmattan with zImage.pr13 and standard openmode Kernel.
I copied both kernels inside /mnt/boot (Without Harmattan or Nemo Folders). and modiefied /etc/boot.conf to point to my kernels inside /boot. Is it a bad idea ?

Maybe anybody can give me a tip for Tripleboot (Harmattan, Nitdroid, Nemo) ?

Has anybody of you have a running tripleboot with the UBIBoot ?

THX guys...

TMavica 2013-03-20 22:38
Can you post out your boot.conf file?

explit 2013-03-20 22:45
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Code:
# Original version is based on the MOSLO kernel & boot OS.
#
G_UBIBOOT_VERSION="0.2.0"

# Enable timeout for the main boot menu. If this is set to 0 then we will wait forever
# for user interaction in the menu... propably not a wise selection.
# If timeout is specified and reached, the default OS & kernel are booted.
#
G_MENU_TIMEOUT=1

# Exported partitions if USB is connected.
# Even if you set this to (none), you can export these manually when you telnet to the device.
# Exporting them all is handy for backup purposes as you can then tar off everything on a partition
# to external computer. Note that windows computers cannot normally mount ext2 partitions...
# This could be thought as a minor security breach, but then again, same thing can always be accomplished
# using flasher and maintanace boot so I do not see this as an additional high risk...
#
G_EXPORTED_PARTITONS="/dev/mmcblk0"      # This exports all partitons of the device
#G_EXPORTED_PARTITONS="/dev/mmcblk0p1"    # this exports just the Mydocs partiton
#G_EXPORTED_PARTITONS="/dev/mmcblk0p2"    # this exports just the root partition
#G_EXPORTED_PARTITONS="/dev/mmcblk0p3"    # this exports just the home partiton                           
#G_EXPORTED_PARTITONS="/dev/mmcblk0p4"    # this exports just the nemo partition                                         
#G_EXPORTED_PARTITONS=""                  # this turns off partition exporting                           

# Start DHCP server on the USB, to give address for a host for telnet access.                     
# If this is set to 0, you must ifconfig the interface yourself to access the device.             
#                                                                                                 
G_START_DHCP_SERVER=1                                                                             

# Enable telnet server on the device.
# If the USB is connected when the device boots, no menu will be shown and instead you may login
# to the device for maintanance purposes.
# This could be thought as a minor security breach, since no password is required.
# However, same thing can always be accomplished using flasher and maintanace boot so I do not see
# this as an additional high risk...
#
G_START_TELNET_SERVER=1

# Enable SSH server on the device.
# If the USB is connected when the device boots, no menu will be shown and instead you may login                         
# to the device for maintanance purposes.                                                                                 
# This is better than telnet as you need to use the harmattan root password to login to the device.
# Hey, of course you have changed the default password from "rootme" to something else? What, not? hmmm...
# Unfortunately this is not ready yet... I need to rebuild the SSH server to not ***** about missing PAM's...
# ... hence not enabled :)
#
G_START_SSH_SERVER=0

# Now follow the bootable OS'es and kernels on the device, this is the structure of the 2nd level menu.
# Due to screen resolution issues, the maximum length of the kernel label is 30 characters.                 
# Each OS has 6 slots for kernels, but all need not be defined. The G_<osname>_NUM parameter defines
# the number of kernel lines shown on the 2nd level menu.

# Init scripts for different OS'es. Make sure that you have these in place, or else booting will fail.
# Note that you have to escape the forward slashes here as this is a substituting expression in sedscript...
G_HARMATTAN_INITSCRIPT="\/sbin\/preinit_harmattan"
G_NITDROID_INITSCRIPT="\/sbin\/preinit_nitdroid"
G_NEMO_INITSCRIPT="\/sbin\/init"

# Nitdroid kernels
G_NITDROID_NUM=1
G_NITDROID_1_LABEL="E-yes PR 1.3 kernel"
G_NITDROID_1_FILE="/boot/zImage.pr13"
G_NITDROID_2_LABEL=""
G_NITDROID_2_FILE=""
G_NITDROID_3_LABEL=""                                                                                 
G_NITDROID_3_FILE=""                                                                                   
G_NITDROID_4_LABEL=""                                                                                 
G_NITDROID_4_FILE=""                                                                                   
G_NITDROID_5_LABEL=""                                                                                 
G_NITDROID_5_FILE=""                                                                                   
G_NITDROID_6_LABEL=""                                                                                 
G_NITDROID_6_FILE=""                                                                                   

# Harmattan kernels
G_HARMATTAN_NUM=2
G_HARMATTAN_1_LABEL="E-yes PR 1.3 kernel"
G_HARMATTAN_1_FILE="/boot/zImage.pr13"
G_HARMATTAN_2_LABEL="Plain OpenMode kernel"
G_HARMATTAN_2_FILE="/boot/zImage-2.6.32.54-dfl61-20121301"
G_HARMATTAN_3_LABEL=""
G_HARMATTAN_3_FILE=""
G_HARMATTAN_4_LABEL=""                                                                                 
G_HARMATTAN_4_FILE=""                                                                                 
# G_HARMATTAN_5_LABEL="2.6.32.54-dfl61-oma"
# G_HARMATTAN_5_FILE="/boot/Harmattan/boot/zImage-2.6.32.54-dfl61-oma"
# G_HARMATTAN_6_LABEL="2.6.32.54 Nemo backport"
# G_HARMATTAN_6_FILE="/boot/Harmattan/boot/zImage-2.6.32.54-juice_backport"


# Nemo kernels
G_NEMO_NUM=2
G_NEMO_1_LABEL="Latest 2.6.32"
G_NEMO_1_FILE="/boot/Nemo/boot/bzImage"
G_NEMO_2_LABEL="Unstable 3.5.3 SabreTSq"
G_NEMO_2_FILE="/boot/Nemo/altboot/vmlinuz-3.5.3-juice"
G_NEMO_3_LABEL=""
G_NEMO_3_FILE=""
G_NEMO_4_LABEL=""                                                                                     
G_NEMO_4_FILE=""                                                                                       
G_NEMO_5_LABEL=""                                                                                     
G_NEMO_5_FILE=""                                                                                       
G_NEMO_6_LABEL=""                                                                                     
G_NEMO_6_FILE=""                                                                                       

# Default boot kernel
# If timeout is reached before user interaction this is booted
G_DEFAULT_OS="Harmattan"
G_DEFAULT_KERNEL="/boot/zImage-2.6.32.54-dfl61-20121301"

juiceme 2013-03-21 08:37
Re: Introducing ubiboot N9 (multiboot OS loader)
 
Quote:
Originally Posted by coderus (Post 1330228)
@juiceme instructions 3. ends with umount. 4. starts with configuring boot.conf. but partition was unmounted :)
Thanks, coderus :D
I will fix that in instructions...


All times are GMT. The time now is 03:51.
Page 4 of 35 « First 23 4 5614 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8