Subject: Re: Q: SCSI controller (Initio) and HDD (Fujitsu) not seen in
To: Andrew Doran <ad@netbsd.org>
From: Markus A. Boeing <markus@boeing-online.de>
List: port-alpha
Date: 05/14/2001 19:55:14
Hi Andrew,

thanks for your interest. Please find below the output of the dmesg 
command. There is just a single line referring to the Initio controller. 
The lines before and after refer to two Ethernet (ne0 and ep0) controllers.

root@Tigerente > dmesg
[ preserving 445000 bytes of netbsd ELF symbol table ]
consinit: not using prom console
Copyright (c) 1996, 1997, 1998, 1999, 2000
     The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

NetBSD 1.5 (GENERIC) #10: Wed Nov 22 03:00:56 PST 2000
     root@frau-farbissina.shagadelic.org:/amd/swinger/u1/netbsd-1-5/src/sys/arch/alpha/compile/GENERIC
AlphaStation 200 4/233, 233MHz
8192 byte page size, 1 processor.

<snip>

ne0: interrupting at isa irq 9
Initio INIC-950 SCSI (SCSI mass storage, revision 0x02) at pci0 dev 13 
function 0 not configured
isa0 at sio0
ep0 at isa0 port 0x300-0x30f irq 10: 3Com 3C509 Ethernet

<snip>

root@Tigerente > scsictl /dev/scsibus1 scan all all
scsictl: /dev/scsibus1: Device not configured
root@Tigerente >

Later,
/Markus.

At 17:18 14.05.2001, Andrew Doran wrote:
>"Markus A. Boeing" <markus@boeing-online.de> wrote:
>
> > I added an Initio INI-9100-UW SCSI controller and a Fujitsu MAH3091MP disk
> > drive to my DEC AlphaStation 200. Unfortunately the system does not
> > recognize the new components.
> >
> > The Alpha's SRM (v6.9-4) console shows the new controller but not the disk
> > drive. When booting up NetBSD 1.5 the startup messages show that NetBSD
> > recognizes the INI-9100-UW controller but not the disk drive. Funny enough
> > NetBSD does complain about /dev/scsibus1 not to be existent (/dev/scsibus0
> > is the build-in controller). I expected the device to exist because the
> > controller was recognized.
>
>I wasn't aware that we had a driver for this... Can you post the output of
>dmesg please?
>
>Andrew