![]() |
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
Quote:
|
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
Quote:
|
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
Obviously, the black colour is normal at this point, when backupmenu is starting. But backupmenu do not change to the next screen. It stops exactly there, where it stops before with the red screen.
|
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
going back to miami...
ops to initrd-progs_0.81-7+0m5_armel.deb |
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
Hm, this is interesting. I probably should get myself a spare N900 so I can do some devel work... I don't have the time to finish a "code -> debug -> get working" cycle in one day anymore(and actually use my N900 on a daily basis), so I'm going to need to get myself a second device. Shouldn't be too long now that I've got a good job... Might be able to order it next week...
If you guys take a look at the code, the word 'chrooting' is being displayed from the rootfs-based pre-BM system, and anything after it is being displayed from the chroot. I'd look at the beginning of BackupMenu.item and see what isn't available so it won't start... And yes, if Q works, then that means BM is actually booting, it just isn't displaying. text2screen problems perhaps? |
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
I see, we will mange this problem. Thanks!
|
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
I can definitely confirm Acurus_'s and alexporta's findings. The only version of initrd-progs that works with BM is 0.81-7+0m5 0. Both 1.0-1 0 and 1.0-2 0 get stuck at "Chrooting...". On top of that, 1.0-1 0 has a red background. This is on CSSU-T with KP52.
|
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
All right, I've narrowed the problem down to the new text2screen. When text2screen from the 1.x version of initrd-progs is used, the problem happens. If the stock version of text2screen is used, there is no problem.
So backupmenu does the chroot and after that, the new t2s doesn't react in the same manner as the old one. Is it expecting a file to be there that isn't copied by BackupMenuLauncher.item? ...thinking... |
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
The problem is most likely that the new text2screen needs libpopt.so.0.
The older text2screen did not need libpopt.so.0. If you start backupmenu with "modprobe fbcon" in /sbin/preinit, you can clearly see the error message that libpopt.so.0 cannot be loaded. Latest version: Code:
text2screen Code:
text2screen |
Re: [Announce] BackupMenu - OS backup & restore | New version - Jul 9th(v1.1)
In that case, the fix is simple - inside extrafiles.tar.gz there's a text file with all the files to be in the new chroot. add it to the file, recompress the .gz and you should be good to go
|
| All times are GMT. The time now is 02:12. |
vBulletin® Version 3.8.8