Subject: Re: Netbooting 1.6_BETA3?
To: Gregory McGarry <g.mcgarry@ieee.org>
From: Sageev George <sageev@bmsrs.usc.edu>
List: port-hp300
Date: 07/02/2002 20:11:16
Hello Gregory and Bernd and others on this list:

Strangely, a few days before Bernd's posting, I had been
setting up my remote console to attempt an upgrade of
my 1.5.3RC1 system to whatever system was specified
in the 20020415-current snapshot, as per Gregory's
instructions.

Using the serial port console did allow me to see
the kernel booting, but I now get a different error
towards the end of this process. I'll just put the
error here, but I'll put the complete console output
at the end of this message.

    le0 at dio0 scode 21 ipl 5: address 08:00:09:15:ae:95
    le0: 8 receive buffers, 2 transmit buffers
    topcat0 at dio0 scode 133: 1280 x 1024 256 color hi-res catseye display
    grf0 at topcat0
    ite0 at grf0
    interrupt levels: bio = 4, net = 5, tty = 5
    hil0 device 1: US ASCII keyboard
    boot device: le0
    root on le0
    no file system for le0
    cannot mount root, error = 79
    root device (default le0):le0a
    dump device: sd1b
    file system (default generic): nfs
    root on le0 dumps on sd1b
    cannot mount root, error = 49
    root device (default le0):

I was trying to netboot, which works for the 1.5.3 system,
(meaning I am confident that rbootd, rarp, bootparams, and
nfs are set up correctly)

For the above attempt, I was using the 20020415's SYS_UBOOT and
miniroot.fs.  I first tried using vnconfig -c, and providing
miniroot as the NFS mount at /export/client/root, and I got
the above error.  Next, I tried copying the filesystem created
by vnconfig to a local partition, which I then exported, but
this also resulted in the above error.

Finally, I tried dd if=miniroot.fs of=/dev/sd1b
(where /dev/sd1b was the swap partition of a local harddrive
on the 425t).  This was much more successful, but there were
still very strange errors, which I'll describe in another email.

For now: Is there anything that I'm doing wrong that you
might see?  Should I be trying a more recent set of installation
tools?  Or a different installation method?



OUTPUT FROM NETBOOT and BOOTING FROM REMOTE SYSTEM
----------------------------------------------------------------
BOOTROM  Rev. 3.0  11 APR 91
MD11 REV 3.0 1991/03/25.17:03:08
MC68040 Processor
Configuration EEPROM
Utility Chip at 41
HP-HIL.Keyboard
 RESET To Restart
 Self-Test Mode
 RESET To Restart, SPACE clears input    Select System, type RETURN       ?
DMA-C0
 Self-Test Mode
3
RAM 25165482 Bytes
HP98644 (RS-232) at 9
HP PARALLEL at 12
HP98658 (SCSI S 32) at 14
HP98643 (LAN) at 21, AUI, 08000915AE95
Bit Mapped Video at 133 (Console)
 System Search Mode
                                        :LAN, 21, 080020729F11 hbptwb
                                           1Z SYS_UBOOT

1Z
                                         1Z is System Selected
 Booting System


>> NetBSD/hp300 Primary Boot, Revision 1.13
>> (gregm@mcgarry, Mon Apr 15 08:46:32 NZST 2002)
>> HP 9000/425t SPU
>> Enter "reset" to reset system.
Boot: [[[le0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-
WARNING: bad date in battery clock
net_open: client addr: 192.168.1.6
net_open: server addr: 192.168.1.2
net_open: server path: /export/client/root
boot: client IP address: 192.168.1.6
root addr=192.168.1.2 path=/export/client/root
692350+24936+164544 [75424+51665]=0xf86e0
Start @ 0xfe803400 [1=0xfe8db4a8-0xf86e0]...
Entry point: 0xfe803400
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.5ZC (INSTALL) #0: Fri Apr 12 20:11:26 NZST 2002
    gregm@mcgarry:/storage/scratch/netbsd/obj/current/kern/hp300/INSTALL
HP 9000/425t (25MHz MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches)
total memory = 24564 KB
avail memory = 21880 KB
using 16 buffers containing 65536 of memory
mainbus0 (root)
intio0 at mainbus0
rtc0 at intio0 addr 0x420000
frodo0 at intio0 addr 0x41c000
dnkbd at frodo0 offset 0x0 not configured
apci0 at frodo0 offset 0x40: no fifo
apci1 at frodo0 offset 0x60: no fifo
hil0 at intio0 addr 0x428000
fb at intio0 addr 0x560000 not configured
dio0 at mainbus0: 98620C, 2 channels, 32 bit DMA
dca0 at dio0 scode 9 ipl 5: console, working fifo
device id = 0x6 secid = 0x0 at dio0 scode 12 not configured
oscsi0 at dio0 scode 14 ipl 4: 32 bit dma, async, scsi id 7
sd0 at oscsi0 targ 0 lun 0: <RODIME, RO3000T, 5.76>
sd0: 1216 cylinders, 9 heads, 410211 blocks, 512 bytes/block
sd1 at oscsi0 targ 3 lun 0: <HP, C2235, 0B11> (SCSI-2)
sd1: 1574 cylinders, 9 heads, 825012 blocks, 512 bytes/block
le0 at dio0 scode 21 ipl 5: address 08:00:09:15:ae:95
le0: 8 receive buffers, 2 transmit buffers
topcat0 at dio0 scode 133: 1280 x 1024 256 color hi-res catseye display
grf0 at topcat0
ite0 at grf0
interrupt levels: bio = 4, net = 5, tty = 5
hil0 device 1: US ASCII keyboard
boot device: le0
root on le0
no file system for le0
cannot mount root, error = 79
root device (default le0):

----- Original Message -----
From: "Gregory McGarry" <g.mcgarry@ieee.org>
To: "Bernd Sieker" <bsieker@freenet.de>
Cc: <port-hp300@netbsd.org>
Sent: Tuesday, July 02, 2002 7:45 PM
Subject: Re: Netbooting 1.6_BETA3?


> > The resulting kernel finds the framebuffer and makes its kernel output
> > there, but when trying to boot, it complains:
> >
> >   root file system type: nfs
> >   init: copying out path '/sbin/init' 11
> >   Jul  6 15:57:28 init: can't get /dev/console for controlling terminal:
\
> >     Inappropriate ioctl for device
> >
> > And on and on, until I reset.
>
> You need to populate /dev on the nfs server.
>
> -- Gregory McGarry <g.mcgarry@ieee.org>
>