mceusb on the newer version (1.0 beta)

[sharktooth]

Hello, everyone;

I used to have a nice, wonderful, working version of xbian complete with using the mceusb receiver and a learning remote. It was working great until an update completely destroyed it (I can't even get the lirc configuration files off of the old system, and there was nothing in /boot any more). As a result, I had to reinstall, but the only option was xbian 1.0 beta. This wonderful system doesn't follow the old ways of using /etc/init.d, and even then, mode2 no longer shows anything. I know the receiver is receiving because it flashes a light when I press a button.

I now no longer have an /dev/lirc0 device. Using irrecord on event0 gives :

irrecord: gap not found, can't continue
irrecord: closing '/dev/input/event0'

mode2 simply either says it can't handle the /dev/input/event0 hardware :

root@xbian:/home/xbian# mode2 -H devinput -d /dev/input/event0
mode2: initializing '/dev/input/event0'
mode2: WARNING: can't get exclusive access to events coming from `/dev/input/event0' interface
This program does not work for this hardware yet
root@xbian:/home/xbian#

Or it tells me it can't open /dev/lirc0 :

root@xbian:/home/xbian# mode2
mode2: could not get file information for /dev/lirc0
mode2: default_init(): No such file or directory
root@xbian:/home/xbian#

Because irrecord or mode2 are failing, I've scoured the Internet looking for ANYTHING to help me fix this on my own. The tutorials that all call out using mode2 and irrecord have failed for me. Theses documents were used when I set it up last time, too, so I know they are old enough that they probably don't apply any more. Has anyone set up an mceusb with the xbian 1.0 beta system? If so, how did you do it? Are you using a new process?

[IriDium]

Why are you still using Beta 1.0.

We've moved on to Beta 1.1, Beta 2 and now RC1.

I's upgrade to the latest edition and see if you still get the same error.

[sharktooth]

(25th Feb, 2014 03:03 AM)IriDium Wrote:  Why are you still using Beta 1.0.

Thanks for the help, IriDium!

I was using 1.0 Beta 2 because it was the only option from the OS X "installer" (which was obtained using the downloads page at http://www.xbian.org/download/). The "dd" image linked to from that same download page is "XBian 1.0 Beta 2". When I try the Linux installer on my CentOS computer, I simply get :

[root@arsenic tmp]# ./XBian-installer
./XBian-installer: error while loading shared libraries: libxkbcommon.so.0: cannot open shared object file: No such file or directory
[root@arsenic tmp]#

Can't find an RPM providing that, either :

[root@aconite tmp]# yum provides '*/lib*/libxkbcommon.*'
[snipping to shorten the response]
No Matches found
[root@aconite tmp]#

And the missing library is definitely not installed :

[root@aconite tmp]# ldconfig -p|grep libxkbcommon
[root@aconite tmp]#

I am definitely running X windows, because I'm typing this response in Chrome on the same CentOS computer. If you have a link to an updated dd image (e.g. the RC1 image), I'd take that in a heart beat.

Again, thanks for even looking and for any pointers you can send my direction, IriDium!

[IriDium]

You are NOT running X windows - well on the RPi and Xbian unless you have the RaspXbian installed.

To get to RC1 - use the current image and upgrade - see the steps in the thread Beta 2.

[sharktooth]

(26th Feb, 2014 02:08 AM)IriDium Wrote:  You are NOT running X windows - well on the RPi and Xbian unless you have the RaspXbian installed.

To get to RC1 - use the current image and upgrade - see the steps in the thread Beta 2.

Very true - I wasn't running X on the RPi - I was running it on a CentOS workstation - it wasn't specified it required to be running on xbian from what I saw. I'll get it updated through the xbian-config command. Thanks again!

[sharktooth]

(26th Feb, 2014 03:23 AM)sharktooth Wrote:  I'll get it updated through the xbian-config command. Thanks again!

So, I updated it. No dice - it seems to be exactly the same. Leaving lira running and firing off irw doesn't give me any output when hitting buttons. Stopping lirc and running irrecord still gives me :

Terminal

irrecord: gap not found, can't continue
irrecord: closing '/dev/input/event0'

Looking at the USB, the device is definitely recognized (and it also flashes a red LED when I push buttons, so the device is recognizing data from the remote).

Terminal

root@xbian:/home/xbian# lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
root@xbian:/home/xbian# mode2 -H devinput -d /dev/input/event0
mode2: initializing '/dev/input/event0'
mode2: WARNING: can't get exclusive access to events coming from `/dev/input/event0' interface
This program does not work for this hardware yet
root@xbian:/home/xbian#

I've seen posts about running "dpkg-reconfigure lirc", but that simply fails with :

Terminal

root@xbian:/home/xbian# dpkg-reconfigure lirc
dpkg-query: package 'lirc' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
/usr/sbin/dpkg-reconfigure: lirc is not installed
root@xbian:/home/xbian#

Yet, I can start it up :

Terminal

root@xbian:/home/xbian# service lirc start
lirc start/running
root@xbian:/home/xbian# ps awx|grep lircd
766 ? Ss 0:00 sudo -u xbian /usr/local/lib/xbmc/xbmc.bin --standalone -fs --lircdev /run/lirc/lircd
820 ? RNl 321:02 /usr/local/lib/xbmc/xbmc.bin --standalone -fs --lircdev /run/lirc/lircd
10144 ? Ss 0:00 /usr/local/sbin/lircd --device=/dev/lirc0
10151 pts/2 S+ 0:00 grep lircd
root@xbian:/home/xbian#

Any ideas? Or, are there direct IR receivers that plug in and work the best with this? (Yes, I'm willing to abandon the old device that worked with a previous implementation of xbian in order to have something that works).

[f1vefour]

What is the output from 'lsmod'?

[sharktooth]

(27th Feb, 2014 04:34 PM)f1vefour Wrote:  What is the output from 'lsmod'?

lsmod output, and also the release information (just in case) :

Terminal

xbian@xbian ~ $ sudo lsmod
[sudo] password for xbian:
Module Size Used by
lirc_dev 8952 0
frandom 3296 1
vchiq 183244 2
mceusb 11301 0
rc_core 12464 3 lirc_dev,mceusb
xbian@xbian ~ $ cat /etc/*release
PRETTY_NAME="XBian RC1"
NAME="XBian"
VERSION_ID="knockout"
VERSION="RC1"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.xbian.org/"
SUPPORT_URL="http://forum.xbian.org/"
BUG_REPORT_URL="https://github.com/xbianonpi"
xbian@xbian ~ $

Again, thanks for looking here.

[f1vefour]

And the contents of /etc/lirc/lircd.conf

[sharktooth]

(28th Feb, 2014 01:08 AM)f1vefour Wrote:  And the contents of /etc/lirc/lircd.conf

lircd.conf and hardware/custom.conf :

Terminal

xbian@xbian ~ $ cat /etc/lirc/lircd.conf
begin remote

name mceusb
bits 13
flags RC6|CONST_LENGTH
eps 30
aeps 100

header 2698 843
one 461 423
zero 461 423
pre_data_bits 24
pre_data 0x1BFF83
gap 106225
suppress_repeat 2

toggle_bit_mask 0x8000
rc6_mask 0x100000000

begin codes
KEY_POWER 0x1B9A
KEY_POWER 0x1BF3
KEY_RECORD 0x1BE8
KEY_STOP 0x1BE6
KEY_PAUSE 0x1BE7
KEY_REWIND 0x1BEA
KEY_PLAY 0x1BE9
KEY_FORWARD 0x1BEB
KEY_PREVIOUSSONG 0x1BE4
KEY_NEXTSONG 0x1BE5
KEY_BACK 0x1BDC
KEY_CONTEXT_MENU 0x1BF0
KEY_UP 0x1BE1
KEY_LEFT 0x1BDF
KEY_RIGHT 0x1BDE
KEY_DOWN 0x1BE0
KEY_OK 0x1BDD
KEY_VOLUMEUP 0x1BEF
KEY_VOLUMEDOWN 0x1BEE
KEY_MUTE 0x1BF1
KEY_CHANNELUP 0x1BED
KEY_CHANNELDOWN 0x1BEC
KEY_SUBTITLE 0x1BDB
KEY_TV 0x1BDA
KEY_TV 0x1BB9
KEY_1 0x1BFE
KEY_2 0x1BFD
KEY_3 0x1BFC
KEY_4 0x1BFB
KEY_5 0x1BFA
KEY_6 0x1BF9
KEY_7 0x1BF8
KEY_8 0x1BF7
KEY_9 0x1BF6
KEY_STAR 0x1BE2
KEY_0 0x1BFF
KEY_HASHTAG 0x1BE3
KEY_DELETE 0x1BF5
KEY_TEXT 0x1BA5
KEY_RED 0x1BA4
KEY_GREEN 0x1BA3
KEY_YELLOW 0x1BA2
KEY_BLUE 0x1BA1
KEY_AUDIO 0x1BB8
KEY_PICTURES 0x1BB6
KEY_VIDEO 0x1BB5
KEY_HOME 0x1BF2
KEY_RECORD 0x1BB7
KEY_GUIDE 0x1BD9
KEY_SELECT 0x1BF4
KEY_RETURN 0x1BD8
end codes

end remote
xbian@xbian ~ $ cat /etc/lirc/hardware/custom.conf
# /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 ~ $

[f1vefour]

What do you get from:

Terminal

mode2 -H devinput -d /dev/lirc0

[sharktooth]

(28th Feb, 2014 01:30 AM)f1vefour Wrote:  What do you get from:

Terminal

mode2 -H devinput -d /dev/lirc0

Terminal

xbian@xbian ~ $ sudo mode2 -H devinput -d /dev/lirc0
[sudo] password for xbian:
mode2: initializing '/dev/lirc0'
mode2: unable to open '/dev/lirc0'
xbian@xbian ~ $

[f1vefour]

Your custom configuration is incorrect then.

What is in the /dev/input directory ?

[sharktooth]

(28th Feb, 2014 01:44 AM)f1vefour Wrote:  Your custom configuration is incorrect then.

What is in the /dev/input directory ?

Terminal

drwxr-xr-x 2 root root 60 Jan 1 1970 by-id
drwxr-xr-x 2 root root 60 Jan 1 1970 by-path
crw-rw---T 1 root input 13, 64 Feb 25 18:11 event0
crw-rw---T 1 root input 13, 63 Feb 25 18:11 mice

Additionally, drivers :

Terminal

xbian@xbian /sys/bus/usb/devices/1-1.2:1.0 $ ls -l
total 0
-r--r--r-- 1 root root 4096 Feb 27 03:19 bAlternateSetting
-r--r--r-- 1 root root 4096 Jan 1 1970 bInterfaceClass
-r--r--r-- 1 root root 4096 Jan 1 1970 bInterfaceNumber
-r--r--r-- 1 root root 4096 Feb 27 03:19 bInterfaceProtocol
-r--r--r-- 1 root root 4096 Feb 27 03:19 bInterfaceSubClass
-r--r--r-- 1 root root 4096 Feb 27 03:19 bNumEndpoints
lrwxrwxrwx 1 root root 0 Jan 1 1970 driver -> ../../../../../../../bus/usb/drivers/mceusb
drwxr-xr-x 2 root root 0 Feb 27 03:19 ep_01
drwxr-xr-x 2 root root 0 Feb 27 03:19 ep_81
-r--r--r-- 1 root root 4096 Feb 27 03:19 modalias
drwxr-xr-x 3 root root 0 Jan 1 1970 rc
lrwxrwxrwx 1 root root 0 Jan 1 1970 subsystem -> ../../../../../../../bus/usb
-r--r--r-- 1 root root 4096 Feb 27 03:19 supports_autosuspend
-rw-r--r-- 1 root root 4096 Jan 1 1970 uevent
xbian@xbian /sys/bus/usb/devices/1-1.2:1.0 $

If you can tell me the process of setting up the custom.conf, that would be a victory I'd take.

[f1vefour]

(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.