Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-12 Thread Roger Neth Jr

Hello Theo and List, will do and thank you for pointing that out to me.

Best regards,

rogern


From: Theo de Raadt <[EMAIL PROTECTED]>
To: "Roger Neth Jr" <[EMAIL PROTECTED]>
CC: misc@openbsd.org, [EMAIL PROTECTED]
Subject: Re: sgi 02 latest snapshot CD37.iso boot problems Date: Fri, 12 
Aug 2005 17:01:46 -0600


Look Roger, you have a SERIOUS READING PROBLEM.

> Hello Mark and List, thank you for the reply and assistance.
>
> I have tried "Booting from CD-ROM installation media" with cd38.iso but 
the

> 02 does not recognize the media.
>
> When I go into the maintenance menu and boot -f dksc(0,4,8)boot, it 
boots to

> /bsd but panic at no init

As Mark Kettenis said:

> >Please reread the current INSTALL.sgi again, in particular the section
> >on "Booting from CD-ROM installation media".
> >
> >It should no longer be necessary to enter the Command Monitor to boot
> >from CD-ROM; just choose "Install System Software" from the System
> >Maintenance Menu.
> >
> >Mark

Now stop it Roger, and read the bloody documentation!


_
Dont just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-12 Thread Theo de Raadt
Look Roger, you have a SERIOUS READING PROBLEM.

> Hello Mark and List, thank you for the reply and assistance.
> 
> I have tried "Booting from CD-ROM installation media" with cd38.iso but the 
> 02 does not recognize the media.
> 
> When I go into the maintenance menu and boot -f dksc(0,4,8)boot, it boots to 
> /bsd but panic at no init

As Mark Kettenis said:

> >Please reread the current INSTALL.sgi again, in particular the section
> >on "Booting from CD-ROM installation media".
> >
> >It should no longer be necessary to enter the Command Monitor to boot
> >from CD-ROM; just choose "Install System Software" from the System
> >Maintenance Menu.
> >
> >Mark

Now stop it Roger, and read the bloody documentation!



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-12 Thread Roger Neth Jr
50a, 16 byte fifo

com0: console

com1 at macebus0: ns16550a, 16 byte fifo

mec0 at macebus0: MAC-110 rev 1, address 08:00:69:02:df:19

nsphy0 at mec0 phy 8: DP83840 10/100 PHY, rev. 1

mavb0 at macebus0: AD1843 rev 1

audio0 at mavb0

boot device: sd0.

root device (default sd0a):

swap device (default sd0b):

root on sd0a

ahc0: target 1 using 16bit transfers

ahc0: target 1 synchronous at 10.0MHz, offset = 0x8

rootdev=0x0 rrootdev=0x900 rawdev=0x902

warning: /dev/console does not exist

init: not found

panic: no init

Stopped at  Debugger+0x4:   jr  ra

nop

RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!

DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!

ddb> trace

Debugger+0x4 (,,500,d) sp c6a93eb0 
ra f


fff801b7d58, sz 0

panic+0xe0 (,,500,d) sp c6a93eb0 ra 
fff


f801927dc, sz 96

start_init+0x23c (,,500,d) sp 
c6a93f10 r


a 803601a8, sz 176

proc_trampoline+0x48 (,,500,d) sp 
c6a93


fc0 ra 0, sz 0

User-level: pid 1

ddb> ps

  PID   PPID   PGRPUID  S   FLAGS  WAIT   COMMAND

8  0  0  0  30x100204  crypto_wa  crypto

7  0  0  0  30x100204  aiodoned   aiodoned

6  0  0  0  30x100204  syncer update

5  0  0  0  30x100204  cleanercleaner

4  0  0  0  30x100204  reaper reaper

3  0  0  0  30x100204  pgdaemon   pagedaemon

2  0  0  0  30x100204  kmallockmthread

*1  0  0  0  7 0x4 swapper

0 -1  0  0  3 0x80204  scheduler  swapper

ddb> dmesg

NOTE: TLB code too large, using trampolines

[ using 263136 bytes of bsd ELF symbol table ]

Copyright (c) 1982, 1986, 1989, 1991, 1993

   The Regents of the University of California.  All rights reserved.

Copyright (c) 1995-2005 OpenBSD. All rights reserved.  
http://www.OpenBSD.org



OpenBSD 3.7 (GENERIC) #89: Sun Mar 20 18:32:30 MST 2005

   [EMAIL PROTECTED]:/usr/src/sys/arch/sgi/compile/GENERIC

real mem = 134217728

rsvd mem = 7020544

avail mem = 108883968

using 1638 buffers containing 6709248 bytes of memory

mainbus0 (root)

cpu0 at mainbus0: MIPS R5000 CPU rev 2.1 180 MHz with R5000 based FPC rev 
1.0


cpu0: cache L1-I 32KB D 32KB 2 way, L2 512KB direct

macebus0 at mainbus0: crime rev 10.1

clock0 at macebus0: TOD with DS1687, ticker on int5 using count register.

macepcibr0 at macebus0: mace rev 1, host system O2

pci0 at macepcibr0 bus 0

ahc0 at pci0 dev 1 function 0 "Adaptec AIC-7880" rev 0x00: irq 9

ahc0: Host Adapter Bios disabled.  Using default SCSI device parameters

scsibus0 at ahc0: 16 targets

--db_more--ahc0: target 1 using 8bit transfers

--db_more--ahc0: target 1 using asynchronous transfers

--db_more--sd0 at scsibus0 targ 1 lun 0:  SCSI3 
0/direct fixed


--db_more--sd0: 8748MB, 11474 cyl, 5 head, 312 sec, 512 bytes/sec, 17916240 
sec total


--db_more--cd0 at scsibus0 targ 4 lun 0:  
SCSI2 5/cdrom r


--db_more--removable

--db_more--ahc1 at pci0 dev 2 function 0 "Adaptec AIC-7880" rev 0x00: irq 10

--db_more--ahc1: Host Adapter Bios disabled.  Using default SCSI device 
parameters


--db_more--scsibus1 at ahc1: 16 targets

--db_more--com0 at macebus0: ns16550a, 16 byte fifo

--db_more--com0: console

--db_more--com1 at macebus0: ns16550a, 16 byte fifo

--db_more--mec0 at macebus0: MAC-110 rev 1, address 08:00:69:02:df:19

--db_more--nsphy0 at mec0 phy 8: DP83840 10/100 PHY, rev. 1

--db_more--mavb0 at macebus0: AD1843 rev 1

--db_more--audio0 at mavb0

--db_more--boot device: sd0.

--db_more--root device (default sd0a):

--db_more--swap device (default sd0b):

--db_more--root on sd0a

--db_more--ahc0: target 1 using 16bit transfers

--db_more--ahc0: target 1 synchronous at 10.0MHz, offset = 0x8

--db_more--rootdev=0x0 rrootdev=0x900 rawdev=0x902

--db_more--warning: /dev/console does not exist

--db_more--init: not found

--db_more--panic: no init

--db_more--Stopped at  Debugger+0x4:   jr  ra

--db_more--nop

--db_more--R


From: Mark Kettenis <[EMAIL PROTECTED]>
To: misc@openbsd.org
CC: [EMAIL PROTECTED]
Subject: Re: sgi 02 latest snapshot CD37.iso boot problems
Date: Fri, 12 Aug 2005 09:53:49 +0200 (CEST)

Please reread the current INSTALL.sgi again, in particular the section
on "Booting from CD-ROM installation media".

It should no longer be necessary to enter the Command Monitor to boot
from CD-ROM; just choose "Install System Software" from the System
Maintenance Menu.

Mark



_
Is your PC infected? Get a FREE online computer virus scan from McAfee. 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963




Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-12 Thread Mark Kettenis
Please reread the current INSTALL.sgi again, in particular the section
on "Booting from CD-ROM installation media".

It should no longer be necessary to enter the Command Monitor to boot
from CD-ROM; just choose "Install System Software" from the System
Maintenance Menu.

Mark



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Roger Neth Jr
]>
To: Roger Neth Jr <[EMAIL PROTECTED]>
Subject: Re: sgi 02 latest snapshot CD37.iso boot problems
Date: Wed, 10 Aug 2005 22:52:51 +0200

* Roger Neth Jr <[EMAIL PROTECTED]> [2005-08-10 22:09]:
> Hello All, and thank you for the assistance.
>
> I was able to boot from CD37.iso, lastest snapshot in serial console but
> run into missing init while boot processing.
>
> Here is the output. Any assistance on getting this running again is
> appreciated.

can you please start reading our documentation?
to install you need to boot bsd.rd of course!

> OSLoadFilename=/bsd


_
Dont just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Roger Neth Jr
d

6  0  0  0  30x100204  syncer update

5  0  0  0  30x100204  cleanercleaner

4  0  0  0  30x100204  reaper reaper

3  0  0  0  30x100204  pgdaemon   pagedaemon

2  0  0  0  30x100204  kmallockmthread

*1  0  0  0  7 0x4 swapper

0 -1  0  0  3 0x80204  scheduler  swapper

ddb> boot halt

System Halt.



From: Per Fogelstrvm <[EMAIL PROTECTED]>
To: Ober Heim <[EMAIL PROTECTED]>
CC: misc@openbsd.org
Subject: Re: sgi 02 latest snapshot CD37.iso boot problems
Date: Wed, 10 Aug 2005 16:56:31 +0200

On Wednesday 10 August 2005 16.54, Ober Heim wrote:
> Yeah and when said docs say "refer to the bootpd(8)" man page which no
> longer exists that can cause frustration. :D
>

Really? It also referes to the dhcpd(8) man page and what you need exactly
depends on what type of system you are going to use as your bootp/dhcp 
server.


---quote---
First, a bootp or dhcpd server needs to be set up. The bootpd(8) or
dhcpd(8) manual page on your server should provide detailed information
on how to set up the server.
---end quote--

But of course...


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, 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

Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Per Fogelström
On Wednesday 10 August 2005 16.54, Ober Heim wrote:
> Yeah and when said docs say "refer to the bootpd(8)" man page which no 
> longer exists that can cause frustration. :D
>

Really? It also referes to the dhcpd(8) man page and what you need exactly
depends on what type of system you are going to use as your bootp/dhcp server.

---quote---
First, a bootp or dhcpd server needs to be set up. The bootpd(8) or
dhcpd(8) manual page on your server should provide detailed information
on how to set up the server.
---end quote--

But of course...


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, 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
> >>>> 0x8010:0x30e0a0, Zero
> >>>> 0x8040e0a0:0x5d2a0, Loading symbol table
> >>>> Start at 0x8010
> >>>> 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



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Ober Heim
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
>>>> 0x8010:0x30e0a0, Zero
>>>> 0x8040e0a0:0x5d2a0, Loading symbol table
>>>> Start at 0x8010
>>>> 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



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Per Fogelström
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
> >> 0x8010:0x30e0a0, Zero
> >> 0x8040e0a0:0x5d2a0, Loading symbol table
> >> Start at 0x8010
> >> 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



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Mats O Jansson
On Wed, 10 Aug 2005, Ober Heim wrote:

> 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 installed the last 3.7 snapshot this saturday with success. If I had
followed the INSTALL.sgi instruction I shouldn't have had any problems.
Booted from CD and installed sets via ftp.

The reason for me to to this was to test the newly added support for
"install software" in maintance mode.

The biggest problem was to find a terminal to hook to the com port on O2.
As the installation note says, if it isn't in the list it isn't supported.

-moj

> "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
> > 0x8010:0x30e0a0, Zero
> > 0x8040e0a0:0x5d2a0, Loading symbol table
> > Start at 0x8010
> > 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



Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Ober Heim

The fix for me was to not use graphical console.

"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
0x8010:0x30e0a0, Zero
0x8040e0a0:0x5d2a0, Loading symbol table
Start at 0x8010
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




Re: sgi 02 latest snapshot CD37.iso boot problems

2005-08-10 Thread Ober Heim
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
0x8010:0x30e0a0, Zero
0x8040e0a0:0x5d2a0, Loading symbol table
Start at 0x8010
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