Author |
Message |
hurnik
|
Posted: Wed Jan 24, 2007 7:45 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
I've been fighting with R5E50 and the PVR-150 MCE edition. Finally just gave up and bought a streamzap remote.
Plugged in the USB receiver and ran lirc-reconfig.sh It detected the streamzap automatically (it did not do this with the PVR MCE edition).
So I thought I was all set.
Go into "live TV" and push the channel up/down on the remote. The receiver flashes red, but nothing happens.
So I rebooted the box (in case it was a USB problem or something).
Still nothing. I use the "arrow" keys and nothing happens.
I've got two tuner cards in the system, do I need to "tell" them which one does what? But I still would've thought that the arrow keys would move the cursor around in the menu. (One is the AirStar HD-5000 so it has no IR Blaster, the PVR-150 is not currently setup to use IR Blasting).
Loading IRW kills lircd, so it's impossible to know if the receiver is receving the correct commands.
I've checked the lircd.conf file (both places) and it's setup for the streamzap.
Am I missing something obvious? Is there another program that can be used instead of IRW that won't kill lircd?
|
|
Top |
|
 |
thornsoft
|
Posted: Wed Jan 24, 2007 8:08 pm |
|
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location:
spencerport, ny (USA)
|
Try this:
cat /dev/lirc0
Hit some buttons. Do you get any output?
|
|
Top |
|
 |
hurnik
|
Posted: Wed Jan 24, 2007 8:55 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
Yes, I get "funky" characters on the screen (for example, channel up shows up as:
yyy (with little double dots above each one) followed by a bunch of solid filled boxes).
But nothing happens in MythTV itself. (I hit ALT-F1 at the console to do this).
|
|
Top |
|
 |
hurnik
|
Posted: Wed Jan 24, 2007 9:28 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
When I do a:
mode2 -d /dev/lirc0
I get all sorts of things for the button presses, so I'm 99% sure the OS is seeing everything okay.
But MythTV is not.
I've checked and the lircrc file is where it's supposed to be in the .mythtv directory under home.
And it looks okay.
Is there another daemon or program that has to run to "see"/read this file? or that passes what the OS sees into MythTv?
|
|
Top |
|
 |
thornsoft
|
Posted: Wed Jan 24, 2007 10:17 pm |
|
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location:
spencerport, ny (USA)
|
Hmmm... Seems like it should be working then. I'm not sure what's up.
|
|
Top |
|
 |
Greg Frost
|
Posted: Thu Jan 25, 2007 12:03 am |
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
hurnik wrote: Is there another daemon or program that has to run to "see"/read this file? or that passes what the OS sees into MythTv? I pretty sure that is the job of lircd. Is it running? Does irw register any button presses?
|
|
Top |
|
 |
tjc
|
Posted: Thu Jan 25, 2007 12:11 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Try this:
Code: grep 'unknown key' /var/log/syslog* When my remote stops working I start seeing this type of stuff in the logfiles: Code: /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=1 /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=0 /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=1 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=0 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=1 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=0 /var/log/syslog.0:Jan 24 02:12:33 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=1 /var/log/syslog.0:Jan 24 02:12:33 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=0
|
|
Top |
|
 |
hurnik
|
Posted: Thu Jan 25, 2007 12:00 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
Greg Frost wrote: hurnik wrote: Is there another daemon or program that has to run to "see"/read this file? or that passes what the OS sees into MythTv? I pretty sure that is the job of lircd. Is it running? Does irw register any button presses?
It claims it start lircd, but when I do a ps ax I don't see "lircd" in the list, but maybe I'm doing something wrong.
IRW kills lircd, so it's impossible to look at with IRW.
But a mode2 -d /dev/lirc0 shows the IR commands going through to the OS.
|
|
Top |
|
 |
hurnik
|
Posted: Thu Jan 25, 2007 12:02 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
tjc wrote: Try this: Code: grep 'unknown key' /var/log/syslog* When my remote stops working I start seeing this type of stuff in the logfiles: Code: /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=1 /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=0 /var/log/syslog.0:Jan 24 02:12:11 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=1 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=0 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=1 /var/log/syslog.0:Jan 24 02:12:12 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3f94 down=0 /var/log/syslog.0:Jan 24 02:12:33 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=1 /var/log/syslog.0:Jan 24 02:12:33 black2 kernel: i2c IR (Hauppauge): unknown key: key=0x14 raw=0x3794 down=0
Nothing comes back, so I'm assuming no errors there.
My assumption is also that with two tuner cards, that the "mythtv" functionality should at least work (ie, drive around the menus with the arrow keys).
|
|
Top |
|
 |
bouncey
|
Posted: Thu Jan 25, 2007 12:27 pm |
|
Joined: Sat Oct 07, 2006 7:18 pm
Posts: 55
|
I'm having a similar problem. MythTV works, lirc works, irw shows button presses, the config files are fine, but my streamzap remote still doesn't control the MythTV menu. It's very frustrating. I thought this kind of remote was supposed to Just Work.
This is with Ubuntu for AMD64 by the way. I'm curious how you resolve your problem.
|
|
Top |
|
 |
bruce_s01
|
Posted: Thu Jan 25, 2007 1:29 pm |
|
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 561
Location:
UK
|
Have you checked your key defintions in /home/mythtv/.mythtv/lircrc are the same as those in /etc/lirc/lircd.conf, for example, from my lircrc: Code: begin prog = mythtv button = Go # # Change Card config = Y end and from lircd.conf: Code: Go 0x0161
Bruce S.
_________________ Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P 16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD, SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080 Hauppauage Nova-T 500, Nova-T LinHes R8.6.1
|
|
Top |
|
 |
hurnik
|
Posted: Thu Jan 25, 2007 5:32 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
A ps -ef will show that lircd is running.
My /etc/lirc/lircd.conf is here:
Code: # brand: Streamzap # model no. of remote control: PC Remote # devices being controlled by this remote: USB receiver #
begin remote
name Streamzap_PC_Remote bits 6 flags RC5|CONST_LENGTH eps 30 aeps 100
one 889 889 zero 889 889 plead 889 pre_data_bits 8 pre_data 0xA3 gap 108344 toggle_bit 2
begin codes 0 0x00 1 0x01 2 0x02 3 0x03 4 0x04 5 0x05 6 0x06 7 0x07 8 0x08 9 0x09 POWER 0x0A MUTE 0x0B CH_UP 0x0C VOL_UP 0x0D CH_DOWN 0x0E VOL_DOWN 0x0F UP 0x10 LEFT 0x11 OK 0x12 RIGHT 0x13 DOWN 0x14 MENU 0x15 EXIT 0x16 PLAY 0x17 PAUSE 0x18 STOP 0x19 |<< 0x1A >>| 0x1B RECORD 0x1C << 0x1D >> 0x1E RED 0x20 GREEN 0x21 YELLOW 0x22 BLUE 0x23 DISP 0x24 PTZ 0x25 HELP 0x26 end codes
end remote
and my /home/mythtv/.mythtv/lircrc file is: Code: # StreamZap Remote # 'config' must either be a literal key, e.g. 'config = l' or must # refer to a defined key in MythTV, e.g. 'config = PLAY' begin prog = mythtv button = 0 config = 0 end
begin prog = mythtv button = 1 config = 1 end
begin prog = mythtv button = 2 config = 2 end
begin prog = mythtv button = 3 config = 3 end
begin prog = mythtv button = 4 config = 4 end
begin prog = mythtv button = 5 config = 5 end
begin prog = mythtv button = 6 config = 6 end
begin prog = mythtv button = 7 config = 7 end
begin prog = mythtv button = 8 config = 8 end
begin prog = mythtv button = 9 config = 9 end
begin prog = mythtv button = POWER config = Esc end
# ??? begin prog = mythtv button = MUTE config = F9 end
begin prog = mythtv button = CH_UP repeat = 3 config = Up end
begin prog = mythtv button = VOL_UP repeat = 3 config = ] end
begin prog = mythtv button = CH_DOWN repeat = 3 config = Down end
begin prog = mythtv button = VOL_DOWN repeat = 3 config = [ end
begin prog = mythtv button = UP repeat = 3 config = Up end
begin prog = mythtv button = LEFT # navigates, or skips back during playback or live tv. config = Left end
begin prog = mythtv button = OK config = Return end
begin prog = mythtv button = RIGHT # navigates, or skips forwards during playback or live tv. config = Right end
begin prog = mythtv button = DOWN repeat = 3 config = Down end
begin prog = mythtv button = MENU config = m end
begin prog = mythtv button = EXIT config = Esc end
begin prog = mythtv button = PLAY config = l end
begin prog = mythtv button = PAUSE config = p end
begin prog = mythtv button = STOP config = Esc end
begin prog = mythtv # skip backward button = |<< config = PgUp end
begin prog = mythtv # skip forward button = >>| config = PgDown end
begin prog = mythtv button = RECORD config = r end
begin prog = mythtv # rewind button = << config = < end
begin prog = mythtv # fast forward button = >> config = > end
begin prog = mythtv button = RED # aka LIVE # Delete config = d end
begin prog = mythtv button = GREEN # aka PLAY # Info config = i end
begin prog = mythtv button = YELLOW # aka PRGM # change aspect ratio config = w end
begin prog = mythtv button = BLUE # aka SET config = Tab end
begin prog = mythtv button = DISP config = e end
begin prog = mythtv button = PTZ config = z end
begin prog = mythtv button = HELP config = Space end
# MPLAYER begin prog = mplayer button = POWER config = quit end
begin prog = mplayer button = MUTE config = mute end
begin prog = mplayer button = VOL_UP repeat = 3 config = volume +1 end
begin prog = mplayer button = VOL_DOWN repeat = 3 config = volume -1 end
begin prog = mplayer button = UP repeat = 3 config = seek +10 end
begin prog = mplayer button = LEFT # navigates, or skips back during playback or live tv. config = seek -60 end
begin prog = mplayer button = RIGHT # navigates, or skips forwards during playback or live tv. config = seek +60 end
begin prog = mplayer button = DOWN repeat = 3 config = seek -10 end
begin prog = mplayer button = EXIT config = quit end
begin prog = mplayer button = play config = speed_set 1.0 end
begin prog = mplayer button = pause config = pause end
begin prog = mplayer button = STOP config = quit end
begin prog = mplayer # skip backward button = |<< config = seek -600 end
begin prog = mplayer # skip forward button = >>| config = seek +600 end
begin prog = mplayer # slow forward button = << config = speed_mult 0.5 end
begin prog = mplayer # fast forward button = >> config = speed_mult 2.0 end
|
|
Top |
|
 |
tjc
|
Posted: Thu Jan 25, 2007 8:03 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
These buttons aren't right.
Quote: Code: begin prog = mplayer button = play config = speed_set 1.0 end
begin prog = mplayer button = pause config = pause end
However, that's just a minor issue. If this is using the USB as a serial port (like /dev/ttyS0) you may have the ownership/permission problem documented elsewhere. Make sure that the mythtv user is a member of the dialout group. Code: root@black2:~# grep dialout /etc/group dialout:x:20:mythtv
|
|
Top |
|
 |
hurnik
|
Posted: Thu Jan 25, 2007 9:35 pm |
|
Joined: Wed Dec 27, 2006 4:13 pm
Posts: 116
|
tjc wrote: These buttons aren't right. Quote: Code: begin prog = mplayer button = play config = speed_set 1.0 end
begin prog = mplayer button = pause config = pause end
However, that's just a minor issue. If this is using the USB as a serial port (like /dev/ttyS0) you may have the ownership/permission problem documented elsewhere. Make sure that the mythtv user is a member of the dialout group. Code: root@black2:~# grep dialout /etc/group dialout:x:20:mythtv The files were auto-generated by MythTV, so if there's some wrong stuff, I guess a bug fix or something will have to be done? Anyway, this is the USB version (not USB to serial, it's plugged directly into the USB port) so I don't think t's using the USB as a serial port (how do I tell?) I think I remember seeing something about the permissions before, but it referenced a diff. area (when I'd checked that it was okay). But with the /etc/group for dialout it does not show like yours. Of course, now I can't find the ownership/permission article I was talking about (may not even be on this site). But I changed the group file and still no go. Again: Code: mode2 -d /dev/lirc0
Will show the pulse codes, etc. when doing things.
But MythTV just ignores everything.
|
|
Top |
|
 |
kfrancek
|
Posted: Fri Jan 26, 2007 10:51 am |
|
Joined: Sun Nov 05, 2006 10:14 pm
Posts: 14
|
Did you figure this out? I am having the same problem. Different remote, but same issue with the mythtv not responding.
|
|
Top |
|
 |