mythtv / PVR-150 / lirc
Jarod Wilson
jarod at wilsonet.com
Fri Apr 27 13:44:30 EDT 2007
On Friday 27 April 2007 13:08:51 Bill McGonigle wrote:
> I'm curious if anybody here is using a PVR-150 with its built-in IR
> receiver. I'm trying to load the lirc_i2c driver, but all I get is:
>
> lirc_i2c: probe 0x1a @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x18 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x71 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x4b @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x64 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x30 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x6b @ ivtv i2c driver #0: no
>
> Which seems to indicate it can't find i2c on the card.
Hrm. I presume you get those because of 'options lirc_i2c debug=1', since I
have no such thing in my logs...
> I do get
> video coming in on the card (kernel 2.6.20-1.2933.fc6).
>
> Based on Jarod's HOWTO, I've got:
>
> modprobe.conf:
> # ivtv modules setup
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> # i2c
> alias char-major-88 i2c-dev
> # lirc remote
> alias char-major-61 lirc_i2c
> #alias char-major-61 lirc_dev
> options lirc_dev debug=1
> install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
> lirc_i2c
> options lirc_i2c debug=1
I've got nothing more than:
alias char-major-61 lirc_i2c
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c
I don't have the exact same card, but none of the other bits should be
necessary anymore... Unless you have some new-fangled version of the PVR-150
that ivtv/lirc don't fully know about yet. :(
> But I seem to have messed something up. If anybody has this working
> I'd appreciate seeing a working config and dmesg output.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.10.1 (tagged release) loading
ivtv: Linux version: 2.6.20-1.2944.fc6 SMP mod_unload 686 4KSTACKS
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 card (cx23416 based)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: Encoder revision: 0x02060039
tveeprom 0-0050: Hauppauge model 32031, rev B210, serial# 6160296
tveeprom 0-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is MSP3435 (idx 10)
tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
tveeprom 0-0050: has no radio, has IR receiver, has no IR transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-250
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
msp3400 0-0040: MSP3435G-B6 found @ 0x80 (ivtv i2c driver #0)
msp3400 0-0040: MSP3435G-B6 supports radio, mode is autodetect and autoselect
ivtv0: Registered device video0 for encoder MPEG (4 MB)
ivtv0: Registered device video32 for encoder YUV (2 MB)
ivtv0: Registered device vbi0 for encoder VBI (1 MB)
ivtv0: Registered device video24 for encoder PCM audio (1 MB)
tuner 0-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
ivtv: ==================== END INIT IVTV ====================
[...]
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.6 loaded
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
lirc_dev: lirc_register_plugin: sample_rate: 10
[...]
> tveeprom 0-0050: has no radio, has IR receiver, has IR transmitter
[...]
Okay, the ivtv side looks mostly happy...
> i2c /dev entries driver
> lirc_i2c: probe 0x1a @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x18 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x71 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x4b @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x64 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x30 @ ivtv i2c driver #0: no
> lirc_i2c: probe 0x6b @ ivtv i2c driver #0: no
>
> #i2cdetect -l 0
> i2c-0 i2c ivtv i2c driver #0
> Algorithm unavailable
Not a clue what's going on here. I take it you've tried running irw and
pushing keys on the remote, and nada? (just making sure those messages aren't
a red herring).
--
Jarod Wilson
jarod at wilsonet.com
More information about the gnhlug-discuss
mailing list