mceusb on the newer version (1.0 beta)

[sharktooth]

(28th Feb, 2014 01:51 AM)f1vefour Wrote:  

(28th Feb, 2014 01:26 AM)sharktooth Wrote:  # /etc/lirc/hardware/mceusb_event0.conf
#
# Arguments which will be used when launching lircd
#LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
#DRIVER="devinput"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
#DEVICE="/dev/input/event0"
MODULES="mceusb lirc_dev"
#MODULES="lirc_dev mceusb"

# Default configuration files for your hardware if any
LIRCD_CONF="/etc/lirc/remotes/mceusb.conf"
#LIRCMD_CONF=""
xbian@xbian ~ $[/term]

You should be able to change the bold section to this:

#DEVICE="/dev/lirc0"
DEVICE="/dev/input/event0"

---

I'm flying by the seat of my pants, I use a GPIO remote.

I made the changes and restarted (and then rebooted, just to make sure), still no dice. irw gives nothing, irrecord still fails with the "gap not found", and mode2 gives nothing. My hardware/custom.conf file now looks like :

Terminal

# /etc/lirc/hardware/mceusb_event0.conf
#
# Arguments which will be used when launching lircd
#LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
#DRIVER="devinput"
# usually /dev/lirc0 is the correct setting for systems using udev
#DEVICE="/dev/lirc0"
DEVICE="/dev/input/event0"
MODULES="mceusb lirc_dev"
#MODULES="lirc_dev mceusb"

# Default configuration files for your hardware if any
LIRCD_CONF="/etc/lirc/remotes/mceusb.conf"
#LIRCMD_CONF=""

Ideas?

[f1vefour]

Let's go about this a different way, see the following information:

http://forum.xbian.org/showthread.php?tid=2003

[sharktooth]

(28th Feb, 2014 05:27 PM)f1vefour Wrote:  Let's go about this a different way, see the following information:

http://forum.xbian.org/showthread.php?tid=2003

That did it! I'll be testing with a few reboots, but that process allowed me to re-learn the remote codes! THANK YOU SO MUCH!

[f1vefour]

(1st Mar, 2014 02:08 PM)sharktooth Wrote:  

(28th Feb, 2014 05:27 PM)f1vefour Wrote:  Let's go about this a different way, see the following information:

http://forum.xbian.org/showthread.php?tid=2003

That did it! I'll be testing with a few reboots, but that process allowed me to re-learn the remote codes! THANK YOU SO MUCH!

Your welcome, it took me awhile to remember what the issue really was.

I'm glad you reported back and let me know it resolved your issue.