Editing Booting from a flash card
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | This article covers the steps you need to follow to boot from a flash card | + | This article covers the steps you need to follow to boot from a flash card. The process is somewhat involved, so some familiarity with the command line is recommended. |
Advanced users may wish to read [[advanced booting]] as well, for more advanced booting-related configuration and setup information. | Advanced users may wish to read [[advanced booting]] as well, for more advanced booting-related configuration and setup information. | ||
== Why would we want to boot from a flash card? == | == Why would we want to boot from a flash card? == | ||
- | |||
* For more space to install applications. | * For more space to install applications. | ||
* An easy-to-use bootable backup. | * An easy-to-use bootable backup. | ||
Line 19: | Line 18: | ||
== Install the necessary tools == | == Install the necessary tools == | ||
- | First, we need to install wget, so open | + | First, we need to install wget, so open Xterm and, '''as root''', run: |
apt-get install wget | apt-get install wget | ||
Line 31: | Line 30: | ||
chmod +x nupgrade.sh tar | chmod +x nupgrade.sh tar | ||
- | Then, to install the proper filesystem tools, | + | Then, to install the proper filesystem tools, run: |
apt-get install e2fsprogs | apt-get install e2fsprogs | ||
- | |||
- | |||
- | |||
- | |||
- | |||
== Install bootmenu == | == Install bootmenu == | ||
Line 54: | Line 48: | ||
This is an optional step, but if you want to customize the bootmenu to properly reflect your partitioning setup, change the partition labels, and a number of other options, then you'll need to rename the appropriate <code>bootmenu.conf.''device''.example</code> file to <code>bootmenu.conf</code> and edit it to your liking. The README included with flasher and the comments in the configuration file should be enough to tell you what everything is. | This is an optional step, but if you want to customize the bootmenu to properly reflect your partitioning setup, change the partition labels, and a number of other options, then you'll need to rename the appropriate <code>bootmenu.conf.''device''.example</code> file to <code>bootmenu.conf</code> and edit it to your liking. The README included with flasher and the comments in the configuration file should be enough to tell you what everything is. | ||
- | The | + | The flasher will ask you if you want to include your bootmenu.conf file if you renamed it properly. |
=== Flash the initfs === | === Flash the initfs === | ||
- | cd /home/user/bin/initfs_flasher/ | + | cd /home/user/local/bin/initfs_flasher/ |
./initfs_flash | ./initfs_flash | ||
Line 70: | Line 64: | ||
To set the default to partition 2 on the internal card. If you would like to set the default to something else, the device is <code>mmc''#''</code> (where # is the partition number) for the internal card, and <code>mmc1''#''</code> for the external card. To set it back the default behavior of booting from the built-in flash, use <code>flash</code>. | To set the default to partition 2 on the internal card. If you would like to set the default to something else, the device is <code>mmc''#''</code> (where # is the partition number) for the internal card, and <code>mmc1''#''</code> for the external card. To set it back the default behavior of booting from the built-in flash, use <code>flash</code>. | ||
- | |||
- | |||
== Clone to the card == | == Clone to the card == | ||
- | + | <small>''Many thanks to [[User:Milhouse|milhouse]] for writing and maintaining this script.''</small> | |
- | <small>''Many thanks to milhouse for writing and maintaining this script.''</small> | + | |
Now it's time to clone your install over to partition 2 of the internal card. The script works in stages to allow better control and error detection, and should take about 10 minutes to complete: | Now it's time to clone your install over to partition 2 of the internal card. The script works in stages to allow better control and error detection, and should take about 10 minutes to complete: | ||
- | |||
* 0 - Create ext2 filesystem on partition 2 of the Internal memory card | * 0 - Create ext2 filesystem on partition 2 of the Internal memory card | ||
* 1 - Mount partition 2 as /opt | * 1 - Mount partition 2 as /opt | ||
Line 89: | Line 79: | ||
cd /home/user/bin | cd /home/user/bin | ||
./nupgrade.sh 0 | ./nupgrade.sh 0 | ||
- | |||
- | |||
- | |||
- | |||
./nupgrade.sh 1 | ./nupgrade.sh 1 | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
./nupgrade.sh 2 | ./nupgrade.sh 2 | ||
./nupgrade.sh 3 | ./nupgrade.sh 3 | ||
Line 109: | Line 89: | ||
== Remove the menu == | == Remove the menu == | ||
- | If you decide you do not wish to see the bootmenu any longer, you can uninstall it by either [[ | + | If you decide you do not wish to see the bootmenu any longer, you can uninstall it by either [[upgrading tablet OS|reflashing the whole OS image]], or just flashing the initfs (in Linux and OS X) by running: |
sudo ./flasher-3.0 -F <FIASCO image> --flash-only=initfs -R | sudo ./flasher-3.0 -F <FIASCO image> --flash-only=initfs -R | ||
- | == | + | == Advance booting == |
- | + | ||
For more advanced configuration and setup information for booting-related stuff, please see [[advanced booting]]. | For more advanced configuration and setup information for booting-related stuff, please see [[advanced booting]]. | ||
- | + | == Testing == | |
- | [[Category: | + | |
+ | Testing it in a 770... (results in a couple of hours...) | ||
+ | |||
+ | |||
+ | [[Category:Users]] |
Learn more about Contributing to the wiki.