> >> On Fri, 2006-06-02 at 12:09 -0700, Simon Baxter wrote: >> >>> [EMAIL PROTECTED] ~]# lsmod | grep lirc >>> lirc_pvr150 18368 0 >> >> Fascinating, I had never heard of a lirc_pvr150 module before. Mine >> works with just lirc_dev and lirc_i2c. (I'll have to check which version >> of LIRC I have when I get home; the machine with the PVR-150 is a slave >> backend/frontend in the living room which is not kept on all the time). >> >> --Greg > > so you're just using the latest LIRC, and not the one from > http://www.blushingpenguin.com/mark/blog/ and it works fine? > > can you send me a 'dmesg | grep tv' - which version of card are you using?
I tried the latest CVS of lirc - get much the same: Jun 2 12:53:02 media.nzbaxters lircd: lircd(hauppauge) ready Jun 2 12:54:07 media.nzbaxters lircd: accepted new client on /dev/lircd Jun 2 12:54:07 media.nzbaxters lircd: could not open /dev/lirc0 Jun 2 12:54:07 media.nzbaxters lircd: default_init(): No such device Jun 2 12:54:07 media.nzbaxters lircd: caught signal lirc_dev: IR Remote Control driver registered, at major 61 bttv: driver version 0.9.16 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture cx2388x v4l2 driver version 0.0.5 loaded lirc_dev ([-1]): open called lirc_dev ([-1]): open result = -ENODEV lirc_dev ([-1]): open called lirc_dev ([-1]): open result = -ENODEV lirc_dev ([-1]): open called lirc_dev ([-1]): open result = -ENODEV _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
