Active Topics

 



Notices


Reply
Thread Tools
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#1101
It was proposed many times ago, and it's not straightforward - indeed would need scavenging flashing code from multiboot.
---

In the meantime - I've introduced .lzma compression instead of .gz one, for backup with compression. Results are much better - rootfs compressed image is about 60 MB, in my case. I've also updated charging script to more recent version.

Updated version sent to robbiethe1st already, so I hope we may expect some kind of update soon We've also discussed possibility of using Pali's bq2415x_charger module for charging, (instead of charge.sh script) for kernel-power users, and depending on i2c-tools, instead of providing i2cget and i2cset as separate binariers, with backupmenu.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 4 Users Say Thank You to Estel For This Useful Post:
Posts: 362 | Thanked: 426 times | Joined on Nov 2010 @ Italy, Lombardia
#1102
Originally Posted by Estel View Post
It was proposed many times ago, and it's not straightforward - indeed would need scavenging flashing code from multiboot.
On Multiboot's package there is a script for flashing the kernel that can be used standalone.
The code of this script is simple and it is:
Code:
#!/bin/sh

export PATH=/usr/sbin:/usr/bin:/sbin:/bin

initctl stop softupd

ifconfig lo 127.0.0.1 netmask 255.0.0.0 up

softupd --local --verbose --stdout --standalone &
pid=$!

flasher --local -f -k $1

sleep 1
kill $pid

echo "Finished flashing."
Strangely multiboot main script does not use this script but the code are embedded on main script too.

I suppose that if N900 was booted (i.e. by u-boot) from an initrd (so Maemo's nand and eMMC are not mounted) it would be possible to flash a full fiasco image (like a flash from usb by pc) and not only a kernel.

Last edited by Fabry; 2012-08-04 at 16:14.
 

The Following 5 Users Say Thank You to Fabry For This Useful Post:
Posts: 45 | Thanked: 5 times | Joined on Oct 2008
#1103
Originally Posted by mrsellout View Post
You could:
Download the right package from
http://maemo.org/packages/view/kernel-power/
(match the backup dates with those on the kernel)

Extract the kernel.

Restore rootfs & optfs then shutdown.

Then use Flasher to flash the kernel only.
The most promising way I tried so far was the following. The 'zimage' FIASCO kernel image I grabbed from the webpage suggested and extracted it using the archive-manager

Code:
sudo flasher-3.5 -F zImage-2.6.28.10-power50.fiasco --flash-only=kernel -f -R
This resulted in
flasher v2.5.2 (Oct 21 2009)

Image 'kernel', size 1741 kB
Version 2.6.28.10-power50
Suitable USB device not found, waiting.
USB device found found at bus 002, device address 008.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_21.2011.38-1.002_PR_002
Sending kernel image (1741 kB)...
100% (1741 of 1741 kB, avg. 27216 kB/s)
Flashing kernel... done.
However, when I try booting all system bitmaps are missing - instead everything onscreen is replaced with a '[]' square character

Since matters were totally messed up by that point, I tried a variation on flash to stock...

Code:
sudo flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R

sudo flasher-3.5 -F RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin -f -R

sudo flasher-3.5 -F zImage-2.6.28.10-power50.fiasco --flash-only=kernel -f -R
to try and get a working barebones system with the power50 kernel but no dice ... boot loop

What am I missing? Thx
 
Posts: 32 | Thanked: 30 times | Joined on Jul 2012 @ Deb & Ian's dooryard
#1104
As far as I understand it by installing KP with apt-get, first it downloads the kernel plus flasher and then flashes it directly inside Maemo.

Wouldn't this produce the same result what you try to achieve by flashing to stock and then the kernel only?

Last edited by conred; 2012-08-07 at 17:39.
 

The Following User Says Thank You to conred For This Useful Post:
Posts: 45 | Thanked: 5 times | Joined on Oct 2008
#1105
Originally Posted by conred View Post
As far as I understand it by installing KP with apt-get, first it downloads the kernel plus flasher and then flashes it directly inside Maemo.

Wouldn't this produce the same result what you try to achieve by flashing to stock and then the kernel only?
I think you can get power51r1 that way, but don't see a full list of previous versions (I need power50) in the repos unfortunately...
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#1106
Specify the version of the kernel-power, kernel-power-modules and kernel-power-flasher on the command line.
You could search for all the versions in your repositories
Code:
apt-cache policy kernel-power kernel-power-modules kernel-power-flasher
The output may look like this (color just done to pick the version string):
Nokia-N900:~# apt-cache policy kernel-power
kernel-power:
Installed: 1:2.6.28-10power51r1
Candidate: 1:2.6.28-10power51r1
Version table:
*** 1:2.6.28-10power51r1 0
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle/free Packages
500 http://repository.maemo.org fremantle/free Packages
100 /var/lib/dpkg/status
1:2.6.28-10power51 0
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle/free Packages
1:2.6.28-10power50 0
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle/free Packages
500 http://repository.maemo.org fremantle/free Packages
1:2.6.28-10power49 0
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle-1.3/free Packages
500 http://repository.maemo.org fremantle/free Packages
500 http://repository.maemo.org fremantle/free Packages
2.6.28-maemo42 0
500 http://repository.maemo.org fremantle-1.3/free Packages
2.6.28-maemo37 0
500 http://repository.maemo.org fremantle-1.3/free Packages
2.6.28-maemo24 0
500 http://repository.maemo.org fremantle-1.3/free Packages
Then install the packages you want
Code:
sudo gainroot
apt-get install kernel-power=2.6.28-10power50 kernel-power-flasher=2.6.28-10power50 kernel-power-modules=2.6.28-10power50
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Posts: 45 | Thanked: 5 times | Joined on Oct 2008
#1107
Originally Posted by michaaa62 View Post
Code:
apt-get install kernel-power=2.6.28-10power50 kernel-power-flasher=2.6.28-10power50 kernel-power-modules=2.6.28-10power50
It turned out to be

Code:
sudo apt-get install kernel-power=1:2.6.28-10power50 kernel-power-flasher=1:2.6.28-10power50 kernel-power-modules=1:2.6.28-10power50
but that worked like a charm. So for anyone else struggling with this and with a backup from somewhere between April and July that needs to clear their NVRAMs and get the phone back up (I'm afraid I may have a somewhat dodgy memory chip as well) or more generally, if you need to match up your backup with a corresponding kernel-power kernel, here's the (detail-free but succinct) pattern that worked for me , just read back in this thread a bit and substitute the kp version you require.

0. Have a backup-menu backup saved on your desktop
1. Reflash EMMC/FIASCO combined images, boot phone.
2. Add maemo-extras, maemo-extras-testing, maemo-extras-devel repositories back in
3. Allow update to 1.3
4. Install bash3, sudser.
5. Run the kernel-power command (see above) to install the next-to most recent kernel power kernel image
6. Reboot phone, put your backup images in ~/MyDocs/systemBackups/
7. Install backupmenu
8. Reboot into the backup menu (keyboard open) and restore your backup... huzzah! it works, no bootloop like if you have a mismatched kernel

Thanks for the help, you folks are the Maemo gods
 
Posts: 12 | Thanked: 12 times | Joined on Jan 2011
#1108
Originally Posted by ivyking View Post
I have gotten backupmenu to start from u-boot without needing r&d mode nor repartitioning and without complex instructions this time..

so forget the complex instructions at
http://talk.maemo.org/showpost.php?p...&postcount=882

new instructions:
download the zip archive from http://ifile.it/d3ehfn2 (5.8 MB)
extract the contents of the archive to the first partition of your sdcard (fat32).
shutdown, then start again and let u-boot timer time out.

thats all !
can't get any easier

---------------------------------------------------------------------------

notes (normally not needed):

1)backupmenu disk gets loaded as an initrd and backupmenu runs from the ram, so configuring network interfaces by modifying backupmenu directly is not possible.(well it is possible but it won't be saved when you reboot)
instead place a file called interfaces, containing your network configuration on the first partition of the sdcard, backupmenu will use that instead.

2)if you already have a boot.scr file on the first partition of your sdcard, rename the one from the archive to backupmenu.scr
u-boot will normally load your original boot.scr file, and when you want to run backupmenu, there are 2 solutions:

a)sane solution:
rename your boot.scr to something else and rename backupmenu.scr to boot.scr and start the device.

b)crazy solution:
interrupt the u-boot timer and write the following :

Code:
mmc init
fatload mmc1 0 0x80000400 backupmenu.scr
source 0x80000400
you will have to type that blazingly fast though if you haven't enabled r&d mode and set no-omap-wd r&d flag.
Unable to download. The file unavailable. Could you pls seed it again.
 
Posts: 1,335 | Thanked: 3,931 times | Joined on Jul 2010 @ Brittany, France
#1109
Please excuse me because I bet you've been asked that a billion times already, but I read somewhere that you got your hands on a N950 last year Robbie. Water under the bridge since then so I just wanted to know what we may expect/hope now. For a long time, I thought you wouldn't work on a port ever as you did not receive a N950 from Nokia (and it was quite disappointing to be honest considering that your app is probably the one app that every N900 user should have, I don't see any other app that could be as useful to as many people), but reading that you finally got one made me recover some hope. Have you been trying to port BackupMenu to the N950 (and then the N9)? If so, any progress to report, a roadmap or something?

Sorry again if you've been answering to that question somewhere, but I couldn't find any mention of that in your lasts posts. Either way, would you be working on a port or would you have decided not to port it (or found it impossible to port), a short mention in the first post to make it clear what is going on on that matter could be nice. It would make questions like mine rarer too!

Thanks in advance for you reply, keep up the great work.
 
Posts: 10 | Thanked: 0 times | Joined on Jun 2012
#1110
Originally Posted by ivyking View Post
I have gotten backupmenu to start from u-boot without needing r&d mode nor repartitioning and without complex instructions this time..

so forget the complex instructions at
http://talk.maemo.org/showpost.php?p...&postcount=882

new instructions:
download the zip archive from http://ifile.it/d3ehfn2 (5.8 MB)
extract the contents of the archive to the first partition of your sdcard (fat32).
shutdown, then start again and let u-boot timer time out.

thats all !
can't get any easier

---------------------------------------------------------------------------

notes (normally not needed):

1)backupmenu disk gets loaded as an initrd and backupmenu runs from the ram, so configuring network interfaces by modifying backupmenu directly is not possible.(well it is possible but it won't be saved when you reboot)
instead place a file called interfaces, containing your network configuration on the first partition of the sdcard, backupmenu will use that instead.

2)if you already have a boot.scr file on the first partition of your sdcard, rename the one from the archive to backupmenu.scr
u-boot will normally load your original boot.scr file, and when you want to run backupmenu, there are 2 solutions:

a)sane solution:
rename your boot.scr to something else and rename backupmenu.scr to boot.scr and start the device.

b)crazy solution:
interrupt the u-boot timer and write the following :

Code:
mmc init
fatload mmc1 0 0x80000400 backupmenu.scr
source 0x80000400
you will have to type that blazingly fast though if you haven't enabled r&d mode and set no-omap-wd r&d flag.
I can not download the file. Can anybody upload it again ? Or send me to e-mail ? thx in advance
 
Reply

Tags
backup, backupmenu, cssusupplement, max(useful), rescue-console, restore, system


 
Forum Jump


All times are GMT. The time now is 21:25.