[99361] in RedHat Linux List
Re: Wanted, SCSI bus trick
daemon@ATHENA.MIT.EDU (tom@jeeves.seaslug.org)
Fri Nov 13 17:33:14 1998
Date: Fri, 13 Nov 1998 14:26:27 +0000 (PST)
From: tom@jeeves.seaslug.org
To: redhat-list@redhat.com
In-Reply-To: <Pine.LNX.3.96.981106220123.519A-100000@jeeves.seaslug.org>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
On Fri, 6 Nov 1998 tom@jeeves.seaslug.org wrote:
> What does it take to cause a SCSI device to be recognized by the kernel
> after boot time.
>
> Problem here is that I'm using a scanner - seldome used. If it is turned
> on at boot time, it can be turned off and will be recognized by the kernel
> when I go to scan. But, if it fail to turn on the scanner at boot time,
> the kernel knows nothing of it and I have to reboot to use the scanner - a
> drag.
>
> Is there a way to get the kernel to take a look at the SCSI devices after
> boot time, so I can talk to t he scanner even it it wasn't on at boot
> time?
Thought I would post the very favorable results. The answer is yes, it
can be done.
Turns out this is all documented in the SCSI-Programming howto.
My only controler is an aging but reliable Adaptec 1542CF - if anyone
cares, but I don't think it matters.
My scanner device id is 6, so the command:
echo "scsi remove-single-device 0 0 6 0" > /proc/scsi/scsi
removed the device successfully. And the command:
echo "scsi add-single-device 0 0 6 0" > /proc/scsi/scsi
adds the device.
Thanks to all who responded to this, especially Cokey de Percin.
================================================
Red Hat Linux! Where I really went today!
Please send personal replies to:
thos@jeeves.seaslug.org
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
