I was thinking I did have the recommended driver for the PVR-350 but now im not so sure. I tryed running the fallowing comand:
[EMAIL PROTECTED] backup]# irrecord --device /dev/lirc0 /etc/lircd.conf irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus([EMAIL PROTECTED]) irrecord: could not init hardware (lircd running ? --> close it, check permissions) then from /var/log/messages Jan 10 23:34:41 mythtv irrecord: could not open /dev/lirc0 Jan 10 23:34:41 mythtv irrecord: default_init(): No such device or address yet [EMAIL PROTECTED] backup]# ls -l /dev/lir* lrwxrwxrwx 1 root root 10 Jan 10 19:23 /dev/lirc -> /dev/lirc0 crwxrwxrwx 1 mythtv mythtv 212, 0 Jan 10 19:23 /dev/lirc0 srw-rw-rw- 1 mythtv mythtv 0 Jan 10 19:23 /dev/lircd if I try running the command with the other devices in the list i get the same messages except with the /dev/lircd dev Jan 10 23:38:12 mythtv irrecord: could not connect to unix socket /dev/lircd Jan 10 23:38:12 mythtv irrecord: default_init(): Connection refused I downloaded the ivit software using yum as shown below. thanks -Matt Quoting Adam Propeck <[EMAIL PROTECTED]>: > Do you know the recommended driver for your device? The best thing to do is > leave lircd not running. Unless you've copied a valid /etc/lircd.conf file > over, it won't do any good really anyhow. I run (as root) "irrecord -H uirt2 > --device /dev/ttyUSB0 test.conf" You should try replacing the uirt2 with > either the driver that your IR receiver calls for, or simply use "irrecord > --device /dev/something test.conf" where something is the device that your > IR is actually connected to. I'll have some better instructions out in just > a bit as I'm having some quick supper. I went back and redid my universal > remote training with VCR code 0081 as talked about on the FedoraMythology > page, and that seems to work good and give me more buttons on my remote. > Even when lircd wasn't working, when I passed the right parameters to > irrecord, I was able to get input from the remote. > > On 1/10/06, Seth Art <[EMAIL PROTECTED]> wrote: >> >> Adam, Mat, and anyone else who can help, >> >> I am having the same problem actually. I am using a different remote >> control/tuner card (leadtek WinFast cool command) however. I have been >> reading reading all of the lirc documentation over the last couple of days >> but its mostly for compiling the kernel mod and device yourself. I am using >> the atrmps distro for all of my myth/lirc stuff and these are the packages I >> have installed: >> >> [EMAIL PROTECTED] ~]# yum list *lirc* >> Setting up repositories >> Reading repository metadata in from local files >> Installed Packages >> lirc.i386 0.8.0-54_cvs20060107.rinstalled >> lirc-devices.noarch 0.7.0-1.rhfc4.at >> installed >> lirc-kmdl-2.6.14-1.1656_FC4smp.i686 0.8.0-54_cvs20060107.rinstalled >> lirc-lib.i386 0.8.0-54_cvs20060107.rinstalled >> lirc-lib-devel.i386 0.8.0-54_cvs20060107.r installed >> >> >> >> I also just have a lircd in the /dev directory: >> >> [EMAIL PROTECTED] ~]# ls -l /dev/lir* >> srw-rw-rw- 1 root root 0 Jan 10 12:41 /dev/lircd >> >> When i run "lircd -n as root I do not see any errors: >> >> [EMAIL PROTECTED] ~]# lircd -n >> lircd-0.8.0-CVS[2954]: lircd(userspace) ready >> ^H^H >> lircd-0.8.0-CVS[2954]: caught signal >> >> When I run irw it automatically kills my lircd if it is running, but does >> not sit there and listen for commands. It just exits right away. Is this >> the normal behavior? I do remember at one time that when i ran irw is >> actually did receive a signal from one of the buttons on my remote, but >> unfortunately I have made the problem worse. >> >> Any help is definitely appreciated. I can't wait to get this working so >> that I can transfer all of my myth commands from my leadtek remote to my >> all-in-on. Now that will be impressive! >> >> Thanks, >> >> Seth >> >> >> >> On 1/10/06, Adam Propeck <[EMAIL PROTECTED]> wrote: >> >> > Well, this would be specific to the remote "receiver" you are using. I'm >> > assuming that you are using the one that comes with the PVR-350. >> > >> > What do you see when you run 'ls -l /dev/lir*' as root? You should at a >> > minimum have an lircd file, but you may have an lirc0 file which might be >> > the one to point to. Also tell me the output of running 'lircd -n' >> as root. >> > You may have to run 'service lircd stop' first. Give me those and >> I'll check >> > into some of the specific PVR-350 settings in the mean time. Lirc >> was a big >> > problem for me as it seems that the directions are extremely vague for >> > anyone not using the 250 and 150. Since I have a USB Uirt, I had to figure >> > some of it out on my own. I still need to figure out how to rebuild Myth >> > with lirc support built-in. >> > >> > On 1/10/06, Matt Rude < [EMAIL PROTECTED]> wrote: >> > > >> > > So what execting file should I link to? or am I missing a file? >> > > -Matt >> > > >> > > Quoting Adam Propeck <[EMAIL PROTECTED] >: >> > > >> > > > I don't know which /dev file you should be linking the /dev/lirc >> > > file to >> > > > with the PVR-350, but I would recommend that at least while you >> > > test, just >> > > > use (as root or via sudo) 'lircd -n' to see the messages immediately >> > > and >> > > > then you don't have to go and look for them. I have a USB-UIRT, and >> > > so I >> > > > ended up having to edit the /etc/sysconfig/lircd file to show -h >> > > uirt2 >> > > > --device=/dev/ttyUSB0 I'd expect that you simply need to edit your >> > > file >> > > > appropriately. >> > > > >> > > > On 1/9/06, Matt Rude < [EMAIL PROTECTED]> wrote: >> > > >> >> > > >> I have Mythtv running on FC4 with a PVR-350. Everything is running >> > > but the >> > > >> remote control. I have installed lirc & lirc-kmdl via yum along >> > > with the >> > > >> reset >> > > >> of the Mythtv suite. I edited my modprobe.conf file and ran these >> > > >> commands. >> > > >> >> > > >> $mkdir /home/mythtv/.mythtv >> > > >> $wget http://wilsonet.com/mythtv/lircrc-haupgrey-g3.txt >> > > >> $mv lircd-haupgrey-g3.conf.txt ~/.mythtv/lircrc >> > > >> $/sbin/depmod -a >> > > >> $/sbin/modprobe lirc_i2c >> > > >> $/sbin/chkconfig lircd on >> > > >> $/sbin/service lircd start >> > > >> >> > > >> Once this is done I can try to run /usr/bin/irw and the program >> > > exits. if >> > > >> I look >> > > >> at my messages file I get as below. A list for /dev/lircd shows me. >> > > >> > > >> >> > > >> #ll /dev/lir* >> > > >> srw-rw-rw- 1 root root 0 Jan 9 20:31 /dev/lircd >> > > >> >> > > >> I know I need the lirc0 or lirc. >> > > >> >> > > >> >> > > >> What am I missing to make this work? >> > > >> any help would be nice. >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> ### tail /var/log/messages # Fresh after a reboot >> > > >> Jan 9 20:28:50 mythtv lircd-0.8.0-CVS[2280]: lircd(any) ready >> > > >> Jan 9 20:30:03 mythtv lircd-0.8.0-CVS[2280]: accepted new client >> > > on >> > > >> /dev/lircd >> > > >> Jan 9 20:30:03 mythtv lircd-0.8.0-CVS[2280]: could not get file >> > > >> information for >> > > >> /dev/lirc >> > > >> Jan 9 20:30:03 mythtv lircd-0.8.0-CVS[2280]: default_init(): No >> > > such file >> > > >> or >> > > >> directory >> > > >> Jan 9 20:30:03 mythtv lircd-0.8.0-CVS[2280]: caught signal >> > > >> Jan 9 20:31:32 mythtv lircd-0.8.0-CVS[2931]: lircd(any) ready >> > > >> Jan 9 20:31:49 mythtv lircd-0.8.0-CVS[2931]: accepted new client >> > > on >> > > >> /dev/lircd >> > > >> Jan 9 20:31:49 mythtv lircd-0.8.0-CVS[2931]: could not get file >> > > >> information for >> > > >> /dev/lirc >> > > >> Jan 9 20:31:49 mythtv lircd-0.8.0-CVS[2931]: default_init(): No >> > > such file >> > > >> or >> > > >> directory >> > > >> Jan 9 20:31:49 mythtv lircd-0.8.0-CVS [2931]: caught signal >> > > >> >> > > >> >> > > >> ### ll /dev/lirc* >> > > >> srw-rw-rw- 1 root root 0 Jan 9 20:31 /dev/lircd >> > > >> >> > > >> >> > > >> ### cat /etc/modprobe.conf >> > > >> # Enable IF >> > > >> alias char-major-61 lirc_i2c >> > > >> # From Setup >> > > >> alias eth0 e100 >> > > >> alias snd-card-0 snd-intel8x0 >> > > >> options snd-card-0 index=0 >> > > >> options snd-intel8x0 index=0 >> > > >> remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || >> > > : ; }; >> > > >> /sbin/modprobe -r --ignore-remove snd-intel8x0 >> > > >> alias usb-controller uhci-hcd >> > > >> # ivtv modules setup >> > > >> alias char-major-81 ivtv >> > > >> alias char-major-81-0 ivtv >> > > >> alias tveeprom tveeprom-ivtv >> > > >> alias msp3400 msp3400-ivtv >> > > >> install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe >> > > ivtv-fb >> > > >> install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe >> > > --ignore-install >> > > >> lirc_i2c >> > > >> install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && >> > > >> /usr/sbin/alsactl restore >/dev/null 2>&1 || : >> > > >> remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; >> > > }; >> > > >> /sbin/modprobe -r --ignore-remove snd-emu10k >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> Thanks >> > > >> Matt >> > > >> _______________________________________________ >> > > >> mythtv-users mailing list >> > > >> [email protected] >> > > >> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >> > > >> >> > > > >> > > >> > > >> > > _______________________________________________ >> > > mythtv-users mailing list >> > > [email protected] >> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >> > > >> > >> > >> > _______________________________________________ >> > mythtv-users mailing list >> > [email protected] >> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >> > >> > >> > >> >> _______________________________________________ >> mythtv-users mailing list >> [email protected] >> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >> >> >> > _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
