Subject: Re: /dev/rsd0c: Device not configured
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Rick Copeland <rickgc@calweb.com>
List: port-sun3
Date: 09/10/1998 07:45:47
I am interested in the driver you have in what ever state that it is in.
Can you put it up somewhere where I can get it?
Rick Copeland
At 10:22 AM 9/8/98 -0400, der Mouse wrote:
>> [W]hen I run edlable /dev/rsd0c it comes back with "/dev/resd0c:
>> Device not configured".
>
>> Any ideas why this is happening?
>
>The kernel is not finding any SCSI interfaces. Note the lack of any
>scsibus reports:
>
>> mainbus0 (root)
>> obio0 at mainbus0
>> zsc0 at obio0 addr 0x0 level 6 (softpri 3)
>> kbd0 at zsc0 channel 0
>> ms0 at zsc0 channel 1
>> zsc1 at obio0 addr 0x20000 level 6 (softpri 3)
>> zstty0 at zsc1 channel 0 (console)
>> zstty1 at zsc1 channel 1
>> eeprom0 at obio0 addr 0x40000
>> clock0 at obio0 addr 0x60000 level 5
>> memerr0 at obio0 addr 0x80000 (ECC memory)
>> intreg0 at obio0 addr 0xa0000
>> ie0 at obio0 addr 0xc0000 level 3 hwaddr 08:00:20:01:78:72
>> obmem0 at mainbus0
>> vmes0 at mainbus0
>> si_vmes_match: May be an `sc' board at pa=0xff200000
>
>This is almost certainly the problem: you quite likely do have an sc.
>NetBSD does not currently support the sc, only the si. I have some
>fragments of support implemented, but am stalled for two reasons: (1)
>my machine with an sc is currently not in a usable state because the
>monitor for its display died, and (2) I've seen weird misbehavior I
>have no handle on - different devices seem to fail in grossly different
>ways. If you have a sun3 development environment on another machine, I
>will be happy to give you the fragmentary driver I have. It surely
>needs work, as the last time I did anything with it was pre-1.3.
>
> der Mouse
>
> mouse@rodents.montreal.qc.ca
> 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
>
>
Sincerely,
Rick Copeland
Information Systems Manager
InterMag, Inc.
(916) 568-6744 x36