[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[manual][patch] Install report for sparc64 with kernel 2.6 via netboot (failed)

On Mon, Sep 20, 2004 at 08:40:42PM +0200, J? Fahlke wrote:
> Package: installation-reports
> Debian-installer-version: 19-Sep-2004 20:39
> 	http://people.debian.org/~joshk/d-i/images/daily/sparc64/netboot/2.6/boot.img
> uname -a: Linux (none) 2.6.8-1-sparc64 #1 Sat Aug 28 04:28:53 PDT 2004
> 	sparc64 unknown
> Date: Mon Sep 20 19:57:37 CEST 2004
> Method: Booted from network via DHCP and TFTP.  DHCP and TFTP server
> 	were only a hub away.  Command lines at PROM prompt were
> 	  a) boot net:bootp
> 	  b) boot net:bootp debconf/frontend=newt
> 	  c) boot net:bootp hurz debconf/frontend=newt
> 	  d) boot net:bootp debconf/frontend=text
> Machine: Sun Ultra 1 SBus (UltraSPARC 143MHz)
> Processor: TI UltraSPARC I (SpitFire)
> Memory: 256MB
> Comments/Problems:
> First, the installation manual talks about "boot net:dhcp", but my
> machine tries to boot via ARP if I use that.  Please mention "boot
> net:bootp" as an alternative.

Attached patch does that.

Geert Stappers
Index: doc/manual/en/boot-installer/sparc.xml
--- doc/manual/en/boot-installer/sparc.xml	(revision 21886)
+++ doc/manual/en/boot-installer/sparc.xml	(working copy)
@@ -23,10 +23,11 @@
 machine which is being installed (see 
 <xref linkend="invoking-openboot"/>).
 Use the command <userinput>boot net</userinput> to boot from a TFTP
-and RARP server, or <userinput>boot net:dhcp</userinput> to boot from
-a TFTP and DHCP server. Some older OpenBoot revisions require using
+and RARP server, or <userinput>boot net:bootp</userinput> to boot from
+a TFTP and BOOTP server, or <userinput>boot net:dhcp</userinput> to boot from
+a TFTP and DHCP server, Some older OpenBoot revisions require using
 the device name, such as <userinput>boot le()</userinput>; these
-probably don't support DHCP.
+probably don't support BOOTP nor DHCP.

Attachment: pgpiWhmXp_eCl.pgp
Description: PGP signature

Reply to: