Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 14 hrs, 24 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 10 hrs ago - more...
| The Following User Says Thank You to Fabry For This Useful Post: | ||
|
2011-01-04
, 06:51
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#472
|
Let me put in just a couple of notes here:
1. While I appreciate people thinking about using Multiboot and working to make it compatible, Multiboot is somewhat depreciated, and shouldn't be used - It overwrites the kernel partition each time you switch your boot OS!
Remember that the kernel partition is on a raw flash device with -no- block-leveling; if one block goes bad, your whole N900 could die.
uBoot is the replacement, and it simply chainloads a new kernel off whatever partition you want, resulting in -no- extra writes to the kernel partition. It's a far better system and anyone thinking about dual-boot should be using it.
(Note that BootMenu should be compatible with uBoot, though building a BackupMenu module for uBoot(and a boot-menu) would be nice).
2. Manual BackupMenu install would require:
A. Extract "data.tar.gz" from the .deb file(as root). "tar pzvf ./data.tar.gz -C /" IIRC
B. Extract the contents of "data.tar.gz" to '/'. All paths should work out fine.
C. Run these two lines as root:
Everything should run after that.
1. While I appreciate people thinking about using Multiboot and working to make it compatible, Multiboot is somewhat depreciated, and shouldn't be used - It overwrites the kernel partition each time you switch your boot OS!
Remember that the kernel partition is on a raw flash device with -no- block-leveling; if one block goes bad, your whole N900 could die.
uBoot is the replacement, and it simply chainloads a new kernel off whatever partition you want, resulting in -no- extra writes to the kernel partition. It's a far better system and anyone thinking about dual-boot should be using it.
(Note that BootMenu should be compatible with uBoot, though building a BackupMenu module for uBoot(and a boot-menu) would be nice).
2. Manual BackupMenu install would require:
A. Extract "data.tar.gz" from the .deb file(as root). "tar pzvf ./data.tar.gz -C /" IIRC
B. Extract the contents of "data.tar.gz" to '/'. All paths should work out fine.
C. Run these two lines as root:
Code:
cp /opt/maemo/usr/bin/gnu/tar /usr/share/backupmenu/ chmod +x /usr/share/backupmenu/*
__________________
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520
| The Following 3 Users Say Thank You to RobbieThe1st For This Useful Post: | ||
|
|
2011-01-04
, 06:54
|
|
Posts: 309 |
Thanked: 115 times |
Joined on May 2010
@ Malaysia
|
#473
|
Originally Posted by Fabry
erm..sorry for sounding stupid, but would you please be a bit more specific on how to do it?
I suppose that this can be resolved at least in two ways:
- Install manually backupmenu without using dpkg. This can be done extracting scripts (2 files) from deb archive and copying them to /usr/share/backupmenu
- Modify backupmenu deb archive and remove dependency from BootMenu. Then reinstall (dpkg) deb archive
i've downloaded the file,extracted it..inside the folder, there's a file called data.tar..
again i extracted the data.tar, and inside, there are 2 files, named "etc" and "usr"..
now what should i do sir?
EDITED : WOOPSSS...LATE BY 3MINUTES..SORRY =)
Last edited by one1002; 2011-01-04 at 07:18.
|
|
2011-01-04
, 07:26
|
|
Posts: 309 |
Thanked: 115 times |
Joined on May 2010
@ Malaysia
|
#474
|
Originally Posted by RobbieThe1st
Let me put in just a couple of notes here:
1. While I appreciate people thinking about using Multiboot and working to make it compatible, Multiboot is somewhat depreciated, and shouldn't be used - It overwrites the kernel partition each time you switch your boot OS!
Remember that the kernel partition is on a raw flash device with -no- block-leveling; if one block goes bad, your whole N900 could die.
uBoot is the replacement, and it simply chainloads a new kernel off whatever partition you want, resulting in -no- extra writes to the kernel partition. It's a far better system and anyone thinking about dual-boot should be using it.
(Note that BootMenu should be compatible with uBoot, though building a BackupMenu module for uBoot(and a boot-menu) would be nice).
2. Manual BackupMenu install would require:
A. Extract "data.tar.gz" from the .deb file(as root). "tar pzvf ./data.tar.gz -C /" IIRC
B. Extract the contents of "data.tar.gz" to '/'. All paths should work out fine.
C. Run these two lines as root:
Everything should run after that.Code:cp /opt/maemo/usr/bin/gnu/tar /usr/share/backupmenu/ chmod +x /usr/share/backupmenu/*
thank you sir..however, not many people using uboot because of the not-so-user-friendly..getting kernel to load via uboot isn't as simple as multiboot where you create the boot item..
i guess it's because most of the users are booting maemo-nitdroid..as far as i read, there are still no uboot solutions for booting nitdroid..? correct me on this if i'm wrong..
that is why people opt for multiboot..uboot isn't integrated yet for booting multiple OSes right?AFAIK, meego has the compatibility using uboot..but not nitdroid,ubuntu or any other OSes..
sorry if i'm wrong..please enlighten me sir
|
|
2011-01-04
, 10:01
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#475
|
Actually, I think figuring out how to load from multiboot (install bootimg, write item) is just as easy as figuring out how to do it from uboot. Both require a similarly limited and basic set of instructions, HOWEVER, I don't think as simple of an instruction set exists. When I've finished my current project(s) (write localization for Russian for Sleep Analyzer; create my custom clock plugin for Advanced Clock Plugin; try to become useful at python enough to write patches for, and support, Advanced Power, Advanced Power Monitor, and Advanced Interface Switcher), I will do my best to write up such guides, and provide easy-to-use .debs for each OS (NITDroid and MeeGo), as well as see if I can figure out RobbieThe1st's backupmenu and uboot enough to figure out how to make a uboot-only version.
This does not mean get your hopes up - but it does mean that if no one else gets it done reasonably soon, I will make a sincere effort to do so.
RobbieThe1st: Sorry I kinda dropped out from this thread from back before you even implemented SSH in BackupMenu. I greatly appreciate your work, even if I personally haven't used it yet. I've just been busy. But I will be catching up on this thread relatively soon. Really glad to see your latest post being pro-uboot and showing support for a uboot port.
One1002: UBoot supports any OS, pretty much. Literally, just about any OS you can think of, if it can load on the N900, uboot can load it, from MMC, from SD card, from rootfs, over SSH through USB or something, just about anywhere. The only thing is it's not built from the ground up to be user friendly, so selection isn't AS simple as using the arrow keys to select a different OS. Also, you need mkimage if you want to take a not-yet-made-for-uboot kernel image, and convert it from a zImage to a uImage. However, I just took the mkimage binary from the Debian Lenny packages for armel architecture, stuck it on the N900 at /sbin/ and it works just fine.
Speaking of which, RobbieThe1st, any chance you can include the fiasco-flasher (admittedly a Nokia binary, only distributed in the PR1.0 kernel, and not really free to distribute - may need to file a request or bug report for that), the regular on-board-the-N900 'flasher', and mkimage within the backupmenu? This would let people reflash kernels and/or make them from within backupmenu if they'd like, saving the need to use a computer for N900 revival even if the N900 won't load to any of the kernels.
Last edited by Mentalist Traceur; 2011-01-04 at 10:07. Reason: Forgot to reply to one1002
This does not mean get your hopes up - but it does mean that if no one else gets it done reasonably soon, I will make a sincere effort to do so.
RobbieThe1st: Sorry I kinda dropped out from this thread from back before you even implemented SSH in BackupMenu. I greatly appreciate your work, even if I personally haven't used it yet. I've just been busy. But I will be catching up on this thread relatively soon. Really glad to see your latest post being pro-uboot and showing support for a uboot port.
One1002: UBoot supports any OS, pretty much. Literally, just about any OS you can think of, if it can load on the N900, uboot can load it, from MMC, from SD card, from rootfs, over SSH through USB or something, just about anywhere. The only thing is it's not built from the ground up to be user friendly, so selection isn't AS simple as using the arrow keys to select a different OS. Also, you need mkimage if you want to take a not-yet-made-for-uboot kernel image, and convert it from a zImage to a uImage. However, I just took the mkimage binary from the Debian Lenny packages for armel architecture, stuck it on the N900 at /sbin/ and it works just fine.
Speaking of which, RobbieThe1st, any chance you can include the fiasco-flasher (admittedly a Nokia binary, only distributed in the PR1.0 kernel, and not really free to distribute - may need to file a request or bug report for that), the regular on-board-the-N900 'flasher', and mkimage within the backupmenu? This would let people reflash kernels and/or make them from within backupmenu if they'd like, saving the need to use a computer for N900 revival even if the N900 won't load to any of the kernels.
Last edited by Mentalist Traceur; 2011-01-04 at 10:07. Reason: Forgot to reply to one1002
| The Following 2 Users Say Thank You to Mentalist Traceur For This Useful Post: | ||
|
|
2011-01-04
, 10:09
|
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#476
|
I'm willing to do whatever I can to help out - I'm just not the most experienced when it comes to some of the boot stuff.
Also, my n900's currently down - My cracked screen died a couple of days ago, and I'm still waiting for a replacement from Hong Kong, so...
(Replacement itself won't be an issue, I got my n900 apart without issue - it's a -well- designed machine!)
Also, my n900's currently down - My cracked screen died a couple of days ago, and I'm still waiting for a replacement from Hong Kong, so...
(Replacement itself won't be an issue, I got my n900 apart without issue - it's a -well- designed machine!)
__________________
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520
My projects: BackupMenu - OS Backup & restore | Video: Flashing your n900(LiveCD)
My devices: N770 + 8GB SD card soldered internally, N900 with 8GB SD card + Custom OC(125-950 typically).
OC freqs: 0:22,90 125:22,90 250:28,180 500:30,360 550:32,400 600:34,430 700:39,430 750:41,430 805:45,430 850:47,500 900:50,500 950:54,500 1000:58,500 1100:67,520 1150:71,520
| The Following User Says Thank You to RobbieThe1st For This Useful Post: | ||
|
|
2011-01-04
, 11:51
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#477
|
Just thought I'd point out: You double posted. Also, from all you've managed to do with backupmenu, I'd say you're more experienced when it comes to the boot stuff than I am currently, lol.
| The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
|
|
2011-01-04
, 12:22
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#478
|
Originally Posted by RobbieThe1st
I hate kernel reflash too, but learning from multiboot's sources I have found out that it can operate in other ways too
Let me put in just a couple of notes here:
1. While I appreciate people thinking about using Multiboot and working to make it compatible, Multiboot is somewhat depreciated, and shouldn't be used - It overwrites the kernel partition each time you switch your boot OS!
Remember that the kernel partition is on a raw flash device with -no- block-leveling; if one block goes bad, your whole N900 could die.
uBoot is the replacement, and it simply chainloads a new kernel off whatever partition you want, resulting in -no- extra writes to the kernel partition. It's a far better system and anyone thinking about dual-boot should be using it.
(Note that BootMenu should be compatible with uBoot, though building a BackupMenu module for uBoot(and a boot-menu) would be nice).
For example multiboot contains code for using kexec (but this code isn't active) and the new script functionallity can be used to change u-boot default script (i.e. multiboot change u-boot script and then reboot, at reboot u-boot load the correct os, all without a single reflash)
I am working on initrd for Backupmenu and Nitdroid, but unfortunately I have low time to dedicate and so I have slow progress for now
With an initrd you can boot with
- u-boot
- Kernel + initrd loaded (not flashed) by flasher-3.5
- kexec (probably not sure)
Last edited by Fabry; 2011-01-04 at 14:08.
| The Following User Says Thank You to Fabry For This Useful Post: | ||
|
|
2011-01-04
, 13:05
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#479
|
Yes, with Multiboot you can have it run a script to change the uboot load script instead, but I feel it's just more round-about that it has to be. Though I'd be happy for that being available as a package. I'd work on a u-boot only solution, but I can understand that most would gravitate towards a UI-only approach, and being able to type a command is a lot less convenient than up/down arrow key-ing, even if the command to be typed is written on the uboot screen (like "run noloboot" is now).
|
|
2011-01-04
, 14:06
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#480
|
Originally Posted by Mentalist Traceur
The main problem is that with u-boot is not simple (but still possible) to make an interactive bootmenu
Yes, with Multiboot you can have it run a script to change the uboot load script instead, but I feel it's just more round-about that it has to be. Though I'd be happy for that being available as a package. I'd work on a u-boot only solution, but I can understand that most would gravitate towards a UI-only approach, and being able to type a command is a lot less convenient than up/down arrow key-ing, even if the command to be typed is written on the uboot screen (like "run noloboot" is now).
It can execute a script, but what commands are available on a u-boot's session?
And I doubt that it can run external program like evkey and text2screen which now are used on BootMenu/Multiboot scripts
Last edited by Fabry; 2011-01-04 at 14:43.
 |
| Tags |
| backup, backupmenu, cssusupplement, max(useful), rescue-console, restore, system |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 15:55.
Last edited by Fabry; 2011-01-03 at 18:05.