I just got N810 after 2 years of using N770 and couldn't be happier. Yesterday got 8GB SD card and decided to set up dual boot using 2GB internal SD as a second bootable partition. I did find instructions on this thread but did a slight variation of these as I did not want to partition internal SD and instead made it one ext2 partition. I had to make a slight change in bootmenu.sh so it is loading from the right partition, and it now boots from 2Gb SD, but my 8GB external card is not mounted at all.
When I boot from flash I get:
/dev/mmcblk0p1 on /media/mmc2 type ext2
/dev/mmcblk1p1 on /media/mmc1 type vfat
When I boot from SD I get:
/dev/mmcblk0p1 on /media/mmc2 type ext2
/dev/mmcblk1p1 on / type ext2
All attempts to mount external SD manually were unsuccessful. I realize that most likely I need to make some changes in bootmenu.sh and re-flash, but for the life of me cannot figure out what - shell scripting is not my forte...

Please help!

TIA

Looks like you have something mounted on /media/mmc2. What happens with mount output (or /proc/mounts) when you open card door or remove the card? Is /media/mmc2 unmounted? But anyway it is easier to keep small FAT partition on the beginning so the system is not confused. Maybe with such small fat partition the external one would work.

BTW you don't need to do any change in bootmenu.sh to boot from first partition, it is better to use bootmenu.conf for such customization.

Fanoush,
Firstly I'd like to thank you for making initfs_flasher available, it certainly makes dual boot easy.
The External card on N810 is mounted as mmc1, and internal as mmc2. When I boot from internal SD, I get /dev/mmcblk1p1 auto-mounted as / (although there is also rootfs mounted to /). I don't even understand how vfat device can get mounted as ext2. If I remove the external SD with device on and pop it back in - system shuts down. If I take the card out and pop it after device is powered on - everything is fine and /dev/mmcblk1p1 is correctly mounted to /media/mmc1, however after subsequent reboot /dev/mmcblk1p1 goes back to being mounted as /, ext2.
Thanks,
Vlad

oh, so when you insert card after system is booted it works fine? Then maybe you are bitten by this bug http://bugs.maemo.org/show_bug.cgi?id=2747

maybe system is confused by this when mounting/unmounting:
/dev/mmcblk0p1 on /media/mmc2 type ext2
/dev/mmcblk1p1 on / type ext2
because both entries actually point to internal card not external one. What you see when you do 'ls /media/mmc2' in this state? Do you see data from internal or external one?

If you want to verify if this is the problem I can make kernel with this fix available. Or maybe you prefer to compile your own one? patch is attached to bugzilla entry

When I do ls /media/mmc2 I see internal card contents. If you can patch the kernel - that would be great as I only have an Ubuntu VM running in Virtual Box and no Maemo tools/source/compiler which I assume is needed for patching.

Thanks!

OK, kernel is here http://fanoush.wz.cz/maemo/kernel-di...2maemo1.tar.gz
modules (optional) here http://fanoush.wz.cz/maemo/modules-d...2maemo1.tar.gz

This is kernel with fix for bug 2747 and bug 3243 and harmless stuff like crypto api enabled (for pptp/mppe) and dsp speed tuning via /sys/power/op_dsp (default is OP 1 = CPU 330/DSP 220 MHz just like in original Nokia kernel, OP_0 is 400/133). No 48MHz sd/mmc modes or rotation included.

If this kernel helps with your issue, feel free to vote for bug 2747.

Fanoush,
Thanks much for compiling this kernel. After some searching, my understanding is that I can only have 1 kernel with the dual boot system, so before applying it, I'd like to back up my current kernel. What is the best way to do this? Also, what is the best way to install a new kernel and modules?
Thanks!

The original one can be extracted from .bin firmware image via Nokia linux flasher (or 0xFFFF flasher). As for custom kernel it shouldn't be hard to re-download from place you got it previously.

There is no ready made tool AFAIK. You can dump kernel partition via nanddump and strip NOLO header (first 2048 bytes) and truncate it (not strictly needed). Good idea would be to put such backup functionality to my kernel flasher, It is quite easy.

nanddump is inside my initfs_flasher.tgz, nanddump -o -b -s 2048 -f zImage.backup /dev/mtd2 should produce flashable kernel backup (with some extra garbage)

Fanoush, this has fixed the issue, thanks again! I did leave my vote in Bugzilla. What are the chances of this making into a standard distribution, so if there are any system updates in the future the kernel does not have to be re-built?

kernel is updated also with fix for bug https://bugs.maemo.org/show_bug.cgi?id=3243 - usb networking in Windows doesn't work