On Saturday, April 28, 2012 11:12 CEST, "Sebastian Reitenbach" 
<sebas...@l00-bugdead-prods.de> wrote: 
 
> On Friday, April 27, 2012 19:58 CEST, Miod Vallat <m...@online.fr> wrote: 
>  
> > > Then I got this far, until the box froze:
> > [...]
> > > grtwo0 at gio0 addr 0x1f000000: GR2-Elan
> > > grtwo0: device has not been setup by firmware!
> > > light0 at gio0 addr 0x1f3f0000
> > 
> > Oops, I have introduced an IP20-specific bug in the last gio.c commit. I
> > am testing a fix for it, in the meantime you can try booting the kernel
> > with the `c' option (something like
> >   bootp()bootecoff bootp()bsd.rd.IP22 --c
> > and be sure to use two dashes before the `c' letter) and `disable light'
> > in UKC. This will workaround the issue.
> 
> I wasn't aware of this --c . That helped then, and I was able to go on 
> with the installation. I've seen, you already fixed it in CVS, thanks.
> 
> But then later, while installing the packages, I got this:
> 
> base51.tgz    98% |************************************ | 56481 KB    00:06 
> ETAgzip: stdout: Broken pipe
> ftp: -: short write
> base51.tgz    98% |************************************ | 56481 KB    09:19   
>  
> Segmentation fault (core dumped) 
> 'base51.tgz' did not install correctly.
> 
> The same happended for the xetc51.tgz (I know X11 is not supported yet)
> 
> When the installer was done with all the sets, I just went ahead, trying to
> reinstall both again, but they failed the same way again.
> 
> Is this due to the processor bugs you mentioned, one of those instabilities?
> 
> Since my processor is:
> cpu0 at mainbus0: MIPS R4000 CPU rev 2.2 100 MHz, R4010 FPC rev 0.0
> cpu0: cache L1-I 8KB D 8KB direct, L2 1024KB direct
> 
> and this one may have such weirdo processor bugs you mentioned
> in your initial mail, and may run unstable.
> 
> going on, I had again boot from tftp due to the light:
> bootp()bootecoff bootp()bsd.IP22 --c
> 
> 
> While in the installer, at the point where I configure the disks, it showed
> me sd0, sd1, and sd2. sd0 and sd1, were easily configured, until it came to 
> sd2, where it did hang for a long time, unsuccessfully trying to read the
> disk layout. Only afterwards I recognized, this sd2 is not a disk, but is the 
> Floptical drive installed in the box. I don't know whether there is an easy
> way to prevent the installer from trying to install on such device, or 
> maybe its just easier to mention that as a limitation in the INSTALL.sgi
> file.
> 
> # dmesg                                                                 
> [ using 308880 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-2012 OpenBSD. All rights reserved.  http://www.OpenBSD.org
> 
> uvm_km_kmem_grow: grown to 0xc000000005000000
> OpenBSD 5.1-current (GENERIC-IP22) #15: Thu Apr 26 05:46:27 MDT 2012
>     dera...@sgi.openbsd.org:/usr/src/sys/arch/sgi/compile/GENERIC-IP22
> real mem = 83886080 (80MB)
> rsvd mem = 802816 (1MB)
> avail mem = 77660160 (74MB)
> User Kernel Config
> UKC> disable light
>  15 light* disabled
> UKC> exit\^H \^H\^H \^H\^H \^H\^H \^Hexit
> Continuing...
> mainbus0 at root: Indigo
> cpu0 at mainbus0: MIPS R4000 CPU rev 2.2 100 MHz, R4010 FPC rev 0.0
> cpu0: cache L1-I 8KB D 8KB direct, L2 1024KB direct
> clock0 at mainbus0: ticker on int5 using count register
> int0 at mainbus0 addr 0x1fb801c0
> imc0 at mainbus0: revision 3
> gio0 at imc0
> grtwo0 at gio0 addr 0x1f000000: GR2-Elan
> grtwo0: device has not been setup by firmware!

So I also cleaned the dust from Monitor and keyboard.
In the maintenance console, I did

setenv console g

with the hope to see something on the monitor. But I guess,
because of the firmware message above, the system is falling
back to the console. If I understood your initial mail right,
the Elan graka is tested?


> light at gio0 addr 0x1f3f0000 not configured
> light at gio0 addr 0x1f3f8000 not configured
> hpc0 at gio0 addr 0x1fb80000: SGI HPC1 (onboard)
> zs0 at hpc0 offset 0x00000d10 irq 5
> zstty0 at zs0 channel 1: console
> zstty1 at zs0 channel 0
> zs1 at hpc0 offset 0x00000d00 irq 5
> zsms0 at zs1 channel 1
> wsmouse0 at zsms0 mux 0
> zskbd0 at zs1 channel 0
> wskbd0 at zskbd0 mux 1

On the keyboard, nothing happens when I e.g. press the Num key.
Is that to be expected when in serial console mode?

Sebastian

> sq0 at hpc0 offset 0x00000100 irq 3: Seeq 80c03, address 08:00:69:06:cc:6f
> wdsc0 at hpc0 offset 0x0000011f irq 2: WD33C93B, 20.0 MHz, burst DMA
> wdsc0: microcode revision 0x0c, fast SCSI
> scsibus0 at wdsc0: 8 targets, initiator 0
> sd0 at scsibus0 targ 1 lun 0: <CONNER, CP3500-540MB-3.5, 3236> SCSI2 0/direct 
> fixed
> sd0: 518MB, 512 bytes/sector, 1062516 sectors
> sd1 at scsibus0 targ 2 lun 0: <IBM OEM, 0663E15, eSfS> SCSI2 0/direct fixed
> sd1: 1150MB, 512 bytes/sector, 2356180 sectors
> sd2 at scsibus0 targ 3 lun 0: <TEAC, FC-1 HF 04, RV E> SCSI1 0/direct 
> removable
> sd2: 0MB, 512 bytes/sector, 1280 sectors
> dpclock0 at hpc0 offset 0x00000e00
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> boot device: sd0
> root on sd0a (8c7c7429cad9e0ad.a) swap on sd0b dump on sd0b
> 
> So far, It booted, and I can login on the console and via ssh, even without
> a fully installed base51.tgz.
> 
>  
> thanks,
> Sebastian
> 
> 
> 
> > 
> > Miod

Reply via email to