Subject: Re: O2 R12000 Support
To: None <port-sgimips@netbsd.org>
From: Stephen Nelson-Smith <sanelson@gmail.com>
List: port-sgimips
Date: 05/26/2007 23:04:32
On 5/26/07, Stephen Nelson-Smith <sanelson@gmail.com> wrote:
> Hello,
>
> I have an O2 (System: IP32, Processor: 300 Mhz R12000, with FPU).
>
> I recall reading that this is unsupported/unusable in Linux.  Is this
> known to be good/stable with netbsd?

Well, I did some further research, at it seems like it should be ok...
so I downloaded sgimipscd-3.1.iso and burned it using k3b, as I do
with any other ISO.

Here's the setup:

> printenv
AutoLoad=Yes
diskless=0
dbaud=9600
volume=80
sgilogo=y
monitor=h
TimeZone=PST8PDT
crt_option=1
netaddr=192.168.0.7
console=d
ConsoleOut=serial(0)
ConsoleIn=serial(0)
cpufreq=300
eaddr=08:00:69:02:c8:74
videostatus=illegal_env_var
SystemPartition=scsi(0)cdrom(4)rdisk(0)partition(8)
OSLoadPartition=scsi(0)cdrom(4)rdisk(0)partition(0)
OSLoadFilename=netbsd
osloadoptions=auto
OSLoader=boot
kernname=pci(0)scsi(0)cdrom(4)rdisk(0)partition(8)ip3xboot

> boot
dks0d4s8: volume header not valid
Unable to execute scsi(0)cdrom(4)rdisk(0)partition(8)/boot:  media not loaded
Unable to load scsi(0)cdrom(4)rdisk(0)partition(8)/boot: no
recognizable file system on device.
> hinv
                   System: IP32
                Processor: 300 Mhz R12000, with FPU
     Primary I-cache size: 32 Kbytes
     Primary D-cache size: 32 Kbytes
     Secondary cache size: 1024 Kbytes
              Memory size: 512 Mbytes
                 Graphics: CRM, Rev C
                    Audio: A3 version 1
                SCSI Disk: scsi(0)disk(2)
               SCSI CDROM: scsi(0)cdrom(4)

I get the same if I try to boot directly:

> boot -f pci(0)scsi(0)cdrom(4)rdisk(0)partition(8)ip3xboot
dks0d4s8: volume header not valid
Unable to execute pci(0)scsi(0)cdrom(4)rdisk(0)partition(8)ip3xboot:
media not loaded
Unable to load pci(0)scsi(0)cdrom(4)rdisk(0)partition(8)ip3xboot: no
recognizable file system on device.

Now, there was a thread in June 2006 with exactly this problem, and
Pete made a bootable image, which is now, I believe, standard.

So what am I missing?

S.