| Author |
Message |
|
tophee
|
 Posted: Sat Sep 19, 2009 11:12 am |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
|
Hello,
Until I upgraded to R6, my remote control was working well. I did have to tweak a few files, hardware.conf and the lirc files (going from memory on that one) to get it going properly.
Through the menus in R6 I can't get the remote to work correctly. The remote is detected - the arrow keys work However selecting either Nova-t or Silver as the remote, and Hauppauge / default as a receiver doesn't seem to do he trick.
Is this just me? I'll file a flyspay bug if necessary.
Running Nova-T card with the attached IR dongle. (full spec in sig.)
Ta
Edit: CHECK NEXT PAGE FOR SOLUTION
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
Last edited by tophee on Fri Feb 05, 2010 2:45 am, edited 5 times in total.
|
|
| Top |
|
 |
|
mad_paddler
|
Posted: Mon Sep 21, 2009 3:25 am |
|
|
Joined: Sun Jun 12, 2005 2:39 pm
Posts: 464
Location:
UK
|
The Nova-T remote has always been a little different, i think it's detected as a keyboard which is why some of the buttons work out of the box but not all of them.
You could try my old guide/configs from this thread: http://mysettopbox.tv/phpBB2/viewtopic.php?t=6089
The paths for files might be slightly different in R6...
|
|
| Top |
|
|
|
tophee
|
Posted: Thu Sep 24, 2009 1:02 pm |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
|
Thanks for the reply (several days late) mad_paddler, but I am at a loss. Can anyone tell me where the equivalent to the hardware.conf file lives under R6?
In previous versions to R6 this file needed a few minor alterations to make everything work properly, i.e. telling myth to stop treating the remote like a keyboard!
I've found all the lirc files by looking in a few folders that looked promising, but I've not found what I've been looking for.
Using the 'find' command hasn't turned anything up either.
Many thanks.
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
goofee
|
Posted: Thu Sep 24, 2009 2:15 pm |
|
|
Joined: Sat Feb 03, 2007 12:52 am
Posts: 187
Location:
Manitoba, Canada
|
|
I noticed a bunch of that hardware stuff in the lircd start up script. Have a look through /etc/sv/lircd/run and see if that's what your looking for.
|
|
| Top |
|
|
|
nmcaullay
|
Posted: Thu Sep 24, 2009 6:38 pm |
|
|
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location:
Perth, Australia
|
second that... i have an avermedia777 which has a remote, and i used to faff around with the lirc* and hardware.conf files... when R6 came along I played around to get the remote working again, and remember that hardware.conf didnt have a place to go... /etc/sv/lircd/run is where I put my changes... theres probably a "correct" method to do it, but I simply replaced the contents of the run file with this..
Code: #!/bin/bash
exec /usr/sbin/lircd -n -H devinput -d "/dev/input/by-path/pci-0000:01:08.0-event-" 2>/dev/null 1>/dev/null
I was looking at udev so that when reboot the device would be adressable at the same location, but then found a simpler way using /by-path/ which seems to map devices identically between reboots..
I couldnt figure out the proper place to make my hardware.conf-like changes, so I just whacked what my remote needed in that /etc/sv/lircd/run file..
Might help, might not?
Nathan
_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector
|
|
| Top |
|
|
|
tophee
|
Posted: Fri Sep 25, 2009 12:49 am |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Thanks for those suggestions guys, I'll have a look in there tonight / over the weekend. Hopefully I won't get stuck. If I work out what changes are needed, I'll update here.
Or I'll be back asking for more help 
-edit-
Actually Nathan what does this do? Code: #!/bin/bash
exec /usr/sbin/lircd -n -H devinput -d "/dev/input/by-path/pci-0000:01:08.0-event-" 2>/dev/null 1>/dev/null
Just for reference you know - I know so little about code in any way shape or form.
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
tjc
|
Posted: Fri Sep 25, 2009 8:15 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
tophee wrote: what does this do? Code: #!/bin/bash
exec /usr/sbin/lircd -n -H devinput -d "/dev/input/by-path/pci-0000:01:08.0-event-" 2>/dev/null 1>/dev/null . Which part? The exec is there so that the rest of the command replaces the bash process with standard output (file descriptor 1) and standard error (2) sent to the bit bucket device (/dev/null). If you want me to break it down further just ask.
|
|
| Top |
|
|
|
tophee
|
Posted: Sat Sep 26, 2009 3:45 pm |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
|
Thank you tjc for offering an explanation but I'm afraid I'm not sure I fully understand it. However, I think it pushed me in the right direction. To knowing what it's supposed to do at least.
Im afraid I was hoping for a "yes this'll fix it" responce but it seems nathan's code will do what I needed it to do. (i.e tell myth to stop treating my remote like a keyboard).
If I've understood it correctly, (after a little reading) is that /usr/sbin/lircd -n -H is telling myth to use lirc deamon without running in the background and use a specific driver which is denoted by the "dev/input/by-path/pci-0000:01:08.0-event"... Correct?
While, the devinput -d refers to giving lirc control of ir devics (because of the HAL conflict).
I'm still not quite sure what the 2>/dev/null 1>/dev/null does though.
Have I got that right so far?
Regards Chris
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
mad_paddler
|
Posted: Mon Sep 28, 2009 4:56 am |
|
|
Joined: Sun Jun 12, 2005 2:39 pm
Posts: 464
Location:
UK
|
|
-H devinput <-- this is the lirc driver
-d "/dev/input/by-path/pci-0000:01:08.0-event-" <-- this is the device lirc will use (you will need to change this to the appropriate one)
2>/dev/null 1>/dev/null <-- this just redirects all logging/output to /dev/null i.e. it effectively disables all logging
|
|
| Top |
|
|
|
tophee
|
Posted: Mon Oct 05, 2009 10:41 am |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Finally I've had five minutes to get back to this...
Anyhow, I changed the /etc/sv/lircd/run file to accommodate the ir receiver on my box, which I identified by using the cat /proc/input/devices command.
I got for the Nova-T which the ir is plugged into:
I: Bus=0001 Vendor=0070 Product=9002 Version=0001
N: Name="cx88 IR (Hauppauge Nova-T DVB-T"
P: Phys=pci-0000:05:00.2/ir0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=100003
B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc And the IR was also identified further down the cat /proc/input/devices list here: I: Bus=0001 Vendor=13c2 Product=100f Version=0001
N: Name="Budget-CI dvb ir receiver saa7146 (0)"
P: Phys=pci-0000:05:02.0/ir0
S: Sysfs=/class/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=100003
B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc
So my version of nmcaullay's line in my /etc/sv/lircd/run looks like this:
Code: #!/bin/bash
exec /usr/sbin/lircd -n -H devinput -d "/dev/input/by-path/pci-0000:05:02.0-event-" 2>/dev/null 1>/dev/null
The remote still works as well as it did, (arrows, OK and the numbers), but the other keys such as 'back' do not.
Any more help would be greatly appreciated.
Chris
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
Greg Frost
|
Posted: Mon Oct 05, 2009 4:57 pm |
|
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
The best way to deal with this so it works "out of the box" would be to create a udev rule which matches on the name of the device. See:
http://linhes.org/cgit/cgit.cgi/LinHES- ... coIR.rules
Which shows how this was done for the Dvico card (which had the additional complication of being a dual care where the rule had to match the first tuner only). The first rule is for the dual card and the second is for the USB dongle that comes with older cards.
|
|
| Top |
|
|
|
tophee
|
Posted: Tue Oct 06, 2009 7:13 am |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Thanks for the reply Greg,
I had to read the link you posted several times to get a sense of what you are telling me. Actually it too me a couple of goes to spot the difference between 5.02.0 and 5.00.2, which I hadn't realised when I posted yesterday.
Now I think I have some understanding of what you are getting at, but I'm not 100% on this at this moment.
What I think I understand is the id of the card and the id of the reciever need to be the same? Or at least pointing at the same thing. If I am to modify your Dvico script, I think it should look something like this?
Code: KERNEL=="event*", \
KERNELS=="*-1", \
ATTRS{manufacturer}=="Hauppauge", \
ATTRS{idVendor}=="0070", \
ATTRS{idProduct}=="9002", \
SYMLINK="input/irremote"
But I may be barking wildly up the wrong tree.
What I am still trying to understand is how this actually does what it's supposed to do.
Further thoughts appreciated.
Ta
Chris
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
Greg Frost
|
Posted: Tue Oct 06, 2009 4:41 pm |
|
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
|
That is only really part of the solution It causes the udev system to create a symbolic link to the device (in the case you have shown it would be calles /dev/input/irremote). You can then access the device using the symbolic link. It means that anyone with hardware that is recognised by its manufacturer name, vendor and product id will create the same symbolic link. That then means that the lirc run script can use the symbolic link in lircd command rather then the /dev/input/by-path/... which would otherwise need to vary from user to user depending on what motherboard they had and which slot the device was installed in.
So getting a udev rule that works for your device is the first step in making your remote just work out of the box via selection from the service menu.
|
|
| Top |
|
|
|
tophee
|
Posted: Tue Oct 13, 2009 7:44 am |
|
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Ok, I've had another look at this again. And I'm still not making any great headway.
I've been looking at some recent logs, specifically: /var/log/lircd which suggests it's sort of working, but there are some issues.
Code: Oct 13 01:02:45 Mythtv lircd: lircd(devinput) ready
Oct 13 01:02:55 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 01:02:55 Mythtv lircd: initializing '/dev/input/by-path/pci-0000:05:02.0-event6'
Oct 13 01:02:55 Mythtv lircd: unable to open '/dev/input/by-path/pci-0000:05:02.0-event6'
Oct 13 01:02:55 Mythtv lircd: WARNING: Failed to initialize hardware
Oct 13 01:02:56 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 02:07:35 Mythtv lircd: caught signal
Oct 13 02:07:35 Mythtv lircd: closing '/dev/input/by-path/pci-0000:05:02.0-event6'
Oct 13 12:21:32 Mythtv lircd: lircd(devinput) ready
Oct 13 12:21:43 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 12:21:43 Mythtv lircd: initializing '/dev/input/by-path/pci-0000:05:02.0-event6'
Oct 13 12:21:43 Mythtv lircd: unable to open '/dev/input/by-path/pci-0000:05:02.0-event6'
Oct 13 12:21:43 Mythtv lircd: WARNING: Failed to initialize hardware
Oct 13 12:21:44 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 12:21:46 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 12:24:05 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 12:24:07 Mythtv lircd: removed client
Oct 13 12:24:07 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 12:24:10 Mythtv lircd: removed client
Oct 13 13:07:50 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:07:52 Mythtv lircd: removed client
Oct 13 13:07:52 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:07:54 Mythtv lircd: removed client
Oct 13 13:08:32 Mythtv lircd: removed client
Oct 13 13:08:49 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:11:12 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:11:41 Mythtv lircd: removed client
Oct 13 13:46:30 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:46:39 Mythtv lircd: removed client
Oct 13 13:46:53 Mythtv lircd: accepted new client on /dev/lircd
Oct 13 13:47:00 Mythtv lircd: removed client
Oct 13 13:47:02 Mythtv lircd: accepted new client on /dev/lircd
Obviously something isn't working right.
I've been trying to understand how LinHES handles lirc and tells it what to look for.
Having has a root around, I've found where the key lircrc and the lircd are:/usr/MythVantage/templates/remotes. I've got the Nova_T remote selects with the default receiver set under >Service menu>Linhes configuration>Remotes, the codes and all that seem to be correct for the remote.
What I'm missing is the bit of code / file that points lirc to use them corectly I've tried to read through the /etc/sv/lircd/run to see if I could work it out, but I'm at a loss.
Any suggestions gratefully received.
_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
| Top |
|
|
|
goofee
|
Posted: Tue Oct 13, 2009 8:34 am |
|
|
Joined: Sat Feb 03, 2007 12:52 am
Posts: 187
Location:
Manitoba, Canada
|
/etc/lircd.conf and /etc/lircrc should point to the proper config templates.
Code: $ more /etc/lircd.conf
include "/usr/MythVantage/templates/transmit/motorola_dsr305/lircd.conf"
Can't say anything about your log errors. I'm seeing some of those to and can't get the ir blaster to work every time.
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register