From: Ben Collins <bcollins@debian.org>
To: Jocelyn Mayer <jma@netgem.com>
Cc: Georg Nikodym <georgn@somanetworks.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2
Date: Tue, 3 Jun 2003 14:54:21 -0400 [thread overview]
Message-ID: <20030603185421.GB10102@phunnypharm.org> (raw)
In-Reply-To: <1054663917.4967.99.camel@jma1.dev.netgem.com>
> First, I never trust hotplug or other tools like this:
> I do all insmod by hand, so I know all drivers have been loaded.
> What is hotplug supposed to do (but wasn't in previous driver
> version...) ?
I didn't say CONFIG_HOTPLUG, I said hotplug. Basically SCSI in 2.4 will
not let recognize devices that were not present when the scsi-host was
initially registered with the SCSI stack. You have to run
rescan-scsi-bus.sh (or manually send the add/remove commands via
procfs).
Please read the linux-kernel and/or linux1394-devel mailing list
archives. I really hate dredging this all up again.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-06-03 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 19:36 [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2 Jocelyn Mayer
2003-06-02 20:34 ` Georg Nikodym
2003-06-02 21:20 ` Jocelyn Mayer
2003-06-03 11:36 ` Ben Collins
2003-06-03 18:11 ` Jocelyn Mayer
2003-06-03 18:27 ` Georg Nikodym
2003-06-03 19:01 ` Jocelyn Mayer
2003-06-03 19:34 ` Richard B. Johnson
2003-06-03 18:54 ` Ben Collins [this message]
2003-06-03 20:20 ` Jocelyn Mayer
2003-06-03 19:26 ` Ben Collins
2003-06-03 21:12 ` Jocelyn Mayer
2003-06-03 19:28 ` Ben Collins
2003-06-03 20:25 ` Matthew Dharm
2003-06-03 21:12 ` Jocelyn Mayer
2003-06-03 23:01 ` Matthew Dharm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030603185421.GB10102@phunnypharm.org \
--to=bcollins@debian.org \
--cc=georgn@somanetworks.com \
--cc=jma@netgem.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).