You are not logged in.

Dear visitor, welcome to VDR Portal. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Friday, March 30th 2012, 3:51pm

nova-t 500 remote only works on cold boot, not after reboot

Output of cat /proc/bus/input/device is attached. The output is the same for both cold and warm boot.
iampivot has attached the following file:
  • coldstate.txt (1.47 kB - 48 times downloaded - latest: Nov 24th 2014, 1:20pm)
-Tor

2

Friday, March 30th 2012, 4:09pm

Hi,
I found this thread yavdr 4.0; grey hauppauge remote on nova-t 500
Probably you were absolutely right it's a driver related issue - but it seems it existed with v4l-dvb-dkms already.
Are there any hints within the output of dmesg if there is a problem loading the firmware?

There are two other recognized IR-receivers attached to your VDR - probably you could use them, too.
yaVDR-Doku

Meine VDRs

VDR 1: Point of View Ion-330-1 (Intel Atom 330@1,6 GHz). 2GB, 4TB HDD, KNC One DVB-C, Sundtek MediaTV Pro (DVB-C), Atric IR-Einschalter Rev.5, yaVDR 0.5 testing
VDR 2: Acer Revo 3610, 4GB Ram, 1x HDD 320 GB, Pinnacle PCTV SAT 452e, Medion X10, YaVDR 0.5
VDR 3: Intel DH67BL, Celeron 540, 4 GB Ram, POV Geforce 210 512 MB, 500 GB, DD Duo-flex CT, Arch LInux, VDR 2.1.6, CIR-Empfänger
Client 1: Raspberry Pi Model B, Arch Linux ARM, VDR 2.1.6
vdr-epg-daemon + MariaDB auf Cubietruck mit 32 GB SSD, Arch Linux ARM, optional Sundtek MediaTV Pro III + VDR 2.1.6
Ceterum censeo enchiridia esse lectitanda.

3

Friday, March 30th 2012, 5:52pm

Hi,
I found this thread yavdr 4.0; grey hauppauge remote on nova-t 500
Probably you were absolutely right it's a driver related issue - but it seems it existed with v4l-dvb-dkms already.
Are there any hints within the output of dmesg if there is a problem loading the firmware?

It appears that the only significant difference is the line "dib0700: rc submit urb failed"

A google search turns up a few other people with the same problem, but no apparent solution. Am wondering if some recent dib0700 cleanups would possibly fix the issue? See eg. http://patchwork.linuxtv.org/patch/9858/

I assume there's no way to run more recent kernels except using the test repositories?

There are two other recognized IR-receivers attached to your VDR - probably you could use them, too.
Well, there's one additional nova-t 500 card with the same problem, and the driver for the other, a c1501 dvb-c card doesn't implement generic RC-5 reception as the nova-t 500 does.
-Tor

5

Friday, March 30th 2012, 6:04pm

c1501 dvb-c card doesn't implement generic RC-5 reception as the nova-t 500 does.

What protocols are supported by this card?

Source code

1
sudo ir-keytable
yaVDR-Doku

Meine VDRs

VDR 1: Point of View Ion-330-1 (Intel Atom 330@1,6 GHz). 2GB, 4TB HDD, KNC One DVB-C, Sundtek MediaTV Pro (DVB-C), Atric IR-Einschalter Rev.5, yaVDR 0.5 testing
VDR 2: Acer Revo 3610, 4GB Ram, 1x HDD 320 GB, Pinnacle PCTV SAT 452e, Medion X10, YaVDR 0.5
VDR 3: Intel DH67BL, Celeron 540, 4 GB Ram, POV Geforce 210 512 MB, 500 GB, DD Duo-flex CT, Arch LInux, VDR 2.1.6, CIR-Empfänger
Client 1: Raspberry Pi Model B, Arch Linux ARM, VDR 2.1.6
vdr-epg-daemon + MariaDB auf Cubietruck mit 32 GB SSD, Arch Linux ARM, optional Sundtek MediaTV Pro III + VDR 2.1.6
Ceterum censeo enchiridia esse lectitanda.

6

Sunday, April 1st 2012, 2:18pm

c1501 dvb-c card doesn't implement generic RC-5 reception as the nova-t 500 does.

What protocols are supported by this card?

Source code

1
sudo ir-keytable

root@htpc2:~# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event2) with:
Driver budget_ci, table rc-tt-1500
Supported protocols:
Enabled protocols:
Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc1/ (/dev/input/event3) with:
Driver (null), table rc-dib0700-rc5
Supported protocols: NEC RC-5 RC-6
Enabled protocols: RC-5
Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc2/ (/dev/input/event4) with:
Driver (null), table rc-dib0700-rc5
Supported protocols: NEC RC-5 RC-6
Enabled protocols: RC-5
Repeat delay = 500 ms, repeat period = 125 ms
-Tor

Similar threads