Date: Mon, 6 Mar 1995 19:29:00 -0500 (EST) From: Peter Dufault <dufault@hda.com> To: roberto@blaise.ibp.fr Cc: freebsd-current@FreeBSD.org Subject: Re: New SCSI config Message-ID: <199503070029.TAA05197@hda.com> In-Reply-To: <199503062224.XAA06988@keltia.frmug.fr.net> from "Ollivier Robert" at Mar 6, 95 11:24:33 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Ollivier Robert writes:
>
> ------------------------------------------------------------
> # new wired down SCSI devices
> disk sd0 at scbus0 target 0 unit 0
> disk sd1 at scbus0 target 1
> tape st0 at scbus0 target 4
> device cd0 at scbus0 target 6
>
> device sd0 #Only need one of these, the code dynamically grows
> device st0 #Only need one of these, the code dynamically grows
> device cd0 #Only need one of these, the code dynamically grows
> ------------------------------------------------------------
>
> With or without the last three lines, config -- newly recompiled of course
> -- gives me these messages :
You can remove the last three lines; they won't do anything.
>
> 321 [23:12] root@keltia:i386/conf# config KELTIA
> Removing old directory ../../compile/KELTIA: Done.
> sd0: Warning, can't tell what is attached to scbus0.
> sd1: Warning, can't tell what is attached to scbus1.
> st0: Warning, can't tell what is attached to scbus0.
> cd0: Warning, can't tell what is attached to scbus0.
You haven't missed anything; I may have.
This warning is saying that the wired down devices are wired
to something that can float, so that if you add another host
adapter your devices might move.
If you add something like:
> controller scbus0 at aha0
or whatever corresponds to your SCSI controller is then the messages
should go away.
This is worrisome:
> sd1: Warning, can't tell what is attached to scbus1.
It should be printing out "scbus0" and not "scbus1", and a quick
look at mkioconf.c shows that it is using the "wnum()" function
that foolishly sprintfs the unit into a fixed buffer and so can't
be used twice in a single printf. Grumble. Trust me, it really means
it can't tell what is attached to scbus0.
I should perhaps clarify the warning to:
> sd0: Warning, scbus0 is not fixed and could change
The resulting kernel should work fine; I config'd it
here and the table entry for sd1 is (check bottom of ioconf.c
in your compile directory):
>/* name unit cunit target LUN flags */
> { "sd", 1, 0, 1, SCCONF_UNSPEC, 0x0 },
with sd1 wired to whatever happens to be SCSI bus 0 for target
1 and LUN unspecified.
Peter
--
Peter Dufault Real Time Machine Control and Simulation
HD Associates, Inc. Voice: 508 433 6936
dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503070029.TAA05197>