linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: juuso.alasuutari@tamperelainen.org
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug and udev - a question
Date: Tue, 11 Apr 2006 10:57:16 +0000	[thread overview]
Message-ID: <1144753036.443b8b8ccb95e@cs1.alpha12.l-secure.net> (raw)
In-Reply-To: <ada605fb0603310036s68fdb8d0x3fc6d73d135ffd7e@mail.gmail.com>

Quoting Anssi Saari <as@sci.fi>:

> From a user's perspective, I'd say the advantage of getting rid of stinky
> hotplug is speed. On my desktop Debian Sarge box hotplug scripts grind
> away incredibly long stretching boot time well into annoying lenght. OTOH,
> in my Arch laptop the modules get loaded in a snap. Considering the
> Arch machine is an old Thinkpad X20 with 600 MHz CPU, you can imagine
> my pleasure when a recent Arch update did away with hotplug...
>
> Now that we are on the subject, has anyone dumped hotplug on their Debian
> Sarge machine? I think I have all the parts I need already, udev, kernel
> 2.6.15, but I'm not sure what changes I'd have to make to get rid of
> hotplug and load drivers in the udev way.

I use Source Mage, but I believe rules for module loading are more or less
universal. Here's how I was able to rid my box of hotplug.


After all other lines, at the very end of my rules file, I have these:

# Load firmware
SUBSYSTEM="firmware", ACTION="add", RUN+="/lib/udev/firmware_helper"

# Autoload modules
SYSFS{modalias}="?*", ACTION="add", RUN+="/sbin/modprobe $env{MODALIAS}"

# Autoload modules that lack aliases but have them defined in
# /etc/modprobe.conf
SUBSYSTEM="pnp", ENV{MODALIAS}!="?*", RUN+="/bin/sh -c 'while read id; do
/sbin/modprobe pnp:d$$id; done < /sys$devpath/id'"


I also have certain module aliases set in /etc/modprobe.conf:

# These are needed by udev to autoload some modules
alias pnp:dPNP0510 irtty-sir
alias pnp:dPNP0511 irtty-sir
alias pnp:dPNP0700 floppy
alias pnp:dPNP0800 pcspkr
alias pnp:dPNP0b00 rtc
alias pnp:dPNP0303 atkbd
alias pnp:dPNP0f13 psmouse
alias pnp:dPNPb02f analog


Those edits should take care of module loading. Just make sure you remove any
previous firmware loading rules you might find in your present rules files.
The people on this list helped me earlier with this same issue, so in case I
missed or misrepresented something in this mail, check out this thread:
http://marc.theaimsgroup.com/?t\x114141804400005&r=1&w=2

Oh, and you might learn more by looking at the udev and modprobe configuration
of your Arch laptop.

Juuso Alasuutari

PS: If these rules work for you, please let me hear about it.

----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2006-04-11 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  8:36 Hotplug and udev - a question John Que
2006-03-31 10:41 ` Chris Smith
2006-03-31 17:17 ` Greg KH
2006-04-02 14:04 ` John Que
2006-04-02 20:21 ` Chris Smith
2006-04-02 20:24 ` Greg KH
2006-04-10 14:03 ` Anssi Saari
2006-04-11 10:57 ` juuso.alasuutari [this message]

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=1144753036.443b8b8ccb95e@cs1.alpha12.l-secure.net \
    --to=juuso.alasuutari@tamperelainen.org \
    --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 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).