[mythtv-users] Need help getting Lirc to work with pvr-150

Trev Jackson trev at g7pvs.freeserve.co.uk
Tue Mar 29 00:00:37 UTC 2005


Hi

I believe the pvr-150 should also be supported in the 7.1pre2.
If when you load lirc_i2c you load it using the debug parameter e.g.
modprobe lirc_i2c debug
You then load lircd and irw hopefully when you press different keys you will 
be able to see in dmesg a specific number for each key you press.
If this works ok I can only assume that when you ran irrecord you didn't 
follow the onscreen instructions and hold down a button at the start type a 
key name hold that button down and press enter etc.

If you are still not getting anything, you may need to check what i2c address 
your infra-red port is on by loading the lm-sensors package and running 
i2cdetect with the correct bus address, e.g. run i2cdetect on its own and it 
will list the busses, then run e.g. i2cdetect 0 and all the i2c bus addresses 
will be listed.  If you look through your logs and check which i2c bus 
addresses are used by the other devices, the only one left should be your 
infra-red port.  The next stage is to look at the lirc_i2c.c code.

Best Regards

Trev


On Tuesday 29 Mar 2005 00:20, Andy Alsup wrote:
> I have been trying 7.1pre2 and am now trying 7.1pre3
>
> Thanks for the input.
>
>
> On Mon, 28 Mar 2005 23:21:23 +0100, Trev Jackson
>
> <trev at g7pvs.freeserve.co.uk> wrote:
> > Hi
> >
> > I just looked at the NEWS file in my lirc-0.7.1pre3 directory.
> > Per Jonsson added support for the Hauppauge PVR150 in this particular
> > version. Therefore you need to download a CVS snapshot of 0.7.1pre3 or
> > download the latest CVS of lirc for you pvr-150 to work.
> > My card is not a pvr-150 and I was looking at your query as a general
> > lirc query and was therefore offering general help.  But it looks like
> > your card is not supported in the lirc_i2c module you are using.
> >
> > Best Regards
> >
> > Trev
> >
> > On Monday 28 Mar 2005 21:56, Andy Alsup wrote:
> > > Ok, I ran irrecord -d /dev/lircm test-lircd.conf  and it looked like
> > > it connected, but after 10 seconds says:
> > >
> > > irrecord: no data for 10 secs, aborting
> > > irrecord: gap not found, can't continue
> > >
> > > I guess what I'm looking for is some sort of troubleshooting steps
> > > that will tell me if the hardware is being addressed correctly, and if
> > > the module is loading right.
> > >
> > > Does everything look right in the logs that I posted?
> > >
> > > Thanks.
> > >
> > > On Mon, 28 Mar 2005 12:57:44 +0100, Trev Jackson
> > >
> > > <trev at g7pvs.freeserve.co.uk> wrote:
> > > > Hi Andy
> > > >
> > > > On Monday 28 Mar 2005 03:02, Andy Alsup wrote:
> > > > > Hi,
> > > > >
> > > > > I used Jarod's doc to set up:
> > > > >
> > > > > - Myth 0.17 from rpm
> > > > > - lirc from rpm with New Hauppauge grey/black lircd.conf from
> > > > > Jarod's howto - FC3 upgraded kernel to 2.6.10-1.770_FC3 with apt
> > > > > - pvr-150 using ivtv  0.3.2m compiled from source
> > > > >
> > > > > using this setup, I load the lirc_i2c module, start lircd, start
> > > > > irw and don't see any output from button pushes.
> > > > >
> > > > > I do see that irw opens and closes the conection to lircd.  and if
> > > > > I load myth, I see that a connection was opened as well.
> > > > >
> > > > > So, it would seem that the lirc part is at least connecting.  I'm
> > > > > not sure lircd is seeing the hardware though.  The device in /dev
> > > > > is a socket.  Shouldn't it be a char 61 device?
> > > > >
> > > > > srw-rw-rw-  1 root root 0 Mar 24 14:57 /dev/lircd
> > > > >
> > > > > One more thing, when I load the lirc_i2c module, I get:
> > > > >
> > > > > lirc_dev: no version for "struct_module" found: kernel tainted.
> > > > > lirc_dev: IR Remote Control driver registered, at major 61
> > > > >
> > > > > Does "kernel tainted" mean anything?
> > > > >
> > > > > Here's the relevant logs:
> > > > >
> > > > > Linux video capture interface: v1.00
> > > > > ivtv: ==================== START INIT IVTV ====================
> > > > > ivtv: version 0.3.2 (m) loading
> > > > > ivtv: Linux version: 2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4
> > > > > ivtv: In case of problems please include the debug info
> > > > > ivtv: between the START INIT IVTV and END INIT IVTV lines when
> > > > > ivtv: mailing the ivtv-devel mailinglist.
> > > > > ivtv: Autodetected WinTV PVR 150 card
> > > > > ivtv: Found an iTVC16 based chip
> > > > > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
> > > > > PCI: setting IRQ 10 as level-triggered
> > > > > ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 10 (level, low) -> IRQ
> > > > > 10 ivtv: Unreasonably low latency timer, setting to 64 (was 32)
> > > > > ivtv: VIA PCI device: 0x0305 vendor: 0x1106
> > > > > tveeprom: Hauppauge: model = 26052, rev = C185, serial# = 7579491
> > > > > tveeprom: tuner = TCL 2002N 6A (idx = 85, type = 50)
> > > > > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> > > > > tveeprom: audio_processor = MSP3410D (type = 5)
> > > > > ivtv: i2c attach [client=tveeprom[0],ok]
> > > > > ivtv: Tuner Type 50, Tuner formats 0x00001000, Radio: yes, Model
> > > > > 0x008d1615, Revision 0x00000000
> > > > > ivtv: NTSC tuner detected
> > > > > ivtv: Radio detected
> > > > > tuner: Ignoring new-style parameters in presence of obsolete ones
> > > > > tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> > > > > ivtv: i2c attach [client=(tuner unset),ok]
> > > > > cx25840: Ignoring new-style parameters in presence of obsolete ones
> > > > > cx25840: FW image '/lib/modules/HcwMakoA.ROM' of size 13883 loaded.
> > > > > cx25840: FW image md5 digest: a6f6a90a3be338cdb89d59e835798408
> > > > > cx25840: FW image sha1 digest:
> > > > > ad2872fb98ad43b6c4afa45d239a57010edebe84 ivtv: i2c attach
> > > > > [client=cx25840[0],ok]
> > > > > ivtv: i2c attach [client=wm8775[0],ok]
> > > > > ivtv: Encoder revision: 0x02040024
> > > > > ivtv: Encoder Firmware may be buggy, use version 0x02040011
> > > > > ivtv: Configuring WinTV PVR 150 card with 5 streams
> > > > > ivtv: Registered v4l2 device, streamtype 0 minor 0
> > > > > ivtv: Create DMA stream 0 using 1024 16384 byte buffers  0 kbytes
> > > > > total ivtv: Allocate DMA stream 0 using 1024 16384 byte buffers 
> > > > > 16777216 kbytes total ivtv: Registered v4l2 device, streamtype 1
> > > > > minor 32 ivtv: Create DMA stream 1
> > > > > ivtv: Allocate DMA stream 1
> > > > > ivtv: Registered v4l2 device, streamtype 2 minor 224
> > > > > ivtv: Create stream 2 using 40 52224 byte buffers  0 kbytes total
> > > > > ivtv: Allocate stream 2 using 40 52224 byte buffers  2097152 kbytes
> > > > > total ivtv: Registered v4l2 device, streamtype 3 minor 24
> > > > > ivtv: Create DMA stream 3 using 455 4608 byte buffers  0 kbytes
> > > > > total ivtv: Allocate DMA stream 3 using 455 4608 byte buffers 
> > > > > 2097152 kbytes total ivtv: Registered v4l2 device, streamtype 4
> > > > > minor 64
> > > > > ivtv: Create stream 4
> > > > > ivtv: Allocate stream 4
> > > > > ivtv: Setting Tuner 50
> > > > > tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
> > > > > ivtv: Switching standard to NTSC.
> > > > > ivtv: Initialized WinTV PVR 150, card #0
> > > > > ivtv: ====================  END INIT IVTV  ====================
> > > > > ivtv: ivtv_enc_thread: pid = 4437, itv = 0xf0cf2920
> > > > > lirc_dev: no version for "struct_module" found: kernel tainted.
> > > > > lirc_dev: IR Remote Control driver registered, at major 61
> > > > > bttv: driver version 0.9.15 loaded
> > > > > bttv: using 8 buffers with 2080k (520 pages) each for capture
> > > > >
> > > > > Any advice?
> > > > >
> > > > > Thanks!
> > > > > _______________________________________________
> > > > > mythtv-users mailing list
> > > > > mythtv-users at mythtv.org
> > > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > > >
> > > > Try:
> > > >
> > > > irrecord -d /dev/lirc0 lircd.conf
> > > >
> > > > if it doesn't work use whatever lirc device you have in /dev instead
> > > > of /dev/lirc0.
> > > > after running the command copy lircd.conf to /etc
> > > > kill the lircd process
> > > > do an rmod lirc-i2c
> > > >
> > > > reload the lirc-i2c module
> > > > restart lircd
> > > >
> > > > Now if you run irw hopefully when you press keys the buttons you
> > > > press should be displayed.
> > > >
> > > > Best Regards
> > > >
> > > > Trev
> > > >
> > > > _______________________________________________
> > > > mythtv-users mailing list
> > > > mythtv-users at mythtv.org
> > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > >
> > > _______________________________________________
> > > mythtv-users mailing list
> > > mythtv-users at mythtv.org
> > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


More information about the mythtv-users mailing list