yup, i had the exact same problems with the remote. stracing the
process showed all they keypresses, but nothing showed up in irw. it
was the lirc.conf file. I've got a "new" hauppauge remote, one with a
grey top and black bottom.
i've not done this but i've heard/read you can create your own conf
file with irrecord.
On Sun, 6 Feb 2005 10:48:44 -0800 (PST), Joe Rizzo <[EMAIL PROTECTED]> wrote:
> I have posted this to the lirc mailing list, but figured it would be worth
> posting here as many MythTV users are using the PVR-350.
>
> I am unable to use the PVR-350 remote. I never see output when running irw.
>
> The system I am running on is Fedora Core 3 with the 2.6.9-1.724_FC3 kernel.
>
> -- The driver loads --
> # /sbin/modprobe lirc_i2c
>
> # dmesg
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> ivtv: i2c attach [client=Hauppauge IR,ok]
> lirc_dev: lirc_register_plugin:sample_rate: 10
>
> # lsmod |grep lirc
> lirc_i2c 9092 0
> lirc_dev 13708 1 lirc_i2c
> i2c_core 22081 8
> lirc_i2c,bttv,msp3400,saa7127,saa7115,tuner,tveeprom,i2c_algo_bit
>
> # ls -la /dev/lirc*
> crw-r--r-- 1 root root 61, 0 Feb 6 07:57 /dev/lirc0
>
> -- If I cat /dev/lirc0 and press buttons on the remote, I see output. -- #
> cat /dev/lirc0 | od -ch
> 0000000 037 340 037 340 037 340 037 340 037 340 027 320 027 320 027 320
> e01f e01f e01f e01f e01f d017 d017 d017
> 0000020 027 320 027 320 027 320 037 341 037 341 037 341 037 341 037 341
> d017 d017 d017 e11f e11f e11f e11f e11f
> 0000040 027 321 027 321 027 321 027 321 027 321 027 321 027 321 037 305
> d117 d117 d117 d117 d117 d117 d117 c51f
> 0000060 027 305 027 306 027 306 037 301 027 302 037 303 037 303 027 306
> c517 c617 c617 c11f c217 c31f c31f c617
> 0000100 027 306 037 304 037 304 027 305 027 305 037 306 027 307 027 307
> c617 c41f c41f c517 c517 c61f c717 c717
>
> -- lircd runs and attches to /dev/lirc0. If I run irw and strace the
> lircd process, I see lircd reading from /dev/lirc0. I do not see it
> writing however. irw attaches to /dev/lircd. --
>
> # lircd -d /dev/lirc0 -n
> # ls -l /dev/lirc*
> crw-r--r-- 1 root root 61, 0 Feb 6 07:57 /dev/lirc0
> srw-rw-rw- 1 root root 0 Feb 6 08:02 /dev/lircd
>
> # irw
>
> # strace -p 1532
> Process 1532 attached - interrupt to quit
> select(8, [4 6 7], NULL, NULL, NULL) = 1 (in [7])
> gettimeofday({1107705875, 168161}, NULL) = 0
> read(7, "\27\375", 2) = 2
> gettimeofday({1107705875, 168401}, NULL) = 0
> gettimeofday({1107705875, 168508}, NULL) = 0
> select(8, [4 6 7], NULL, NULL, NULL) = 1 (in [7])
> gettimeofday({1107705875, 270118}, NULL) = 0
> read(7, "\27\375", 2) = 2
>
> # lircd -d /dev/lirc0 -n
> lircd 0.7.1pre1: lircd(hauppauge) ready
>
> lircd 0.7.1pre1: accepted new client on /dev/lircd
> lircd 0.7.1pre1: removed client
>
> ----
> I have tried lirc versions 0.7.0 and 0.7.1pre1. I have seen posts with
> simular symptoms. Could someone point me in the right direction for
> resloving this?
>
> Based on the strace I think lircd is not writing to /dev/lircd.
>
> Any help is appreciated,
> Joe
>
> _______________________________________________
> 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
