I've also captured this:

dmesg:
lirc_dev: IR Remote Control driver registered, at major 61
lirc_pvr150: probe 0x70 @ ivtv i2c driver #0: no
lirc_pvr150: probe 0x71 @ ivtv i2c driver #0: no
lirc_pvr150: ivtv i2c driver #0: no devices found
lirc_dev ([-1]): open called
lirc_dev ([-1]): open result = -ENODEV

[EMAIL PROTECTED] ~]# tail /var/log/lircd
Jun  1 17:42:53 media.nzbaxters lircd: could not open /dev/lirc0
Jun  1 17:42:53 media.nzbaxters lircd: default_init(): No such device
Jun  1 17:42:53 media.nzbaxters lircd: caught signal
Jun  2 10:53:52 media.nzbaxters lircd: lircd(hauppauge_pvr150) ready
Jun  2 11:19:24 media.nzbaxters lircd: caught signal
Jun  2 11:19:30 media.nzbaxters lircd: lircd(hauppauge_pvr150) ready
Jun  2 11:20:03 media.nzbaxters lircd: accepted new client on /dev/lircd
Jun  2 11:20:03 media.nzbaxters lircd: could not open /dev/lirc0
Jun  2 11:20:03 media.nzbaxters lircd: default_init(): No such device
Jun  2 11:20:03 media.nzbaxters lircd: caught signal


any ideas??

----- Original Message ----- 
From: "Simon Baxter" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, June 01, 2006 6:04 PM
Subject: [ivtv-users] LIRCD on PVR-150 no go. TVEEPROM problem??


> Hi.
>
> I'm unable to get my IR working on the new PVR-150.  lirc-0.8.1-CVS-pvr150
>
> Here's some bits of 'dmesg':
>
>
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.6.2 (tagged release) loading
> ivtv:  Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS gcc-4.1
> ivtv:  In case of problems please include the debug info between
> ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
> ivtv:  any module options, when mailing the ivtv-users mailinglist.
> ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX25841 (idx 35)
> tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> tveeprom 1-0050: has no radio, has IR remote
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB 
> total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB 
> total)
> ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv:  ====================  END INIT IVTV  ====================
> <snip>
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_pvr150: no version for "lirc_unregister_plugin" found: kernel 
> tainted.
> lirc_pvr150: probe 0x70 @ ivtv i2c driver #0: no
> lirc_pvr150: probe 0x71 @ ivtv i2c driver #0: no
> lirc_pvr150: ivtv i2c driver #0: no devices found
>
>
> Looks like the tuner is at i2c 0x0061, with nothing at 0x0070 or 0x0071
>
>
>    i2c-1       unknown         ivtv i2c driver #0 Algorithm unavailable
>    i2c-0       unknown         SMBus Via Pro adapter at 5000 Algorithm 
> unavailable
> [EMAIL PROTECTED] lirc-0.8.1-CVS-pvr150]# i2cdetect 1
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-1.
> I will probe address range 0x03-0x77.
> Continue? [Y/n] Y
>     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          XX XX XX XX XX XX XX XX XX XX XX XX XX
> 10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 40: XX XX XX XX UU XX XX XX XX XX XX XX XX XX XX XX
> 50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 70: XX XX XX XX XX XX XX XX
>
>
> Is TVEEPROM not registering the i2c device??
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users 



_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to