Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] udev 171 is broken
Date: Tue, 31 May 2011 19:25:52 +0200	[thread overview]
Message-ID: <is38b0$k1j$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTimE2Y=zrWtyWPKekDeUpcmdfFNENA@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31-05-11 18:39, Otavio Salvador wrote:
> On Tue, May 31, 2011 at 15:27, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Hmm, it works on all the platforms I tested. What kind of failures are
>> you getting? And more importantly, which kernel versions are you using?
> 
> It doesn't load any module on the system. I am using 2.6.37 and it
> does work fine with udev 164 and previous meta-oe one too.

That's expected, the OE modprobe rule move to udev-extra-rules:

http://cgit.openembedded.org/cgit.cgi/meta-openembedded/commit/?id=7aa7dd55db8db6ec350c743ce42eb469395a3208

I was thinking of putting it back in, could you try creating a rule with

ACTION=="add", DEVPATH=="/devices/*", ENV{MODALIAS}=="?*",
RUN+="/sbin/modprobe $env{MODALIAS}"

and rebooting?

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN5SSgMkyGM64RGpERAkG5AJ4x3sF4pb0ahPW7zW7uSMHVy788dQCfYc4g
KjXhd+Ih2usYzPLftl6ewBc=
=RUMT
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-05-31 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 15:13 [meta-oe] udev 171 is broken Otavio Salvador
2011-05-31 15:27 ` Koen Kooi
2011-05-31 16:39   ` Otavio Salvador
2011-05-31 17:25     ` Koen Kooi [this message]
2011-05-31 18:19       ` Otavio Salvador
2011-06-01  8:04         ` Koen Kooi

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='is38b0$k1j$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox