[pvrusb2] IR help linux newbie

Ryan Schmitz rrschmitz at gmail.com
Fri Dec 29 21:28:15 CST 2006


Ok,

So I made some changes, but I'm still not any closer to a solution
unfortunately.

I used the commands you suggested:
mknod /dev/lirc0 c 61 0
ln -s /dev/lirc0 /dev/lirc

And now I have this:
[root at schmitzerLNX dev]# ls -l /dev/lir*
lrwxrwxrwx 1 root root    10 Dec 29 22:06 /dev/lirc -> /dev/lirc0
crw-r--r-- 1 root root 61, 0 Dec 29 22:05 /dev/lirc0
srw-rw-rw- 1 root root     0 Dec 29 22:09 /dev/lircd

*I noticed I don't have lircm, could this be an issue?
Also before I ran mknod and ln -s, lircd was the only one listed.  Should
lirc already exist or does that just get created during the ln -s step?

Then I restarted the lircd service, and still no luck.  Here is the
messages:

Dec 29 22:09:26 schmitzerLNX lircd-0.8.1-CVS[3106]: lircd(userspace) ready
Dec 29 22:09:29 schmitzerLNX lircd-0.8.1-CVS[3106]: accepted new client on
/dev/lircd
Dec 29 22:09:29 schmitzerLNX lircd-0.8.1-CVS[3106]: could not open
/dev/lirc0
Dec 29 22:09:29 schmitzerLNX lircd-0.8.1-CVS[3106]: default_init(): No such
device
Dec 29 22:09:29 schmitzerLNX lircd-0.8.1-CVS[3106]: caught signal

*Same errors as before, but now I do have lirc0 created via mknod

Also here is my lirc.rules file if that helps at all
KERNEL=="lirc[0-9]*",   NAME="lirc%n"
KERNEL=="lirc0",                SYMLINK="lirc"


On 12/29/06, Roger J. Allen <rja at firkraag.rogera.net> wrote:
>
> On Thu, 28 Dec 2006, Ryan Schmitz wrote:
>
> > Date: Thu, 28 Dec 2006 13:55:46 -0500
> > From: Ryan Schmitz <rrschmitz at gmail.com>
> > Reply-To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> > To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> > Subject: Re: [pvrusb2] IR help linux newbie
> >
> > Thanks, I have tried that before with little luck, but I will try it
> > again....ok done.  I still can't get the remote to work.
> >
> > When I follow Jarods instructions and start the lircd, the start says
> OK.
> > Then if I run /usr/bin/irw, it doesn't do anything, and lircd seems to
> > crash.
> >
> > Here is the output from my /var/log/messages:
> >
> > Dec 28 13:51:36 schmitzerLNX lircd-0.8.1-CVS[8392]: accepted new client
> on
> > /dev/lircd
> > Dec 28 13:51:36 schmitzerLNX lircd-0.8.1-CVS[8392]: could not get file
> > information for /dev/lirc/0
>
> The lirc device file doesn't exist.  I think that file should be created
> by
> udev.  The atrpms mythtv-suite installs a lirc-devices rpm which addes a
> lirc.rules to udev.  Those lirc rpms were compiled to use /dev/lirc0 thru
> /dev/lirc9 while your binaries are looking for a /dev/lirc/0.  Maybe that
> is a configure option for compiling lircd.
>
> I have these devices:
>
> [root at firkraag ~]# ls -l /dev/lir*
> lrwxrwxrwx 1 root root     5 Dec 26 12:30 /dev/lirc -> lirc0
> crw------- 1 root root 61, 0 Dec 26 12:30 /dev/lirc0
> srw-rw-rw- 1 root root     0 Dec 26 12:30 /dev/lircd
> prw-r--r-- 1 root root     0 Dec 28 00:44 /dev/lircm
>
> You might need to use:
>
> ls -l /dev/lirc/*
>
>
> I guess that you either need to add a udev rule to create the lirc device
> files at boot time or create them with the mknod command.  Something like
> this:
>
> mknod /dev/lirc/0 c 61 0
>
> and maybe:
>
> ln -s /dev/lirc/0 /dev/lirc
>
> > Dec 28 13:51:36 schmitzerLNX lircd-0.8.1-CVS[8392]: default_init(): No
> such
> > file or directory
> > Dec 28 13:51:36 schmitzerLNX lircd-0.8.1-CVS[8392]: caught signal
> >
> > So whats going on here?
> >
> > Thanks again,
> > Ryan
> >
> > On 12/28/06, Roger J. Allen <rja at firkraag.rogera.net> wrote:
> >>
> >> On Thu, 28 Dec 2006, Ryan Schmitz wrote:
> >>
> >>> Date: Thu, 28 Dec 2006 11:36:18 -0500
> >>> From: Ryan Schmitz <rrschmitz at gmail.com>
> >>> Reply-To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> >>> To: pvrusb2 at isely.net
> >>> Subject: [pvrusb2] IR help linux newbie
> >>>
> >>> Hi
> >>>
> >>> I have been having a very difficult time getting the Remote to work
> with
> >> the
> >>> PVRUSB2, and I could really use some help.  I'm sure this has probly
> >> been
> >>> covered before, but i searched the forums and couldn't find anything
> >> that
> >>> helped me yet.
> >>>
> >>> So first off, I want to point out I'm pretty new at Linux, I just
> >> starting
> >>> working with it to use Mythtv, so step by step instructions would be
> >> nice.
> >>>
> >>> About my setup:
> >>> Fedora Core 6
> >>> PVRUSB2 driver 12/27
> >>> WinTV PVR USB2  24xxx
> >>> lircd 0.8.1-CVS
> >>>
> >>> What I've done:
> >>> I compiled the driver, ran fwextract on the driver from the CD, and
> >>> transfered the 4 v41* files to /lib/firmware.
> >>> The PVR plays live TV and Records just fine.  Its just the remote I
> >> can't
> >>> get to work.
> >>>
> >>> I've tried many things, but currently all I have done is add:
> >>>
> >>> alias char-major-61  lirc_i2c
> >>>
> >>> to my /etc/modprobe.conf file
> >>>
> >>>
> >>> So what am I missing, or what have I done wrong.  I've been trying to
> >> figure
> >>> this out for two weeks, and I give up.
> >>
> >> For instructions on setting up lirc (along with mythtv) on FC6,
> >> this link spells out what you need to do:
> >>
> >> http://wilsonet.com/mythtv/fcmyth.php#lirc
> >>
> >> It uses pre-built packages from atrpms, but since you already have
> >> compiled lirc from source, you can skip the "yum install" steps.
> >>
> >> Choose the "Using the IR port on a PVR-x50:" section.
> >> When it mentions "ivtv" substitute "pvrusb2".
> >>
> >> If you still have problems after reading this link, I'll be glad to
> help.
> >>
> >>>
> >>> Thanks,
> >>> Ryan
> >>
> >> --
> >> Roger J. Allen
> >
>
> --
> Roger J. Allen
> Internet: rja at rogera.net
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>


More information about the pvrusb2 mailing list