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

Bug#266727: [sparc64] [rc1] [netboot] No problems.



Package: installation-reports

INSTALL REPORT

Debian-installer-version: d-i rc1
(http://http.us.debian.org/debian/dists/testing/main/installer-sparc/rc1/images/sparc64/netboot/boot.img, 02-Aug-2004)
uname -a: Linux ultra 2.4.26-sparc64 #1 Sun Jun 20 02:39:17 PDT 2004 sparc64 GNU/Linux
Date: 17-Aug-2004
Method: Netboot, using rarpd to serve IP, atftpd to serve image, dhcp for
network configuration, package install via net/apt-proxy

Machine: SUN Ultra1/Creator
Processor: TI UltraSparc I   (SpitFire) sun4u
Memory: 382136 kB
Root Device: SCSI, /dev/sda1
Root Size/partition table:

Disk /dev/sda (Sun disk label): 14 heads, 72 sectors, 2036 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
   /dev/sda1             0      1872    943488    1  Boot
   /dev/sda2          1872      2036     82656   82  Linux swap
   /dev/sda3             0      2036   1026144    5  Whole disk
   
Output of lspci and lspci -n: no PCI, only SBus

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:

Using the simple (non-expert modus) install, this works like a breeze, no
problems.

Some comments on the installation manual for sparc: 

In "4.4. Preparing Files for TFTP Net Booting" it says that you can use either
of RARP, BOOTP or DHCP for net booting. On this machine, I had to setup rarpd
_and_ dhcpd, rarpd for giving the machine an IP, which is then used to retrieve
the netboot image via tftp. It uses the IP in hex format as the image name, not
IP_in_hex.SUN4M as the text suggests. d-i then uses dhcp to retrieve the
network information.

And in the dhcp setup example, there is the line

filename "/tftpboot/tftpboot.img";

This should read 

filename "/tftpboot.img";

since tftpd serves only from the tftboot directory anyway (whatever it is named).



Reply to: