From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug/coldplug loads modules but doesn't bind correctly to a device
Date: Tue, 22 Feb 2005 12:47:23 +0000 [thread overview]
Message-ID: <20050222124723.GA26544@vrfy.org> (raw)
In-Reply-To: <200502272044.01952.javi@gsmlandia.com>
On Sun, Feb 27, 2005 at 08:44:01PM +0000, Javi wrote:
> Hi list.
>
> I'm runing a pure udev system with hotplug and coldplug. Coldplug loads well the kernel modules but it doesnt' bind them to a device.
> Building the drivers statically, devices are correctly binded. Building the driver as a kernel module and manually loading them with "modprobe" works well.
> But if modules are loaded at boot time by coldplug , no devices are binded.
>
> At the moment, the missing devices are
> -Although emu10k1, soundcore and ac97_codec are loaded, /dev/dsp, /dev/mixer and /dev/sound/* are missing
> -Although parport, parport_pc and ppdev are loaded, /dev/parport* and /dev/parport/* are missing.
> -Although rtc is loaded, /dev/rtc is missing
>
> Why devices are not created at boot time? How can I solve it?
Are these devices represented in sysfs and you just miss the device nodes?
Thanks,
Kay
And fix your systems date. :)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-02-22 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 19:45 Hotplug/coldplug loads modules but doesn't bind correctly to a device Javi
2005-02-22 12:47 ` Kay Sievers [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=20050222124723.GA26544@vrfy.org \
--to=kay.sievers@vrfy.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).