[mythtv-users] pvr-150 ir receiver
Brad Crotchett
brad at bradandkim.net
Wed Jun 6 00:11:46 UTC 2007
On Fri, 2007-06-01 at 00:00 -0400, Francis wrote:
> Daniel:
> Yes I have the pvr-150 with the transmitter and receiver on the same
> cable ( but I don't care about the transmitter for now) plus a serial
> ir blaster. The lirc_imon is required for the VFD on my antec fusion
> case, and is loaded with LCDproc. I don't even know how the module is
> loaded because I don't start LCDproc.
> I would like to stop it from loading so I could test without any lirc
> modules loaded.
>
> I don't understand everything on how linux work yet, it's been about 2
> months I try to figure it out.
>
> What I understand is is that ivtv need to be loaded first then
> lirc_i2c which will attach to it, which obviously doesn't do because I
> don't see the message in the log file.
>
> Rusty:
> I might try the instructions you game me and rebuild lirc, so yes
> could you send your config files to me, maybe I could find some hints
> in them.
>
> Thanks
>
> 2007/5/29, Daniel Agar < daniel at agar.ca>:
> > Thanks Groepaz and Daniel for your help, I tried both of
> your suggestion
> > (except compiling the lirc module into the kernel, which I
> really don't
> > how
> > to do that), but none have worked.
> >
> > I have seen the following line from other people messages
> log file:
> >
> > ivtv0: i2c attach to card #0 ok [client=Hauppauge IR
> (PVR150), addr=71]
> >
> > but in my messages log file this line doesn't appear
> anywhere, here its
> > content, I did just include the stuff from lirc and ivtv:
> >
> > May 29 01:48:03 localhost kernel: lirc_dev: no version for
> "struct_module"
> > found: kernel tainted.
> > May 29 01:48:03 localhost kernel: lirc_dev: IR Remote
> Control driver
> > registered, at major 61
> > May 29 01:48:03 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-0.8.2/drivers/lirc_imon/lirc_imon.c:
> > Driver for Soundgraph iMON MultiMedian IR/VFD, v0.3
> > May 29 01:48:03 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-0.8.2/drivers/lirc_imon/lirc_imon.c:
> > Venky Raju <dev at venky.ws>
> > May 29 01:48:03 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-
> 0.8.2/drivers/lirc_imon/lirc_imon.c:
> > imon_probe: found IMON device
> > May 29 01:48:03 localhost kernel: lirc_dev:
> lirc_register_plugin:
> > sample_rate: 0
> > May 29 01:48:03 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-
> 0.8.2/drivers/lirc_imon/lirc_imon.c:
> > imon_probe: Registered iMON plugin (minor:0)
> > May 29 01:48:03 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-0.8.2/drivers/lirc_imon/lirc_imon.c:
> > imon_probe: iMON device on usb<4:2> initialized
> >
> > May 29 01:48:03 localhost kernel:
> ivtv: ==================== START INIT
> > IVTV ====================
> > May 29 01:48:03 localhost kernel: ivtv: version 0.10.2
> (tagged release)
> > loading
> > May 29 01:48:03 localhost kernel: ivtv: Linux version:
> > 2.6.20-1.2944.fc6SMP mod_unload 686 4KSTACKS
> > May 29 01:48:03 localhost kernel: ivtv: In case of problems
> please
> > include
> > the debug info between
> > May 29 01:48:03 localhost kernel: ivtv: the START INIT IVTV
> and END INIT
> > IVTV lines, along with
> > May 29 01:48:03 localhost kernel: ivtv: any module options,
> when mailing
> > the ivtv-users mailinglist.
> > May 29 01:48:03 localhost kernel: ivtv0: Autodetected
> Hauppauge card
> > (cx23416 based)
> > May 29 01:48:03 localhost kernel: ACPI: PCI Interrupt
> 0000:02:0a.0[A] ->
> > GSI
> > 21 (level, low) -> IRQ 20
> > May 29 01:48:03 localhost kernel: sd 0:0:0:0: Attached scsi
> generic sg0
> > type
> > 0
> > May 29 01:48:03 localhost kernel: ivtv0: loaded
> v4l-cx2341x-enc.fw
> > firmware
> > (376836 bytes)
> > May 29 01:48:03 localhost kernel: Floppy drive(s): fd0 is
> 1.44M
> > May 29 01:48:03 localhost kernel: FDC 0 is a post-1991 82077
> > May 29 01:48:03 localhost kernel: ivtv0: Encoder revision:
> 0x02060039
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: Hauppauge
> model 26132,
> > rev F1B2, serial# 10258655
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: tuner
> model is TCL
> > M2523_5N_E (idx 112, type 50)
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: TV
> standards NTSC(M)
> > (eeprom 0x08)
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: audio
> processor is
> > CX25841 (idx 35)
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: decoder
> processor is
> > CX25841 (idx 28)
> > May 29 01:48:03 localhost kernel: tveeprom 0-0050: has no
> radio, has IR
> > receiver, has IR transmitter
> > May 29 01:48:03 localhost kernel: ivtv0: Autodetected
> Hauppauge WinTV
> > PVR-150
> > May 29 01:48:03 localhost kernel: ivtv0: reopen i2c bus for
> IR-blaster
> > support
> > May 29 01:48:03 localhost kernel: tuner 0-0061: chip found @
> 0xc2 (ivtv
> > i2c
> > driver #0)
> > May 29 01:48:03 localhost kernel: cx25840 0-0044: cx25841-23
> found @ 0x88
> > (ivtv i2c driver #0)
> > May 29 01:48:03 localhost kernel: cx25840 0-0044: loaded
> > v4l-cx25840.fwfirmware (16382 bytes)
> > May 29 01:48:03 localhost kernel: wm8775 0-001b: chip found
> @ 0x36 (ivtv
> > i2c
> > driver #0)
> > May 29 01:48:03 localhost kernel: ivtv0: Registered device
> video0 for
> > encoder MPEG (4 MB)
> > May 29 01:48:03 localhost kernel: ivtv0: Registered device
> video32 for
> > encoder YUV (2 MB)
> > May 29 01:48:03 localhost kernel: ivtv0: Registered device
> vbi0 for
> > encoder
> > VBI (1 MB)
> > May 29 01:48:03 localhost kernel: ivtv0: Registered device
> video24 for
> > encoder PCM audio (1 MB)
> > May 29 01:48:03 localhost kernel: tuner 0-0061: type set to
> 50 (TCL 2002N)
> > May 29 01:48:03 localhost kernel: ivtv0: Initialized
> Hauppauge WinTV
> > PVR-150, card #0
> > May 29 01:48:03 localhost kernel: ACPI: PCI Interrupt
> 0000:00:1f.5[B] ->
> > GSI
> > 17 (level, low) -> IRQ 21
> > May 29 01:48:03 localhost kernel:
> ivtv: ==================== END INIT
> > IVTV ====================
> >
> > May 29 01:48:23 localhost kernel: bttv: driver version
> 0.9.16 loaded
> > May 29 01:48:23 localhost kernel: bttv: using 8 buffers with
> 2080k (520
> > pages) each for capture
> > May 29 01:48:23 localhost kernel: cx2388x v4l2 driver
> version 0.0.6 loaded
> > May 29 01:48:23 localhost kernel: lirc_i2c: chip found @
> 0x71 (Hauppauge
> > IR
> > (PVR150))
> > May 29 01:48:23 localhost kernel: lirc_dev:
> lirc_register_plugin:
> > sample_rate: 10
> > May 29 01:48:23 localhost lircd-0.8.2-CVS[2941]:
> lircd(userspace) ready
> > May 29 01:48:23 localhost lircd-0.8.2-CVS [2941]: accepted
> new client on
> > /dev/lircd
> > May 29 01:48:23 localhost kernel:
> > /var/tmp/bach-build/BUILD/lirc-0.8.2/drivers/lirc_imon/lirc_imon.c:
> > IR port opened
> >
> > thanks
> >
> > 2007/5/29, Daniel Agar <daniel at agar.ca>:
> >>
> >> > Hello I have tried for countless hours to make the ir
> receiver of the
> >> > pvr-150 to work, I have the one that come with a
> irblaster, but this
> >> is
> >> > not
> >> > a must for this one to work because I have a serial
> irblaster and
> >> anyway
> >> I
> >> > would need to patch the lirc if I want it to work, which
> is beyond my
> >> > knowledge right now .
> >> >
> >> > Everything seems to load correctly but I got nothing on
> the console
> >> when
> >> I
> >> > start irw and press a button on my remote ( I know the
> card/ir
> >> > receiver/remote works, i tried them on windows).
> >> >
> >> > By the way I try to install it on MythDora 4
> >> >
> >> > Any help would be extremely appreciated.
> >> >
> >> > Here is the contents of my files
> >> > ----------------
> >> > /etc/modprobe.conf:
> >> >
> >> > alias char-major-61-0 lirc_i2c
> >> > alias char-major-61-1 lirc_serial
> >> > options lirc_serial irq=4 io=0x3f8
> >> > ####IR setup####
> >> > install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe
> --ignore-install
> >> > lirc_i2c
> >> > install lirc_serial setserial /dev/ttyS0 uart
> none; /sbin/modprobe
> >> > --ignore-install lirc_serial
> >> >
> >> > ----------------
> >> > /etc/rc.d/rc.local
> >> >
> >> > /sbin/modprobe lirc_i2c
> >> > /sbin/modprobe lirc_serial
> >> > /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd
> >> > /usr/sbin/lircd --driver=default --device=/dev/lirc1
> >> --output=/dev/lircd1
> >> > --pidfile=/var/run/lircd1.pid
> >> >
> >> > ------------------
> >> >
> >> > /etc/lircd.conf
> >> >
> >> > in this file I have the grayHauppauge remote and my cable
> box, I don't
> >> > think
> >> > I need to post it.
> >> >
> >> > ------------------
> >> >
> >> > /etc/sysconfig/lircd
> >> >
> >> > #Options to lircd
> >> > LIRCD_OPTIONS=
> >> >
> >> > ------------------
> >> >
> >> > here is the list of currently loaded lirc modules:
> >> >
> >> > lsmod | grep lirc
> >> >
> >> > lirc_serial 15104 0
> >> > lirc_i2c 11780 0
> >> > i2c_core 24897 11
> >> >
> >>
> cx88xx,bttv,lirc_i2c,i2c_ec,wm8775,cx25840,tuner,nvidia,ivtv,i2c_algo_bit,tveeprom
> >> > lirc_imon 17924 1
> >> > lirc_dev 16292 3
> lirc_serial,lirc_i2c,lirc_imon
> >> >
> >> > --------------------
> >> >
> >> > and here is the lirc devices
> >> >
> >> > ls -l /dev/lirc*
> >> >
> >> > lrwxrwxrwx 1 root root 5 May 28 18:46 /dev/lirc ->
> lirc0
> >> > crw------- 1 root root 61, 0 May 28 18:46 /dev/lirc0
> >> > crw------- 1 root root 61, 1 May 28 18:46 /dev/lirc1
> >> > crw------- 1 root root 61, 2 May 28 18:46 /dev/lirc2
> >> > srw-rw-rw- 1 root root 0 May 28 18:46 /dev/lircd
> >> > srw-rw-rw- 1 root root 0 May 28 18:46 /dev/lircd1
> >> > prw-r--r-- 1 root root 0 May 28 18:46 /dev/lircm
> >> >
> >> > Thanks
> >>
> >> I use fc6 with a pvr 150 and IR. I don't have anything in
> >> /etc/modprobe.conf concerning lirc and I don't have fedora
> start lircd
> >> on
> >> its own. I simply have the following in /etc/rc.local
> >>
> >> modprobe lirc_i2c
> >> /etc/init.d/lircd start
> >>
> >> You might try using this, and you could simply have
> the /dev/lirc
> >> symlink
> >> point to the proper ir device. I don't have any options in
> my
> >> /etc/sysconfig/lircd file.
> >>
> So you have the IR built into the pvr 150, plus a serial
> device and
> something that requires the module lirc_imon? Have you tried
> only loading
> the module for the pvr 150 lirc_i2c? Then start lircd without
> any other
> options.
>
> _______________________________________________
You might try starting just one instance of lircd and play with the
different /dev/lirc devices it listens on. The modules could be loading
in a different order. If you make a selection from the keyboard does
the serial ir blaster work? That would tell us something.
Brad Crotchett
http://www.bradandkim.net
More information about the mythtv-users
mailing list