Yeah and when said docs say "refer to the bootpd(8)" man page which no longer exists that can cause frustration. :D
"I am not your puppet. Since when? Now, get your spongy pink ass out there, and dance for the cameras." -Death to Smoochy On Wed, 10 Aug 2005, Per [iso-8859-1] Fogelstrvm wrote: > Date: Wed, 10 Aug 2005 16:21:05 +0200 > From: "Per [iso-8859-1] Fogelstrvm" <[EMAIL PROTECTED]> > To: misc@openbsd.org > Subject: Re: sgi 02 latest snapshot CD37.iso boot problems > > On Wednesday 10 August 2005 10.18, you wrote: >> The fix for me was to not use graphical console. >> > > Well, the install doc pretty much says "serial console", doesn't it? > > ---- > Switching from serial to graphics console and vice versa: > > Booting the ramdisk kernel can be done from the ARCS graphic console > although it might be more convenient to use the serial console since > the kernel currently only supports the serial console. Some systems > come with the serial console enabled by default but sometimes > this must be changed. > > To change to serial console, go into the ARCS Maintenance Console > and change the ``console'' environment variable, and power-cycle > the machine. > > > setenv console d > > will select 9600 8N1, no flow control, serial console on the first > serial port (labeled ``(1)''), while > > > setenv console g > ----- > > People put a lot of effort into writing these documents to make setting > up an OpenBSD system an easy task... > > The reason you can see the output until the "Setting up" > is that this is the point where OpenBSD switches from the > ARCBios console to its own console driver. > > P. > >> "I am not your puppet. Since when? Now, get your spongy pink ass out >> there, and dance for the cameras." -Death to Smoochy >> >> On Wed, 10 Aug 2005, Ober Heim wrote: >> >>> Date: Wed, 10 Aug 2005 02:25:13 -0500 (CDT) >>> From: Ober Heim <[EMAIL PROTECTED]> >>> To: mrservices <[EMAIL PROTECTED]> >>> Cc: misc@openbsd.org >>> Subject: Re: sgi 02 latest snapshot CD37.iso boot problems >>> >>> I never been able to boot a single bsd.rd for as long as sgi has been >>> "supported". It tftps fine, but just like your cd error hangs at the "Setting >>> up" portion of the boot you reference. >>> 3.7 fails as does the snapshot. >>> I also get the same error on latest cd37.iso and cd38.iso >>> >>> "I am not your puppet. Since when? Now, get your spongy pink ass out there, >>> and dance for the cameras." -Death to Smoochy >>> >>> On Tue, 9 Aug 2005, mrservices wrote: >>> >>>> Date: Tue, 09 Aug 2005 16:34:10 -0700 >>>> From: mrservices <[EMAIL PROTECTED]> >>>> To: misc@openbsd.org >>>> Subject: sgi 02 latest snapshot CD37.iso boot problems >>>> >>>> Hello List, >>>> >>>> I was able to install OpenBSD on an sgi 02 R5000 but corrupted bsd when the >>>> ftp stalled on download >>>> I am unable to boot back into the system trying boot or /bsd or /bsd.rd >>>> with the latest sgi snapshot CD37.iso >>>> >>>> The system freezes at this point and I have to unplug the unit and plug >>>> back in to restart. >>>> >>>> arg0: dksc(0,4,8)boot >>>> arg1: ConsoleIn=Keyboard() >>>> arg2: ConsoleVideo=Video() >>>> arg3: SystemPartition= pci(0)scsi(0)disk(1)rdisk(0)partition(8) >>>> arg4: OSLoader=sash >>>> arg5: OSLoadPartition= pci(0)scsi(0)disk(1)rdisk(0)partition(0) >>>> arg6: OSLoadFilename=/bsd >>>> 34192+1264 >>>> entry: 0x80010120 SystemPartition pci(0)scsi(0)disk(1)rdisk(0)partition(8) >>>> OpenBSD/sgi Arcbios boot >>>> Boot pci(0)scsi(0)disk(1)rdisk(0)partition(0)/bsd >>>> Loading ELF64 File >>>> 0xffffffff80100000:0x30e0a0, Zero >>>> 0xffffffff8040e0a0:0x5d2a0, Loading symbol table >>>> Start at 0xffffffff80100000 >>>> ARC32 Firmware 1.10 >>>> SR=34010080 >>>> Found SGI-IP32, Setting Up >>>> >>>> I have tried unsetenv OSLoader, OSLoadPartition, OSFilename >>>> >>>> Command menu ls device shows >>>> >>>> ls pci(0)scsi(0)disk(1)rdisk(0)partition(8) >>>> boot >>>> >>>> I don't have any IRIX tool disks or other disks to work with. >>>> >>>> Any help on this is much appreciated. >>>> >>>> Thank you, >>>> >>>> rogern
