linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <udev@dervishd.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Loading modules on demand with /sbin/hotplug
Date: Wed, 28 Feb 2007 12:45:27 +0000	[thread overview]
Message-ID: <20070228124526.GA2498@DervishD> (raw)
In-Reply-To: <20070227172320.GA10176@DervishD>

    Hi Kay :)

 * Kay Sievers <kay.sievers@vrfy.org> dixit:
> If you find MODALIAS in the environment, just run /sbin/modprobe with
> a RUN rule and almost all needed modules should get auto-loaded. There
> are only a few exceptions for exotic subsystems.

    I've done this and now the systems hangs up at bootup. I can't find
any information in any log, so I don't know the cause (probably modprobe
caused some driver to load, which caused an udev event, which caused
modprobe to run again, causing an infinite loop).

    At boot time I mount sysfs, load udevd, launch udevtrigger and
udevsettle and after that, the rest of services of my system (I use my
own init, so the boot scheme is a bit different, but not that much). The
services are launched OK.

    In my rules file I have this:

KERNEL="pty*",      OPTIONS+="ignore_device"
KERNEL="tty[a-z]*", OPTIONS+="ignore_device"

KERNEL="tty",  GROUP="tty"
KERNEL="vcs",  GROUP="tty"
KERNEL="vcsa", GROUP="tty"

KERNEL="hda1", GROUP="disk", MODE="660", SYMLINK+="root"
KERNEL="hdb1", GROUP="disk", MODE="660", SYMLINK+="ubuntu"
KERNEL="hdb2", GROUP="disk", MODE="660", SYMLINK+="swap"

KERNEL="full", MODE="222" 
KERNEL="null", MODE="666"
KERNEL="zero", MODE="444"

KERNEL="random", MODE="444"
KERNEL="urandom", MODE="444"

SUBSYSTEM="usb_endpoint", OPTIONS+="ignore_device"

SUBSYSTEM="mem", GROUP="kmem"

SUBSYSTEM="usb_device", ATTRS{serial}="5B6B0990DFC6", NAME="pendrive"

#ACTION="add", ENV{MODALIAS}="?*", RUN="/sbin/modprobe $env{MODALIAS}"
#ACTION="remove", ENV{MODALIAS}="?*", RUN="/sbin/modprobe -r $env{MODALIAS}"

RUN+="/usr/sbin/hal &>> /tmp/hal.log"

-----------------------------

    The two commented lines are the ones that caused the problem. Any
idea about the possible causes? If I move the modprobe command to my
"hal" script (IT IS NOT freedesktop HAL, but my own script), the problem
is the same: the system hangs as soon as the booting process finishes,
and I don't have any evidence of modprobe being hung or whatever.

    I think I'm missing something VERY simple here, but I can't see
what: have you any idea about which the problem may be? Should I delete
the second commented line and don't unload modules on demand? May any of
the commented lines be causing an infinite loop?

    Thanks a lot in advance and sorry for bothering you with this kind
of questions. If I'm crossing the line, please tell O:)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2007-02-28 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 17:23 Loading modules on demand with /sbin/hotplug DervishD
2007-02-27 17:45 ` DervishD
2007-02-27 19:16 ` Kay Sievers
2007-02-27 20:17 ` DervishD
2007-02-28 12:45 ` DervishD [this message]
2007-02-28 15:36 ` Kay Sievers
2007-02-28 19:26 ` Dan Nicholson
2007-02-28 22:02 ` DervishD
2007-02-28 22:05 ` DervishD
2007-02-28 22:20 ` Kay Sievers
2007-03-01  8:42 ` DervishD

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=20070228124526.GA2498@DervishD \
    --to=udev@dervishd.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 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).