From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lirc and mceusb2 - no /dev/lirc0 node
Date: Mon, 19 Jan 2009 20:44:24 +0900 [thread overview]
Message-ID: <1232365464.15091.33.camel@rattus> (raw)
In-Reply-To: <20090119112132.0b1e75d3@krikkit>
Thanks Niel,
the symptoms are the same, but I know I need a kernel module and the
module is loaded, but no node is formed except the /dev/lircd from lircd
itself. It looks like udev is not triggering node creation when the
mceusb module is loaded. Will keep looking ...
BillK
On Mon, 2009-01-19 at 11:21 +0000, Neil Bothwick wrote:
> On Mon, 19 Jan 2009 19:17:28 +0900, William Kenworthy wrote:
>
> > However, inserting the lirc_mceusb2 module and starting lircd doesnt
> > give any lirc nodes in /dev except for /dev/lircd. Previously I
> > had /dev/lirc0. Ive gone back to the older 2.6.23 kernel - now there is
> > no /dev/lirc0 with that one also, either before or after rebuilding
> > lirc :(
>
> Try this http://bugs.gentoo.org/show_bug.cgi?id=189022
>
>
--
William Kenworthy <billk@iinet.net.au>
Home in Perth!
prev parent reply other threads:[~2009-01-19 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 10:17 [gentoo-user] lirc and mceusb2 - no /dev/lirc0 node William Kenworthy
2009-01-19 11:21 ` Neil Bothwick
2009-01-19 11:44 ` William Kenworthy [this message]
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=1232365464.15091.33.camel@rattus \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.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