Re: OpenBSD 3.5 on HP PA-RISC

From: Robert S. Sciuk (rob_at_ControlQ.com)
Date: 06/29/04

  • Next message: Matt Bostock: "Re: Rebuilding my system binaries led to some kind of kernel panic..?"
    Date: Tue, 29 Jun 2004 11:36:17 -0400
    
    

    Hugo,

    As you were the only one to reply, I figured I'd just email you, I hope
    you don't mind.

    It turns out that the dhcpd was running on an older (FreeBSD 2.2.5)
    release from circa 1996. By updating to a modern release of FreeBSD for
    dhcpd and tftp, all was well, and booting the 712 was not a problem. I'm
    just now burning a release cd with the OpenBSD contents, and hope to get
    through an install in the next day or so ...

    Again, thanks for your reply ..

    Cheers,
    Rob Sciuk.

    On Wed, 23 Jun 2004, Hugo Villeneuve wrote:

    > Date: Wed, 23 Jun 2004 03:23:46 GMT
    > From: Hugo Villeneuve <hugo@EINTR.net>
    > Newsgroups: comp.unix.bsd.openbsd.misc
    > Subject: Re: OpenBSD 3.5 on HP PA-RISC
    >
    > spam@controlq.com wrote:
    > > The last time I installed OpenBSD, was 2.8 on an intel box. As I have an
    > > HP9000 712/60 (Bootrom version 2.0 (BOOT_ADMIN>)), I figured it was high
    > > time that I put a fresh version on the box, and tried it out again. I'm a
    > > little confused, however.
    > >
    > > While the install doc has info for net-booting, I've had little success
    > > (either with rbootd or dhcpd/bootp). The dhcpd sees the request, and
    >
    > My understanding is that rbootd is for those machine that don't have the
    > BOOT_ADMIN prompt. So you can't use it.
    >
    > So you have to use bootp/dhcpd.
    >
    > > grants an IP address, but there seems to be a tftpd glitch, and no attempt
    > > to boot the lif35.fs is made. Hmmm ... I've configured the host machine
    > > to serve up tftpd, and the lif35.fs is available so that should work.
    >
    > You must provide the filename via dhcp too. This is how my hppa
    > dhcpd.conf entry looks like:
    >
    > host hp712 {
    > filename "lif35.fs";
    > next-server 192.168.12.1;
    > fixed-address 192.168.12.5;
    > hardware ethernet 0:60:b0:20:82:1e;
    > }
    >
    > next-server is needed because my dhcpd server is not my tftpd server.
    > the filename doesn't have a path because I run tftpd with the "-s
    > /tftpboot" arguments (because of my sparcs).
    >
    > Use tcpdump to see the tftp request. It might help you see why it fails.
    >
    > lif35.fs contains a compressed bsd.rd. So installation should be similar
    > to what you know.
    >
    > >
    > > Be that as it may, I'd prefer to boot from a cd. In the distro, I see the
    > > xxboot file, which mkisofs refuses to put into a boot image (wrong size
    >
    > Those -b -c flags are i386 centric. Creating bootable media for other
    > arch is not so easy. See the ${CDROM} target in:
    >
    > http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/src/distrib/hppa/ramdisk/Makefile?rev=1.5&content-type=text/plain
    >
    > > for a floppy I guess). Now in browsing the main ftp site, I see a file
    > > (cd35.iso) with no information. The FreeBSD file command identifies it as
    > > a .lif file. Is that the cd boot segment for creating/burning an install
    > > .iso? Is it possible to create a PA-RISC boot cd in OpenBSD 3.5??
    > >
    >
    > LIF is a HP special archive format that can contain multiple member. The
    > boot rom expect to find the beginning of a lif archive at block 0 of the
    > boot disk (scsi or network).
    >
    > So it's not abnormal that xxboot, lif35.fs and cd35.iso have .lif file
    > signature since they need to be hppa bootable.
    >
    > I never tried cd35.iso but it should work. Just burn it with your
    > favorite cd burning software. I don't know if it require a
    > 512bytes/block CD-ROM to be bootable.
    >
    > > Sorry to trouble the group with this, but I'm not exactly a beginner, and
    > > yet I seem to be having more grief than I should. Any pointers would be
    > > appreciated!
    > >
    > > Cheers,
    > > Rob.
    >

    -- 
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=
    Robert S. Sciuk		http://www.controlq.com		259 Simcoe St. S.
    Control-Q Research	tel: 905.576.8028		Oshawa, Ont.
    rob@controlq.com	fax: 905.576.8386  		Canada, L1H 4H3
    

  • Next message: Matt Bostock: "Re: Rebuilding my system binaries led to some kind of kernel panic..?"

    Relevant Pages

    • Re: Speeding up boot process
      ... >some services (cupsd, lm-sensors, dhcpd, ntpd, etc) it's getting more. ... With the lilo boot loader, as an example, if ... recover from a mistake in the initial single user sequence too, ...
      (comp.os.linux.misc)
    • Re: DHCPD starting before ETH0 gives error.
      ... put in a delay in starting up dhcpd. ... assuming of course that network is started before dhcpcd. ... >> If I start DHCPD after boot, ... >> Should I define the subnet 0.0.0.0? ...
      (comp.os.linux.networking)
    • Re: Promiscuous BOOTP server?
      ... I'm trying to set up a BOOTP/tftpd server so that I can boot diskless ... I've read the dhcpd docs, ... require MAC addresses. ... Is there a way to set up a server without requiring the MAC addresses? ...
      (comp.os.linux.setup)
    • Re: Stupid DHCP Problem
      ... I suggest changing the dhcpd line to not run, but echo its line to a log file. ... See if you can see any difference, between the first time it runs (ie at boot ... Now, it works the second time, but not the first, so what has changed between ... You might want to mess around with your boot scripts to stop them at the dhcpd ...
      (comp.os.linux)
    • Re: DHCPD starting before ETH0 gives error.
      ... > When it starts at boot time it states that there is no subnet for ... > If I start DHCPD after boot, ... > So the question is how to properly setup DHCPD so it starts on boot. ... > Should I define the subnet 0.0.0.0? ...
      (comp.os.linux.networking)