<br><br><div class="gmail_quote">On Thu, Sep 1, 2011 at 10:34 AM, Dan Littlejohn <span dir="ltr"><<a href="mailto:dan.littlejohn@gmail.com">dan.littlejohn@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p class="MsoNormal">I am running gentoo and recently upgraded my myth box.<span> </span>Everything seemed to go well, but I am having
problems getting lirc to work again.<span>
</span>This is a frontend with a pvr350 that I use for the remote input and an
ir blaster to change channels on my satellite box so I need to get both a
hauppauge grey remote and an ir blaster working at the same time</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Before the upgrade, I was running lirc8.7 and kernel 2.6.35,
and at boot I would load lirc_i2c and lirc_serial.<span> </span>My init.d lircd file looked like this</p>
<p class="MsoNormal"> </p>
<p style="margin-left:40px" class="MsoNormal">start-stop-daemon --start --pidfile /var/run/lirc/lircd1.pid
--quiet --exec /usr/sbin/lircd -- --driver=default --device=/dev/lirc1
--output=/var/run/lirc/lircd1 --pidfile=/var/run/lirc/lircd1.pid --listen=8765</p>
<p style="margin-left:40px" class="MsoNormal">start-stop-daemon --start --pidfile /var/run/lirc/lircd.pid
--quiet --exec /usr/sbin/lircd -- --driver=default --device=/dev/lirc0
--output=/var/run/lirc/lircd --pidfile=/var/run/lirc/lircd.pid
--connect=localhost:8765</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Now I am using lirc 9.0 and kernel 2.6.39 and understand a
lot of stuff has been moved into the kernel, but I am a bit stumped as to how
to get this working again.<span> </span>Here is some
of the log that shows dmesg and that the keymap seems to look ok for rc5</p>
<p class="MsoNormal"> </p>
<p style="margin-left:40px" class="MsoNormal">one linux # dmesg | grep ivtv</p>
<p style="margin-left:40px" class="MsoNormal">ivtv: Start initialization, version 1.4.2</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Initializing card 0</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Autodetected Hauppauge card (cx23415 based)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv 0000:05:02.0: PCI INT A -> GSI 18 (level, low) ->
IRQ 18</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Unreasonably low latency timer, setting to 64 (was
32)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Autodetected Hauppauge WinTV PVR-350</p>
<p style="margin-left:40px" class="MsoNormal">saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv
i2c driver #0)</p>
<p style="margin-left:40px" class="MsoNormal">saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)</p>
<p style="margin-left:40px" class="MsoNormal">msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver
#0)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device video0 for encoder MPG (4096 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device video32 for encoder YUV (2048 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device vbi0 for encoder VBI (1024 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device video24 for encoder PCM (320 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device radio0 for encoder radio</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device video16 for decoder MPG (1024 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device vbi8 for decoder VBI (64 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device vbi16 for decoder VOUT</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Registered device video48 for decoder YUV (1024 kB)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Initialized card: Hauppauge WinTV PVR-350</p>
<p style="margin-left:40px" class="MsoNormal">ivtv: End initialization</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Encoder revision: 0x02060039</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Decoder revision: 0x02020023</p>
<p style="margin-left:40px" class="MsoNormal">ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)</p>
<p style="margin-left:40px" class="MsoNormal">Modules linked in: snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device</p>
<p style="margin-left:40px" class="MsoNormal">snd_pcm_oss snd_mixer_oss nvidia(P) tuner_simple tuner_types
tda9887 tda8290</p>
<p style="margin-left:40px" class="MsoNormal">tuner msp3400 saa7127 snd_hda_codec_hdmi saa7115 ivtv
snd_hda_codec_realtek</p>
<p style="margin-left:40px" class="MsoNormal">cx2341x i2c_algo_bit v4l2_common videodev snd_hda_intel
tveeprom snd_hda_codec</p>
<p style="margin-left:40px" class="MsoNormal">i2c_core 8250_pnp snd_hwdep snd_pcm 8250 snd_timer
serial_core snd_page_alloc</p>
<p style="margin-left:40px" class="MsoNormal">ir-kbd-i2c: i2c IR (Hauppauge WinTV PVR-350 detected at
i2c-0/0-0018/ir0 [ivtv</p>
<p style="margin-left:40px" class="MsoNormal">i2c driver #0]</p>
<p style="margin-left:40px" class="MsoNormal"> </p>
<p style="margin-left:40px" class="MsoNormal">one linux # dmesg | grep lirc</p>
<p style="margin-left:40px" class="MsoNormal">lirc_dev: IR Remote Control driver registered, major 253</p>
<p style="margin-left:40px" class="MsoNormal">rc rc0: lirc_dev: driver ir-lirc-codec (rc-loopback)
registered at minor = 0</p>
<p style="margin-left:40px" class="MsoNormal"> </p>
<p style="margin-left:40px" class="MsoNormal">one linux # ir-keytable</p>
<p style="margin-left:40px" class="MsoNormal">Found /sys/class/rc/rc0/ (/dev/input/event2) with:</p>
<p style="margin-left:40px" class="MsoNormal">Driver rc-loopback, table rc-empty</p>
<p style="margin-left:40px" class="MsoNormal">Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other</p>
<p style="margin-left:40px" class="MsoNormal">Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC other</p>
<p style="margin-left:40px" class="MsoNormal">Found /sys/class/rc/rc1/ (/dev/input/event5) with:</p>
<p style="margin-left:40px" class="MsoNormal">Driver ir-kbd-i2c, table rc-hauppauge</p>
<p style="margin-left:40px" class="MsoNormal">Supported protocols: RC-5<span> </span>Enabled protocols: RC-5</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Currently, I have LIRC_DEVICES='userspace' (have also tried devinput, default, serial and combos of those). <span> </span>I enable all the lirc modules and the ir
staging modules in the kernel.<span> </span><span> </span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have tried devinput (lircd –n –H devinput –d /dev/input5) and
ir-kbd-i2c (modprobe ir-kdb-i2c hauppauge=1 with lircd -n -d /dev/lirc0) and neither seems to work when
using iwr, but I do see dmesg key presses when using modprobe ir-kbd-i2c
debug=1, but not in irw.<span> </span><span> </span>I am not sure which approach I should be
focusing on to get both the pvr350 remote and the ir blaster to both work.<span> </span>I have read everything I can in the list and
what I can find, but it is a bit confusing.<span>
</span>Right now, neither work.<span> </span>Would
appreciate any advice to get this working.<span>
</span></p>
</blockquote></div><br><br>Is there anything I could add that would make it easier to provide some advice to this? Would really like to get this sorted out.<br><br>Dan<br>