On Wed, Jun 9, 2010 at 1:27 PM, Jarod Wilson <jarod@wilsonet.com> wrote:
On Wed, Jun 9, 2010 at 1:53 PM, Christoph Bartelmus <lirc@bartelmus.de> wrote:
> Hi!
> You didn't paste the relevant parts of the log.
I suppose I should have shown you more logs.   Here's the dmesg for ivtv and lirc. 
I'm not sure which other logs you may need (/var/log/lircd.log) doesn't show anything interesting.

###
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
lirc_dev: IR Remote Control driver registered, major 61
lirc_i2c: chip 0x0 found @ 0x18 (Hauppauge IR)
lirc_dev: lirc_register_driver: sample_rate: 10
caller is init_timing_params+0x28/0x110 [lirc_serial]
 [<ffffffffa0f5c528>] init_timing_params+0x28/0x110 [lirc_serial]
 [<ffffffffa0f61000>] ? lirc_serial_init_module+0x0/0x31c [lirc_serial]
 [<ffffffffa0f61000>] ? lirc_serial_init_module+0x0/0x31c [lirc_serial]
 [<ffffffffa0f6112e>] lirc_serial_init_module+0x12e/0x31c [lirc_serial]
 [<ffffffffa0f61000>] ? lirc_serial_init_module+0x0/0x31c [lirc_serial]
lirc_serial: auto-detected active high receiver
lirc_dev: lirc_register_driver: sample_rate: 0
lirc_serial $Revision: 5.104 $ registered
ivtv: Start initialization, version 1.4.1
ivtv0: Initializing card 0
ivtv0: Autodetected Hauppauge card (cx23415 based)
ivtv 0000:02:05.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: Autodetected Hauppauge WinTV PVR-350
saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 1-0040: MSP4448G-B3 found @ 0x80 (ivtv i2c driver #0)
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
IRQ 16/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs
ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv0: Registered device video32 for encoder YUV (2048 kB)
ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPG (1024 kB)
ivtv0: Registered device vbi8 for decoder VBI (64 kB)
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV (1024 kB)
ivtv0: Initialized card: Hauppauge WinTV PVR-350
ivtv1: Initializing card 1
ivtv1: Autodetected Hauppauge card (cx23416 based)
ivtv 0000:02:06.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
ivtv1: Autodetected Hauppauge WinTV PVR-150
ivtv1: Reopen i2c bus for IR-blaster support
cx25840 2-0044: cx25841-24 found @ 0x88 (ivtv i2c driver #1)
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
IRQ 17/ivtv1: IRQF_DISABLED is not guaranteed on shared IRQs
ivtv1: Registered device video1 for encoder MPG (4096 kB)
ivtv1: Registered device video33 for encoder YUV (2048 kB)
ivtv1: Registered device vbi1 for encoder VBI (1024 kB)
ivtv1: Registered device video25 for encoder PCM (320 kB)
ivtv1: Initialized card: Hauppauge WinTV PVR-150
ivtv: End initialization
ivtv 0000:02:05.0: firmware: requesting v4l-cx2341x-enc.fw
ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv 0000:02:05.0: firmware: requesting v4l-cx2341x-dec.fw
ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv 0000:02:06.0: firmware: requesting v4l-cx2341x-enc.fw
ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: Encoder revision: 0x02060039
ivtv0: Decoder revision: 0x02020023
ivtv 0000:02:05.0: firmware: requesting v4l-cx2341x-init.mpg
ivtv1: Encoder revision: 0x02060039
ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
ivtvfb0: Framebuffer at 0xed510000, mapped to 0xffffc90005290000, size 1665k
ivtvfb0: Framebuffer registered on ivtv0
###

i2c relevant dmesg:
###
i2c i2c-0: nForce2 SMBus adapter at 0x1c40
saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 1-0040: MSP4448G-B3 found @ 0x80 (ivtv i2c driver #0)
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv1: Reopen i2c bus for IR-blaster support
cx25840 2-0044: cx25841-24 found @ 0x88 (ivtv i2c driver #1)
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
lirc_i2c: chip 0x0 found @ 0x18 (Hauppauge IR)
###


> You load lirc_serial first, so I'd expect /dev/lirc0 to be associated with
> lirc_serial.

Yes, thanks for pointing that out.  I had always loaded lirc_serial last but somehow
I was loading it first this time.  I'm modprobing it last now so my lirc_serial blaster
problem is fixed (actually probably never was since I wasn't testing /dev/lirc0). 
I'm now able to change channels on the settopbox.  Thanks once again.


There was a work-around that went into lirc_i2c. The i2c adapter id
for a number of Hauppauge cards was removed from upstream, as the
adapter id field has been deprecated. Basically, a check in lirc_i2c
was inverted to look for the adapter id of another device where it
hadn't yet been removed, and if we don't find that, we assume its the
device w/o the id anymore... This really needs more work to come to a
complete solution, using some of the new i2c device detection and
binding routines, but I'm currently tied up with some other work right
now...

The "lirc_i2c: chip 0x0 found @ 0x18 (Hauppauge IR)" bit actually
looks to be the code w/the work-around, and the 0x0 is the device w/o
any i2c adapter id field set anymore, so best as I can tell, lirc_i2c
is actually doing the expected thing here.

I believe none of my hauppauge IR's work anymore.  lirc_serial works now but I can't change channels in mythtv with any of my hauppauge IRs.  Basically I still see only two dev entries (lirc0 & lirc1).  lirc1 is my serial ir blaster but lirc0 should belong to anyone of the hauppauge IR.  I'm seeing the logs and I only see one hauppauge IR being recognized and I don't know which one is it. 

Thanks to both of you for providing the insight.