| Author |
Message |
|
navilor
|
 Posted: Sat Jul 09, 2005 6:02 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
I bought a PVR-150 and it came with the silver remote. I found this link to be essentially priceless. Using it and a variety of other links I have created a script that I can use after mounting a CD with all of my assorted drivers.
But I can't seem to get my silver Hauppage remote to work in MythTV. I am running KnoppMyth R5A16. I do get valid return values when I run irw. I got these results with the lirc-0.7.0 version (with the appropriate patch) as well. I'm running lirc-0.7.1 right now with the same results.
To get an idea of what I am doing (I used dd to backup my system so I can recover with less pain) here is the script that I use:
Code: #!/bin/bash
# Mount the cdrom to /cdrom
mount /dev/hdc /cdrom
cd /cdrom
# Get the DVD player running
apt-get update
apt-get install libdvdcss
/usr/share/doc/libdvdread3/examples/install-css.sh
# Get the NVidia FX5200 working
/usr/local/bin/install-nvidia-7174-debian.sh
# With Custom line in XF86Config-4
# Option "TVOverScan" "0.5"
cp --reply=yes /cdrom/XF86Config-4 /etc/X11/XF86Config-4
# Originaly from /etc/X11/XF86Config-4.nvidia-tvout.sample
chmod 644 /etc/X11/XF86Config-4
# Unload the lirc_i2c driver
rmmod lirc_i2c
# Kill off the lircd process if running
killall lircd
# Get my damn Silver Hauppauge remote working
cd /usr/src/
apt-get remove lirc
tar -xzpvf /cdrom/lirc-0.7.1.tar.gz -C /usr/src/
cd /usr/src/lirc-0.7.1
./setup.sh
make
make install
# Backup original lircd.conf
mv /etc/lirc/lircd.conf /etc/lirc/lircd.conf.old
# copy lircd.conf that I made via irrecord to system
cp /cdrom/lircd.conf /etc/lirc/lircd.conf
chmod 644 /etc/lirc/lircd.conf
# copy lircrc that came from
# http://www.mysettopbox.tv/phpBB2/viewtopic.php?t=4609
# to default file location under mythtv's user directory
cp /cdrom/lircrc /home/mythtv/.mythtv/lircrc
chmod 644 /home/mythtv/.mythtv/lircrc
# append the following line to /etc/modules
# lirc_i2c
# by copying my custom file to /etc/modules
# or by appending it to the end of the file
cp -f /etc/modules /etc/modules.old
# cp /cdrom/modules /etc/
echo "lirc_i2c" >> /etc/modules
# append the following line to bootmisc.sh
# /etc/init.d/bootmisc.sh
echo "/usr/local/sbin/lircd" >> /etc/init.d/bootmisc.sh
# This line exists in my default install already
# vi /etc/mythtv/modules/ivtv
# alias char-major-61 lirc_i2c
# Load the lirc_i2c module and the lircd daemon
modprobe lirc_i2c
lircd
# Add the following line to the crontab to keep the clock time accurate
# /etc/crontab
# 0 4 * * * /usr/sbin/ntpdate ntp.knowledge.or.id
echo "0 4 * * * /usr/sbin/ntpdate ntp.knowledge.or.id" >> /etc/crontab
# Adjust volume on Master and PCM to 100%
# Exit
Everything installs without error. I checked this out by running each line seperately and the order shown above before finalizing my script.
What ultra obvious thing is it that I'm doing wrong?
|
|
| Top |
|
 |
|
robert.pdx
|
Posted: Sun Jul 10, 2005 4:20 pm |
|
|
Joined: Sat May 14, 2005 12:25 am
Posts: 51
Location:
Portland, Oregon
|
|
If it's not a permissions thing, then check that the lircd.conf file you created with irrecord matches up command-wise with the lircrc file you're using.
My lircrc file is owned by mythtv with permissions 644.
|
|
| Top |
|
|
|
navilor
|
Posted: Sun Jul 10, 2005 10:45 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
|
I checked out on the web after I got the remote working (I made sure the permissions were correct and did things slightly differently) to see why lircd dies after I do a recording.
The solution to getting this error in /var/log/lircd:
could not open /dev/lirc
is to do a cold shutdown and reboot.
It works flawlessly until I do a recording. Then I need to do a cold boot to get it back working. It even dies when watching "live tv" as that is actually a time delayed recording. It only takes a few minutes before it gives it up.
I have tested it with irw and while I do have lircd loaded it goes away as soon as a call is made. irw just dumps back to the command prompt without any error message given by it.
Reloading lircd (and I verify that it is actually loaded) works until a program tries to access lircd. It fails every time until I cold boot, then it works every time until I record something.
What would cause this?
How can I prevent this?
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Jul 11, 2005 4:18 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
What does running this this print? Code: grep mythtv /etc/passwd | wc -l
|
|
| Top |
|
|
|
navilor
|
Posted: Mon Jul 11, 2005 7:23 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
tjc wrote: What does running this this print? Code: grep mythtv /etc/passwd | wc -l It returns: Code: root@mythtv:~# grep mythtv /etc/passwd | wc -l
1
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Jul 11, 2005 8:58 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
OK, so you haven't fallen into the sophmore install extra mythtv user trap. How about:
Code: ls -l /dev/lirc
Oh, and you are running things as mythtv right?
|
|
| Top |
|
|
|
navilor
|
Posted: Mon Jul 11, 2005 10:46 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
tjc wrote: OK, so you haven't fallen into the sophmore install extra mythtv user trap. How about: Code: ls -l /dev/lirc Oh, and you are running things as mythtv right? Yes, I am running things as mythtv. BTW: I really appreciate your helping me out on this. You rock. It goes like this: Code: root@mythtv:~# ls -l /dev/lirc
crw-r--r-- 1 root root 61, 0 Jul 29 2004 /dev/lirc
root@mythtv:~# file /dev/lirc
/dev/lirc: character special (61/0)
I figured you might want that last bit. Need dmesg or anything specific. Lay it all out and I shall post it. My processes: Code: root@mythtv:~# ps -eaf
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Jul10 ? 00:00:00 init [5]
root 2 1 0 Jul10 ? 00:00:00 [migration/0]
root 3 1 0 Jul10 ? 00:00:00 [ksoftirqd/0]
root 4 1 0 Jul10 ? 00:00:00 [events/0]
root 5 1 0 Jul10 ? 00:00:00 [khelper]
root 10 1 0 Jul10 ? 00:00:00 [kthread]
root 19 10 0 Jul10 ? 00:00:00 [kacpid]
root 136 10 0 Jul10 ? 00:00:00 [kblockd/0]
root 189 10 0 Jul10 ? 00:00:00 [pdflush]
root 190 10 0 Jul10 ? 00:00:00 [pdflush]
root 192 10 0 Jul10 ? 00:00:00 [aio/0]
root 191 1 0 Jul10 ? 00:00:00 [kswapd0]
root 193 1 0 Jul10 ? 00:00:00 [jfsIO]
root 194 1 0 Jul10 ? 00:00:00 [jfsCommit]
root 195 1 0 Jul10 ? 00:00:00 [jfsSync]
root 196 10 0 Jul10 ? 00:00:00 [xfslogd/0]
root 197 10 0 Jul10 ? 00:00:00 [xfsdatad/0]
root 198 1 0 Jul10 ? 00:00:00 [xfsbufd]
root 791 1 0 Jul10 ? 00:00:00 [kseriod]
root 866 10 0 Jul10 ? 00:00:00 [ata/0]
root 871 1 0 Jul10 ? 00:00:00 [scsi_eh_0]
root 872 1 0 Jul10 ? 00:00:00 [scsi_eh_1]
root 891 10 0 Jul10 ? 00:00:00 [kcryptd/0]
root 892 10 0 Jul10 ? 00:00:00 [kmirrord/0]
root 895 1 0 Jul10 ? 00:00:00 [kjournald]
root 1101 1 0 Jul10 ? 00:00:00 [khubd]
root 1211 1 0 Jul10 ? 00:00:00 [khpsbpkt]
root 1393 1 0 Jul10 ? 00:00:00 [knodemgrd_0]
root 1961 10 0 Jul10 ? 00:00:00 [ivtv_vbi/0]
root 1962 10 0 Jul10 ? 00:00:00 [ivtv_fw/0]
root 2048 1 0 Jul10 ? 00:00:00 [ivtv-enc]
root 2091 1 0 Jul10 ? 00:14:41 [lirc_dev]
root 2110 1 0 Jul10 ? 00:00:00 [kjournald]
daemon 2147 1 0 Jul10 ? 00:00:00 /sbin/portmap
root 2348 1 0 Jul10 ? 00:00:00 /sbin/syslogd
root 2351 1 0 Jul10 ? 00:00:00 /sbin/klogd
root 2375 1 0 Jul10 ? 00:00:00 /usr/sbin/apache
www-data 2379 2375 0 Jul10 ? 00:00:00 /usr/sbin/apache
www-data 2380 2375 0 Jul10 ? 00:00:00 /usr/sbin/apache
www-data 2381 2375 0 Jul10 ? 00:00:00 /usr/sbin/apache
www-data 2382 2375 0 Jul10 ? 00:00:00 /usr/sbin/apache
www-data 2383 2375 0 Jul10 ? 00:00:00 /usr/sbin/apache
root 2385 1 0 Jul10 ? 00:00:00 /usr/sbin/inetd
root 2892 1 0 Jul10 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe
mysql 2928 2892 0 Jul10 ? 00:00:21 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-f
root 2929 2892 0 Jul10 ? 00:00:00 logger -p daemon.err -t mysqld_safe -i -t mysqld
root 2959 1 0 Jul10 ? 00:00:00 /usr/local/sbin/lircd
root 2965 1 0 Jul10 ? 00:00:00 /usr/sbin/sshd
mythtv 2970 1 0 Jul10 ? 00:00:02 /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pid
root 3628 1 0 Jul10 ? 00:00:00 [shpchpd_event]
daemon 3906 1 0 Jul10 ? 00:00:00 /usr/sbin/atd
root 3909 1 0 Jul10 ? 00:00:00 /usr/sbin/cron
root 3914 1 0 Jul10 ? 00:00:00 /usr/bin/gdm
root 3927 1 0 Jul10 tty1 00:00:00 /sbin/getty 38400 tty1
root 3938 1 0 Jul10 tty2 00:00:00 /sbin/getty 38400 tty2
root 3939 1 0 Jul10 tty3 00:00:00 /sbin/getty 38400 tty3
root 3940 1 0 Jul10 tty4 00:00:00 /sbin/getty 38400 tty4
root 3941 1 0 Jul10 tty5 00:00:00 /sbin/getty 38400 tty5
root 3942 1 0 Jul10 tty6 00:00:00 /sbin/getty 38400 tty6
root 3953 3914 0 Jul10 ? 00:00:00 /usr/bin/gdm
root 3997 3953 0 Jul10 ? 00:00:06 /usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
mythtv 4061 3953 0 Jul10 ? 00:00:00 x-window-manager
mythtv 4101 4061 0 Jul10 ? 00:00:00 /usr/bin/ssh-agent x-window-manager
mythtv 4103 4061 0 Jul10 ? 00:00:13 mythfrontend
root 5074 2965 0 21:54 ? 00:00:00 sshd: root@ttyp0
root 5077 5074 2 21:54 ttyp0 00:00:00 -bash
root 5087 5077 0 21:54 ttyp0 00:00:00 ps -eaf
And modules loaded Code: root@mythtv:~# lsmod
Module Size Used by
snd_pcm_oss 48032 0
sg 30880 0
nvidia 3916796 16
sata_nv 8068 0
shpchp 91524 0
pci_hotplug 31048 1 shpchp
ehci_hcd 31112 0
analog 11936 0
pcspkr 5324 0
tsdev 7744 0
evdev 9088 0
cx8800 27276 0
cx88xx 47904 1 cx8800
ir_common 7300 1 cx88xx
v4l1_compat 14852 1 cx8800
wm8775 11164 0
sha1 10496 1
cx25840 131756 0
ivtv 808420 2
saa7115 13720 0
msp3400 27576 0
tuner 26536 0
bttv 144336 0
video_buf 18436 3 cx8800,cx88xx,bttv
firmware_class 9728 1 bttv
i2c_algo_bit 10504 3 cx88xx,ivtv,bttv
v4l2_common 6528 2 cx8800,bttv
btcx_risc 5768 3 cx8800,cx88xx,bttv
tveeprom 13336 2 cx88xx,bttv
videodev 9600 4 cx8800,cx88xx,ivtv,bttv
lirc_i2c 10116 1
lirc_dev 14852 1 lirc_i2c
md5 5760 2
ipv6 235808 12
autofs4 17284 0
af_packet 18696 0
snd_mixer_oss 18048 1 snd_pcm_oss
snd_emu10k1 84996 0
snd_rawmidi 21536 1 snd_emu10k1
snd_seq_device 8716 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 68984 1 snd_emu10k1
snd_pcm 79364 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 22532 2 snd_emu10k1,snd_pcm
snd_page_alloc 9348 2 snd_emu10k1,snd_pcm
snd_util_mem 5376 1 snd_emu10k1
snd_hwdep 9248 1 snd_emu10k1
snd 47460 9 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore 9312 1 snd
forcedeth 17792 0
emu10k1_gp 4864 0
gameport 5632 2 analog,emu10k1_gp
i2c_nforce2 7552 0
i2c_core 20224 11 cx88xx,wm8775,cx25840,saa7115,msp3400,tuner,bttv,i2c_algo_bit,tveeprom,lirc_i2c,i2c_nforce2
nvidia_agp 7708 1
agpgart 29616 2 nvidia,nvidia_agp
parport_pc 37444 0
parport 32456 1 parport_pc
8250 23108 0
serial_core 19840 1 8250
ohci1394 31748 0
pcmcia 20624 0
yenta_socket 20616 0
rsrc_nonstatic 10496 1 yenta_socket
pcmcia_core 42656 3 pcmcia,yenta_socket,rsrc_nonstatic
video 16260 0
thermal 12936 0
processor 22504 1 thermal
fan 5252 0
container 5248 0
button 7056 0
battery 10372 0
ac 5508 0
rtc 11980 0
ieee1394 301752 1 ohci1394
usb_storage 63552 0
ohci_hcd 20488 0
uhci_hcd 30224 0
usbcore 101368 5 ehci_hcd,usb_storage,ohci_hcd,uhci_hcd
tmscsim 22976 0
BusLogic 77588 0
root@mythtv:~#
I have had my MythTV machine going for 24 hours of uptimes with no recording and the remote still is working. So by this I know that it (probably) isn't a time based issue.
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Jul 11, 2005 11:26 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
OK, lets get ready to rumble... What do these show before, during, and after a recording?
Code: pgrep -f lirc -l
fuser -av /dev/lirc BTW - I see: Code: root@black2:~# fuser -av /dev/lirc
USER PID ACCESS COMMAND
/dev/lirc root 3153 f.... lircd
root@black2:~# pgrep -f lirc -l
3150 lirc_dev
3153 /usr/sbin/lircd --driver=default --device=/dev/lirc
3155 /usr/sbin/lircmd
|
|
| Top |
|
|
|
navilor
|
Posted: Tue Jul 12, 2005 10:22 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
tjc wrote: OK, lets get ready to rumble... What do these show before, during, and after a recording? Code: pgrep -f lirc -l
fuser -av /dev/lirc BTW - I see: Code: root@black2:~# fuser -av /dev/lirc
USER PID ACCESS COMMAND
/dev/lirc root 3153 f.... lircd
root@black2:~# pgrep -f lirc -l
3150 lirc_dev
3153 /usr/sbin/lircd --driver=default --device=/dev/lirc
3155 /usr/sbin/lircmd The items are the same. I don't know why. It broke during recording again. The items are identical before, during, and after recording. Code: login as: root
Using keyboard-interactive authentication.
Password:
Last login: Tue Jul 12 19:37:55 2005 from 192.168.1.101
root@mythtv:~# pgrep -f lirc -l
2091 lirc_dev
2959 /usr/local/sbin/lircd
root@mythtv:~# fuser -av /dev/lirc
USER PID ACCESS COMMAND
/dev/lirc root 2959 f.... lircd
root@mythtv:~# Code: root@mythtv:~# pgrep -f lirc -l
2091 lirc_dev
2959 /usr/local/sbin/lircd
root@mythtv:~# fuser -av /dev/lirc
USER PID ACCESS COMMAND
/dev/lirc root 2959 f.... lircd
root@mythtv:~# Before and after. During was the same. And just because it might help: Code: root@mythtv:~# file /dev/lirc
/dev/lirc: character special (61/0)
root@mythtv:~# ps -eaf | grep lirc
root 2091 1 0 20:07 ? 00:00:31 [lirc_dev]
root 2959 1 0 20:07 ? 00:00:00 /usr/local/sbin/lircd
root 4317 4303 0 20:59 ttyp0 00:00:00 grep lirc
root@mythtv:~# lsmod | grep irc
lirc_i2c 10116 1
lirc_dev 14852 1 lirc_i2c
i2c_core 20224 11 cx88xx,wm8775,cx25840,saa7115,msp3400,tuner,bttv,i2c_algo_bit,tveeprom,lirc_i2c,i2c_nforce2
root@mythtv:~# After a fresh cold boot Code: root@mythtv:~# ps -eaf | grep irc
root 2084 1 0 21:07 ? 00:00:01 [lirc_dev]
root 2951 1 0 21:07 ? 00:00:00 /usr/local/sbin/lircd
root@mythtv:~# file /dev/lirc
/dev/lirc: character special (61/0)
root@mythtv:~# lsmod | grep irc
lirc_i2c 10116 1
lirc_dev 14852 1 lirc_i2c
i2c_core 20224 11 cx88xx,wm8775,cx25840,saa7115,msp3400,tuner,bttv,i2c_algo_bit,tveeprom,lirc_i2c,i2c_nforce2
root@mythtv:~# I don't get it. Oh, /var/log/lircd says: Code: Jul 12 18:53:58 mythtv lircd 0.7.1: removed client
Jul 12 18:53:58 mythtv lircd 0.7.1: caught signal
Jul 12 18:55:04 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 18:55:27 mythtv lircd 0.7.1: accepted new client on /dev/lircd
Jul 12 18:55:27 mythtv lircd 0.7.1: could not open /dev/lirc
Jul 12 18:55:27 mythtv lircd 0.7.1: default_init(): No such device
Jul 12 18:55:27 mythtv lircd 0.7.1: caught signal
Jul 12 18:56:00 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 18:56:01 mythtv lircd 0.7.1: caught signal
Jul 12 18:57:40 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 18:58:03 mythtv lircd 0.7.1: accepted new client on /dev/lircd
Jul 12 20:06:15 mythtv lircd 0.7.1: caught signal
Jul 12 20:07:21 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 20:07:45 mythtv lircd 0.7.1: accepted new client on /dev/lircd
Jul 12 21:01:21 mythtv lircd 0.7.1: removed client
Jul 12 21:01:21 mythtv lircd 0.7.1: caught signal
Jul 12 21:02:28 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 21:02:52 mythtv lircd 0.7.1: accepted new client on /dev/lircd
Jul 12 21:02:52 mythtv lircd 0.7.1: could not open /dev/lirc
Jul 12 21:02:52 mythtv lircd 0.7.1: default_init(): No such device
Jul 12 21:02:52 mythtv lircd 0.7.1: caught signal
Jul 12 21:05:29 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 21:05:31 mythtv lircd 0.7.1: caught signal
Jul 12 21:07:20 mythtv lircd 0.7.1: lircd(hauppauge) ready
Jul 12 21:07:44 mythtv lircd 0.7.1: accepted new client on /dev/lircd
If you feel it would help I can clear the log and get you a clean boot with a recording with no use of the remote at any time until after the program has ended.
Or any other information you might need in the way that you need it.
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Jul 13, 2005 9:18 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
I'm slightly concerned about the differences in how lircd is being invoked... if the options and the version are different enough that could be part of the issue...
I'll have to ponder this for a bit...
|
|
| Top |
|
|
|
navilor
|
Posted: Wed Jul 13, 2005 9:43 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
tjc wrote: I'll have to ponder this for a bit...
You rock.
I am willing to do a reinstall (again) if you feel that is necessary. KnoppMyth R5A16 is what I'm running right now. I install the NVidia drivers, DVD decoding library, remove the running lirc modules from memory, remove lirc via apt-get, reinstall the new version (0.7.1) that includes support for my remote (vs. the 0.7.0 version with the patch), and update my lircrc file so the remote will work (full gruesome details at the top of this page.
You have much more of a clue on this than I do. My feeling is that since the remote receiver plugs into the capture card that somehow when a recording happens it interferes with the receiver portion of the card but not enough to break the device as linux views it. A power cycle will bring it back to normal operating status.
The only problem with this theory is that other people seem to have this all working with no problem.
I am in the Seattle, WA area. If you know of someone who would like to see how insane this problem is in person they are more than welcome to take a look at my rig.
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Jul 13, 2005 11:37 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
 You shouldn't have to install a different version of lirc for the new "dog bone" shaped (vs old "cigar shaped") silver remote, just a couple new config files... At least that was my understanding when the topic first came up several months ago...
|
|
| Top |
|
|
|
navilor
|
Posted: Thu Jul 14, 2005 7:19 pm |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
tjc wrote: :!: You shouldn't have to install a different version of lirc for the new "dog bone" shaped (vs old "cigar shaped") silver remote, just a couple new config files... At least that was my understanding when the topic first came up several months ago...
This page is what I was using as my source document to get the remote working.
I did a recording last night and did a cold boot. I can play recorded video just fine. Pause, cue, review, and everything else appears to work perfectly. I just had to make certain that it wasn't something like it being allergic to MPEG-2 or something silly like that.
|
|
| Top |
|
|
|
shplad
|
Posted: Fri Jul 15, 2005 8:04 am |
|
|
Joined: Sun Nov 14, 2004 10:04 am
Posts: 263
Location:
Toronto, Canada
|
navilor:
I am having very similar but slightly different problem, except I'm using lirc 0.7.0. Notice what robert wrote in his HOWTO:
"lirc-0.7.1 has support for this remote, but I was unable to get it to work"
So perhaps you'll want to try 0.7.0, if all else fails.
Either way, please let us know what works for you.
shplad
navilor wrote: tjc wrote: :!: You shouldn't have to install a different version of lirc for the new "dog bone" shaped (vs old "cigar shaped") silver remote, just a couple new config files... At least that was my understanding when the topic first came up several months ago... This page is what I was using as my source document to get the remote working. I did a recording last night and did a cold boot. I can play recorded video just fine. Pause, cue, review, and everything else appears to work perfectly. I just had to make certain that it wasn't something like it being allergic to MPEG-2 or something silly like that.
_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick
|
|
| Top |
|
|
|
navilor
|
Posted: Fri Jul 15, 2005 9:03 am |
|
|
Joined: Tue Jun 28, 2005 11:54 am
Posts: 26
Location:
Seattle, WA
|
shplad wrote: navilor:
I am having very similar but slightly different problem, except I'm using lirc 0.7.0. Notice what robert wrote in his HOWTO:
"lirc-0.7.1 has support for this remote, but I was unable to get it to work"
So perhaps you'll want to try 0.7.0, if all else fails.
Either way, please let us know what works for you.
shplad
shplad,
Thanks, but I've been down that road. My issue when I was running 0.7.0 with the patch was that lirc was able to recognize the remote but MythTV wasn't. I may uninstall and reinstall lirc just to see what happens, but I really want to be able to get repeatable results from a base install. This will help me out making a nice full install disk in case I have a bad hardware issue.
That, and a friend of mine wants to get a MythTV box going, but since I'm going through hell right now on this remote thing he is going to wait. When I am successful he will get the same exact hardware that I'm running and I can just run my disk on his machine and it should start working right away.
That's the plan anyway.
navilor
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register