Subject: Argh. Can't create bootdisk.
To: None <port-hp300@NetBSD.ORG>
From: Kerry Schwab <kschwab@nyx10.cs.du.edu>
List: port-hp300
Date: 07/25/1995 07:44:51
Argh!
I am having problems getting NetBSD installed on a 425e that
was formally set up with Domain/OS.
1) Short version: Is there anyone in the Dallas area that
would make a bootable disk for me if I
brought the drive over ? (Or I'll pay shipping
both ways on the drive if someone out of
town can help)
I mistakenly said I had a 425t in an earlier
post, it is a 425e. I figured out how to get
the PROM prompt, and how to configure to boot
in HPUX mode, but never found any choice for
configuring the console to run off the tty
port... anyone know how to do this ?
(It would appear that you can't... the only
options for configurable devices are LAN,
HP parallel, and SCSI)
2) Long version:
I had no passwords for the Domain/OS, and no MC680x0 machines
running HPUX or NetBSD. So, in order to get the os onto a hard
drive, I installed NetBSD/i386 onto one of my PC's. This was
fairly simple, and went beautifully.
At this point, I put my target disk on the scsi bus, and booted
NetBSD on the PC... all well, sd1 was recognized.
I brought the hp300 install directory onto the PC, and
extracted the makedisk program (makedisk.tar.gz)...
I then edited the included "disklabel.h" header file and removed
the lines between "#ifdef i386" and "#endif /* i386 */".
(Which would appear to reserve space for DOS bootblock, etc...)
I then ran the resulting "makedisk" program with no problems...
I am pretty sure I supplied "correct" values (sectors/track, etc),
as I installed NetBSD on the PC on an identical Quantum425S drive.
I also included a one sector offset for the a partition as explained
in the INSTALL file.
In any event, when I try to boot this disk, everything looks fine,
It finds the "SYS_PBOOT" image, then says "Booting System", then
hangs. I haven't gotten my HP-HIL keyboard yet, is this what's
hanging ? (I was hoping to see the system get to the NetBSD boot
prompt)
Here's the output from "makedisk":
>./makedisk /dev/rsd1d mylabel boot rootimage.gz
>Using calculated value 820800 for sectors/unit.
>makedisk: warning: boot overlaps partition c: markes as FS_BOOT
>makedisk: warning: boot overlaps partition d: markes as FS_BOOT
>sh: warning: running as root with dot in PATH
>Generating bootblock: 8192+31232
>Generating label at offset: 1024+276
>Writing bootblock/disklabel.
>Jumping to partition a.
>sh: warning: running as root with dot in PATH
>Writing root image:
> [lots of .'s deleted]
>0+3914 records in
>0+3914 records out
>16017408 bytes transferred in 21 secs (762733 bytes/sec)
Here's the prototype disklabel I used:
># /dev/rsd1d:
>type: SCSI
>disk: mysd
>label:
>flags:
>bytes/sector: 512
>sectors/track: 60
>tracks/cylinder: 9
>sectors/cylinder: 540
>cylinders: 1520
>rpm: 3600
>interleave: 1
>trackskew: 0
>cylinderskew: 0
>headswitch: 0 # milliseconds
>track-to-track seek: 0 # milliseconds
>drivedata: 0
>
>7 partitions:
># size offset fstype [fsize bsize cpg]
> a: 30780 540 4.2BSD 1024 8192 16 # (Cyl. 1 - 57)
> b: 128520 31320 swap # (Cyl. 58 - 295)
> c: 820800 0 unused 0 0 # (Cyl. 0 - 1519)
> d: 820800 0 unused 0 0 # (Cyl. 0 - 1519)
> e: 39960 159840 4.2BSD 1024 8192 16 # (Cyl. 296 - 369)
> f: 295920 199800 4.2BSD 1024 8192 16 # (Cyl. 370 - 917)
> g: 325080 495720 4.2BSD 1024 8192 16 # (Cyl. 918 - 1519)
>
Here's what I see when booting the 425e:
>Copyright 1991,
>Hewlett-Packard Company.
>All rights reserved
>
>BOOTROM Rev 3.01 2 May 91
>MD11 Rev3.0 1991/03/25.17:03:08
>Bit Mapped Video
>MC68040 Processor
>Configuration EEPROM
>Utility CHIP at 41
>HP-HIL
>DMA-C0
>RAM 33554090 Bytes
>Digital Audio at 8
>HP Parallel at 12
>HP 98265 (SCSI S 32) at 14
>HP 98643 (LAN) at 21, AUI, 0800091746F3
>EVRX at SGC slot 0 (Console)
>
>Reset to Restart, SPACE clears input
>Select System, type RETURN
>[after a while, the following appears at the top of the screen]
>:QUANTUM PD425S, 1406, 0
>1Z SYS_PBOOT
>[then I type "1Z" and hit return, and see the following]
>1Z is system selected
>Booting system
>[the screen now goes blank, the drive access light comes on, and
> the machine stays in this state indefinitely]
--
Kerry
(please forward any replies to 'kschwab@nyx.cs.du.edu', as my account
quotas are too small for mailing lists)