Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 20 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 5 hrs ago - more...
| The Following User Says Thank You to alexporta For This Useful Post: | ||
 |
|
2013-07-04
, 11:39
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#1242
|
Hi RobbieThe1st,
I wondered if it's high time to implement a logic into BM restore that checks kernel in /dev/mtd3 against any kernel modules in a backup about to get restored, and WARNS resp offers an option to not restore kernel modules if they don't match.
We seen zillions of users ending with a complete reflash and even maybe not able to restore at all (due to lack of proper guidance how to proceed) just because they did a BM backup and then installed powerkernel or uBoot. I think it should be rather easy for BM to test for and catch those problem cases, and even offer proper guidance:
What do you think? If you plan to implement such function, don't hesitate to ping me for help.
Many thanks for what's undoubtly the most useful and important app on fremantle ever :-)
cheers
jOERG
I wondered if it's high time to implement a logic into BM restore that checks kernel in /dev/mtd3 against any kernel modules in a backup about to get restored, and WARNS resp offers an option to not restore kernel modules if they don't match.
We seen zillions of users ending with a complete reflash and even maybe not able to restore at all (due to lack of proper guidance how to proceed) just because they did a BM backup and then installed powerkernel or uBoot. I think it should be rather easy for BM to test for and catch those problem cases, and even offer proper guidance:
Code:
PROBLEM during RESTORE detected: Your system has kernel foo but backup has kernel modules for bar, which will most likely conflict and render your system unbootable! Do you want to a) exclude the bar components from restore (may or may not work) b) abort the restore and replace your foo kernel by bar manually, then restart the restore (recommended) c) ignore the conflict and restore anyway, probably risking a bootloop? (you should know exactly what you're doing to choose this option)
Many thanks for what's undoubtly the most useful and important app on fremantle ever :-)
cheers
jOERG
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
| The Following 14 Users Say Thank You to joerg_rw For This Useful Post: | ||
|
|
2013-07-04
, 11:52
|
|
Posts: 10 |
Thanked: 4 times |
Joined on Apr 2011
|
#1243
|
Originally Posted by joerg_rw
To me this sounds like a good idea. Hopefully it's doable.
Hi RobbieThe1st,
I wondered if it's high time to implement a logic into BM restore that checks kernel in /dev/mtd3 against any kernel modules in a backup about to get restored, and WARNS resp offers an option to not restore kernel modules if they don't match.
(Just restored backup with wrong kernel version. Reflashed and now in the process of restoring again..)
:-]
|
|
2013-07-04
, 13:12
|
|
Posts: 502 |
Thanked: 366 times |
Joined on Jun 2010
@ /dev/null
|
#1244
|
Originally Posted by joerg_rw
I completely agree this is a good idea, many of us were not initially aware of the fact that power kernel (let alone nokia kernel) would not get reflashed as a result of using backupmenu to restore original state hence resulting in indefinite bootloops.
Hi RobbieThe1st,
I wondered if it's high time to implement a logic into BM restore that checks kernel in /dev/mtd3 against any kernel modules in a backup about to get restored, and WARNS resp offers an option to not restore kernel modules if they don't match.
... (truncated)
The idea stated by jOERG is far more easier (in my opinion) to implement compared to making backupmenu somehow flashing whatever the kernel the user has setup the device in. Although by then most users would be stuck high and dry should they see the warning message when hoping to resort to a simple restore operation.
__________________
- IRC handle: psycho_oreos
- 3 x Nokia N900 | 2 x 32GB TopRAM microSDHC class 10 inserted in two devices | 2 x SIM cards inserted in two devices.
- N900/ Nokia N900 is not a phone/smartphone! its an internet tablet with phone functionality - so quit assuming its still a phone/smartphone when it isn't!!
- Help fight spam together!
- WANTED: Token/Karma system staff
|
|
2013-07-19
, 09:54
|
|
Posts: 6 |
Thanked: 3 times |
Joined on Jul 2013
@ Italy
|
#1245
|
Hi everyone, when I try to do a backup it stops on Chrooting.. and nothing more appears. What can I do?
 |
|
2013-07-19
, 14:44
|
|
Posts: 209 |
Thanked: 156 times |
Joined on Jun 2012
|
#1246
|
Look here.
__________________
History: Nokia 9000; Nokia 9110i; Nokia 9210, Nokia E90 / Currently: Nokia N900 (3x)
History: Nokia 9000; Nokia 9110i; Nokia 9210, Nokia E90 / Currently: Nokia N900 (3x)
| The Following User Says Thank You to Acurus_ For This Useful Post: | ||
|
|
2013-07-19
, 15:16
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#1247
|
Originally Posted by RobbieThe1st
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
Originally Posted by ade
Guys, are you going to fix this and push new version to Extras-Devel?
I added the file I suggested (the way you described it), and ... backupmenu is working again.
So there is no reason not to push a new version in the repo with "cp /lib/libpopt.so.0 /tmp/disk/lib/" added in filelist.txt.
|
|
2013-07-19
, 17:12
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#1248
|
Originally Posted by pali
Too bad RobbieThe1st does not upload an update. I only did some research on why was not working anymore. I don't even use backupmenu on my primary device
Guys, are you going to fix this and push new version to Extras-Devel?
But updating the package is an easy step, so I could try to upload a new version.
Code:
backupmenu (1.2.0-2) stable; urgency=low Added libpopt.so.0, removed vi swapfile .functions.sh.swp
Last edited by ade; 2013-07-20 at 18:39.
| The Following 8 Users Say Thank You to ade For This Useful Post: | ||
|
|
2013-07-19
, 17:23
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#1249
|
@ade: thanks very much. After package will be updated in extras-devel then new initrd-progs can be ready for next cssu-testing.
| The Following 3 Users Say Thank You to pali For This Useful Post: | ||
 |
| Tags |
| backup, backupmenu, cssusupplement, max(useful), rescue-console, restore, system |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 02:04.
is the problem with initrd-progs solved?
maybe a new package?