All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: rawhide hotplug broken
Date: Wed, 11 Apr 2001 00:39:25 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98694962525171@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98692454026185@msgid-missing>

>    In case folks here are unaware, RedHat has been hacking
> the hotplug srpm releases here for their rawhide releases
> (and I assume their upcoming RH 7.1 release) doing such things
> as removing the rc scripts from hotplug.

It'd be interesting to know why that isn't being included.

Despite what Trond said (in a separate email on this thread), it
does more than just load modules; it also mounts "usbdevfs" at
the _right_ time (before USB host controller modules load) to
deal with some boot-time hotplugging ("cold-plugging") issues
that come up in some configurations ... like the way RedHat 7.0
initialized USB, or the last 7.1 init scripts I saw did.

Also, perhaps of more relevance to USB developers, "rc.usb"
provides some simple USB diagnostics ("rc.usb status") and
makes it easy to start, stop, and restart the USB subsystem.


>     On my linuxppc (running
> Linux 2.4.4pre1, glibc 2.2.3 and the rawhide srpms), I find
> that RedHat's modified hotplug doesn't work for loading the
> usb print module when it sees my Epson 740i printer. ...

Well, I did notice RedHat wasn't using current RPMs,
but I don't think that'd be the whole problem.


>    I discovered last night that if I installed the latest 
> hotplug-2001_02_28 and usbutils-0.7-101 rpms on my machine
> that the usb print module was loaded on boot or hotplugging
> the Epson 740i printer. I also discovered that I had to have
> usbutils installed for the hotplugging to work. 

Curious.  Can you try debugging the script invocation to see
why?  I usually:  (a) modify /sbin/hotplug to "env >/tmp/debug";
(b) insert the device, (c) modify a copy of that /tmp/debug file
and turn it into a script that exports all variables (or at least the
six used by USB hotplug :) and then does something like

    cd /etc/hotplug
    sh -x usb.agent

Then there's copious debug output (save it to a log file) which
can be examined ... in this case, to see why the "printer" driver
listing in /lib/modules/.../modules.usbmap doesn't match.

- Dave




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-04-11  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 17:41 rawhide hotplug broken Jack Howarth
2001-04-10 18:50 ` Trond Eivind Glomsrød
2001-04-10 18:57 ` Jack Howarth
2001-04-10 20:21 ` Bill Nottingham
2001-04-11  0:39 ` David Brownell [this message]
2001-04-11  1:03 ` Bill Nottingham
2001-04-11  1:11 ` David Brownell

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=marc-linux-hotplug-98694962525171@msgid-missing \
    --to=david-b@pacbell.net \
    --cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.