All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Angstrom, udev, and kernel version
Date: Wed, 24 Feb 2010 03:28:04 -0500	[thread overview]
Message-ID: <20100224082804.GB17798@denix.org> (raw)
In-Reply-To: <4B84DE66.4080602@dresearch.de>

On Wed, Feb 24, 2010 at 09:08:06AM +0100, Steffen Sledz wrote:
> Since Angstrom updated to udev_151 we've a big problem.
> 
> 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. Unfortunately we are forced to use 2.6.24 because of special driver/machine support for hipox. :(
> 
> Is there a way to rollback to udev_141 for hipox machine?
> 
> Or is there a backport patch available for 2.6.24 to support udev_151?

You can add the following line to either your conf/local.conf or 
conf/distro/include/angstrom-2008-preferred-versions.inc:

PREFERRED_VERSION_udev_hipox = "141"

I too learned that udev-151 (>147) requires glibc-2.9 or higher. Seems like a 
very demanding version of udev...

-- 
Denys



  reply	other threads:[~2010-02-24  8:30 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 [this message]
2010-02-24 11:26 ` Koen Kooi
2010-02-25  8:06   ` Steffen Sledz
2010-02-25  8:44     ` Koen Kooi
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=20100224082804.GB17798@denix.org \
    --to=denis@denix.org \
    --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.