blob: ee1df65e480919b16415c52a3ae2431b75657407 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
--- INSTALL.orig 2004-04-21 01:18:46.000000000 -0400
+++ INSTALL 2004-04-21 01:20:09.000000000 -0400
@@ -8,11 +8,11 @@ possible to use the original Cobalt boot
loader - chain mode. This does away with the risk of trashing your unit,
though it extends the time required to boot.
-Just copy 'chain.bin' to your boot directory, rename into 'vmlinux' and gzip
+Just copy 'colo-chain.elf' to your boot directory, rename into 'vmlinux' and gzip
it to 'vmlinux.gz'
cp -f /boot/vmlinux.gz /boot/backup.gz
- cp chain.bin /boot/vmlinux
+ cp colo-chain.elf /boot/vmlinux
gzip -9 /boot/vmlinux
reboot
@@ -82,7 +82,7 @@ Step 4 - install the new boot loader
Write the new boot loader into the Flash. Don't interrupt the programming
process or you will probably land up with a unit that doesn't boot!
- flash-tool -w boot.bin
+ flash-tool -w colo-rom-image.bin
If for any reason programming fails you might just be able to write the
original boot loader back into the Flash
--- README.shell.orig 2004-04-21 01:23:51.000000000 -0400
+++ README.shell 2004-04-21 01:24:02.000000000 -0400
@@ -11,7 +11,7 @@ If no SPACE character is detected the bo
using the default script :-
mount
- -script /boot/default.boot
+ -script /boot/default.colo
load /boot/vmlinux.gz
execute
|
GitWeb
