From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Angstrom, udev, and kernel version
Date: Thu, 25 Feb 2010 09:44:09 +0100 [thread overview]
Message-ID: <hm5d8q$6c7$1@dough.gmane.org> (raw)
In-Reply-To: <4B862F8F.4050001@dresearch.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25-02-10 09:06, Steffen Sledz wrote:
> Koen Kooi wrote:
>>> udevd started from within /etc/init.d/udev crashes with
>>>
>>> /sbin/udevd -d --debug
>>> 1266997931.250494 [297] udev_monitor_new_from_netlink: error getting socket: Invalid argument error initializing netlink socket
>>> 1266997931.250718 [297] main: error initializing netlink socket
>>>
>>> Searching the internet for this error i found some hints that this udev version requires at least linux 2.6.27.
>>
>> 2.6.27 is only required for signalfd, your error seems to be about a
>> missing networking option in defconfig.
>
> Any hints, how we can isolate this problem?
The README in the udev source should have a fairly complete summary of
needed kernel options. If you use angstrom or shr linux.inc will set
them all except CONFIG_NET. So you could try rebuilding your kernel and
see if it works then. If not, compare your .config with the udev readme.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLhjhZMkyGM64RGpERAgVGAJ9UsDHvNhMSZ1Uis6z6Zbg8gwohswCgpN/t
G89BmgNucXDjiBjtlCVJjmw=
=q11y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-25 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 8:08 Angstrom, udev, and kernel version Steffen Sledz
2010-02-24 8:28 ` Denys Dmytriyenko
2010-02-24 11:26 ` Koen Kooi
2010-02-25 8:06 ` Steffen Sledz
2010-02-25 8:44 ` Koen Kooi [this message]
2010-02-24 12:05 ` Koen Kooi
2010-02-25 7:59 ` Steffen Sledz
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='hm5d8q$6c7$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.