Well I am at a wits end where to go next. Since installing 5E50 I have not been able to get the remote to work.

I have changed the hardware.conf to point /dev/usb/hiddev0

to get irw to work I have to /usr/sbin/lircd --drivers=dvico --device=/dev/usb/hiddev0. I have added that line to bootmisc.sh till I can find the proper place to put it. This is less than ideal because I have to manually enter the /usr/sbin/lircd thing if I stop or restart lircd

Mode2 reports "error opening /dev/lirc" thats because there is no /dev/lirc

lircd.conf and lircrc look to be correct for my remote.

I can not get irrecord to work, it thinks maybe lircd is running but I have stopped it using /etc/init.d/lirc stop. I wanted to do this to check that the lircd.conf was correct. I think it probably is ok because when I run irw the description on the screen is correct for those buttons that I have pushed.

Eddy

_________________
R8.1 combined backend/frontend
ASUS P7H55-M Pro
Intel i3-550, 4Gb Ram
Seagate 500GB (Sata)
2x Dvico DVB-T Lite & Sony PlayTV (usb twin tuner)
TP-Link TL-WN881ND PCIe wifi card (not working)
Logitech Harmony One remote, CoolerMaster ATC-S case

- The /etc/lirc/hardware.conf file is not used directly by lircd it's used by the /etc/init.d/lirc script that starts lircd, and passes the information from the file on the command line.

- You have to tell those other commands the right device to use on the command line just like the init script does for lircd. e.g.:

Otherwise it will default to /dev/lirc. Also note that "--driver" is singular for both lircd and irrecord. The mode2 command needs similar options.


- Before attempting to run irrecord or mode2 make _really_ sure that there is no lircd process running using pgrep and pkill.

If you've _really_ stopped it you should not see that second entry. You can kill it using:


- Use lsmod to see if the driver has been loaded and check the /dev directory to see if the lirc devices are present once the driver has been modprobed.

BTW - Using a bit of BBS code to mark up you postings can make them easier to read...

When my room mate and I updated our KnoppMyth box we had some weird issues with lirc as well. We had config files that out of the box were pointing both to /dev/lirc and /dev/hiddev0 when in reality the device was /dev/lirc0. A temporary fix was to symlink the device, but that gets wiped out any time you reboot. We had to go in and change the appropriate scripts. Make sure you get them all because there may be a few you need to reconfigure for your system.

_________________
thanky

Hint taken, I will study the BBCode.

I now understand the irrecord and mode2 syntax, I will try that when the family are not watching tele.

Perhaps I didn't explain it very well or I misunderstood your reply but I can not get irw to work unless I input in a terminal
what I am looking for is where to put that code so it loads with lircd. At least that is what I thought it ought to do.


There is obviously more scripts than I thought. I have only be playing with which scripts are you referring too?

Gee the BBCode does add some Bling!

The lirc init script /etc/init.d/lirc should assemble that command for you, if you get the settings in /etc/lirc/hardware.conf right. I suspect this is the "other script" xearthianx was talking about. If you look at the lirc init script you can actually trace how it reads in hardware.conf, assembles the arguments (mostly in the build_args function) and puts them on the lircd command line.