Created attachment 463827 [details]
modified keycodes and added BTN_STAR and BTN_POUND

Created attachment 463828 [details]
DIsh Network and other old remotes

I made a mistake using "OK" as a dish key.  It should have been "select":

[rja@moria lirc]$ irsend SEND_ONCE dish select
irsend: command failed: SEND_ONCE dish select
irsend: hardware does not support sending

Same result.

Load mceusb and ir-core with debugging enabled (options ir-core debug=1, options mceusb debug=1), run lircd in the foreground (lircd -n), then try an irsend. Collect dmesg output and lircd output, and I'll see what I can see. I've got five mceusb devices of my own that all work just fine though, transmit and receive.

I didn't need to use the debug options on those modules.  Running "lircd -n", which uses the default driver was all it took to get irsend to work.  It does not transmit if lircd is configured by gnome-lirc-properties to run as:

/usr/sbin/lircd --driver=devinput --device=/dev/input/event9

with the devinput driver, /var/log/messages shows:

Dec  1 06:48:14 moria lircd-0.8.7[4864]: you should specify a valid gap value
Dec  1 06:48:14 moria lircd-0.8.7[4864]: lircd(devinput) ready, using /var/run/lirc/lircd
Dec  1 06:48:23 moria lircd-0.8.7[4864]: accepted new client on /var/run/lirc/lircd
Dec  1 06:48:23 moria lircd-0.8.7[4864]: initializing '/dev/input/event9'
Dec  1 06:48:23 moria lircd-0.8.7[4864]: error processing command: SEND_ONCE dish select
Dec  1 06:48:23 moria lircd-0.8.7[4864]: hardware does not support sending
Dec  1 06:48:23 moria lircd-0.8.7[4864]: removed client
Dec  1 06:48:23 moria lircd-0.8.7[4864]: closing '/dev/input/event9'

This also appears in the syslog when configured with gnome-lirc-properties:

Dec  1 13:25:42 moria lircd-0.8.7[3495]: you are using an obsolete devinput config file: Success
Dec  1 13:25:42 moria lircd-0.8.7[3495]: get the new version at http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput: Success

If I replace the /etc/sysconfig/lirc and /etc/lirc/lircd.conf files that gnome-lirc-properties created with the files that I was using with Fedora 13, then lircd runs as:

/usr/sbin/lircd --device=/dev/lirc0

and both irw and irsend work.  The /etc/lirc/lircd.conf file that I was using in Fedora 13 is already attached as the second comment.  I'll attach the /etc/sysconfig/lirc file after this comment.

I did have to disable the in-kernel decoders and enable only the lirc bridge dirver (which I saw from your post on mythtv-users) because the arrow keys would cause a double entry with mythtv.  Running irw, the arrow keys would display both the keycodes and the escape sequence for an arrow key.  

[rja@moria ~]$ irw
^[[A000000037ff07be1 00 Up mceusb
000000037ff07be0 00 Down mceusb
^[[B000000037ff07be0 01 Down mceusb
000000037ff07bde 00 Right mceusb
^[[C000000037ff07bde 01 Right mceusb
^[[D000000037ff07bdf 00 Left mceusb

[root@moria ~]# cat /sys/class/rc/rc0/protocols
[rc-5] [nec] [rc-6] [jvc] [sony] [lirc]
[root@moria ~]# echo none +lirc > /sys/class/rc/rc0/protocols
[root@moria ~]# cat /sys/class/rc/rc0/protocols
rc-5 nec rc-6 jvc sony [lirc]

[rja@moria ~]$ irw
000000037ff07be1 00 Up mceusb
000000037ff07be0 00 Down mceusb
000000037ff07be0 01 Down mceusb
000000037ff07bde 00 Right mceusb
000000037ff07bdf 00 Left mceusb

If you still want debug output from the modules, then I can do that.

Created attachment 464116 [details]
/etc/sysconfig/lirc Fedora 13 config file which allows irsend to work.

D'oh. Yeah. I'd assumed you were using the same configs that were previously working. Yeah, tx definitely won't work if you're using it via lirc's devinput driver.

Nb: even better than 'none +lirc', you can just  echo 'lirc' into protocols. We still need an 'all' magic value to re-enable all of them, to make scripting this in the lirc initscript a bit more user-friendly... But in any case, yeah, I'll try to get a new package out the door sooner or later here that disables the in-kernel decode if lircd has been started up.

In the mean time... Not sure exactly what we should do with this bug. Technically, possibly NOTABUG.

Hello!  I have been using Fedora 14 for a few months now, so somewhere in between newbie and somewhat green, hahha.

I have a USB IR blaster, ...RECEIVER_MODEL="Media\ Center\ Ed.\ eHome\ Infrared\ Remote\ Transceiver\ \(1934:5168\)", that I cannot seem to get working.

Note that I have entered various command outputs to http://pastebin.com/37RqEwxb.

I have been following various posts, mentioned at the end of my pastebin, on the mceusb and Fintek/ehome 1934:5168.  I cannot seem to get it working.  I have been following instructions from various sites with no luck.

As roger mentioned above, the error I keep getting is "irsend: hardware does not support sending" which makes me believe the IR blaster is not enabled.

Does anyone have advice?  I just updated my kernel last night to the latest per Software Update, and now I am running "2.6.35.13-91.fc14.i686" and still have the same problem.

Jared mentioned, "tx definitely won't work if you're using it via lirc's devinput
driver", which is what mine is set to.

Can someone point me to specific instructions on what to do?  Or feel free to ask me to run a command to see the output.  I'd greatly appreciate it.

Thanks,
Mike

Today I noticed there was a new update for lirc 0.9.0, labeled 0.9.0-2.  I installed this and have noticed a few differences.  For one, I'm now able to see commands when I run irw.  That's a start!

Any thoughts or comments to get my IR blaster working will greatly be appreciated!
~NewBuntu81 (Mike)


A. Firmware from DMESG 
[root@OptiPlex280-mbe Michael]# dmesg | grep firmware
[   10.576781] intel_rng: don't want to disable this in firmware setup, and if
[   11.849023] saa7164_downloadfirmware() no first image
[   11.849036] saa7164_downloadfirmware() Waiting for firmware upload (NXP7164-2010-03-10.1.fw)
[   12.389394] saa7164_downloadfirmware() firmware read 4019072 bytes.
[   12.389400] saa7164_downloadfirmware() firmware loaded.
[   12.389424] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072
[   12.389433] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[   12.389437] saa7164_downloadfirmware() BSLSize = 0x0
[   12.389441] saa7164_downloadfirmware() Reserved = 0x0
[   12.389446] saa7164_downloadfirmware() Version = 0x1661c00
[   13.359677] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   13.359966] ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   17.146667] cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   17.197288] cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   19.109047] starting firmware download(2)
[   23.739045] firmware download complete.



B. LIRC from DMESG
[root@OptiPlex280-mbe Michael]# dmesg | grep lirc
[   11.530128] lirc_dev: IR Remote Control driver registered, major 250 
[   11.534698] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[   44.106111] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[   44.108196] lirc_zilog: Zilog/Hauppauge IR driver initializing
[   44.111200] lirc_zilog: initialization complete
[root@OptiPlex280-mbe Michael]# 


C. IRSEND shows much more than ever showed before.
irsend LIST "" ""
buffer: -BEGIN-
buffer: -LIST  -
buffer: -SUCCESS-
buffer: -DATA-
buffer: -3-
buffer: -DC50X-
irsend: DC50X
buffer: -Hauppauge-
irsend: Hauppauge
buffer: -linux-input-layer-
irsend: linux-input-layer
buffer: -END-



D. IRSEND Additional info
irsend LIST DC50x ""
buffer: -BEGIN-
buffer: -LIST DC50x -
buffer: -SUCCESS-
buffer: -DATA-
buffer: -11-
buffer: -0000000000000001 1-
irsend: 0000000000000001 1
buffer: -0000000000000002 2-
irsend: 0000000000000002 2
buffer: -0000000000000003 3-
irsend: 0000000000000003 3
buffer: -0000000000000004 4-
irsend: 0000000000000004 4
buffer: -0000000000000005 5-
irsend: 0000000000000005 5
buffer: -0000000000000006 6-
irsend: 0000000000000006 6
buffer: -0000000000000007 7-
irsend: 0000000000000007 7
buffer: -0000000000000008 8-
irsend: 0000000000000008 8
buffer: -0000000000000009 9-
irsend: 0000000000000009 9
buffer: -000000000000000a 0-
irsend: 000000000000000a 0
buffer: -000000000000000b Enter-
irsend: 000000000000000b Enter
buffer: -END-
[root@OptiPlex280-mbe Michael]# irsend LIST DC50x 7
buffer: -BEGIN-
buffer: -LIST DC50x 7-
buffer: -SUCCESS-
buffer: -DATA-
buffer: -1-
buffer: -0000000000000007 7-
irsend: 0000000000000007 7
buffer: -END-


E. This now shows lircd1, which never showed before.
ls -al /dev/ |grep lirc
crw-------   1 root root    250,   0 May 15 18:01 lirc0
srw-rw-rw-   1 root root           0 May 15 18:01 lircd1


F. However, I'm still getting errors when I try to do an IRSEND to my device

G. The DC50X shown in part C is the name for the Comcast Pace DTA.  It is loaded in the lircd.conf file, located at /etc/lirc, which shows:

# This configuration has been automatically generated
# by the GNOME LIRC Properties control panel.
#
# Feel free to add any custom remotes to the configuration
# via additional include directives or below the existing
# include directives from your selected remote and/or
# transmitter.
#

# Configuration selected with GNOME LIRC Properties
include </etc/lirc/lircd.conf.pace>
include </etc/lirc/lircd.conf.gnome>
include </usr/local/bin/pace.conf>


H. The /etc/sysconfig/lirc shows:

# Note: in addition to these parameters, you need to have working    -*- sh -*-
# configuration file for lircd (and lircmd if enabled).

# Options to lircd(8).  Typically, this will be empty, as which driver to use
# should be specified using the LIRC_DRIVER variable below.
LIRCD_OPTIONS=""

# The infrared receiver (and/or transmitter) driver to be used by lircd(8),
# similar to passing "-H driver" to lircd(8).
# Run "/usr/sbin/lircd -H help" to get a listing of supported drivers.
LIRC_DRIVER="devinput"

# Which lirc device will be used by lircd(8).
# This is the same as passing "-d device" to lircd.
# An empty value will use the default /dev/lirc0 device.
LIRC_DEVICE="name=Media\?Center\?Ed.\?eHome\?Infrared\?Remote\?Transceiver\?\(1934:5168\)"

# If "yes", the init script will try to start lircmd(8) too.
ENABLE_LIRCMD="no"

# Options to lircmd(8).
LIRCMD_OPTIONS=""


# Remote settings required by gnome-lirc-properties
MODULES=""
LIRCD_CONF=""

# Receiver settings required by gnome-lirc-properties
RECEIVER_MODEL="Media\ Center\ Ed.\ eHome\ Infrared\ Remote\ Transceiver\ \(1934:5168\)"
RECEIVER_VENDOR="Linux\ Input\ Device"

# Remote settings required by gnome-lirc-properties
MODEL="Linux\ Input\ Layer\ compatible\ Remote"
VENDOR="Generic"

(In reply to comment #9)
> Today I noticed there was a new update for lirc 0.9.0, labeled 0.9.0-2.  I
> installed this and have noticed a few differences.  For one, I'm now able to
> see commands when I run irw.  That's a start!
> 
> Any thoughts or comments to get my IR blaster working will greatly be
> appreciated!
> ~NewBuntu81 (Mike)


It looks like you are trying to use "devinput" for transmitting, which won't work.  Instead, use "mceusb".

Try replacing your /etc/sysconfig/lirc file with the one that I use.  It is attached to comment #6 above.

I also had to add this command to /etc/rc.local:


echo lirc > /sys/class/rc/rc0/protocols

Thanks All.  I made those changes to my /etc/sysconfig/lirc file and restarted my computer; specifically, in the file I changed the LIRC_DRIVER from =
devinput" to ="mceusb.

I also added echo lirc > /sys/class/rc/rc0/protocols to my /etc/rc.local file.

I am receiving a different message now, that irsend could not connect to the socket.  So I tried restarting the LIRC and am receiving an error that the drier "mceusb" is not supported, and hence LIRC start has failed.  Any ideas?


DETAILS:

I'm now showing 3 lirc devies.
[root@OptiPlex280-mbe Michael]# ls -al /dev/ |grep lirc
crw-------   1 root root    250,   0 May 16 12:31 lirc0
srw-rw-rw-   1 root root           0 May 16 12:32 lircd
srw-rw-rw-   1 root root           0 May 16 12:32 lircd1


[root@OptiPlex280-mbe Michael]# dmesg | grep lirc
[   12.145115] lirc_dev: IR Remote Control driver registered, major 250 
[   12.150269] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[   34.377259] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[   34.379388] lirc_zilog: Zilog/Hauppauge IR driver initializing
[   34.381457] lirc_zilog: initialization complete
[root@OptiPlex280-mbe Michael]# 



[root@OptiPlex280-mbe Michael]# irsend LIST ""
irsend: could not connect to socket
irsend: No such file or directory


[root@OptiPlex280-mbe Michael]# /etc/init.d/lirc restart 
Stopping infrared remote control daemon (lircd):           [  OK  ]
Starting infrared remote control daemon (lircd): Driver `mceusb' not supported.
Supported drivers:
	accent
	alsa_usb
	asusdh
	atilibusb
	atwf83
	audio
	audio_alsa
	awlibusb
	bte
	bw6130
	commandir
	creative
	creative_infracd
	default
	devinput
	dfclibusb
	dsp
	dvico
	ea65
	ftdi
	i2cuser
	irlink
	irman
	livedrive_midi
	livedrive_seq
	logitech
	macmini
	mp3anywhere
	mplay
	mplay2
	mouseremote
	mouseremote_ps2
	null
	pcmak
	pinsys
	pixelview
	samsung
	sb0540
	silitek
	srm7500libusb
	tira
	tira_raw
	udp
	uirt2
	uirt2_raw
	usb_uirt_raw
	usbx
                                                           [FAILED]

OTHER OUTPUT:

[root@OptiPlex280-mbe Michael]# dmesg | grep lirc
[   12.145115] lirc_dev: IR Remote Control driver registered, major 250 
[   12.150269] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[   34.377259] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[   34.379388] lirc_zilog: Zilog/Hauppauge IR driver initializing
[   34.381457] lirc_zilog: initialization complete


[root@OptiPlex280-mbe Michael]# sudo gedit /etc/sysconfig/lirc
^C[root@OptiPlex280-mbe Michael]# dmesg | grep mceusb
[   11.844089] mceusb 5-1:1.0: Registered FINTEK eHome Infrared Transceiver on usb5:2
[   11.844175] usbcore: registered new interface driver mceusb
[   12.150269] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0

(In reply to comment #11)
> Thanks All.  I made those changes to my /etc/sysconfig/lirc file and restarted
> my computer; specifically, in the file I changed the LIRC_DRIVER from =
> devinput" to ="mceusb.

That's wrong. LIRC_DRIVER="" will work. (Or LIRC_DRIVER="default"). Its not the kernel driver you need to specify, its the lircd driver, which for all /dev/lircX devices, is "default".

Closing this NOTABUG, this is purely a configuration issue.

> I also added echo lirc > /sys/class/rc/rc0/protocols to my /etc/rc.local file.

This shouldn't be necessary with lirc-0.9.0-2, its done automatically by the lirc initscript.