On Thu, Mar 18, 2004 at 08:39:48PM -0500, Steve Rumble wrote:
> On Thu, Mar 18, 2004 at 07:32:19PM -0600, Tillman Hodgson wrote:
> > I'd really like to use the on-board NIC. Is there a recommended install
> > kernel that I can use?
> 
> As far as I'm aware the onboard nic isn't yet supported. You'll
> have to toss in a pci one that's compiled into GENERIC_IP3x. It
> looks like most common ones are. 

Based on this I tossed a 3Com 905B in and installed the Jan 05/2004
install kernel build via Ftp. Yay, it worked :-)

When I went to boot the new installation, though, it bombed out with:

> boot
SCSI Hard Error on (0,1) unexpected bus free (hastat 0x13) -- check cabling
cdb: 12 0 0 0 1 0
SCSI Hard Error on (0,1) unexpected bus free (hastat 0x13) -- check cabling
cdb: 12 0 0 0 1 0
SCSI Hard Error on (0,1) unexpected bus free (hastat 0x13) -- check cabling
cdb: 12 0 0 0 1 0
SCSI Hard Error on (0,1) unexpected bus free (hastat 0x13) -- check cabling
cdb: 12 0 0 0 1 0
SCSI Hard Error on (0,1) unexpected bus free (hastat 0x13) -- check cabling
cdb: 12 0 0 0 1 0
Unable to execute scsi(0)disk(1)rdisk(0)partition(8)/boot:  IO error
Unable to load scsi(0)disk(1)rdisk(0)partition(8)/boot: no such device.

Are those "check cabling" messages common or normal?

My printenv and hinv look like this:

> printenv
AutoLoad=Yes
diskless=0
dbaud=9600
volume=80
sgilogo=y
monitor=h
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
console=d
TimeZone=CST6CST
netaddr=192.168.23.8
ConsoleOut=serial(0)
ConsoleIn=serial(0)
cpufreq=200
eaddr=08:00:69:02:e3:cb
videostatus=illegal_env_var
OSLoadFilename=netbsd
OSLoadOptions=auto
OSLoader=boot
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
kernname=scsi(0)disk(1)rdisk(0)partition(8)/boot
> hinv
                   System: IP32
                Processor: 200 Mhz R5000, with FPU
     Primary I-cache size: 32 Kbytes
     Primary D-cache size: 32 Kbytes
     Secondary cache size: 1024 Kbytes
              Memory size: 64 Mbytes
                 Graphics: CRM, Rev C
                    Audio: A3 version 1
                SCSI Disk: scsi(0)disk(1)
               SCSI CDROM: scsi(0)cdrom(4)

My guess is that I need to set one or more "BIOS" options to tell it
what to boot on the harddrive. The culprits I have in mind are
OSLoadFilename, SystemPartition, OSLoadPartition and OSLoader.

-T


-- 
You can have peace. Or you can have freedom. Don't ever count on having both
at once.
	- Robert Heinlein