View Single Post
Posts: 842 | Thanked: 1,197 times | Joined on May 2010
#15
Originally Posted by debernardis View Post
Hello Robbie,
after I backed up with this latest method I rebooted and found my n900 completely messed up. This happened also last time I did it, with your previous version (the tar one). To be clear, I didn't try any reboot.
Now I'm restoring with your first version, the img one, which works for me by flashing the rootfs and restoring the optfs.
Do you have any hint why the simple action of backup in some way damages the filesystem? This sounds me quite strange, but it's what is happening to me.
Thanks for testing. Lets see what went wrong here:

First, a sanity check: Is the outer border of the BackupMenu window -blue- or -orange-? Also, the new one should be v0.45.
My first thought is that /etc/bootmenu.d/BackupMenuLauncher.item was not removed from your test of my earlier alphas, and it "took precedence", potentially resulting in a problem.
Make sure that both BackupMenu and BackupMenuLauncher in /usr/share/backupmenu/ are infact the same version as the ones in the package I released, and that "backupmenu.item"(all lowercase) exists in /etc/bootmenu.d/ and is the only file there.

Second thing to try is installing a framebuffer kernel and watching where it dies on.
Stock: http://mohammadag.xceleo.org/public/...e-fb-omap1.bin
power40: http://mohammadag.xceleo.org/public/...ebuffer-kernel
Flash one of those to your N900 with "flasher-3.5 -k ./zImage..... -f -R", then watch it boots. Note that it slightly interferes with the graphics of BackupMenu, but its -more or less- legible even with it on.

Let me know how things work out - I'm under pressure to get this fixed and out there replacing my old version, due to that one using DD to write directly to the NAND flash of the rootfs, which, I have been told, is dangerous and should never be done. So... Yea.
 

The Following 3 Users Say Thank You to RobbieThe1st For This Useful Post: