View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 21 posts ] 
Go to page 1, 2  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Fri Jul 24, 2015 7:00 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
TL;DR - skip to bfransen's post at the end. These remotes are no longer supported the way they used to be. I'm still working on how to support it, but it's definitely not working out of the box in an upgrade.

I followed the instructions to upgrade that ended in Pacman -Syu and a reboot. Everything seemed to look normal although now my Hauppauge remote no longer works. I've been hanging on to my old PVR-150 solely for the IR receiver. My recordings happen on an HDHOMERUN. The remote was working normally until I rebooted at the end of the upgrade process.

At first I thought it was an lircd.conf issue, but then I saw in the lircd log:

Code:
2015-07-24T19:36:34.290755-05:00 mythmaster lircd-0.9.2a[2973]: Notice: caught signal
2015-07-24T19:36:41.839767-05:00 mythmaster lircd-0.9.2a[4010]: Warning: Running as root
2015-07-24T19:36:41.839847-05:00 mythmaster lircd-0.9.2a[4010]: Info: Using remote: Hauppauge_350.
2015-07-24T19:36:41.840078-05:00 mythmaster lircd-0.9.2a[4010]: Notice: lircd(default) ready, using /var/run/lirc/lircd
2015-07-24T19:36:42.291453-05:00 mythmaster lircd-0.9.2a[4010]: Notice: accepted new client on /var/run/lirc/lircd
2015-07-24T19:36:42.291493-05:00 mythmaster lircd-0.9.2a[4010]: Error: could not get file information for /dev/lirc0
2015-07-24T19:36:42.291520-05:00 mythmaster lircd-0.9.2a[4010]: default_init(): No such file or directory
2015-07-24T19:36:42.291539-05:00 mythmaster lircd-0.9.2a[4010]: Warning: Failed to initialize hardware
2015-07-24T19:36:42.611070-05:00 mythmaster lircd-0.9.2a[4010]: Notice: accepted new client on /var/run/lirc/lircd


When I run irw I get no results from any button presses, meaning this probably isn't an lircd.conf issue. The issue is in /dev I have no lircd devices.

I played around with config files for awhile and then decided to run the LinHES remotes setup. I told it I was using a hauppauge silver, and the appropriate file seems to have been linked to a .conf file in /etc/lirc/lircd.d.conf.

ivtv is installed and seems to be working normally. I can cat /dev/video0 > test.mpg and get some test static from the PVR-150 that's not connected to cable. I just can't get the system to recognize the IR receiver. I'm poring through the many log files but not finding anything that's helpful--other than the fact that /dev/lirc0 doesn't exist. What else can I try?


Last edited by DoomedTX on Wed Aug 12, 2015 9:57 am, edited 1 time in total.


Top
 Profile  
 
PostPosted: Fri Jul 24, 2015 8:45 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
Update: I found some other info that seemed interesting:

Code:
2015-07-24T18:12:16.957424-05:00 mythmaster kernel: [162312.253721] lirc_i2c: chip found @ 0x18 (Hauppauge IR)
2015-07-24T18:18:41.040163-05:00 mythmaster kernel: [   10.609267] ivtv0: Autodetected Hauppauge card (cx23416 based)
2015-07-24T18:18:41.040202-05:00 mythmaster kernel: [   10.663093] tveeprom 1-0050: Hauppauge model 26032, rev C182, serial# 7935010
2015-07-24T18:18:41.040209-05:00 mythmaster kernel: [   10.663103] ivtv0: Autodetected Hauppauge WinTV PVR-150
2015-07-24T18:18:41.040236-05:00 mythmaster kernel: [   10.912864] ivtv0: Initialized card: Hauppauge WinTV PVR-150
2015-07-24T18:18:41.040238-05:00 mythmaster kernel: [   10.912928] ivtv1: Autodetected Hauppauge card (cx23416 based)
2015-07-24T18:18:41.040240-05:00 mythmaster kernel: [   10.967379] tveeprom 2-0050: Hauppauge model 32062, rev C199, serial# 8552317
2015-07-24T18:18:41.040249-05:00 mythmaster kernel: [   10.967391] ivtv1: Autodetected Hauppauge WinTV PVR-250
2015-07-24T18:18:41.040265-05:00 mythmaster kernel: [   11.298832] ivtv1: Initialized card: Hauppauge WinTV PVR-250
2015-07-24T18:18:41.040330-05:00 mythmaster kernel: [   20.091551] lirc_i2c: chip found @ 0x18 (Hauppauge IR)


[I forgot I also had a PVR250 in the box. Its IR port also yields nothing when I use irw.]

So, it is detecting the IR but not using it. I'm chasing the lirc_i2c rabbit down its hole. Apparently at one point "modprobe lirc_i2c" was expected to ensure the lirc_i2c module was running, but that gives a fatal error, module not installed error. I'm guessing that's a red herring because the system is obviously using lirc_i2c. I'll keep digging and post my results here. In the meantime, plese reply if you're sure how to fix this. Thanks.


Top
 Profile  
 
PostPosted: Fri Jul 24, 2015 9:30 pm 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 892
Location: Lexington, Ky
What method did you use to do the upgrade?

If you used the ISO method you need to run "pacman -Syu" in order to pickup some updates and fixes to lirc. Additional information can be found here: http://forum.linhes.org/viewtopic.php?f=22&t=24192#p140010


Top
 Profile  
 
PostPosted: Sat Jul 25, 2015 8:57 am 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
I didn't use the ISO method. I followed the software instructions that ended with pacman -Syu (force fontconfig, uninstall xbmc, install kodi, then pacman -Syu).

I've seen others with similar problems trying to use ir-keytable so I gave that a shot. Once I enabled that module, the four directional keys and number keys work but nothing else on the remote. In both irw and ir-keytable -t, the button presses show up as something like "[[A [[B [[C [[D" for directional keys and "123456789" for number keys instead of the hex codes. I think that means it was recognizing the remote as a keyboard and not a remote. I rebooted to clear out ir-keytable and now I'm back to no keys working and no output when I select irw and press buttons.

Would it help to remove lirc and start over? Does the linhes remotes menu install and configure lircd if it's not installed, or do I need to install it with pacman first?


Top
 Profile  
 
PostPosted: Sat Jul 25, 2015 10:14 am 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
Ok so I can't uninstall lircd because it's required by several other programs. I suppose I could force it but I didn't want to mess up anything. Instead I reinstalled lirc and am at the same place. In the logs it shows:

Code:
2015-07-25T10:21:01.723852-05:00 mythmaster lircd-0.9.2a[1301]: Warning: Running as root
2015-07-25T10:21:01.723935-05:00 mythmaster lircd-0.9.2a[1301]: Info: Using remote: Hauppauge_350.
2015-07-25T10:21:01.724146-05:00 mythmaster lircd-0.9.2a[1301]: Notice: lircd(default) ready, using /var/run/lirc/lircd
2015-07-25T10:21:02.290255-05:00 mythmaster lircd-0.9.2a[1301]: Notice: accepted new client on /var/run/lirc/lircd
2015-07-25T10:21:02.290273-05:00 mythmaster lircd-0.9.2a[1301]: Error: could not get file information for /dev/lirc0
2015-07-25T10:21:02.290276-05:00 mythmaster lircd-0.9.2a[1301]: default_init(): No such file or directory
2015-07-25T10:21:02.290279-05:00 mythmaster lircd-0.9.2a[1301]: Warning: Failed to initialize hardware


We can use phone remotes for now, but WAF is hovering near zero. What can I try next to get this IR receiver working?

As an aside, I see posts where people mention that lirc_i2c is no longer used and ir-kbd-i2c must be used in its place. As I mentioned earlier, when I modprobe this module, the arrow keys and number keys work, but nothing else. I found a post here discussing this very issue 2 years ago, but graysky's AUR package of the lirc_i2c module is no longer available. I also didn't have this trouble two years ago, so I don't know if I'm looking in the wrong place or not. It seems like using ir-kbd-i2c requires a lot of fundamental changes to the lirc setup that would have been discussed if they were really required in LinHES.


Top
 Profile  
 
PostPosted: Tue Aug 11, 2015 2:51 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
Anyone else have an idea how to fix this? I'm back in town and would like to get this fixed before I leave again. I was able to plug in my old MCE IR sensor and use my MCE remote, but it functions differently than the Hauppauge remote. I'd rather not have to configure LinHES and Kodi to use that remote, but I'll do it if I have to. I think I might need to find the lirc_i2c module since that seems to be what the lircd is expecting to use for my PVR-150 remote. Can someone with a working Hauppauge grey remote do an 'lsmod | grep i2c' and let me know if the lirc_i2c module is on your system?


Top
 Profile  
 
PostPosted: Tue Aug 11, 2015 4:19 pm 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 892
Location: Lexington, Ky
I'm using a Hauppauge grey remote but an using the ir receiver from my HDHomerun. That being said here is the output.
Code:
[root@mythtv ~]# lsmod | grep i2c
cx88_vp3054_i2c        12564  0
i2c_algo_bit           12744  2 cx88_vp3054_i2c,cx88xx
i2c_piix4              20857  0
i2c_core               50152  11 drm,hdpvr,lirc_zilog,i2c_piix4,i2c_algo_bit,cx88_vp3054_i2c,cx88xx,nvidia,v4l2_common,tveeprom,videodev


Top
 Profile  
 
PostPosted: Tue Aug 11, 2015 7:08 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
Thanks for the reply. Looks like yours is working without lirc_i2c. Maybe that's not the trouble with mine. I'll keep poking around the logs to see if I get an idea why it detects the IR receiver but doesn't properly configure it.


Top
 Profile  
 
PostPosted: Tue Aug 11, 2015 8:07 pm 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 892
Location: Lexington, Ky
Make sure that you've run pacman -Syu after the update to ensure all the latest fixes have been included. I had to so some major hacks to get my remote working after the R8.2 - R8.3 upgrade.

Those problems were addressed in the fixes, and I just ran the remote setup. Everything worked. Also lirc is now built into the kernel and is no longer a process.

Make sure that your really looking at lirc(x) or whatever is the correct lirc device.


Top
 Profile  
 
PostPosted: Tue Aug 11, 2015 11:17 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
Yep, as you can see in my first and third posts, I ran pacman -Syu as the method of upgrading. I ran it a time or two since then just in case something new popped up--nothing has.

Are you saying your major hacking would have been avoided by pacman -Syu? In my case, it certainly wasn't. I'm either going to give up and use the MCE remote or give up and use the Hauppauge grey as a keyboard with the ir-kbd-i2c module and its associated configuration. I'm not sure what else to try to get the Hauppauge running like it used to.


Top
 Profile  
 
PostPosted: Wed Aug 12, 2015 8:44 am 
Offline
Joined: Wed Jan 04, 2006 10:20 am
Posts: 365
Location: South New Jersey, USA
I had my PVR150 remote stop working after upgrading to 8.3. Take a look at my posts here. Maybe they will help you.
http://forum.linhes.org/viewtopic.php?f=21&t=24151

_________________
LINHES 8.3 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 1GB Ram. 1.5TB WD. HDHR Prime & PVR150. Nvidia GT210. Silver remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote


Top
 Profile  
 
PostPosted: Wed Aug 12, 2015 9:20 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1016
Location: SC
DoomTX,

You will not find lirc_i2c on a R8.3 system. The reason is that R8.3 uses lirc 0.9.2 and lirc_i2c was removed from lirc with version 0.9.2. The same thing happened with the lirc_atiusb module for the firefly remote. I tried pulling in the old code for both modules but it didn't work with our kernel. To get these remotes that used either of these modules to work the remote template will probably need to be updated with some combination of remote.run and lircd.conf file. http://www.linhes.org/projects/linhes/w ... tomization


Top
 Profile  
 
PostPosted: Wed Aug 12, 2015 9:55 am 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 207
Location: Little Rock
brfransen wrote:
DoomTX,

You will not find lirc_i2c on a R8.3 system. The reason is that R8.3 uses lirc 0.9.2 and lirc_i2c was removed from lirc with version 0.9.2. The same thing happened with the lirc_atiusb module for the firefly remote. I tried pulling in the old code for both modules but it didn't work with our kernel. To get these remotes that used either of these modules to work the remote template will probably need to be updated with some combination of remote.run and lircd.conf file. http://www.linhes.org/projects/linhes/w ... tomization


Well that's as disappointing as it is definitive. I would have expected more noise about a fundamental change to the way one of the big time legacy remotes works, but I guess that shows how few people are using Hauppauge PVR remotes these days. So what are the cool kids using? Every time I search for "best mythtv remote" or something similar, I wind up with an MCE-type remote. As far as I remember from using my MCE remote on my secondary FE a few years ago, MCE remote buttons send actual keys instead of IR codes that can be mapped to whatever key I choose, right? I remember that limiting how I could customize the remote functions since they were tied to specific keyboard keys. I guess this is a discussion for a new topic; I'll consider this one closed.


Top
 Profile  
 
PostPosted: Wed Aug 12, 2015 10:27 am 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 892
Location: Lexington, Ky
DoomTX,

Just a thought, but have you looked in dmesg and verified that an lirc device has been detected?


Top
 Profile  
 
PostPosted: Wed Aug 12, 2015 11:58 am 
Offline
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1198
Location: Orlando FL
how much is your time worth? Maybe $20 http://www.ebay.com/sch/i.html?_from=R4 ... p&_sacat=0

The streamzap works without any hassle with LinHES, It's not an MCE remote and they are relatively cheap. They don't work out of the box with Kodi but I Brfransen, Graysky, and I figured out the issue over here. viewtopic.php?f=21&t=24165&p=139850&hilit=streamzap#p139850
If you don't use Kodi it's no problem at all.

_________________
My System


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 21 posts ] 
Go to page 1, 2  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu