To be fair, I tnought I aready -did- a guide on the first post.
@ednunez70:
I'm currently leery of suggesting someone like you use my product. It's still not bug free, and at least one person has ended up with an unbootable system by just installing it(not sure how that could happen - bugs in bootmenu-n900).
If you do want to use it, you can make a backup now, and should be able to restore unless your rootfs is -totally- wiped. But, be warned about my previous comment - I take no responsibility if you manage to brick your system.
I would also suggest asking around, I know people have fixed the usb ports themselves - the replacement part is like $5 - and perhaps one of them would be willing to fix it for a fee.
Okay, so finally had a chance to install and test 0.50-3 (after a long time with MfE which seems messed up after PR 1.3). Ran perfectly though I did get one error:
Sure. I'm assuming you've already got multiboot 0.2.10 installed here - if not, you'll need to look up the instructions for that elsewhere (the multiboot/NITDroid/power kernel threads).
Unfortunately the only implementations of patch appear to be in the SDK repository, so rather than using the diff, just grab the patched files and save them to the MyDocs directory.
Now overwrite the existing multiboot files with the new versions:
Code:
root
cd /sbin
tar -xzf /home/user/MyDocs/multiboot_patched.tar.gz
chmod 755 multiboot multiboot_read_item
That's the patched multiboot all done, so you now just need to create a new boot item. You'll need to create a file (either on the N900, or on a desktop/laptop then copied to the N900) containing:
Move this file to /etc/multiboot.d/99-BackupMenu.item (you'll need to be root to do this).
Now when you reboot with the keyboard open, you'll get an option for BackupMenu. I think this'll work irrespective of which OS/kernel you've been booting with, but I've only tested it from the standard Maemo kernel so far.
Haven't had a chance to tackle this yet but much appreciated. One question though: you say "create a file" and then move it to .../99-BackupMenu.item. Do we name the file we create "99-BackupMenu.item"
A while back I asked multiboot vs. bootmenu compatibility with this. I appreciate the replies and help I got. After digging up more information I realized that I liked the 'uboot' method better. So my other question - can bootmenu and backup menu be installed 'inside' a system already loaded from uboot? So say I flash my kernel to a combined kernel-uboot image - could I then safely install bootmenu on the Maemo OS, and avoid conflicts?
BackupMenu is just a (long and complicated) shell script. All you need to do is somehow run '/usr/share/backupmenu/BackupMenuLauncher.item' using Busybox's ash(bash'd probably work too).
It also needs access to a number of files and a couple of other commands, all listed inside the above file.
Also of note is the mostly hard-coded partition structure - rootfs is ubi0, optfs is /dev/mmblk0p1, mydocs is /dev/mmcblk0p2, and SD is /dev/mmcblk1p1. If you change partition structure, you may need to edit those names in /usr/share/BackupMenu.item.
Personally, I use bootmenu-n900, but am open to adding any changes that would make it more compatible - I'll add that multiboot file if peope think it'd help.
