From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 038 release
Date: Fri, 15 Oct 2004 11:20:26 +0000 [thread overview]
Message-ID: <20041015112026.GC5024@vrfy.org> (raw)
In-Reply-To: <20041014003936.GA8810@kroah.com>
On Fri, Oct 15, 2004 at 11:07:56AM +0200, Prakash K. Cheemplavam wrote:
> Hi,
>
> going from udev-036 to 038 on gentoo resulted in following problem for me:
>
> I load the nvidia module via /etc/modules.autoload.d/kernel-2.6. With
> udev-036 the device nodes eventually were created fast enough so that
> kdm could start. With udev-038 it is not the case. The boot ends at the
> log-in, and I have to manually start kdm.
>
> What is the right way to get this going?
Is there anything in the syslog regarding this?
Do you use the latest bitkeeper version or the "real" v038?
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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
next prev parent reply other threads:[~2004-10-15 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 0:39 [ANNOUNCE] udev 038 release Greg KH
2004-10-14 7:09 ` Frank Steiner
2004-10-14 13:56 ` Kay Sievers
2004-10-14 10:14 ` Arkadiusz Miskiewicz
2004-10-14 18:46 ` Greg KH
2004-10-15 9:07 ` Prakash K. Cheemplavam
2004-10-15 11:20 ` Kay Sievers [this message]
2004-10-15 15:23 ` Prakash K. Cheemplavam
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=20041015112026.GC5024@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).