From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] /run/udev missing ?
Date: Tue, 16 Aug 2011 10:40:59 +0200 [thread overview]
Message-ID: <1313484062.2127.13.camel@sven> (raw)
In-Reply-To: <87ty9kh4sh.fsf@macbook.be.48ers.dk>
On Sun, 2011-08-14 at 08:43 +0200, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
>
> Sven> Hi,
> Sven> after updating to latest buildroot, udevd has problems starting:
>
> Sven> udevd[1114]: error: runtime directory '/run/udev' not writable, for now
> Sven> falling back to '/dev/.udev'
> Sven> udevd[1114]: failed to create queue file: No such file or directory
> Sven> udevd[1114]: error creating queue file
>
> Sven> It looks like udevd is not running or not working properly then as it
> Sven> fails to load the firmware for the Wifi chip.
>
> Sven> This is a configuration with static device management.
>
> All other configurations than static dev (devtmpfs/mdev/udev) expects
> CONFIG_DEVTMPFS_MOUNT to be enabled in the kernel, not a static /dev.
Do you have a suggestion on how to use udev with a kernel that does not
yet have this option? We are stuck with 2.6.31 on one of our platforms
and I haven't been able to get udev working with recent buildroot on
this platform.
Sven
next prev parent reply other threads:[~2011-08-16 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 8:29 [Buildroot] /run/udev missing ? Sven Neumann
2011-08-14 6:43 ` Peter Korsgaard
2011-08-15 8:21 ` Sven Neumann
2011-08-15 9:05 ` Peter Korsgaard
2011-08-15 9:34 ` Sven Neumann
2011-08-15 12:10 ` Peter Korsgaard
2011-08-15 14:01 ` Sven Neumann
2011-08-15 14:18 ` Daniel Mack
2011-08-15 14:24 ` Baruch Siach
2011-08-16 8:40 ` Sven Neumann [this message]
2011-08-16 11:59 ` Diego Iastrubni
2011-08-16 12:44 ` Michael S. Zick
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=1313484062.2127.13.camel@sven \
--to=s.neumann@raumfeld.com \
--cc=buildroot@busybox.net \
/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