Update installation instructions

Apparently the ss4000e installer firmware image does not work. Since I
wrote the support on a borrowed machine, I cannot test any fixes.

Since the installer requires a manual serial console step anyway,
explain how to manually load the installer ramdisk and kernel in the
manual. It's a bit more involved than loading an image through a web
interface, but at least it will work.

1 files changed, 34 insertions, 35 deletions

diff --git a/en/boot-installer/arm.xml b/en/boot-installer/arm.xml
index b4463c15b..46f90a61d 100644
--- a/en/boot-installer/arm.xml
+++ b/en/boot-installer/arm.xml
@@ -138,17 +138,13 @@ serial ports.
 
 </para><para>
 
-To boot the SS4000-E, first load the Debian-provided firmware image
-(ss4000e.pkg) through the SS4000-E's web interface (go to
-<quote>administration</quote>, then to <quote>firmware</quote>, and
-upload the image). Next,
-use your serial nullmodem cable and the ribbon cable to connect to the
-serial port of the SS4000-E, and reboot the machine. You need to use a
-serial terminal application to communicate with the machine; a good
-option on a Debian GNU/Linux is to use the <command>cu</command>
-program, in the package of the same name. Assuming the serial port on
-your computer is to be found on <filename>/dev/ttyS0</filename>, use the
-following command line:
+To boot the SS4000-E, use your serial nullmodem cable and the ribbon
+cable to connect to the serial port of the SS4000-E, and reboot the
+machine. You need to use a serial terminal application to communicate
+with the machine; a good option on a Debian GNU/Linux is to use the
+<command>cu</command> program, in the package of the same name. Assuming
+the serial port on your computer is to be found on
+<filename>/dev/ttyS0</filename>, use the following command line:
 
 </para>
 
@@ -186,42 +182,45 @@ just powercycle the machine and try again.
 </para>
 
 </footnote>. This will give you the RedBoot prompt. Enter the
-following command:
+following commands:
 
 </para>
 
 <informalexample><screen>
-fconfig boot_script_data
+load -v -r -b 0x01800000 -m ymodem ramdisk.gz
+load -v -r -b 0x01008000 -m ymodem zImage
+exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
 </screen></informalexample>
 
-<para>
-
-RedBoot is now waiting for you to enter the boot script. Make sure to
-<emphasis>exactly</emphasis> enter the following script:
+<para>After every 'load' command, the system will expect a file to be
+transmitted using the YMODEM protocol. When using cu, make sure you have
+the package <quote>lrzsz</quote> installed, then hit enter, followed by
+the <quote>~&lt;</quote> escape sequence to start an external program,
+and run <command>sb initrd.gz</command> or <command>sb
+vmlinuz</command>.</para>
 
-</para>
+<para>Alternatively, it is possible to load the kernel and ramdisk using
+HTTP rather than YMODEM. This is faster, but requires a working HTTP
+server on the network. To do so, first swith the bootloader to RAM mode:
 
 <informalexample><screen>
-fis load ramdisk.gz
-fis load zImage
+fis load rammode
+g
+</screen></informalexample>
+<para>This will seemingly restart the machine; but in reality, it loads
+reboot to RAM and restarts it from there. Not doing this step will cause
+the system to hang in the necessary ip_address step that comes
+next.</para>
+<para>You will need to hit Ctrl-C again to interrupt the boot.
+Then:</para>
+<informalexample><screen>
+ip_address -l 192.168.2.249 -h 192.168.2.4
+load -v -r -b 0x01800000 -m http /initrd.gz
+load -v -r -b 0x01008000 -m http /zImage
 exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
 </screen></informalexample>
-
 <para>
-
-Finish the script with an empty line, and enter <quote>y</quote> at the
-prompt to update the non-volatile configuration. Finally, use
-<quote>reset</quote> to restart the system, and allow it to boot normally.
-The installer should now come up as normal. You can either install Debian
-through the serial port, or use an SSH client to connect through SSH.
-
-</para><para>
-
-Note that it is not necessary to update the boot script after the
-installation. The system will be configured to take the root device from
-system configuration, rather than from the kernel command line. It will
-not do any harm to do so anyway, however.
-
+The installer will now start as usual.
 </para>
    </sect3>
   </sect2>