Mailing List Archive

Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04
I am really close, so I hope someone can help me finish the race without
having to buy a MCE USB remote...

I am building my first MythTv system. I got the Hauppauge HVR-1600 kit with
the IR remote, receiver, and blaster, on the mistaken impression that they
would be easy to get working in Linux.

Here is what I did:

1) I started with fresh install of mythbuntu 0.23/10.04. I could see that
the analog and digital tuners of the HVR-1600 were recognized, but the
remote was not working.

2) I was easily able to make the IR receiver and remote work by modifying
/etc/lirc/hardware.conf to add ir_kbd_i2c to REMOTE_MODULES and
/dev/input/event9 to REMOTE_DEVICE. Then I used "Edit Keys" to remap the
keys that were not working. So receiving is fine, but I need to make the IR
blaster work.

2) I found lots of posts pointing me to lirc_pvr150, but I concluded that
was too out of date to work with Ubuntu 10.04.

3) I found this article in Jarod Wilson's blog: http://wilsonet.com/?p=40
that looks very relevant.

4) I am pretty much a noob when it comes to Linux kernels and drivers, but I
found this post:
http://ubuntuforums.org/showthread.php?t=1294825&highlight=zilog+lirc&page=7
which seems to be an easy way to build lirc_zilog by patching lirc source
code. I did that, and also copied over Mark Weaver's firmware and
lircd.conf files.

5) I do a "modprobe lirc_zilog". I can see in dmesg that the driver is
successfully loading its firmware, but I don't see any evidence that it
recognized my HVR-1600. When I restart /etc/init.d/lirc, I see errors like
this:

error in configfile line 30938:
"2195390514" is out of range

Can anyone give me some advice on what to look for, or how to proceed?

Please note that everything is currently from the stock mythbuntu install
with the sole exception of the lirc patch to create lirc_zilog. Do I need to
update anything else from source?

Is lirc_zilog supposed to handle the receiving as well as the blasting? Or
will I continue to use ir-kbd-i2c for receiving? What should be in my lirc
hardware.conf?

Or is there a better way to do this without using lirc_zilog?

Thanks for the help!

Dave





_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
I got a bit further. It looks like the HVR-1600 IR receiver/blaster is being
recognized.

Here is the syslog generated by "modprobe lirc_zilog debug=1":

Jul 3 08:37:56 mythtv kernel: [ 318.888673] lirc_zilog: Zilog/Hauppauge IR
driver initializing
Jul 3 08:37:56 mythtv kernel: [ 318.890408] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x70
Jul 3 08:37:56 mythtv kernel: [ 318.890804] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 3 08:37:56 mythtv kernel: [ 318.891197] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 3 08:37:56 mythtv kernel: [ 318.891199] lirc_zilog: chip found with RX
and TX
Jul 3 08:37:56 mythtv kernel: [ 318.891285] lirc_zilog: poll thread
started
Jul 3 08:37:56 mythtv kernel: [ 318.891296] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 3 08:37:56 mythtv kernel: [ 318.891364] Zilog/Hauppauge i2c IR 8-0070:
firmware: requesting haup-ir-blaster.bin
Jul 3 08:37:56 mythtv kernel: [ 318.909500] lirc_zilog: firmware of size
302355 loaded
Jul 3 08:37:56 mythtv kernel: [ 318.909648] lirc_zilog: 743 IR blaster
codesets loaded
Jul 3 08:37:56 mythtv kernel: [ 318.909670] lirc_zilog: 01 60 00 01 5b
Jul 3 08:37:56 mythtv kernel: [ 318.910836] lirc_zilog: 05 02 04 4b 1a
Jul 3 08:37:56 mythtv kernel: [ 318.911986] lirc_zilog: 09 79 88 b1 1f
Jul 3 08:37:56 mythtv kernel: [ 318.913182] lirc_zilog: 0d 87 f5 16 61
Jul 3 08:37:56 mythtv kernel: [ 318.915892] lirc_zilog: 11 a6 d9 ec 9a
Jul 3 08:37:56 mythtv kernel: [ 318.917098] lirc_zilog: 15 0f a7 ab 27
Jul 3 08:37:56 mythtv kernel: [ 318.918258] lirc_zilog: 19 48 9d 7e 1a
Jul 3 08:37:56 mythtv lircd-0.8.6[1937]: lircd(default) ready, using
/var/run/lirc/lircd1
Jul 3 08:37:56 mythtv lircd-0.8.6[1937]: connected to localhost
Jul 3 08:37:56 mythtv lircd-0.8.6[1933]: lircd(default) ready, using
/var/run/lirc/lircd
Jul 3 08:37:56 mythtv lircd-0.8.6[1933]: accepted new client from 127.0.0.1
Jul 3 08:37:56 mythtv kernel: [ 318.919519] lirc_zilog: 1d d9 0c 0e 48
Jul 3 08:37:56 mythtv kernel: [ 318.920720] lirc_zilog: 21 91 77 d6 3d
Jul 3 08:37:56 mythtv kernel: [ 318.921875] lirc_zilog: 25 09 44 18 60
Jul 3 08:37:56 mythtv kernel: [ 318.922505] lirc_zilog: poll called
Jul 3 08:37:56 mythtv kernel: [ 318.922510] lirc_zilog: poll result = 0
Jul 3 08:37:56 mythtv kernel: [ 318.923027] lirc_zilog: 29 e5 12 c6 6c
Jul 3 08:37:56 mythtv kernel: [ 318.924187] lirc_zilog: 2d ba 32 c4 26
Jul 3 08:37:56 mythtv kernel: [ 318.925974] lirc_zilog: 31 e3 76 01 48
Jul 3 08:37:56 mythtv kernel: [ 318.927116] lirc_zilog: 35 a2 7d 81 59
Jul 3 08:37:56 mythtv kernel: [ 318.928290] lirc_zilog: 39 90 28 8f 48
Jul 3 08:37:56 mythtv kernel: [ 318.929457] lirc_zilog: 3d 79 61 b4 0a
Jul 3 08:37:56 mythtv kernel: [ 318.930595] lirc_zilog: 41 0b 57 21 6e
Jul 3 08:37:56 mythtv kernel: [ 318.931725] lirc_zilog: 45 00 78 ad 62
Jul 3 08:37:56 mythtv kernel: [ 318.932889] lirc_zilog: 49 b5 68 a2 27
Jul 3 08:37:56 mythtv kernel: [ 318.934020] lirc_zilog: 4d 42 4e da 6c
Jul 3 08:37:56 mythtv kernel: [ 318.935150] lirc_zilog: 51 94 63 0e 2a
Jul 3 08:37:56 mythtv kernel: [ 318.936307] lirc_zilog: 55 1a 30 3b 45
Jul 3 08:37:56 mythtv kernel: [ 318.937446] lirc_zilog: 59 fa 34 25 e5
Jul 3 08:37:56 mythtv kernel: [ 318.938572] lirc_zilog: 5d cb 1e c1 ee
Jul 3 08:37:56 mythtv kernel: [ 318.939702] lirc_zilog: 61 00 00 00 ee
Jul 3 08:37:56 mythtv kernel: [ 318.943013] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 3 08:37:56 mythtv kernel: [ 318.943027] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x71
Jul 3 08:37:56 mythtv kernel: [ 318.943415] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 3 08:37:56 mythtv kernel: [ 318.943803] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 3 08:37:56 mythtv kernel: [ 318.943805] lirc_zilog: chip found with RX
and TX
Jul 3 08:37:56 mythtv kernel: [ 318.943856] lirc_zilog: poll thread
started
Jul 3 08:37:56 mythtv kernel: [ 318.943859] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 3 08:37:56 mythtv kernel: [ 318.943914] lirc_zilog: 01 60 00 01 5b
Jul 3 08:37:56 mythtv kernel: [ 318.945072] lirc_zilog: 05 02 04 4b 1a
Jul 3 08:37:56 mythtv kernel: [ 318.946200] lirc_zilog: 09 79 88 b1 1f
Jul 3 08:37:56 mythtv kernel: [ 318.947327] lirc_zilog: 0d 87 f5 16 61
Jul 3 08:37:56 mythtv kernel: [ 318.948480] lirc_zilog: 11 a6 d9 ec 9a
Jul 3 08:37:56 mythtv kernel: [ 318.949617] lirc_zilog: 15 0f a7 ab 27
Jul 3 08:37:56 mythtv kernel: [ 318.950756] lirc_zilog: 19 48 9d 7e 1a
Jul 3 08:37:56 mythtv kernel: [ 318.951891] lirc_zilog: 1d d9 0c 0e 48
Jul 3 08:37:56 mythtv kernel: [ 318.953054] lirc_zilog: 21 91 77 d6 3d
Jul 3 08:37:56 mythtv kernel: [ 318.954193] lirc_zilog: 25 09 44 18 60
Jul 3 08:37:56 mythtv kernel: [ 318.955320] lirc_zilog: 29 e5 12 c6 6c
Jul 3 08:37:56 mythtv kernel: [ 318.956468] lirc_zilog: 2d ba 32 c4 26
Jul 3 08:37:56 mythtv kernel: [ 318.957605] lirc_zilog: 31 e3 76 01 48
Jul 3 08:37:56 mythtv lircd-0.8.6[1937]: caught signal
Jul 3 08:37:56 mythtv lircd-0.8.6[1933]: removed client
Jul 3 08:37:56 mythtv lircd-0.8.6[1933]: caught signal
Jul 3 08:37:56 mythtv kernel: [ 318.958738] lirc_zilog: 35 a2 7d 81 59
Jul 3 08:37:56 mythtv kernel: [ 318.960425] lirc_zilog: 39 90 28 8f 48
Jul 3 08:37:56 mythtv kernel: [ 318.961567] lirc_zilog: 3d 79 61 b4 0a
Jul 3 08:37:56 mythtv kernel: [ 318.961774] lirc_zilog: poll called
Jul 3 08:37:56 mythtv kernel: [ 318.961777] lirc_zilog: poll result = 0
Jul 3 08:37:56 mythtv kernel: [ 318.962717] lirc_zilog: 41 0b 57 21 6e
Jul 3 08:37:56 mythtv kernel: [ 318.963845] lirc_zilog: 45 00 78 ad 62
Jul 3 08:37:56 mythtv kernel: [ 318.965003] lirc_zilog: 49 b5 68 a2 27
Jul 3 08:37:56 mythtv kernel: [ 318.966148] lirc_zilog: 4d 42 4e da 6c
Jul 3 08:37:56 mythtv kernel: [ 318.967277] lirc_zilog: 51 94 63 0e 2a
Jul 3 08:37:56 mythtv kernel: [ 318.968432] lirc_zilog: 55 1a 30 3b 45
Jul 3 08:37:56 mythtv kernel: [ 318.969572] lirc_zilog: 59 fa 34 25 e5
Jul 3 08:37:56 mythtv kernel: [ 318.970699] lirc_zilog: 5d cb 1e c1 ee
Jul 3 08:37:56 mythtv kernel: [ 318.971827] lirc_zilog: 61 00 00 00 ee
Jul 3 08:37:56 mythtv kernel: [ 318.975418] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 3 08:37:56 mythtv kernel: [ 318.975453] lirc_zilog: initialization
complete
Jul 3 08:37:56 mythtv lircd-0.8.6[1956]: lircd(default) ready, using
/var/run/lirc/lircd
Jul 3 08:37:56 mythtv lircd-0.8.6[1960]: lircd(default) ready, using
/var/run/lirc/lircd1
Jul 3 08:37:56 mythtv lircd-0.8.6[1956]: accepted new client from 127.0.0.1
Jul 3 08:37:56 mythtv lircd-0.8.6[1960]: connected to localhost
Jul 3 08:37:56 mythtv kernel: [ 318.982145] lirc_zilog: poll called
Jul 3 08:37:56 mythtv kernel: [ 318.982148] lirc_zilog: poll result = 0
Jul 3 08:37:57 mythtv kernel: [ 319.649775] lirc_zilog: key (0x00/0x00)

The 0x00 line keeps repeating indefinitely.

When I click a remote key I see this:

Jul 3 08:38:46 mythtv kernel: [ 368.795441] lirc_zilog: poll called
Jul 3 08:38:46 mythtv kernel: [ 368.795444] lirc_zilog: poll result =
POLLIN|POLLRDNORM
Jul 3 08:38:46 mythtv kernel: [ 368.795454] lirc_zilog: read called
Jul 3 08:38:46 mythtv kernel: [ 368.795457] lirc_zilog: read result = OK
(0)

So it looks to me like the receive part of the driver is working.

So I changed hardware.conf like this:

REMOTE_MODULES="lirc_dev lirc_zilog"
REMOTE_DEVICE="/dev/lirc0"
TRANSMITTER_MODULES="lirc_dev lirc_zilog"
TRANSMITTER_DEVICE="/dev/lirc0"

and reboot. After the reboot I see that both /dev/lirc0 and /dev/lirc1 are
created:

dave@mythtv:~$ ls /dev/lirc*
/dev/lirc0 /dev/lirc1 /dev/lircd /dev/lircd1

Is that supposed to happen?

Here is dmesg output:

dave@mythtv:~$ dmesg|grep lirc
[ 27.667068] lirc_dev: IR Remote Control driver registered, major 61
[ 27.738407] lirc_zilog: Zilog/Hauppauge IR driver initializing
[ 27.740892] lirc_zilog: chip found with RX and TX
[ 27.740950] lirc_dev: lirc_register_driver: sample_rate: 0
[ 28.283592] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0
loaded
[ 28.284379] lirc_zilog: chip found with RX and TX
[ 28.311270] lirc_dev: lirc_register_driver: sample_rate: 0
[ 28.401981] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0
loaded
[ 28.402050] lirc_zilog: initialization complete

Here is syslog output:

Jul 3 09:03:04 mythtv kernel: [ 27.667068] lirc_dev: IR Remote Control
driver registered, major 61
Jul 3 09:03:04 mythtv kernel: [ 27.724081] cx18 0000:05:04.0: firmware:
requesting v4l-cx23418-cpu.fw
Jul 3 09:03:04 mythtv kernel: [ 27.738407] lirc_zilog: Zilog/Hauppauge IR
driver initializing
Jul 3 09:03:04 mythtv kernel: [ 27.740892] lirc_zilog: chip found with RX
and TX
Jul 3 09:03:04 mythtv kernel: [ 27.740950] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 3 09:03:04 mythtv kernel: [ 27.741004] Zilog/Hauppauge i2c IR 8-0070:
firmware: requesting haup-ir-blaster.bin
Jul 3 09:03:04 mythtv lircd-0.8.6[1110]: error in configfile line 62:
Jul 3 09:03:04 mythtv lircd-0.8.6[1110]: "2147549184" is out of range
.
...lots of out of range errors deleted...
.
Jul 3 09:03:06 mythtv lircd-0.8.6[1156]: error in configfile line 30944:
Jul 3 09:03:06 mythtv lircd-0.8.6[1156]: "2195390542" is out of range
Jul 3 09:03:06 mythtv lircd-0.8.6[1320]: lircd(default) ready, using
/var/run/lirc/lircd1
Jul 3 09:03:06 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:03:06 mythtv lircd-0.8.6[1320]: Connection refused
Jul 3 09:03:11 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:03:11 mythtv lircd-0.8.6[1320]: Connection refused
Jul 3 09:03:21 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:03:21 mythtv lircd-0.8.6[1320]: Connection refused
Jul 3 09:03:36 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:03:36 mythtv lircd-0.8.6[1320]: Connection refused
Jul 3 09:03:56 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:03:56 mythtv lircd-0.8.6[1320]: Connection refused
Jul 3 09:04:21 mythtv lircd-0.8.6[1320]: failure connecting to localhost
Jul 3 09:04:21 mythtv lircd-0.8.6[1320]: Connection refused

I am thinking I will be OK if I can fix the out of range messages. Any
suggestions on how to do that?

Thanks for the help!

Dave

-----Original Message-----
From: David Lasker [mailto:dave@altosdesign.com]
Sent: Friday, July 02, 2010 8:41 PM
To: 'Discussion about mythtv'
Subject: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in
Mythbuntu .23/10.04

I am really close, so I hope someone can help me finish the race without
having to buy a MCE USB remote...

I am building my first MythTv system. I got the Hauppauge HVR-1600 kit with
the IR remote, receiver, and blaster, on the mistaken impression that they
would be easy to get working in Linux.

Here is what I did:

1) I started with fresh install of mythbuntu 0.23/10.04. I could see that
the analog and digital tuners of the HVR-1600 were recognized, but the
remote was not working.

2) I was easily able to make the IR receiver and remote work by modifying
/etc/lirc/hardware.conf to add ir_kbd_i2c to REMOTE_MODULES and
/dev/input/event9 to REMOTE_DEVICE. Then I used "Edit Keys" to remap the
keys that were not working. So receiving is fine, but I need to make the IR
blaster work.

2) I found lots of posts pointing me to lirc_pvr150, but I concluded that
was too out of date to work with Ubuntu 10.04.

3) I found this article in Jarod Wilson's blog: http://wilsonet.com/?p=40
that looks very relevant.

4) I am pretty much a noob when it comes to Linux kernels and drivers, but I
found this post:
http://ubuntuforums.org/showthread.php?t=1294825&highlight=zilog+lirc&page=7
which seems to be an easy way to build lirc_zilog by patching lirc source
code. I did that, and also copied over Mark Weaver's firmware and
lircd.conf files.

5) I do a "modprobe lirc_zilog". I can see in dmesg that the driver is
successfully loading its firmware, but I don't see any evidence that it
recognized my HVR-1600. When I restart /etc/init.d/lirc, I see errors like
this:

error in configfile line 30938:
"2195390514" is out of range

Can anyone give me some advice on what to look for, or how to proceed?

Please note that everything is currently from the stock mythbuntu install
with the sole exception of the lirc patch to create lirc_zilog. Do I need to
update anything else from source?

Is lirc_zilog supposed to handle the receiving as well as the blasting? Or
will I continue to use ir-kbd-i2c for receiving? What should be in my lirc
hardware.conf?

Or is there a better way to do this without using lirc_zilog?

Thanks for the help!

Dave





_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
If I were you, I would use a Fedora and/or MythDora distro, rather than Mythbuntu. Why? Because the maintainer of lirc_zilog, Jarod Wilson, is a Fedora developer and a current Fedora based distro may "just work" at least when it comes to IR blasting/receiving.

FWIW, I do use Mythbuntu and have two HVR-1600 cards, but I don't need the IR blaster functionality. I tried briefly to get lirc_zilog to work for receiving, but ran into a snag. I forget what the snag was and switched to ir-kbd-i2c, which works for me.

HTH,
Helen
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
I found the answer to the "out of range" errors here:

http://www.gossamer-threads.com/lists/mythtv/users/441961#441961

which is to patch lirc.h to change lirc_t to unsigned int.

It took me a while to make this work until I figured out that the lirc
configure script generated by setup.sh installed to /usr/local/sbin but the
daemon was running from /usr/sbin.

So now I am able to use lirc_zilog for both receiving and transmitting. Next
step is to figure out which codes work with my Motorola DCH70 cable box.

Thanks to Jarod Wilson for your work on this driver!

Dave

-----Original Message-----
From: David Lasker [mailto:dave@altosdesign.com]
Sent: Saturday, July 03, 2010 9:27 AM
To: 'Discussion about mythtv'
Subject: RE: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in
Mythbuntu .23/10.04

Jul 3 09:03:04 mythtv lircd-0.8.6[1110]: error in configfile line 62:
Jul 3 09:03:04 mythtv lircd-0.8.6[1110]: "2147549184" is out of range
.
...lots of out of range errors deleted...
.
Jul 3 09:03:06 mythtv lircd-0.8.6[1156]: error in configfile line 30944:
Jul 3 09:03:06 mythtv lircd-0.8.6[1156]: "2195390542" is out of range

I am thinking I will be OK if I can fix the out of range messages. Any
suggestions on how to do that?

Thanks for the help!

Dave

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
On Sat, Jul 3, 2010 at 12:27 PM, David Lasker <dave@altosdesign.com> wrote:
...
> So it looks to me like the receive part of the driver is working.

Yep, that all looks sane.

> So I changed hardware.conf like this:
>
> REMOTE_MODULES="lirc_dev lirc_zilog"
> REMOTE_DEVICE="/dev/lirc0"
> TRANSMITTER_MODULES="lirc_dev lirc_zilog"
> TRANSMITTER_DEVICE="/dev/lirc0"
>
> and reboot. After the reboot I see that both /dev/lirc0 and /dev/lirc1 are
> created:
>
> dave@mythtv:~$ ls /dev/lirc*
> /dev/lirc0  /dev/lirc1  /dev/lircd  /dev/lircd1
>
> Is that supposed to happen?

No. This is because of debian/ubuntu's brain-dead setup, which I've
long since filed a bug against, not being bright enough to simply ask
the user "hey, are the rx and tx device one in the same, because if
they are, I should only start ONE lircd and not create this bogus
second device node!". Oh, and the inclusion of lirc_dev on the
_MODULES lines is almost as dumb. If you modprobe
lirc_anything_but_dev, lirc_dev is *always* automagically also loaded,
because modprobe is bright enough to understand that lirc_dev is a
dependency of every single lirc_anything_but_dev module.

In short, the proper hardware.conf for your device should omit all
references to lirc_dev, as well as removing the redundant
TRANSMITTER_* lines. All you need is the one section and the one
lircd.conf from Mark's pages, which has all the needed bits for both
rx from the bundled remote and tx.

--
Jarod Wilson
jarod@wilsonet.com
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
Hi Jarod, thanks for the reply!

It's sorta working now, but I always get a crash of lircd on bootup. I don't
see any errors in dmesg or syslog. There isn't much useful info in
/var/log/lircd, just:

Jul 4 08:55:16 mythtv lircd: lircd(default) ready, using
/var/run/lirc/lircd
Jul 4 08:55:16 mythtv lircd: caught signal

It always seems to recover when I run
/etc/init.d/lirc restart.

Maybe this is a result of adding the "unsigned int" to lirc.h? Or maybe it's
an initialization order problem?

Is there any way I can get additional info (like a backtrace) to help debug
this?

After deleting the transmitter section as you suggested, I now have only a
single lircd socket, but there are still 2 /dev/lircx devices:

crw-rw---- 1 root root 61, 0 2010-07-04 08:55 /dev/lirc0
crw-rw---- 1 root root 61, 1 2010-07-04 08:55 /dev/lirc1
lrwxrwxrwx 1 root root 19 2010-07-04 09:03 /dev/lircd ->
/var/run/lirc/lircd

Is that OK?

Thanks for the help!

Dave

-----Original Message-----
From: mythtv-users-bounces@mythtv.org
[mailto:mythtv-users-bounces@mythtv.org] On Behalf Of Jarod Wilson
Sent: Saturday, July 03, 2010 7:19 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] Need help with Hauppauge HRV-1600 IR Blaster and
lirc_zilog in Mythbuntu .23/10.04

In short, the proper hardware.conf for your device should omit all
references to lirc_dev, as well as removing the redundant
TRANSMITTER_* lines. All you need is the one section and the one
lircd.conf from Mark's pages, which has all the needed bits for both
rx from the bundled remote and tx.

--
Jarod Wilson
jarod@wilsonet.com
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
Some more tests show that the bootup crash is intermittent. With

REMOTE_MODULES="lirc_zilog"

it crashes most of the time. Just for fun I tried

REMOTE_MODULES="lirc_dev lirc_zilog"

and it works most of the time.

So I think there is a race condition somewhere.

Any suggestions on how to debug this would be appreciated.

Thanks...

Dave

-----Original Message-----
From: David Lasker [mailto:dave at altosdesign.com]
Sent: Sunday, July 04, 2010 9:23 AM
To: 'Discussion about mythtv'
Subject: RE: [mythtv-users] Need help with Hauppauge HRV-1600 IR Blaster and
lirc_zilog in Mythbuntu .23/10.04

Hi Jarod, thanks for the reply!

It's sorta working now, but I always get a crash of lircd on bootup. I don't
see any errors in dmesg or syslog. There isn't much useful info in
/var/log/lircd, just:

Jul 4 08:55:16 mythtv lircd: lircd(default) ready, using
/var/run/lirc/lircd
Jul 4 08:55:16 mythtv lircd: caught signal

It always seems to recover when I run
/etc/init.d/lirc restart.

Maybe this is a result of adding the "unsigned int" to lirc.h? Or maybe it's
an initialization order problem?

Is there any way I can get additional info (like a backtrace) to help debug
this?

After deleting the transmitter section as you suggested, I now have only a
single lircd socket, but there are still 2 /dev/lircx devices:

crw-rw---- 1 root root 61, 0 2010-07-04 08:55 /dev/lirc0
crw-rw---- 1 root root 61, 1 2010-07-04 08:55 /dev/lirc1
lrwxrwxrwx 1 root root 19 2010-07-04 09:03 /dev/lircd ->
/var/run/lirc/lircd

Is that OK?

Thanks for the help!

Dave

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
On Sun, Jul 4, 2010 at 5:35 PM, David Lasker <dave@altosdesign.com> wrote:
> Some more tests show that the bootup crash is intermittent. With
>
> REMOTE_MODULES="lirc_zilog"
>
> it crashes most of the time. Just for fun I tried
>
> REMOTE_MODULES="lirc_dev lirc_zilog"
>
> and it works most of the time.
>
> So I think there is a race condition somewhere.

Hrm, that's not so good. First report I've seen of anything like this.
Will be digging into lirc_zilog again RSN, will keep an eye out for
possible causes.

> Any suggestions on how to debug this would be appreciated.

Load both lirc_zilog and lirc_dev with debug=1 module options, see
what falls out. After that, its code inspection and possibly manually
adding assorted printk fun and rebuilding a very verbose lirc_zilog
module to try to narrow down where things are going south.


--
Jarod Wilson
jarod@wilsonet.com
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
I have captured both good and crashed logs with modprobe parameter of
debug=1, with hardware.conf set to:

REMOTE_MODULES="lirc_zilog"

I don't see anything suspicious; the crashed log just stops in the middle. I
will try again with both lirc_dev and lirc_zilog loaded.

One thing I don't understand from both logs is why 2 clients are being found
at 0x70 and 0x71. I only have one HVR-1600 in my system. I also have an
HVR-1250, but that is the OEM version without the IR jack on the rear panel.
Maybe it also has the same I2C chip in it? Does lirc_zilog work on the newer
Hauppauge PCI express cards as well?

A 2nd question: are the messages
NAK expected: i2c_master_send failed with -6 (try x)
in the success log anything to be concerned about?

Here is /var/log/syslog (grepped for "lirc") from a successful startup:

Jul 7 11:58:36 mythtv kernel: [ 20.205645] lirc_dev: IR Remote Control
driver registered, major 61
Jul 7 11:58:36 mythtv kernel: [ 20.266442] lirc_zilog: Zilog/Hauppauge IR
driver initializing
Jul 7 11:58:36 mythtv kernel: [ 20.485542] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x70
Jul 7 11:58:36 mythtv kernel: [ 20.485962] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 7 11:58:36 mythtv kernel: [ 20.486376] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 7 11:58:36 mythtv kernel: [ 20.486378] lirc_zilog: chip found with RX
and TX
Jul 7 11:58:36 mythtv kernel: [ 20.486397] lirc_zilog: poll thread
started
Jul 7 11:58:36 mythtv kernel: [ 20.486399] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 7 11:58:36 mythtv kernel: [ 20.753476] lirc_zilog: firmware of size
302355 loaded
Jul 7 11:58:36 mythtv kernel: [ 20.753561] lirc_zilog: 743 IR blaster
codesets loaded
Jul 7 11:58:36 mythtv kernel: [ 20.753573] lirc_zilog: 01 60 00 01 5b
Jul 7 11:58:36 mythtv kernel: [ 20.754706] lirc_zilog: 05 02 04 4b 1a
Jul 7 11:58:36 mythtv kernel: [ 20.755841] lirc_zilog: 09 79 88 b1 1f
Jul 7 11:58:36 mythtv kernel: [ 20.757001] lirc_zilog: 0d 87 f5 16 61
Jul 7 11:58:36 mythtv kernel: [ 20.758704] lirc_zilog: 11 a6 d9 ec 9a
Jul 7 11:58:36 mythtv kernel: [ 20.759832] lirc_zilog: 15 0f a7 ab 27
Jul 7 11:58:36 mythtv kernel: [ 20.760988] lirc_zilog: 19 48 9d 7e 1a
Jul 7 11:58:36 mythtv kernel: [ 20.762259] lirc_zilog: 1d d9 0c 0e 48
Jul 7 11:58:36 mythtv kernel: [ 20.763401] lirc_zilog: 21 91 77 d6 3d
Jul 7 11:58:36 mythtv kernel: [ 20.764582] lirc_zilog: 25 09 44 18 60
Jul 7 11:58:36 mythtv kernel: [ 20.765976] lirc_zilog: 29 e5 12 c6 6c
Jul 7 11:58:36 mythtv kernel: [ 20.767183] lirc_zilog: 2d ba 32 c4 26
Jul 7 11:58:36 mythtv kernel: [ 20.768328] lirc_zilog: 31 e3 76 01 48
Jul 7 11:58:36 mythtv kernel: [ 20.769503] lirc_zilog: 35 a2 7d 81 59
Jul 7 11:58:36 mythtv kernel: [ 20.770908] lirc_zilog: 39 90 28 8f 48
Jul 7 11:58:36 mythtv kernel: [ 20.772055] lirc_zilog: 3d 79 61 b4 0a
Jul 7 11:58:36 mythtv kernel: [ 20.773232] lirc_zilog: 41 0b 57 21 6e
Jul 7 11:58:36 mythtv kernel: [ 20.774692] lirc_zilog: 45 00 78 ad 62
Jul 7 11:58:36 mythtv kernel: [ 20.775831] lirc_zilog: 49 b5 68 a2 27
Jul 7 11:58:36 mythtv kernel: [ 20.776996] lirc_zilog: 4d 42 4e da 6c
Jul 7 11:58:36 mythtv kernel: [ 20.778356] lirc_zilog: 51 94 63 0e 2a
Jul 7 11:58:36 mythtv kernel: [ 20.779486] lirc_zilog: 55 1a 30 3b 45
Jul 7 11:58:36 mythtv kernel: [ 20.780649] lirc_zilog: 59 fa 34 25 e5
Jul 7 11:58:36 mythtv kernel: [ 20.781889] lirc_zilog: 5d cb 1e c1 ee
Jul 7 11:58:36 mythtv kernel: [ 20.783174] lirc_zilog: 61 00 00 00 ee
Jul 7 11:58:36 mythtv kernel: [ 20.786990] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 7 11:58:36 mythtv kernel: [ 20.787005] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x71
Jul 7 11:58:36 mythtv kernel: [ 20.787461] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 7 11:58:36 mythtv kernel: [ 20.787910] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 7 11:58:36 mythtv kernel: [ 20.787912] lirc_zilog: chip found with RX
and TX
Jul 7 11:58:36 mythtv kernel: [ 20.787946] lirc_zilog: poll thread
started
Jul 7 11:58:36 mythtv kernel: [ 20.787949] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 7 11:58:36 mythtv kernel: [ 20.788010] lirc_zilog: 01 60 00 01 5b
Jul 7 11:58:36 mythtv kernel: [ 20.789185] lirc_zilog: 05 02 04 4b 1a
Jul 7 11:58:36 mythtv kernel: [ 20.790319] lirc_zilog: 09 79 88 b1 1f
Jul 7 11:58:36 mythtv kernel: [ 20.791447] lirc_zilog: 0d 87 f5 16 61
Jul 7 11:58:36 mythtv kernel: [ 20.792603] lirc_zilog: 11 a6 d9 ec 9a
Jul 7 11:58:36 mythtv kernel: [ 20.793738] lirc_zilog: 15 0f a7 ab 27
Jul 7 11:58:36 mythtv kernel: [ 20.794866] lirc_zilog: 19 48 9d 7e 1a
Jul 7 11:58:36 mythtv kernel: [ 20.795997] lirc_zilog: 1d d9 0c 0e 48
Jul 7 11:58:36 mythtv kernel: [ 20.797160] lirc_zilog: 21 91 77 d6 3d
Jul 7 11:58:36 mythtv kernel: [ 20.798293] lirc_zilog: 25 09 44 18 60
Jul 7 11:58:36 mythtv kernel: [ 20.799428] lirc_zilog: 29 e5 12 c6 6c
Jul 7 11:58:36 mythtv kernel: [ 20.800581] lirc_zilog: 2d ba 32 c4 26
Jul 7 11:58:36 mythtv kernel: [ 20.801718] lirc_zilog: 31 e3 76 01 48
Jul 7 11:58:36 mythtv kernel: [ 20.802854] lirc_zilog: 35 a2 7d 81 59
Jul 7 11:58:36 mythtv kernel: [ 20.806606] lirc_zilog: 39 90 28 8f 48
Jul 7 11:58:36 mythtv kernel: [ 20.807741] lirc_zilog: 3d 79 61 b4 0a
Jul 7 11:58:36 mythtv kernel: [ 20.808901] lirc_zilog: 41 0b 57 21 6e
Jul 7 11:58:36 mythtv kernel: [ 20.810078] lirc_zilog: 45 00 78 ad 62
Jul 7 11:58:36 mythtv kernel: [ 20.811209] lirc_zilog: 49 b5 68 a2 27
Jul 7 11:58:36 mythtv kernel: [ 20.812344] lirc_zilog: 4d 42 4e da 6c
Jul 7 11:58:36 mythtv kernel: [ 20.813492] lirc_zilog: 51 94 63 0e 2a
Jul 7 11:58:36 mythtv kernel: [ 20.814645] lirc_zilog: 55 1a 30 3b 45
Jul 7 11:58:36 mythtv kernel: [ 20.825654] lirc_zilog: 59 fa 34 25 e5
Jul 7 11:58:36 mythtv kernel: [ 20.826785] lirc_zilog: 5d cb 1e c1 ee
Jul 7 11:58:36 mythtv kernel: [ 20.827916] lirc_zilog: 61 00 00 00 ee
Jul 7 11:58:36 mythtv kernel: [ 20.837292] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 7 11:58:36 mythtv kernel: [ 20.837334] lirc_zilog: initialization
complete
Jul 7 11:58:42 mythtv kernel: [ 26.404387] lirc_zilog: poll called
Jul 7 11:58:42 mythtv kernel: [ 26.404392] lirc_zilog: poll result = 0
Jul 7 11:58:42 mythtv kernel: [ 26.404632] lirc_zilog: 01 60 6e 33 d9
Jul 7 11:58:42 mythtv kernel: [ 26.405768] lirc_zilog: 05 d1 0e 48 91
Jul 7 11:58:42 mythtv kernel: [ 26.406902] lirc_zilog: 09 77 d6 3d 09
Jul 7 11:58:42 mythtv kernel: [ 26.408058] lirc_zilog: 0d 44 18 60 e8
Jul 7 11:58:42 mythtv kernel: [ 26.409439] lirc_zilog: 11 34 ce 78 be
Jul 7 11:58:42 mythtv kernel: [ 26.410572] lirc_zilog: 15 23 8c fc 78
Jul 7 11:58:42 mythtv kernel: [ 26.411704] lirc_zilog: 19 cb 01 48 a2
Jul 7 11:58:42 mythtv kernel: [ 26.412886] lirc_zilog: 1d 7d 81 59 90
Jul 7 11:58:42 mythtv kernel: [ 26.415609] lirc_zilog: 21 28 8f 59 08
Jul 7 11:58:42 mythtv kernel: [ 26.416789] lirc_zilog: 25 10 c5 7b 7a
Jul 7 11:58:42 mythtv kernel: [ 26.417923] lirc_zilog: 29 26 50 1f 71
Jul 7 11:58:42 mythtv kernel: [ 26.419053] lirc_zilog: 2d 09 dc 13 c4
Jul 7 11:58:42 mythtv kernel: [ 26.420189] lirc_zilog: 31 19 d3 55 c0
Jul 7 11:58:42 mythtv kernel: [ 26.421345] lirc_zilog: 35 4f c9 ac 17
Jul 7 11:58:42 mythtv kernel: [ 26.422478] lirc_zilog: 39 9c f1 d5 e5
Jul 7 11:58:42 mythtv kernel: [ 26.423613] lirc_zilog: 3d cf c4 ba 05
Jul 7 11:58:42 mythtv kernel: [ 26.424772] lirc_zilog: 41 cb 81 e5 26
Jul 7 11:58:42 mythtv kernel: [ 26.425911] lirc_zilog: 45 f3 f1 b7 6e
Jul 7 11:58:42 mythtv kernel: [ 26.427051] lirc_zilog: 49 88 29 c2 f6
Jul 7 11:58:42 mythtv kernel: [ 26.428250] lirc_zilog: 4d bb e7 9f 1a
Jul 7 11:58:42 mythtv kernel: [ 26.429422] lirc_zilog: 51 ed 39 93 45
Jul 7 11:58:42 mythtv kernel: [ 26.430563] lirc_zilog: 55 cd 3b d9 1c
Jul 7 11:58:42 mythtv kernel: [ 26.431705] lirc_zilog: 59 89 fe b7 5d
Jul 7 11:58:42 mythtv kernel: [ 26.432888] lirc_zilog: 5d 82 7e fc 2f
Jul 7 11:58:42 mythtv kernel: [ 26.434033] lirc_zilog: 61 00 00 00 2f
Jul 7 11:58:42 mythtv kernel: [ 26.489447] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 1)
Jul 7 11:58:42 mythtv kernel: [ 26.602919] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 2)
Jul 7 11:58:42 mythtv kernel: [ 26.660911] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 3)
Jul 7 11:58:42 mythtv kernel: [ 26.712914] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 4)
Jul 7 11:58:42 mythtv kernel: [ 26.764829] lirc_zilog: sent code 84, key
0
Jul 7 11:58:42 mythtv kernel: [ 26.764855] lirc_zilog: poll called
Jul 7 11:58:42 mythtv kernel: [ 26.764857] lirc_zilog: poll result = 0
Jul 7 11:58:42 mythtv kernel: [ 26.764910] lirc_zilog: poll called
Jul 7 11:58:42 mythtv kernel: [ 26.764911] lirc_zilog: poll result = 0
Jul 7 11:58:42 mythtv kernel: [ 26.764961] lirc_zilog: poll called
Jul 7 11:58:42 mythtv kernel: [ 26.764963] lirc_zilog: poll result = 0
Jul 7 11:58:42 mythtv kernel: [ 26.862208] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:43 mythtv kernel: [ 27.122189] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:43 mythtv kernel: [ 27.382004] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:43 mythtv kernel: [ 27.431619] lirc_zilog: 01 60 6e 33 d9
Jul 7 11:58:43 mythtv kernel: [ 27.432792] lirc_zilog: 05 d1 0e 48 91
Jul 7 11:58:43 mythtv kernel: [ 27.433920] lirc_zilog: 09 77 d6 3d 09
Jul 7 11:58:43 mythtv kernel: [ 27.435049] lirc_zilog: 0d 44 18 60 e8
Jul 7 11:58:43 mythtv kernel: [ 27.436206] lirc_zilog: 11 34 ce 78 be
Jul 7 11:58:43 mythtv kernel: [ 27.437345] lirc_zilog: 15 23 fc e8 78
Jul 7 11:58:43 mythtv kernel: [ 27.438474] lirc_zilog: 19 cb 01 48 a2
Jul 7 11:58:43 mythtv kernel: [ 27.439604] lirc_zilog: 1d 7d 81 59 90
Jul 7 11:58:43 mythtv kernel: [ 27.440765] lirc_zilog: 21 28 8f 58 09
Jul 7 11:58:43 mythtv kernel: [ 27.441896] lirc_zilog: 25 10 c5 7b 7a
Jul 7 11:58:43 mythtv kernel: [ 27.443044] lirc_zilog: 29 26 50 1f 71
Jul 7 11:58:43 mythtv kernel: [ 27.444197] lirc_zilog: 2d 09 dc 12 c4
Jul 7 11:58:43 mythtv kernel: [ 27.445374] lirc_zilog: 31 18 d2 55 c0
Jul 7 11:58:43 mythtv kernel: [ 27.446552] lirc_zilog: 35 4f c9 ac 17
Jul 7 11:58:43 mythtv kernel: [ 27.447779] lirc_zilog: 39 9c f1 d5 e5
Jul 7 11:58:43 mythtv kernel: [ 27.449055] lirc_zilog: 3d cf c4 ba 05
Jul 7 11:58:43 mythtv kernel: [ 27.450248] lirc_zilog: 41 cb 81 e5 26
Jul 7 11:58:43 mythtv kernel: [ 27.451382] lirc_zilog: 45 f3 f1 b7 6e
Jul 7 11:58:43 mythtv kernel: [ 27.452541] lirc_zilog: 49 88 29 c2 f6
Jul 7 11:58:43 mythtv kernel: [ 27.453717] lirc_zilog: 4d bb e7 9f 1a
Jul 7 11:58:43 mythtv kernel: [ 27.454855] lirc_zilog: 51 ed 39 93 45
Jul 7 11:58:43 mythtv kernel: [ 27.455984] lirc_zilog: 55 cd 3b d9 1c
Jul 7 11:58:43 mythtv kernel: [ 27.457141] lirc_zilog: 59 89 fe b7 5d
Jul 7 11:58:43 mythtv kernel: [ 27.458347] lirc_zilog: 5d 82 7e e9 5f
Jul 7 11:58:43 mythtv kernel: [ 27.459512] lirc_zilog: 61 00 00 00 5f
Jul 7 11:58:43 mythtv kernel: [ 27.512916] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 1)
Jul 7 11:58:43 mythtv kernel: [ 27.564935] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 2)
Jul 7 11:58:43 mythtv kernel: [ 27.616926] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 3)
Jul 7 11:58:43 mythtv kernel: [ 27.668941] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 4)
Jul 7 11:58:43 mythtv kernel: [ 27.720947] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 5)
Jul 7 11:58:43 mythtv kernel: [ 27.772946] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 6)
Jul 7 11:58:43 mythtv kernel: [ 27.824846] lirc_zilog: sent code 84, key
3
Jul 7 11:58:43 mythtv kernel: [ 27.824872] lirc_zilog: poll called
Jul 7 11:58:43 mythtv kernel: [ 27.824876] lirc_zilog: poll result = 0
Jul 7 11:58:43 mythtv kernel: [ 27.824878] lirc_zilog: poll called
Jul 7 11:58:43 mythtv kernel: [ 27.824878] lirc_zilog: poll result = 0
Jul 7 11:58:43 mythtv kernel: [ 27.824918] lirc_zilog: poll called
Jul 7 11:58:43 mythtv kernel: [ 27.824921] lirc_zilog: poll result = 0
Jul 7 11:58:43 mythtv kernel: [ 27.826547] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:44 mythtv kernel: [ 28.085711] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:44 mythtv kernel: [ 28.345697] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:44 mythtv kernel: [ 28.491613] lirc_zilog: 01 60 6e 33 d9
Jul 7 11:58:44 mythtv kernel: [ 28.492779] lirc_zilog: 05 d1 0e 48 91
Jul 7 11:58:44 mythtv kernel: [ 28.493908] lirc_zilog: 09 77 d6 3d 09
Jul 7 11:58:44 mythtv kernel: [ 28.495036] lirc_zilog: 0d 44 18 60 e8
Jul 7 11:58:44 mythtv kernel: [ 28.496180] lirc_zilog: 11 34 ce 78 be
Jul 7 11:58:44 mythtv kernel: [ 28.497315] lirc_zilog: 15 23 84 f2 78
Jul 7 11:58:44 mythtv kernel: [ 28.498449] lirc_zilog: 19 cb 01 48 a2
Jul 7 11:58:44 mythtv kernel: [ 28.499678] lirc_zilog: 1d 7d 81 59 90
Jul 7 11:58:44 mythtv kernel: [ 28.500842] lirc_zilog: 21 28 8f 59 08
Jul 7 11:58:44 mythtv kernel: [ 28.502028] lirc_zilog: 25 11 c5 7b 7a
Jul 7 11:58:44 mythtv kernel: [ 28.503155] lirc_zilog: 29 26 50 1f 71
Jul 7 11:58:44 mythtv kernel: [ 28.504303] lirc_zilog: 2d 09 dc 13 c4
Jul 7 11:58:44 mythtv kernel: [ 28.505467] lirc_zilog: 31 18 d2 55 c0
Jul 7 11:58:44 mythtv kernel: [ 28.506597] lirc_zilog: 35 4f c9 ac 17
Jul 7 11:58:44 mythtv kernel: [ 28.507725] lirc_zilog: 39 9c f1 d5 e5
Jul 7 11:58:44 mythtv kernel: [ 28.508875] lirc_zilog: 3d cf c4 ba 05
Jul 7 11:58:44 mythtv kernel: [ 28.510052] lirc_zilog: 41 cb 81 e5 26
Jul 7 11:58:44 mythtv kernel: [ 28.511182] lirc_zilog: 45 f3 f1 b7 6e
Jul 7 11:58:44 mythtv kernel: [ 28.512329] lirc_zilog: 49 88 29 c2 f6
Jul 7 11:58:44 mythtv kernel: [ 28.513494] lirc_zilog: 4d bb e7 9f 1a
Jul 7 11:58:44 mythtv kernel: [ 28.514640] lirc_zilog: 51 ed 39 93 45
Jul 7 11:58:44 mythtv kernel: [ 28.515768] lirc_zilog: 55 cd 3b d9 1c
Jul 7 11:58:44 mythtv kernel: [ 28.516936] lirc_zilog: 59 89 fe b7 5d
Jul 7 11:58:44 mythtv kernel: [ 28.518098] lirc_zilog: 5d 82 7e f2 26
Jul 7 11:58:44 mythtv kernel: [ 28.519245] lirc_zilog: 61 00 00 00 26
Jul 7 11:58:44 mythtv kernel: [ 28.573003] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 1)
Jul 7 11:58:44 mythtv kernel: [ 28.624978] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 2)
Jul 7 11:58:44 mythtv kernel: [ 28.676921] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 3)
Jul 7 11:58:44 mythtv kernel: [ 28.728926] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 4)
Jul 7 11:58:44 mythtv kernel: [ 28.780944] lirc_zilog: NAK expected:
i2c_master_send failed with -6 (try 5)
Jul 7 11:58:44 mythtv kernel: [ 28.834213] lirc_zilog: sent code 84, key
4
Jul 7 11:58:44 mythtv kernel: [ 28.834240] lirc_zilog: poll called
Jul 7 11:58:44 mythtv kernel: [ 28.834242] lirc_zilog: poll result = 0
Jul 7 11:58:44 mythtv kernel: [ 28.835894] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:44 mythtv kernel: [ 28.836128] lirc_zilog: poll called
Jul 7 11:58:44 mythtv kernel: [ 28.836131] lirc_zilog: poll result = 0
Jul 7 11:58:44 mythtv kernel: [ 28.836174] lirc_zilog: poll called
Jul 7 11:58:44 mythtv kernel: [ 28.836176] lirc_zilog: poll result = 0
Jul 7 11:58:45 mythtv kernel: [ 29.097699] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:45 mythtv kernel: [ 29.361690] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:45 mythtv kernel: [ 29.622487] lirc_zilog: key (0x00/0x00)
Jul 7 11:58:45 mythtv kernel: [ 29.881779] lirc_zilog: key (0x00/0x00)

Here is /var/log/syslog from the startup that failed:

Jul 8 08:52:02 mythtv kernel: [ 18.449321] lirc_dev: IR Remote Control
driver registered, major 61
Jul 8 08:52:02 mythtv kernel: [ 18.545207] lirc_zilog: Zilog/Hauppauge IR
driver initializing
Jul 8 08:52:02 mythtv kernel: [ 18.546311] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x70
Jul 8 08:52:02 mythtv kernel: [ 18.546702] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 8 08:52:02 mythtv kernel: [ 18.547089] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 8 08:52:02 mythtv kernel: [ 18.547090] lirc_zilog: chip found with RX
and TX
Jul 8 08:52:02 mythtv kernel: [ 18.547149] lirc_zilog: poll thread
started
Jul 8 08:52:02 mythtv kernel: [ 18.547154] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 8 08:52:02 mythtv kernel: [ 18.759135] lirc_zilog: firmware of size
302355 loaded
Jul 8 08:52:02 mythtv kernel: [ 18.759266] lirc_zilog: 743 IR blaster
codesets loaded
Jul 8 08:52:02 mythtv kernel: [ 18.759278] lirc_zilog: 01 60 00 01 5b
Jul 8 08:52:02 mythtv kernel: [ 18.760936] lirc_zilog: 05 02 04 4b 1a
Jul 8 08:52:02 mythtv kernel: [ 18.762565] lirc_zilog: 09 79 88 b1 1f
Jul 8 08:52:02 mythtv kernel: [ 18.764197] lirc_zilog: 0d 87 f5 16 61
Jul 8 08:52:02 mythtv kernel: [ 18.765844] lirc_zilog: 11 a6 d9 ec 9a
Jul 8 08:52:02 mythtv kernel: [ 18.782147] lirc_zilog: 15 0f a7 ab 27
Jul 8 08:52:02 mythtv kernel: [ 18.783799] lirc_zilog: 19 48 9d 7e 1a
Jul 8 08:52:02 mythtv kernel: [ 18.785441] lirc_zilog: 1d d9 0c 0e 48
Jul 8 08:52:02 mythtv kernel: [ 18.787198] lirc_zilog: 21 91 77 d6 3d
Jul 8 08:52:02 mythtv kernel: [ 18.788850] lirc_zilog: 25 09 44 18 60
Jul 8 08:52:02 mythtv kernel: [ 18.798150] lirc_zilog: 29 e5 12 c6 6c
Jul 8 08:52:02 mythtv kernel: [ 18.799793] lirc_zilog: 2d ba 32 c4 26
Jul 8 08:52:02 mythtv kernel: [ 18.801453] lirc_zilog: 31 e3 76 01 48
Jul 8 08:52:02 mythtv kernel: [ 18.803215] lirc_zilog: 35 a2 7d 81 59
Jul 8 08:52:02 mythtv kernel: [ 18.805066] lirc_zilog: 39 90 28 8f 48
Jul 8 08:52:02 mythtv kernel: [ 18.814137] lirc_zilog: 3d 79 61 b4 0a
Jul 8 08:52:02 mythtv kernel: [ 18.815767] lirc_zilog: 41 0b 57 21 6e
Jul 8 08:52:02 mythtv kernel: [ 18.817416] lirc_zilog: 45 00 78 ad 62
Jul 8 08:52:02 mythtv kernel: [ 18.819178] lirc_zilog: 49 b5 68 a2 27
Jul 8 08:52:02 mythtv kernel: [ 18.820838] lirc_zilog: 4d 42 4e da 6c
Jul 8 08:52:02 mythtv kernel: [ 18.838151] lirc_zilog: 51 94 63 0e 2a
Jul 8 08:52:02 mythtv kernel: [ 18.839785] lirc_zilog: 55 1a 30 3b 45
Jul 8 08:52:02 mythtv kernel: [ 18.841444] lirc_zilog: 59 fa 34 25 e5
Jul 8 08:52:02 mythtv kernel: [ 18.851027] lirc_zilog: 5d cb 1e c1 ee
Jul 8 08:52:02 mythtv kernel: [ 18.852687] lirc_zilog: 61 00 00 00 ee
Jul 8 08:52:02 mythtv kernel: [ 18.867129] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 8 08:52:02 mythtv kernel: [ 18.867144] lirc_zilog: ir_probe: adapter
id=0x0, client addr=0x71
Jul 8 08:52:02 mythtv kernel: [ 18.867700] lirc_zilog: probe 0x70 @ cx18
i2c driver #0-0: success
Jul 8 08:52:02 mythtv kernel: [ 18.868260] lirc_zilog: probe 0x71 @ cx18
i2c driver #0-0: success
Jul 8 08:52:02 mythtv kernel: [ 18.868261] lirc_zilog: chip found with RX
and TX
Jul 8 08:52:02 mythtv kernel: [ 18.876518] lirc_zilog: poll thread
started
Jul 8 08:52:02 mythtv kernel: [ 18.876521] lirc_dev:
lirc_register_driver: sample_rate: 0
Jul 8 08:52:02 mythtv kernel: [ 18.876951] lirc_zilog: 01 60 00 01 5b
Jul 8 08:52:02 mythtv kernel: [ 18.878544] lirc_zilog: 05 02 04 4b 1a
Jul 8 08:52:02 mythtv kernel: [ 18.880135] lirc_zilog: 09 79 88 b1 1f
Jul 8 08:52:02 mythtv kernel: [ 18.881741] lirc_zilog: 0d 87 f5 16 61
Jul 8 08:52:02 mythtv kernel: [ 18.884625] lirc_zilog: 11 a6 d9 ec 9a
Jul 8 08:52:02 mythtv kernel: [ 18.886467] lirc_zilog: 15 0f a7 ab 27
Jul 8 08:52:02 mythtv kernel: [ 18.889214] lirc_zilog: 19 48 9d 7e 1a
Jul 8 08:52:02 mythtv kernel: [ 18.890966] lirc_zilog: 1d d9 0c 0e 48
Jul 8 08:52:02 mythtv kernel: [ 18.892577] lirc_zilog: 21 91 77 d6 3d
Jul 8 08:52:02 mythtv kernel: [ 18.902099] lirc_zilog: 25 09 44 18 60
Jul 8 08:52:02 mythtv kernel: [ 18.903687] lirc_zilog: 29 e5 12 c6 6c
Jul 8 08:52:02 mythtv kernel: [ 18.905300] lirc_zilog: 2d ba 32 c4 26
Jul 8 08:52:02 mythtv kernel: [ 18.917654] lirc_zilog: 31 e3 76 01 48
Jul 8 08:52:02 mythtv kernel: [ 18.919013] lirc_zilog: 35 a2 7d 81 59
Jul 8 08:52:02 mythtv kernel: [ 18.920673] lirc_zilog: 39 90 28 8f 48
Jul 8 08:52:02 mythtv kernel: [ 18.923397] lirc_zilog: 3d 79 61 b4 0a
Jul 8 08:52:02 mythtv kernel: [ 18.925380] lirc_zilog: 41 0b 57 21 6e
Jul 8 08:52:02 mythtv kernel: [ 18.927368] lirc_zilog: 45 00 78 ad 62
Jul 8 08:52:02 mythtv kernel: [ 18.929042] lirc_zilog: 49 b5 68 a2 27
Jul 8 08:52:02 mythtv kernel: [ 18.938153] lirc_zilog: 4d 42 4e da 6c
Jul 8 08:52:02 mythtv kernel: [ 18.939778] lirc_zilog: 51 94 63 0e 2a
Jul 8 08:52:02 mythtv kernel: [ 18.941430] lirc_zilog: 55 1a 30 3b 45
Jul 8 08:52:02 mythtv kernel: [ 18.950377] lirc_zilog: 59 fa 34 25 e5
Jul 8 08:52:02 mythtv kernel: [ 18.952006] lirc_zilog: 5d cb 1e c1 ee
Jul 8 08:52:02 mythtv kernel: [ 18.953652] lirc_zilog: 61 00 00 00 ee
Jul 8 08:52:02 mythtv kernel: [ 18.965705] lirc_zilog: Zilog/Hauppauge IR
blaster firmware version 2.1.0 loaded
Jul 8 08:52:02 mythtv kernel: [ 18.966038] lirc_zilog: initialization
complete

On Mon, Jul 5, 2010 at 2:20 PM, Jarod Wilson <jarod [at] wilsonet> wrote:
> Some more tests show that the bootup crash is intermittent. With
>
> REMOTE_MODULES="lirc_zilog"
>
> it crashes most of the time. Just for fun I tried
>
> REMOTE_MODULES="lirc_dev lirc_zilog"
>
> and it works most of the time.
>
> So I think there is a race condition somewhere.

Hrm, that's not so good. First report I've seen of anything like this.
Will be digging into lirc_zilog again RSN, will keep an eye out for
possible causes.

> Any suggestions on how to debug this would be appreciated.

Load both lirc_zilog and lirc_dev with debug=1 module options, see
what falls out. After that, its code inspection and possibly manually
adding assorted printk fun and rebuilding a very verbose lirc_zilog
module to try to narrow down where things are going south.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: Need help with Hauppauge HRV-1600 IR Blaster and lirc_zilog in Mythbuntu .23/10.04 [ In reply to ]
On Thu, Jul 8, 2010 at 12:25 PM, David Lasker <dave@altosdesign.com> wrote:
> I have captured both good and crashed logs with modprobe parameter of
> debug=1, with hardware.conf set to:
>
> REMOTE_MODULES="lirc_zilog"
>
> I don't see anything suspicious; the crashed log just stops in the middle.

Hrm, lame. Can you post the hung log by itself? May be able to tell
where it is in the init sequence (assuming its during init that it
fails) from that.

> I will try again with both lirc_dev and lirc_zilog loaded.
>
> One thing I don't understand from both logs is why 2 clients are being found
> at 0x70 and 0x71.

The chip has separate i2c bus addresses for tx and rx, so that's
normal. (0x70 is tx, 0x71 is rx).

> I only have one HVR-1600 in my system. I also have an
> HVR-1250, but that is the OEM version without the IR jack on the rear panel.
> Maybe it also has the same I2C chip in it?

Nope, there's no zilog on the hvr-1250 (I have that card myself).

> Does lirc_zilog work on the newer
> Hauppauge PCI express cards as well?

It should, if they have zilog z8 chips. I think some of the newer
cards actually switched to a cx23888 chip for IR though (which Andy
Walls is working on support for right now).

> A 2nd question: are the messages
> NAK expected: i2c_master_send failed with -6 (try x)
> in the success log anything to be concerned about?

Nope. Code snippet:

/*
* This bit NAKs until the device is ready, so we retry it
* sleeping a bit each time. This seems to be what the windows
* driver does, approximately.
* Try for up to 1s.
*/
for (i = 0; i < 20; ++i) {
set_current_state(TASK_UNINTERRUPTIBLE);
schedule_timeout((50 * HZ + 999) / 1000);
ret = i2c_master_send(&ir->c_tx, buf, 1);
if (ret == 1)
break;
dprintk("NAK expected: i2c_master_send "
"failed with %d (try %d)\n", ret, i+1);
}

As long as you get a reply within 20 tries, its fine.

--
Jarod Wilson
jarod@wilsonet.com
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users