dynamite is disabled? The other plugin is compiled against the right vdr-package?
Otherwise: Good luck...!
I found the problem... And it was skinflatplus plugin. 
For some reason it freezes with combination of that other plugin. Well now using lcars and everything seems to be working great!
Moving to testing was easy, but I have big problem with one plugin (which is not allowed to talk here). 
Channel changing will freeze vdr quite often.
Ok, Thanks. How about if I am going to go to the vdr testing, do I have to move xbmc testing too or does it matter at all ?
You could try the testing-PPAs, there's a vdr 2.2.0. Moving to testing is described somewhere on this board. Important is to apt-pin the testing-PPAs.
Lars.
Hmm. I am not familiar with pinning ? Why it has to be done. I have using testing repo before, but never pinned anything. Well it seems that I have to start searching. (quite hard, because I am not understanding german at all). 
Do we still see upgrades to the yaVDR 0.5 stable ? I mean that do vdr 2.0.6 to be upgraded newer version ?
I have problem that channels does not get updated and I understand it is cause of some patch which is in this release.
If vdr is not going to be updated anymore, I am thinking of move to the testing or start compiling vdr manually.
Thank you for your great work !
How about using static builds ? http://johnvansickle.com/ffmpeg/
I would love to have yaVDR based on rolling release like archlinux or debian.. I hate all of these reinstall things every now and then..
Well keep up to the good work !
Just use softhddevice and you won't need the restart of vdr-sxfe.
SoftHDDevice works for me without any freezes (about month).
Well I have just opposite. Xineliboutput without any problems, but softhddevice freezes all the time. (some alsa broken pipe error)
Just installed yaVDR 0.5 .... and gettig this problem... Is there some fix ? I don't want go back to 0.4.
So, no fault from our side, but since I'm anyway need to work on the repository to push some newer versions of plugins, I'll try to provide them. Not today, sometime tomorrow ...
Thank you for your effort !!
You'll get the latest available VDR developer version, 1.7.27.
Damn. Now I lost vdr-plugin-epgsync, vdr-plugin-svdrpservice and vdr-plugin-ttxtsubs.
Do you think you would have done it better?
No.. I just hope we get simple upgrade solution without clean start.
Afterwards you got an rock solid, fast and modern 64-bit installallation, most VDPAU performance issues did dissapear from one second to the other ...
That is correct ! And I am very pleased.
Upgrade option for what?
Upgrade yavdr 0.4 -> 0.(5) ...I mean that when we "upgraded" from yavdr 0.3 -> 0.4 we had to start from zero.
Most probably never.
Honestly I would push 1.7.27 to stable-vdr, but then I might have some very good friends here
Therefore I'll keep status quo, since Natty support will end in autumn and a new version of yaVDR is not that far away.
I hope that there will be upgrade option instead of "fresh start". 
Well.. For now I did not update. I've got some unmet depencies problems with some plugins. Do you know when stable repository will get newer vdr ?
Check if the driver is part of the package linux-media-dkms first. If so, you only need to install linux-media-dkms.
Cheers,
hepi
Thanks again hepi. My stick arrived today and indeed that linux-media-dkms included those needed drivers.
Only problem is that dvb-t tuners want to tune those dvb-t2 channels and I need manually change tuner for those. But I got information that vdr-1.7.23 or newer (which are compiled against DVBAPI 5.3) will fix that. Now I am wondering if I need to choose testing-vdr repository ? If I choose that do I have to choose all testing (testing-vdr, testing-xmc and testing-yavdr) repositories too ? Or can I only choose testing-vdr repository ?
Check if the driver is part of the package linux-media-dkms first. If so, you only need to install linux-media-dkms.
Cheers,
hepi
Hmm. I don't know how to check that. Tried to google with that linux-media.dkms... but quite bad result.
Stick is this: http://www.pctvsystems.com/Pro…nguage/en-GB/Default.aspx
Maybe someone can help ?
Hi,
I maybe buy nanostick t2 290e and kernel 3.x includes drivers for that stick. Am I getting trouble with yaVDR 0.4 if I upgrade kernel to 3.x version ?
If there is no problem, how should I proceed installing newer kernel ?
ZitatOriginally posted by schneisa
It is sufficient to deaktivate noad withCodedpkg-reconfigure vdr-addon-noad
Thanks, that helped.
![:]](https://www.vdr-portal.de/images/smilies/pleased.gif "Freude"){kind=small}