> -----Original Message----- > From: Marius Schrecker [mailto:[EMAIL PROTECTED] > Sent: Sunday, October 02, 2005 6:26 AM > To: Steve ; Discussion about mythtv > Subject: Re: [mythtv-users] [OT] Remote Help > > > Sooo can anyone help me? > > > > On 10/1/05, Steve G <[EMAIL PROTECTED]> wrote: > >> > >> > -----Original Message----- > >> > From: [EMAIL PROTECTED] [mailto:mythtv-users- > >> > [EMAIL PROTECTED] On Behalf Of Marius Schrecker > >> > Sent: Saturday, October 01, 2005 4:28 AM > >> > To: Discussion about mythtv > >> > Subject: Re: [mythtv-users] [OT] Remote Help > >> > > >> > > Did /dev/lirc exist before you started irw ? Did you set the access > >> > rights > >> > > on the lirc* devices ? > >> > > > >> > > Niels Dybdahl > >> > > ----- Original Message ----- > >> > > From: Steve > >> > > To: Discussion about mythtv > >> > > Sent: Saturday, October 01, 2005 7:39 AM > >> > > Subject: [mythtv-users] [OT] Remote Help > >> > > > >> > > > >> > > A friend of mine gave me an "ATI Remote Wonder" remote and usb > >> > receiver. > >> > > From my understanding it is a RF setup here, not an IR setup. > >> > > I am running gentoo, so someone told me I needed to emerge lirc > when > >> I > >> > > have LIRC_OPTS="--with-driver=atiusb" in my make.conf. So I did "# > >> > > emerge unmerge lirc" and then I did "emerge --newuse lirc". The > >> problem > >> > > I have is I start lircd by doing "# lircd -n" It says whatever it > >> > > says... then I log in to another terminal as a normal user and do > "$ > >> > > irw". This just brings me back to "$ " and causes the "# lircd -n" > >> that > >> > > I ran to crash whilst complaining about not finding /dev/lirc. > >> > > > >> > > Any help is greatly appreciated. > >> > > > >> > > > >> > This sounds very much like the problem I had with my usb receiver. > >> > > >> > What are you getting in /var/log/messages when you start lircd? > >> Oct 1 12:32:55 MythTv lircd-0.7.2[21570]: lircd(atiusb) ready > >> When I start irw and go back to the console I started "lircd -n" on I > >> see > >> this: > >> MythTV ~ # lircd -n > >> lircd-0.7.2[21632]: lircd(atiusb) ready > >> lircd-0.7.2[21632]: accepted new client on /dev/lircd > >> lircd-0.7.2[21632]: could not get file information for /dev/lirc > >> lircd-0.7.2[21632]: default_init(): No such file or directory > >> lircd-0.7.2[21632]: caught signal > >> Terminated > >> MythTV ~ # > >> > >> > I had to symlink my /dev/lirc node to /dev/usb/hiddev0 (your usb > >> device > >> > may well be different). > >> I'm not sure where my USB device is... I've tried various ls's in /dev > >> to > >> find it to no avail. But I gather this much from what you're saying: "# > >> ln > >> -s /dev/lircd /dev/lirc" or am I way off? > >> > >> > If the driver needs a module has this been built and installed, and > >> does > >> > it load? > >> I'm not sure what you mean here, but I have built lirc with "atiusb" in > >> the > >> LIRC_OPTS in my make.conf. > >> > >> > Are you running udev? This should take care of your /dev node > mappings > >> for > >> > you. Unfortunately I can't on my system. > >> > >> Yea, I do have udev... > > udev will probably help you later, if you can figure ouot how to set up > rules for it, I'm afraid I can't help you there. > > First I think you should try to ascertain if your /dev/lirc should be > symlinked to anything else. Make a note of the node major and minor > numbers so you can recreate it later: > > #ls -la /dev |grep lirc When I do this it only shows me /dev/lircd
> then try linking to your usb hid devices in turn and seeing if you can > capture ir activity: > > > # ln -s /dev/usb/hiddev0 (for example) /dev/lirc I don't have any /dev/usb* or /dev/usb/*... Which is probably why this isn't working. Other than that... Yea still doesn't work.
_______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users