[tequila]

Alright, now I moved the whole xbmc to a SSD. Actually of course I did not move it, I reinstalled ubuntu 10.04 LS and reinstalled xbmc and copied my old profile data to the new SSD. So far everything is okay but then came LIRC.

I also copied the LIRC configuration, since I didn´t change anything but the disk
I expected no problems but the remote doesn´t work in XBMC.

The config files are pretty much default since it is a ms compatible mceusb:


lircd.conf

Code:

#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

#Configuration for the Windows Media Center Transceivers/Remotes (all) remote:
include "/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb"

hardware.conf:

Code:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Windows Media Center Transceivers/Remotes (all)"
REMOTE_MODULES="lirc_dev lirc_mceusb"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

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

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""

lirc is in startup but the remote isn´t working in xbmc.

However if I run the "Remote Control Properties" GUI Tool, let it detect the Windows Media Center Remote then "Use supplied remote control"
OR the actually detected one HP / TSGH-IR01 with "Use different remote control". The test inside the tool works and the remote in XBMC then too.

Bad thing is, once I restart the PC nothing works again. Even though the "Remote Control Properties" Tool stores the following:

Code:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Windows Media Center Transceivers/Remotes (all)"
REMOTE_MODULES="lirc_mceusb"
REMOTE_DRIVER="default"
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD=true

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

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""

# Receiver settings required by gnome-lirc-properties
RECEIVER_MODEL="Windows\ Media\ Center\ Remote"
RECEIVER_VENDOR="Microsoft"

# Remote settings required by gnome-lirc-properties
REMOTE_MODEL="TSGH-IR01"
REMOTE_VENDOR="HP"

Code:

#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

#Configuration for the Windows Media Center Transceivers/Remotes (all) remote:
include "/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb"


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

Anyone with an idea what could be wrong ?
I know there is a lot of configuration possible with lirc but actually the former system was also 10.04 with exactly this remote.

thanks

[LB06]

What kernel are you running?

Code:

uname -r

Because it's possible that in the past you ran 2.6.32 (original kernel for Lucid), but now you 2.6.35. This could have been automatically selected by the installer (if you did a netinstall), the virtual package linux-image-2.6-generic/server or of course manually (aptitude install linux-image-2.6.35).

Point is, since 2.6.35 an in-kernel interface for remote events has been merged into the mainline kernel. This can conflict with the LIRC drivers and interface. With newer versions of Linux and lirc I would have suggested to bridge the two interfaces, but with Lucid I would recommend against this, since the new interface is a bit flaky in 35, 36 and 37.

So I suggest you do one of these two things (well, if you indeed run 2.6.35): install 2.6.32 or blacklist all ir-* and rc-* modules. Most notably these ones:

blacklist ir_core
blacklist ir_lirc_codec
blacklist ir_sony_decoder
blacklist ir_jvc_decoder
blacklist ir_rc6_decoder
blacklist ir_rc5_decoder
blacklist ir_nec_decoder
blacklist mceusb

These are all drivers for the new in-kernel interface. You should use the lirc-* modules. Then reboot and lirc should be operational again.

Good article on this: http://wilsonet.com/?page_id=95

[tequila]

hmm it is 2.6.32-32-generic

[LB06]

hmm it is 2.6.32-32-generic

Then forget what I said. It's something else. Does /etc/lirc0 exist? Sometimes it's called /dev/lircd.

[tequila]

you mean /dev/lirc0 ?

yes exists but this and lircd are empty there, I assume this is normal ?


-----SOLUTION-------------------8<------------------------------

I don´t know why but I found out that it works when I restart lirc:

sudo /etc/init.d/lirc restart

to have this automated I simply added the line

"/etc/init.d/lirc restart" before the "end" row in:

/etc/rc.local


thats probably a dirty solution but it works ;-)

[darkscout]

It's a link to a device, it really can't be 'non empty'.

What does irw output?

[tequila]

doesn´t output anything until I press a button on remote.... thats actually not the problem, the remote works well, just xbmc... however found a solution now :-) thanks everybody, thread can be closed I think