[SOLVED upgrading to yaVDR 0.5]Total hang in yaVDR 0.4

BlueVIP · 21. März 2012

Had a similar issue.
Could it be that we resurrect the IRQ-DMA-EPG-Bug by changing the dvb-packages? i know that it was only mantis related but who knows..
Maybe you can try deactivating your EPG-Scan. I think/hope it solved the problem in my case.

jbjbjb · 21. März 2012

Zitat von BlueVIP

Had a similar issue.
Could it be that we resurrect the IRQ-DMA-EPG-Bug by changing the dvb-packages? i know that it was only mantis related but who knows..
Maybe you can try deactivating your EPG-Scan. I think/hope it solved the problem in my case.

Hi.

But if I deactivate EPG-Scan, do I miss the epg info for scheduling recordings?

jbjbjb

fnu · 21. März 2012

Zitat von jbjbjb

But if I deactivate EPG-Scan, do I miss the epg info for scheduling recordings?

Yes, it'll disable the background EIT scan. You still get the EPG information from the activly viewed live tv channels.

What version of VDR do you actually use? The version 1.7.22 from stable-vdr? Do you use Device Bonding? Would you give VDR 1.7.26 from testing-vdr a chance?

Regards
fnu

jbjbjb · 21. März 2012

Zitat von fnu

What version of VDR do you actually use? The version 1.7.22 from stable-vdr? Do you use Device Bonding? Would you give VDR 1.7.26 from testing-vdr a chance?

Regards
fnu

Hi.

I use yaVDR-0.4 updated. I guess the version of VDR came from stable-vdr.

I do not know what is "Device Bonding" so I can not answer you the question.

I would give a chance to VDR 1.7.26, but I am not an advanced user and I do not know how to change the VDR version. I just know how to do "apt-get update" and "apt-get dist-upgrade", so I guess I will have to wait till the version 1.7.26 is in yaVDR repository.

Thanks.
jbjbjb

fnu · 21. März 2012

Zitat von jbjbjb

I do not know what is "Device Bonding" so I can not answer you the question.

Device Bonding has been known in the past as "LNB Sharing Patch". This function is since 1.7.22 part of upstream VDR, called "Device Bonding".

Regards
fnu

jbjbjb · 21. März 2012

Zitat von fnu

Device Bonding has been known in the past as "LNB Sharing Patch". This function is since 1.7.22 part of upstream VDR, called "Device Bonding".

Regards
fnu

Thanks for the answer but I do not know if I am using it.

I only have to install a patch to have infrared working every time there are a kernel update. It is a file (nuvoton-cir.ko) that I copy in:
/lib/modules/2.6.XX-XX-generic/kernel/drivers/media/rc
afterwards I run:
sudo depmod -v
and afterwards I reboot the computer.

Regards.
jbjbjb

fnu · 21. März 2012

Zitat von jbjbjb

Thanks for the answer but I do not know if I am using it.

In that case most probably not, either you have 2x DVB device connect to one LNB connection, supported by an apropriate splitter?

Zitat von jbjbjb

I only have to install a patch to have infrared working every time there are a kernel update. It is a file (nuvoton-cir.ko) that I copy in:
/lib/modules/2.6.XX-XX-generic/kernel/drivers/media/rc

Wow, since some fellows of the yaVDR team do use these nuvoton devices, I would guess we have a proper DKMS solution in our repositories. Let me point one of the guys to this thread here.

If you are interessted in testing VDR 1.7.26, you might add our PPA "testing-vdr" on top of the existing stable ones:

Code

#/> sudo apt-add-repository ppa:yavdr/testing-vdr
#/> sudo apt-get update
#/> sudo apt-get dist-upgrade

Regards
fnu

seahawk1986 · 21. März 2012

Zitat von jbjbjb

I only have to install a patch to have infrared working every time there are a kernel update. It is a file (nuvoton-cir.ko) that I copy in:

Hi, what patch is it? Have you checked if it has been included to our driver-packet linux-media-dkms already?

jbjbjb · 21. März 2012

Zitat von seahawk1986

Hi, what patch is it? Have you checked if it has been included to our driver-packet linux-media-dkms already?

Hi.

Sorry, but I do not know if it is included. I only can say that without the patch my remote control does not work.

I upload the file for your checking.

Thanks.
jbjbjb

seahawk1986 · 21. März 2012

It's hard to tell from a already compiled binary file - have you ever tried to install the package linux-media-dkms?

jbjbjb · 21. März 2012

Zitat von seahawk1986

It's hard to tell from a already compiled binary file - have you ever tried to install the package linux-media-dkms?

Nop, What should I do?, deleting the nuvoton-cir.ko file, do the "sudo depmod -v" and install linux-media-dkms?.

jbjbjb

seahawk1986 · 22. März 2012

Installing linux-media-dkms and a reboot should be enough AFAIK

jbjbjb · 22. März 2012

Hi.

Installed linux-media-dkms and a rebooted. Now the remote works fine except the "Menu" button, it does not work. Some idea how to recover that button?

Edited: Power button does not work neither.

Regards.
jbjbjb

seahawk1986 · 22. März 2012

Zitat von jbjbjb

Now the remote works fine except the "Menu" button, it does not work. Some idea how to recover that button?

Please post the output of "sudo ir-keytabe" and "sudo ir-keytable -r"

jbjbjb · 22. März 2012

Zitat von seahawk1986

Please post the output of "sudo ir-keytabe" and "sudo ir-keytable -r"

Hi.

Results for "sudo ir-keytable":

Code

Found /sys/class/rc/rc0/ (/dev/input/event2) with:
	Driver nuvoton-cir, table rc-rc6-mce
	Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other 
	Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC other 
	Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc1/ (/dev/input/event4) with:
	Driver dib0700, 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/event5) with:
	Driver dib0700, 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/rc3/ (/dev/input/event6) with:
	Driver dib0700, table rc-dib0700-rc5
	Supported protocols: NEC RC-5 RC-6 
	Enabled protocols: RC-5 
	Repeat delay = 500 ms, repeat period = 125 ms

Alles anzeigen

Results for "sudo ir-keytable -r":

Code

scancode 0x800f0400 = KEY_NUMERIC_0 (0x200)
scancode 0x800f0401 = KEY_NUMERIC_1 (0x201)
scancode 0x800f0402 = KEY_NUMERIC_2 (0x202)
scancode 0x800f0403 = KEY_NUMERIC_3 (0x203)
scancode 0x800f0404 = KEY_NUMERIC_4 (0x204)
scancode 0x800f0405 = KEY_NUMERIC_5 (0x205)
scancode 0x800f0406 = KEY_NUMERIC_6 (0x206)
scancode 0x800f0407 = KEY_NUMERIC_7 (0x207)
scancode 0x800f0408 = KEY_NUMERIC_8 (0x208)
scancode 0x800f0409 = KEY_NUMERIC_9 (0x209)
scancode 0x800f040a = KEY_DELETE (0x6f)
scancode 0x800f040b = KEY_ENTER (0x1c)
scancode 0x800f040c = KEY_SLEEP (0x8e)
scancode 0x800f040d = KEY_MEDIA (0xe2)
scancode 0x800f040e = KEY_MUTE (0x71)
scancode 0x800f040f = KEY_INFO (0x166)
scancode 0x800f0410 = KEY_VOLUMEUP (0x73)
scancode 0x800f0411 = KEY_VOLUMEDOWN (0x72)
scancode 0x800f0412 = KEY_CHANNELUP (0x192)
scancode 0x800f0413 = KEY_CHANNELDOWN (0x193)
scancode 0x800f0414 = KEY_FASTFORWARD (0xd0)
scancode 0x800f0415 = KEY_REWIND (0xa8)
scancode 0x800f0416 = KEY_PLAY (0xcf)
scancode 0x800f0417 = KEY_RECORD (0xa7)
scancode 0x800f0418 = KEY_PAUSE (0x77)
scancode 0x800f0419 = KEY_STOP (0x80)
scancode 0x800f041a = KEY_NEXT (0x197)
scancode 0x800f041b = KEY_PREVIOUS (0x19c)
scancode 0x800f041c = KEY_NUMERIC_POUND (0x20b)
scancode 0x800f041d = KEY_NUMERIC_STAR (0x20a)
scancode 0x800f041e = KEY_UP (0x67)
scancode 0x800f041f = KEY_DOWN (0x6c)
scancode 0x800f0420 = KEY_LEFT (0x69)
scancode 0x800f0421 = KEY_RIGHT (0x6a)
scancode 0x800f0422 = KEY_OK (0x160)
scancode 0x800f0423 = KEY_EXIT (0xae)
scancode 0x800f0424 = KEY_DVD (0x185)
scancode 0x800f0425 = KEY_TUNER (0x182)
scancode 0x800f0426 = KEY_EPG (0x16d)
scancode 0x800f0427 = KEY_ZOOM (0x174)
scancode 0x800f0432 = KEY_MODE (0x175)
scancode 0x800f0433 = KEY_PRESENTATION (0x1a9)
scancode 0x800f0434 = KEY_EJECTCD (0xa1)
scancode 0x800f043a = KEY_BRIGHTNESSUP (0xe1)
scancode 0x800f0446 = KEY_TV (0x179)
scancode 0x800f0447 = KEY_AUDIO (0x188)
scancode 0x800f0448 = KEY_PVR (0x16e)
scancode 0x800f0449 = KEY_CAMERA (0xd4)
scancode 0x800f044a = KEY_VIDEO (0x189)
scancode 0x800f044c = KEY_LANGUAGE (0x170)
scancode 0x800f044d = KEY_TITLE (0x171)
scancode 0x800f044e = KEY_PRINT (0xd2)
scancode 0x800f0450 = KEY_RADIO (0x181)
scancode 0x800f045a = KEY_SUBTITLE (0x172)
scancode 0x800f045b = KEY_RED (0x18e)
scancode 0x800f045c = KEY_GREEN (0x18f)
scancode 0x800f045d = KEY_YELLOW (0x190)
scancode 0x800f045e = KEY_BLUE (0x191)
scancode 0x800f0465 = KEY_POWER2 (0x164)
scancode 0x800f046e = KEY_PLAYPAUSE (0xa4)
scancode 0x800f046f = KEY_PLAYER (0x183)
scancode 0x800f0480 = KEY_BRIGHTNESSDOWN (0xe0)
scancode 0x800f0481 = KEY_PLAYPAUSE (0xa4)
Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC other

Alles anzeigen

Regards.
jbjbjb

seahawk1986 · 22. März 2012

All right - please download this script and run it:

Code

wget http://dl.dropbox.com/u/960809/list-rc-core.sh
sudo cmod +x list-rc-core.sh
sudo ./list-rc-core.sh set

It will create all needed files, templates and rules for your receivers. After running my script there should be a new file: /etc/rc_keymaps/rc-rc6-mce you will have to edit as follows:
First line:

Code

# table rc-rc6-mce, type: RC-6

Then rename the keys that aren't working to the standard yaVDR names (as stated in the Documentation http://www.yavdr.org/documentation/de/ch02s03.html#id490366 or in your remote.conf - btw: we are still looking for someone who is able to translate our documentation into good english and other languages), for example change

Code

0x800f040d = KEY_MEDIA

to

Code

0x800f040d = KEY_MENU

After you edited the keytable, you can either reboot your PC or use it by (re)loading the new keytable manually:

Code

sudo ir-keytable -w /etc/rc_keymaps/rc-rc6-mce

jbjbjb · 22. März 2012

Hi.

Thanks for the script and the explanations.

Menu button is working now, but power button is not.

I think the line with "0x800f0465 = KEY_POWER2" is correct but the power button does not work.

Should I change for another key?

Regards.
jbjbjb

seahawk1986 · 22. März 2012

Zitat von jbjbjb

I think the line with "0x800f0465 = KEY_POWER2" is correct but the power button does not work.

What is the output for the power key (when eventlircd is stopped)

Code

sudo ir-keytable -t

And what is the output of "sudo irw" (when eventlircd is started) for the same key?

jbjbjb · 22. März 2012

Zitat von seahawk1986
What is the output for the power key (when eventlircd is stopped)
Code
sudo ir-keytable -t
And what is the output of "sudo irw" (when eventlircd is started) for the same key?

Hi

For sudo irw:

Code

8e 0 KEY_SLEEP devinput

But for sudo ir-keytable -t

Code

Testing events. Please, press CTRL-C to abort.

Nothing more happens, even pressing buttons.

jbjbjb

seahawk1986 · 22. März 2012

Zitat von jbjbjb

Nothing more happens, even pressing buttons.

Did you stop eventlircd before?

Code

sudo stop eventlircd

[SOLVED upgrading to yaVDR 0.5]Total hang in yaVDR 0.4

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema