LinHES Forums :: View topic - R5F27-Hauppauge remote doesn't work after fresh install

Is your COM port enabled in the BIOS? What does

Code:

dmesg | grep ttyS

show you?

Thanks for your suggestion. I don't think this would be a COM port issue but I don't have a clue what to look at. The IR dongle is a receiver and plugs into the PVR-250.

I have 2 identical boxes, one is mine and the other a friends. They have a PVR-250, 7N1F2 MB and Athlon processor. They also have a homemade IRblaster running off COM1 controlling a DISH receiver

Are you sure the dongle is plugged in all the way? I have had problems with the jack not seating properly.

See the R5F27 Hints. Known Issue #5.

I would try re-running lirc-reconfig.sh just to make sure that you configured the correct remote...

Marc

I don't know what's going wrong, but if I understanding correctly, when you move the hard drive over from the "good" machine where the remote works to the "problematic" machine, everything works fine on the "problematic" machine. Do I have this right? If so, I see two potential approaches that could get things up a running:

1. Make an image copy of the "good drive" to the drive that belongs in the "problematic" machine.

2. Alternatively, move the "problematic" machine's HD to the "good" machine, do a fresh install of R5F27 on the "good": machine, confirm that it works on the "good" machine, and then move it over to the "problematic" machine.
Marc

I'm glad to hear that it is working. It is difficult to say for sure why the autoupgrade from r5d1 worked. As you sugggest, it may have something to do with a restored configuration file.

It dawns on me that a useful experiment would have been to run irw to see if the signals were getting through, but now that you're running, it's probably academic...

Marc

Author:	George [ Wed Oct 03, 2007 11:55 am ]
Post subject:	R5F27-Hauppauge remote doesn't work after fresh install
I have 2 identical boxes, one is mine and the other a friends. They have a PVR-250, 7N1F2 MB and Athlon processor. They also have a homemade IRblaster running off COM1 controlling a DISH receiver. Both were running R5D1. I did an upgrade of mine to R5F27 and after following the tips it works fine. My friend didn't care about saving anything so I did a fresh install on his. I was able to configure the inputs and mythfilldatabase ran successfully. I can control the box using the keyboard. It doesn't respond to the Hauppauge silver remote. IRW doesn't show any activity. I am using my IR dongle and remote. I ran lirc-reconfig.sh and picked the silver remote. I looked at various posts and collected info and it seems to agree with working installations: /etc/lirc/hardware.conf seems OK: Code: root@mythtv:/etc/lirc# cat hardware.conf # /etc/lirc/hardware.conf # # Arguments which will be used when launching lircd LIRCD_ARGS="" #Don't start lircmd even if there seems to be a good config file START_LIRCMD=false #Try to load appropriate kernel modules LOAD_MODULES=true # Run "lircd --driver=help" for a list of supported drivers. DRIVER="default" # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be # automatically used instead DEVICE="/dev/lirc0" MODULES="lirc_dev lirc_i2c" lirc devices Code: root@mythtv:/dev# ls -al /dev/lirc* crw-rw---- 1 root video 61, 0 Oct 3 13:21 /dev/lirc0 crw-rw---- 1 root video 61, 1 Oct 3 13:21 /dev/lirc1 srw-rw-rw- 1 root root 0 Oct 3 13:21 /dev/lircd lirc processes: Code: root@mythtv:/dev# pgrep -fl lirc 2908 lirc_dev 2911 /usr/sbin/lircd --driver=default --device=/dev/lirc0 Code: root@mythtv:/dev# lsmod \|grep lirc lirc_serial 16128 0 lirc_i2c 12420 2 lirc_dev 16772 2 lirc_serial,lirc_i2c i2c_core 20864 22 nvidia,lirc_i2c,i2c_ec,cx88_vp3054_i2c,cx88xx,saa7134_dvb,saa7134, ir_kbd_i2c,tda1004x,dvb_bt8xx,bttv,ivtv,saa7115,msp3400,tuner,tea5767, tda8290,tuner_simple,mt20xx,i2c_algo_bit,tveeprom,i2c_nforce2 Any suggestions appreciated.

Author:	slowtolearn [ Wed Oct 03, 2007 1:37 pm ]
Post subject:
Is your COM port enabled in the BIOS? What does Code: dmesg \| grep ttyS show you?

Author:	George [ Wed Oct 03, 2007 2:10 pm ]
Post subject:
slowtolearn wrote: Is your COM port enabled in the BIOS? What does Code: dmesg \| grep ttyS show you? Thanks for your suggestion. I don't think this would be a COM port issue but I don't have a clue what to look at. The IR dongle is a receiver and plugs into the PVR-250 . Here are the COM ports it shows: Code: root@mythtv:~# dmesg \| grep ttyS serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

Author:	slowtolearn [ Wed Oct 03, 2007 2:37 pm ]
Post subject:
George wrote: Thanks for your suggestion. I don't think this would be a COM port issue but I don't have a clue what to look at. The IR dongle is a receiver and plugs into the PVR-250. Ahh, I thought George wrote: I have 2 identical boxes, one is mine and the other a friends. They have a PVR-250, 7N1F2 MB and Athlon processor. They also have a homemade IRblaster running off COM1 controlling a DISH receiver meant you were using the IRBlaster with the remote. Missed the "IR dongle and remote" part. Are you sure the dongle is plugged in all the way? I have had problems with the jack not seating properly.

Author:	George [ Wed Oct 03, 2007 3:57 pm ]
Post subject:
slowtolearn wrote: Are you sure the dongle is plugged in all the way? I have had problems with the jack not seating properly. Yes, reinserted it a few times. I just did a test that proves the hardware is OK. I pulled the HD from mine and put it in my friends box. It sees the Hauppauge remote.

LinHES Forums http://forums.linhes.org/

R5F27-Hauppauge remote doesn't work after fresh install http://forums.linhes.org/viewtopic.php?f=2&t=16841	Page 1 of 1

Author:	tjc [ Wed Oct 03, 2007 5:42 pm ]
Post subject:
See the R5F27 Hints. Known Issue #5.

Author:	George [ Wed Oct 03, 2007 6:22 pm ]
Post subject:
tjc wrote: See the R5F27 Hints. Known Issue #5. Thanks, I checked if the driver was used and then deleted it on mine and then on my friends box. The loaded module you see in my first post was before I deleted it. I encountered the sluggish response on mine but the Hauppauge remote doesn't work at all on my friend's box.

Author:	marc.aronson [ Wed Oct 03, 2007 6:30 pm ]
Post subject:
I would try re-running lirc-reconfig.sh just to make sure that you configured the correct remote... Marc

Author:	George [ Thu Oct 04, 2007 12:00 pm ]
Post subject:
marc.aronson wrote: I would try re-running lirc-reconfig.sh just to make sure that you configured the correct remote... Marc I did that a number of times with no difference. I just did the following: fresh install of R5F27, ran lirc-reconfig.sh and it still doesn't see the remote. Figured since I did a R5D1 install last year on the box with no issues I would try that and upgrade if it works. The R5D1 CD was bad so I installed R5E50, ran lirc-reconfig.sh and it doesn't see the remote. If I swap my working R5F27 HD into the box everything works fine including the remote.

Author:	marc.aronson [ Thu Oct 04, 2007 12:59 pm ]
Post subject:
I don't know what's going wrong, but if I understanding correctly, when you move the hard drive over from the "good" machine where the remote works to the "problematic" machine, everything works fine on the "problematic" machine. Do I have this right? If so, I see two potential approaches that could get things up a running: 1. Make an image copy of the "good drive" to the drive that belongs in the "problematic" machine. 2. Alternatively, move the "problematic" machine's HD to the "good" machine, do a fresh install of R5F27 on the "good": machine, confirm that it works on the "good" machine, and then move it over to the "problematic" machine. Given the facts you've outlined, I would think that either approach would get you to something that works, although neither approach identifies the root-cause of the problem... Marc

Author:	marc.aronson [ Thu Oct 04, 2007 1:01 pm ]
Post subject:
A follow-up to my previous post. If you want to continue pursuing the root-cause of the problem, I would look at the contents of /var/log/messages and /var/log/kern.log after a reboot. Look for any messages that might give a clue... Marc

Author:	George [ Thu Oct 04, 2007 2:47 pm ]
Post subject:
marc.aronson wrote: I don't know what's going wrong, but if I understanding correctly, when you move the hard drive over from the "good" machine where the remote works to the "problematic" machine, everything works fine on the "problematic" machine. Do I have this right? If so, I see two potential approaches that could get things up a running: 1. Make an image copy of the "good drive" to the drive that belongs in the "problematic" machine. 2. Alternatively, move the "problematic" machine's HD to the "good" machine, do a fresh install of R5F27 on the "good": machine, confirm that it works on the "good" machine, and then move it over to the "problematic" machine. Marc Yes, you are correct. I was thinking of doing an image but here is what I just did and everything seems to be working OK. I downloaded R5D1 and installed it. The remote worked. Then I did an auto upgrade to R5F27. I don't understand why that works because it asks you to configure the remote. Maybe something that gets restored from the backup is correct?

Author:	marc.aronson [ Thu Oct 04, 2007 3:56 pm ]
Post subject:
I'm glad to hear that it is working. It is difficult to say for sure why the autoupgrade from r5d1 worked. As you sugggest, it may have something to do with a restored configuration file. It dawns on me that a useful experiment would have been to run irw to see if the signals were getting through, but now that you're running, it's probably academic... Marc

Author:	George [ Fri Oct 05, 2007 7:10 am ]
Post subject:
marc.aronson wrote: I'm glad to hear that it is working. It is difficult to say for sure why the autoupgrade from r5d1 worked. As you sugggest, it may have something to do with a restored configuration file. It dawns on me that a useful experiment would have been to run irw to see if the signals were getting through, but now that you're running, it's probably academic... Marc I had a dim memory about reading about irw and then rediscovered it when I started poking at the problem. It didn't show any activity when I ran it.

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/