Active Topics
-
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 1 hr, 28 mins ago -
Error after installing Leste on sdcard (12)
to Maemo 7 / Leste by teroyk - 2 hrs, 15 mins ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 10 hrs ago -
Maemo repository (3)
to Community by torsen - 4 days, 3 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 7 hrs ago - more...
|
2012-12-03
, 08:44
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#3
|
Have to do that then... Ain't registrered there yet though.
|
|
2012-12-03
, 09:59
|
|
Posts: 1,225 |
Thanked: 1,905 times |
Joined on Feb 2011
@ Quezon City, Philippines
|
#5
|
Slightly off topic, but speaking of your kexec idea, may I suggest setting the flashable kernel's cmdline for boot device to:
so that the system will be completely independent of the state of Harmattan, Nemo and NITDroid?
The base system can probably be done with evtap + Harmattan components (as seen in the touch preinit)
With the right interface script, you can do everything.
It would allow really easy repartitioning and an extra layer of safety (no need to load Rescue Initrds anymore, you can simply not care about whether the eMMC gets wiped, and with modifiable boot menus, you can kexec into Harmattan outside of mmcblk0p2).
You can probably even slap a complete Debian base system into the "var" partition, which is ~500MB.
Oh, and I've answered some of your questions on the triple-boot thread.
Last edited by Hurrian; 2012-12-03 at 10:02.
Code:
ubi.mtd=var root=ubi0:var rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc
The base system can probably be done with evtap + Harmattan components (as seen in the touch preinit)
With the right interface script, you can do everything.
It would allow really easy repartitioning and an extra layer of safety (no need to load Rescue Initrds anymore, you can simply not care about whether the eMMC gets wiped, and with modifiable boot menus, you can kexec into Harmattan outside of mmcblk0p2).
You can probably even slap a complete Debian base system into the "var" partition, which is ~500MB.
Oh, and I've answered some of your questions on the triple-boot thread.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
Last edited by Hurrian; 2012-12-03 at 10:02.
|
|
2012-12-03
, 11:26
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#6
|
Originally Posted by Hurrian
mmh, I am not that familiar using UBIFS so I have not thought of that. (actuallly just now googled it) I guess the rootfs location would then be somewhere outside mmcblk0, in an unpartitioned flash area...?
Slightly off topic, but speaking of your kexec idea, may I suggest setting the flashable kernel's cmdline for boot device to:
so that the system will be completely independent of the state of Harmattan, Nemo and NITDroid?Code:ubi.mtd=var root=ubi0:var rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc
The reason I have now thought of booting Harmattan/Nitdroid as the first stage and then if Nemo is selected, boot to that using kexec is that I was unable to boot reliably to the existing Harmattan/Nitdroid installation from the Nemo loader. I have trouble understanding where does flashing the kernal actually store the kernel and initrd, they seem to be outside the filesystem, maybe in this UBIFS area?
Originally Posted by Hurrian
All of this sounds really good if doable.
The base system can probably be done with evtap + Harmattan components (as seen in the touch preinit)
With the right interface script, you can do everything.
It would allow really easy repartitioning and an extra layer of safety (no need to load Rescue Initrds anymore, you can simply not care about whether the eMMC gets wiped, and with modifiable boot menus, you can kexec into Harmattan outside of mmcblk0p2).
You can probably even slap a complete Debian base system into the "var" partition, which is ~500MB.
Originally Posted by Hurrian
Yes, now I see. I somehow missed that post!
Oh, and I've answered some of your questions on the triple-boot thread.
|
|
2012-12-03
, 11:52
|
|
Posts: 1,225 |
Thanked: 1,905 times |
Joined on Feb 2011
@ Quezon City, Philippines
|
#7
|
Originally Posted by juiceme
Unformatted, not unpartitioned
mmh, I am not that familiar using UBIFS so I have not thought of that. (actuallly just now googled it) I guess the rootfs location would then be somewhere outside mmcblk0, in an unpartitioned flash area...?
http://www.sakoman.com/OMAP/how-to-w...e-to-nand.html
Part 1 of the tutorial can be followed step-by-step to prepare the required UBIFS partition.
[On Harmattan, mtd-utils, which contains the utilities you need to format it to UBIFS, is located in /usr/sbin/.]
(replace all instances of "rootfs" with "var" though, to keep in line with N9/50 naming)
After you have formatted /dev/mtd4 with UBI and setup a UBIFS partition, you are now ready to install a base Linux system, and your /sbin/preinit (or any init script specified in the kernel cmdline)
Originally Posted by juiceme
Well, once you use kexec, Nemo's loader won't quite matter anymore
The reason I have now thought of booting Harmattan/Nitdroid as the first stage and then if Nemo is selected, boot to that using kexec is that I was unable to boot reliably to the existing Harmattan/Nitdroid installation from the Nemo loader.
That is, if said kernel can kexec properly. If it can't, then you may want to check the MeeGo wiki for the patches used on the N900 to do kexec. It may help you.
(However, I believe that because of the way the kernel image is set up, it will need to be rebuilt as a regular zImage without any MOSLO ramdisk)
Originally Posted by juiceme
/dev/mtd2. It's explained in the post I made in the other thread.
I have trouble understanding where does flashing the kernal actually store the kernel and initrd, they seem to be outside the filesystem, maybe in this UBIFS area?
(Note that for booting regular Harmattan, initrds are unnecessary. They are only used when flasher passes initrds to it)
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
Last edited by Hurrian; 2012-12-03 at 12:01.
|
|
2012-12-03
, 12:29
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#8
|
OK now I am beginnig to understand... I can see the stuff in /dev/mtd's like this:
So basically you suggest that I should use the space in mtd4. Size 0x1ca40000 is bytes, right? So it comes to about 480MB of space...
Thats quite OK for a lots of stuff to be put there. I was not even aware that there is such a space, in excess of mmcblk0.
What I find hard to understand now, if this space is called "var", it is not mounted as /var ?
As there is only /var that is part of the / (mounted from /dev/mmcblk0p2) in the system... so what is it actually used for?
Code:
~ # ~ # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00040000 "bootloader" mtd1: 002c0000 00040000 "config" mtd2: 01000000 00040000 "kernel" mtd3: 00200000 00040000 "log" mtd4: 1ca40000 00040000 "var" mtd5: 02000000 00040000 "moslo" mtd6: 20000000 00040000 "omap2-onenand" ~ #
Thats quite OK for a lots of stuff to be put there. I was not even aware that there is such a space, in excess of mmcblk0.
What I find hard to understand now, if this space is called "var", it is not mounted as /var ?
As there is only /var that is part of the / (mounted from /dev/mmcblk0p2) in the system... so what is it actually used for?
|
|
2012-12-03
, 12:42
|
|
Posts: 1,225 |
Thanked: 1,905 times |
Joined on Feb 2011
@ Quezon City, Philippines
|
#9
|
Originally Posted by juiceme
I think it used to/was going to house /var.
What I find hard to understand now, if this space is called "var", it is not mounted as /var ?
As there is only /var that is part of the / (mounted from /dev/mmcblk0p2) in the system... so what is it actually used for?
However, Harmattan team could not decide what do to with it.
If you read thru /sbin/preinit, it checks for the existence of /var/lib on the rootfs, and if it doesn't exist, it mounts /var from the NAND.
But it's not there, so we have this space all to ourselves.
Hey, it's free space, not used by anything. Take it or leave it
This idea is much, much better than swapping on it (also something the Harmattan team thought they'd want to do, and certainly dabbled with as seen in /etc/init/enable-swap.conf)
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
|
|
2012-12-03
, 12:45
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#10
|
Ya, if it really is free, then I will continue on that idea. Amazing really, half a gig of already set up partition with nothing there!
All that I have found is the repository git://gitorious.org/android-n900/kernel-ng.git which is supposed to be the the correct version.
However, the zImage.pr13 is version 2.6.32.54-dfl61-20121301.
The git version on the other hand is 2.6.32.48-dfl61.
I need to compile the nitdroid kernel with kexec support, this is part of my attempt to build tripleboot kernel for Harmattan/Nitdroid/Nemo