Okay...I've got one of these Dvico_MCE remotes and it won't work. I've read several threads here about them and what people have done to make them work. I've tried following their steps (including getting newer config files with the MCE remote stuff included) and copying files to the right places. I've also tried running lirc-reconfig but get no resulting log file to verify. (I do get a splash screen when running it that says 'Dvico' and, looking in the reconfig script, see where that's getting executed from so I believe it's working.)

While trying to trace the logic in my head of what runs when, and performing troublshooting, I checked the daemon.log and find the following lines...

mythtv lircd-0.9.0pre4-pvr150[3366] accepted new client on /dev/lircd
mythtv lircd-0.9.0pre4-pvr150[3366] could not open /dev/lirc
mythtv lircd-0.9.0pre4-pvr150[3366] default_init(): no such device
mythtv lircd-0.9.0pre4-pvr150[3366] caught signal

and, looking in dmesg I see the following:

usbcore: registered new driver hiddev
hiddev96: USB HID v1.10 Device [DVICO DVICO USB HID Remocon v1.00] on USB 0000:00:02.11

I haven't seen any other entries under other posts with these exact messages, so I'm a little in the dark. It would seem LIRC isn't running as attempting to run irw gets me the "connection refused" (or some such) message.

Where do I look to troubleshoot this...?

Look at what you posted. USB remotes don't use /dev/lirc, rather it uses /dev/usb/hiddevX. Check /etc/lirc/hardware.conf.

_________________
cesman

When the source is open, the possibilities are endless!

Well, it says..

DEVICE="/dev/usb/hiddev0"
MODULES="lirc_dev"

As you said, it SHOULD be using hiddev0. Where my confusion is coming from is where the '/dev/lirc' is being set, and is this a change I can make with a text editor or something the config script should be doing?

Hmm strange. Try something like (as root):

set -x
/etc/init.d/lirc start

and post your output. Hopefully this will show the command it is running to start your lircd daemon.

Hi, Greg.

This is what I get onscreen after typing what you've given:

+/etc/init.d/lirc start
Starting lirc daemon: lircd.


So, looking at lirc, I see the following early on in the file:



I'm not very familiar with shell scripting, but I can see where /dev/lirc is being set. Can you (or anyone reading this) help with the proper script change(s) to detect the device on /dev/usb/hiddev0 and set that value? I say detect since the receiver may be plugged into some other port and I'm not sure if that will change the value hiddev0.

The [ "$DEVICE" = /dev/lirc ] test should fail (from your previous post, $DEVICE should be set to /dev/usb/hiddev0), so the argument added when starting lirc should be --device=$DEVICE (i.e. --device=/dev/usb/hiddev0).

edit /dev/init.d/lirc and make the first line after the comments at the top "set -x"

Then run "/etc/init.d/lirc restart" as root.

You will see all of the commands that are executed it may be more enlightening.

Thanks for the excellent tip. I did as you suggested and saw those commands--including several that seemed to point to /dev/usb/hiddev0 as being recognized. However, I wanted to somehow echo the screen results to a logfile I can print and compare to the lirc file's contents offline.

This may be a really simple question, but what do I do to feed the screen output to a file?

Will write both the stdout and stderr into a file.

That was just what I'd needed...I'd found some docs on Debian and tried a variation of that, but it didn't work. I didn't have the syntax right.

Okay, here are the results of lirc when it runs...



What do the lines with ++ mean--environment variables being set, perhaps...?

Does anyone have a pointer to a good tutorial on shell script programming and troubleshooting...?

Wierd. The last few lines logged on my system when I do the same thing are:

Notice that you are missing everything on the line after the /usr/sbin/lircd bit.
Check your /etc/init.d/lirc script.
The relevant line should look like this:
Sorry it took so long to get back to you but I went away for a long weekend and was incommunicado.

I appreciate the reply...it got me to where I can run irw now, and can go on from there. Hope your extended weekend was good!

Regards, Phil C.