dumb question of the day

Hi everyone,

I have a 715/64 that I'm trying to boot across the network.

I grabbed the latest base tar ball from the ftp server and uncompressed it.

I grabbed rboot and set it up and didn't work, so I have set bootps and tftp according to the howto at http://www.oswg.org/oswg-
nightly/oswg/en_US.ISO_8859-1/articles/parisc-linux/parisc-linux- boot.html (very helpful too I might add)

from boot_admin I boot lan, I have tcpdump listening on eth1 where the hppa box is connected via aui/TP and UTP cross over. I can see the broadcast and /var/log/messages shows that tftp is looking for iplboot, as copied from the tar ball boot dir.

The hp box fails with an error on the console (I have a vga screen on the box):

"ERROR: Cannot load IPL, error detected."

Since this is my first time with nfsbooting it's likely I'm not doing something right there, ie, I don't have /etc/exports setup.. should I od this?

Please, some short pointers for a dummy.. :) I _so_ want to IRC on this box!! :)

Thanks.

Pete.

...

Yes. But you also need a *lifimage*.

I don't think matching lifimage's (matching the baseplus /boot/vmlinux) where posted to the ftp site. I've posted a NFSROOT enabled lifimage for a 32-bit/serial console (not STI enabled):

	ftp://puffin.external.hp.com/pub/parisc/binaries/lifimages/lifimage_32_serial_20010418.gz

Matching Systemp.map and vmlinux are in ../kernels directory.

For the 715's, append 'y' to the "boot lan y" in order to interactively change the nfsroot= param (IP needs to point to the NFS server). I don't recall if you need a different vmlinux embedded in the LIF or if you can interactively tweak the palo boot params to use STI console instead of serial.

grant

Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253

Hi,

hmm, very nice indeed.

Did you do a 'search' to get the correct lan boot path and then add it with eg. path lan 192.168.2.1.3?

iplboot is only the file with the information about the bootsignature - the bootloader (see below, its much too small for a Linux kernel), not the kernel. palo needs this file and your out of the box (read: eg. compiled) vmlinux to build a lifimage. That's the file you'll need as the bootable kernel.

I don't use the base tarball for netbooting just afterwards for the actual installation on harddisk. Instead of this tarball I use the tarball distributed via http://mkhppa1.esiee.fr/en/download.html
(fs_hd_20010320.tar.gz_global) for netbooting. But that's a historical issue, everything should also work with the base tarball ;-)

So I don't know anything about the kernel in the base tarball. I use a crosscompiler built from cvs to build a proper kernel capable of netbooting. IIRC you have to compile the following options into the kernel:

root-nfs support
bootp support

and of course the other appropriate network drivers and options.

After compiling you'll get a vmlinux. This file isn't bootable because a special bootsignature - the bootloader - is still lacking. To make the kernel net-bootable you have to use palo with the following option set in its Makefile:

NFSROOT = 192.168.2.1

(when 192.168.2.1 is the IP of the server that's providing the root-FS for your HP9000).

With your crosscompiler environment correctly setup its just a matter of 'make xconfig;make dep;make clean;make palo'

As a result I get a lifimage, rename it to vmlinux and then use this file for netbooting from /usr/tftpboot.

Yes, unless you want a nfsroot-boot without nfsroot ;-) And don't forget to modify the following files in the nfs-root tree on your nfs-server (apart from starting your nfs-server ;-):

/etc/inittab (as the files below its something like /usr/thisismyrootfs/etc/inittab)

make sure you really have a getty waiting for you. I had a problem with this once (possibly my own fault) but now I make sure each time.

/etc/fstab:

Insert the appropriate entry for your remote root-FS apart from a proc-entry, eg.

gandalf:/usr/tftpboot/boromir / nfs defaults 0 0

Here gandalf is my nfs-root server and /usr/tftpboot/boromir is the toplevel directory for the nfsroot tree of my 715/80 called boromir.

/etc/securetty:

Add

ttyp0
ttyp1
ttyp2
ttyp3
ttyp4
ttyp5
ttyp6
ttyp7
ttyp8

when you want to do a telnet to your HP9000 (and your nfs-root provides a telnet ;-). Some might consider this a security hole, but my machine is secured from the internet, so I don't care ;-)

/etc/hosts:

Enter the IP and name of your HP9000 and your nfs-root server, eg:

127.0.0.1       localhost
192.168.2.8     boromir.sigtrap.de boromir
192.168.2.1     gandalf.sigtrap.de gandalf

/etc/hostname:

Insert your hostname in this file.

/etc/resolv.conf:

Insert your nameserver in this file, eg:

domain sigtrap.de
search sigtrap.de
nameserver 192.168.2.1

And now for the most important file:

/etc/network/interfaces:

Her you have to configure eth0, eg:

iface eth0 inet static
address 192.168.2.8
network 192.168.2.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.2.1

iface lo inet loopback

Without our eth0 correctly set up and running you'll have problems to mount your nfs-root via /etc/fstab.

On the bootp-server (which is also my nfsroot-server) you have to configure /etc/bootptab, eg:

.global.prof:\
        :sm=255.255.255.0:\
	:ds=192.168.2.1:\
	:gw=192.168.2.1:\
	:sa=192.168.2.1:\
	:ht=ethernet:\
	:bf=vmlinux:

boromir:hd=/usr/tftpboot:rp=/usr/tftpboot/boromir:tc=.global.prof:hn:ha=ffffffffffff:ip=192.16 8.2.8:vm=rfc1048:

Insert your MAC-adress instead of ffffffffffff.

I hope that was all and I didn't mix up everything said ;-)

Perhaps the snippets of information can help you to get your machine up and running.

Regards,

Oliver

!- Oliver Flimm - Cologne/Germany | [email protected] | http://www.sigtrap.de/ -!
!    Die Zehn Gebote haben 279 Woerter, die amerikanische Unabhaengigkeits-    !
! erklaerung hat 300 Woerter. Die EU-Verordnung zur Einfuhr von Karamelbonbons !
!-----------------------------  hat 25911 Woerter  ----------------------------!