Notices

Update: after switching on again after charging a while (and unplugging charger befor powering up) it did work after second plug in. So now it's charging again with running device but hell knows what happens next time I'll try to charge.

@pali:
I found out the problem, I think - For whatever reason, when /bootmenu.sh runs(for me), text2screen won't/can't work - It returns "cannot find valid screen dimensions". Which means that, until this problem is solved, I -cannot- have the bootmenu working; It can't display anything to the screen!

version 6.0

reboot with kb open.

receive error:

UDev Started
1
2
error with: op /usr/lib/liblzo2.so.2 /tmp/disk/usr/lib/ Code : 1

What is the newest initiative here? I'm a bit lost.

I'm rocking bootmenu/multiboot and BM v0.56 just fine. I've set aside my other boot partitions and kernels, numbered and set up .items. 1). Android, 2). Maemo and 3). BackupMenu.

Works fine. Am I just the odd one out here now or is there something else being worked on?

0.60 is what I'm currently working on, and it adds charging support, and I'm working on adding the ability to create flashable images.

@f2thak:
Any errors like that; just keep pressing space. It looks like I forgot to add a package to the requirement list.

0.60-2 has been uploaded and it fixes that glitch.

Hey Robbie, I can send you my (half-finished) script for the flashable image support, if it helps. I haven't got very far, mostly just the menu items which should be lined up nicely, and it's based on 0.56 of course, so a bit out-of-date now! Also, I've found (through much testing in a chrooted environment) that using flash_eraseall then nandwrite is better than flasher, and zlib'd ubinized images seem to work with that option too. I seem to remember from memory that nandwrite needs a library or two added to the launcher script, but nothing major. Talking of which, I did notice that some of the library symlinks were wrong; I think I've fixed them all in BackupMenuLauncher.item if you'd like me to send that too?

Tigerite, are you able to flash a zlib'd ubinized image on your n900? Does it boot it?

I haven't tried to boot it, but as I say, I believe flash_eraseall to wipe the mtd5 partition, and then nandwrite of the image over the now-clean partition will work better than flasher. It definitely reads it properly when I use nandsim and mount it (using mount -t ubi1:rootfs /tmp/mnt/rootfs) so I see no reason why it wouldn't - after all, it's only a partition at the end of the day. There are no rogue dmesg errors either (there are loads though if you use ubirmvol and then ubimkvol rather than flash_eraseall, and the same if you use just flash_erase to remove the first block - I've tested just about everything, except for ubiformat, which complains about lack of memory and just falls over).

@tigerite:
Sure, let me see what you've got.
0.60 hasn't changed much in backupmenu.item itself, just the launcher.

As far as fixed symlinks, I'd like a diff compared to stock launcher.item.

Oh, and as far as testing out flashing, why not login via ssh and make/flash your images from there? That ought to be the definitive test as to what needs to be done.

Thanks.

Okay, here we go. I couldn't get WinDiff to give me a nice output for the diff file, only the one I've included, hope you can make sense out of it (<! are lines I've added, whereas !> are old lines that have been removed). It's based against the 0.56 launcher as a base, rather than 0.60, hope that's okay. I've included both the diff and my modified version just for completion's sake.

As for SSH, I haven't tried that, but will give it a go a bit later when I've got my USB cable to hand..