Author |
Message |
Ravenium
|
Posted: Tue May 19, 2009 9:16 pm |
|
Joined: Thu Mar 23, 2006 5:47 pm
Posts: 22
|
Argh - I absolutely love the new features and improved performance of R6, but I don't understand why the remote configuration has become so troublesome. I'm now down to using my keyboard
Hardware: Hauppage PVR-150 (non-MCE). Not using the IRblaster because it's recording SD on a separate coax cable while I watch HD programs on the box.
Anyhow, I had the configs all working on the first release of R6 (thanks to you all on the forum). Ever since I upgraded to the 2nd release (with pacman), the remote has ceased to respond. I checked and all the configs are where they should be (links in ~mythtv to /etc/lircrc and lircd.conf). However, it looks as though it's ceased to load the lirc module (not sure if it should be lirc_dev or lirc_pvr150, but I believe the former has always worked for me).
None of the combinations of pseudo-pvr looking remotes, receivers, transmitters, whatever has worked in the LinHES setup menu. I can't find any errors that look to be related in the syslogs. If I modprobe for lirc_dev, it loads and seems to find the device, but it still doesn't seem to recognize my remote (via irw testing).
I feel as though this might result in a "what to look for if your remote isn't working" howto, but perhaps that might be good for everyone
Thanks!
P.S. Anyone else always get "FAIL" when they /etc/rc.d/servicename restart, only to have the service actually successfully restart?
|
|
Top |
|
|
3rdTimesCharm
|
Posted: Wed May 20, 2009 10:50 pm |
|
Joined: Mon Nov 05, 2007 2:30 pm
Posts: 8
|
I've just started using R6 and my lirc seems to be working well with my pvr150
Here's what I would start with for troubleshooting your problem:
What's the results from these commands:
lsmod | grep lirc
grep lirc /var/log/messages.log
ps axu | grep lirc
cat /etc/lircd.conf
Regarding your PS.
I have seen the "FAIL" for services that are restarted via /etc/rc.d/
I'm not positive, but it looks as if the fail occurs during a restart because of it's interaction with runsv, as in the process is already running again.
Do a "ps aux|grep runsv" and you will see the daemons being managed by runsv. Runsv seems to restart these daemons by design to keep them running for us.
I'm sure they will resolve this soon.
runsv is new to me but I did find the maintainers website url from "man runsv" , in case your interested:
http://smarden.org/runit/
|
|
Top |
|
|
3rdTimesCharm
|
Posted: Wed May 20, 2009 10:57 pm |
|
Joined: Mon Nov 05, 2007 2:30 pm
Posts: 8
|
|
Top |
|
|
Ravenium
|
Posted: Wed May 27, 2009 12:54 pm |
|
Joined: Thu Mar 23, 2006 5:47 pm
Posts: 22
|
Here are the outputs. I believe I had to manually modprobe lirc_dev, but I'd have to reboot to remember.
---
lsmod | grep lirc:
lirc_i2c 10756 0
lirc_dev 13492 1 lirc_i2c
i2c_core 22804 38 bttv,lirc_i2c,wm8775,cx25840,tuner,tea5767,tda8290,tda18271,tda827x,mt20xx,tea5761,nvidia,ivtv,v4l2_common,i2c_nforce2,cx88_vp3054_i2c,mt352,cx88xx,i2c_algo_bit,tveeprom,tuner_xc2028,s5h1409,xc5000,dvb_pll,s5h1411,or51132,cx24116,nxt200x,isl6421,stb6000,tda9887,tuner_simple,zl10353,cx24123,lgdt330x,stv0299,stv0288,cx22702
grep lirc /var/log/messages.log - nothing returns. However, /var/log/lircd:
May 27 11:06:02 mythboxen lircd: lircd(default) ready
May 27 11:06:16 mythboxen lircd: accepted new client on /dev/lircd
May 27 11:06:16 mythboxen lircd: could not get file information for /dev/lirc0
May 27 11:06:16 mythboxen lircd: default_init(): No such file or directory
May 27 11:06:16 mythboxen lircd: WARNING: Failed to initialize hardware
May 27 11:06:26 mythboxen lircd: removed client
in /etc/lircd.conf:
include "/usr/MythVantage/templates/remotes/hauppauge-silver/lircd-haupgrey.conf"
---
Out of curiosity, what settings do you have for your PVR150 in the LinHES setup? I can try to duplicate and see what's up.
|
|
Top |
|
|
3rdTimesCharm
|
Posted: Wed May 27, 2009 10:11 pm |
|
Joined: Mon Nov 05, 2007 2:30 pm
Posts: 8
|
I tested:
my setup with
in /etc/lircd.conf:
include "/usr/MythVantage/templates/remotes/hauppauge-silver/lircd-haupgrey.conf"
and it doesn't work with my remote.
Furthermore, this was also the one I picked during the initial install and it didn't work for me then. I use the one below and it works, just for fun try it with irw and see if it works for your remote.
in /etc/lird.conf
include "/usr/MythVantage/templates/remotes/hauppauge-grey-g3/lircd-haupgrey-g3.conf"
Be sure to run:
sv restart lircd
afterwards.
Note the command syntax is "sv restart/up/down servicename" ...
..Not what I quoted you in a previous posting. Sometimes I get a bit dyslexic.
_________________ LinHES R6, Asus P5B-VM SE, Core 2 Duo 4300@1800Mhz,
1Gig Ram, Nvidia 7600 GS, Technisat HD-5000, HDHR, PVR150
|
|
Top |
|
|
Ravenium
|
Posted: Mon Jun 01, 2009 12:35 am |
|
Joined: Thu Mar 23, 2006 5:47 pm
Posts: 22
|
I tried upgrading from the CD - not sure if that did much other than force me to redo my samba and soundcard settings However, I switched my receiver to just "Hauppage" instead of "PVR-150" and now I'm getting:
00000000000017a0 00 Ch+ Hauppauge_350
This is what I think I was getting before all this, though I'll probably have to doublecheck. But...it seems to work! The disparity between the two receiver settings is weird, but if it works, whatever
Now if I can figure out why my fast forwards only forward 5 seconds instead of the 2x/5x/10x...
Thanks for all your help!
|
|
Top |
|
|
tjc
|
Posted: Mon Jun 01, 2009 8:01 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Check your playback profiles under Setup/Utilities -> Setup -> TV -> Playback Profiles -> Default
|
|
Top |
|
|