Just had to start from scratch with yavdr so thought i would upload how i did it for anybody stuck (1st time around it took me hours to figure out!):
Hardware used:
Acer Revo r3610
tevii s660
---------------------------
INSTALL YAVDR
Install yavdr 0.2 including liplianin (dont know if s2-liplianin is required)
its hangs a lot during installation but finally finishes! (especially on finishing installation @ 27%)
then ssh into the yavdr box from another pc and update:
UPDATE YAVDR
1) To obtain the list of available updates:
sudo apt-get update
2) To install available package updates:
sudo apt-get upgrade
3) To install package updates that were kept back:
Either sudo apt-get dist-upgrade
4) Reboot
sudo reboot
check whether tevii driver is detected: dmesg |grep dvb
chances are it will say looking for a driver ..... (note this driver file name)
INSTALL TEVII DRIVER
1) Download drivers (check this is the latest)
wget http://tevii.com/100315_Beta_linux_tevii_ds3000.rar
2) install nano
sudo apt-get install nano
3) install unrar
sudo apt-get install unrar
4) Extract drivers
unrar e 100315_Beta_linux_tevii_ds3000.rar
4) open the Readme
sudo nano README
5) Follow the Readme instructions:
sudo cp *.fw /lib/firmware
sudo tar xjvf linux-tevii-ds3000.tar.bz2
cd linux-tevii-ds3000
sudo make
sudo make install
6) Backup the driver
sudo cp dvb-usb-teviis660.fw dvb-usb-teviis660backup.fw
7) Rename the driver to match the one dmesg is looking for
sudo mv dvb-usb-teviis660.fw dvb-usb-s660.fw 
Reboot
sudo reboot
9) dmesg |grep dvb
should say usb successfully initalized and connected
Download channels.conf from here:
http://www.vdr-settings.com/download/channels/
or scan for your own (tevii takes AGES)
Paste into VDR Config Upload (on the Yavdr webGUI eg 192.168.0.2 or whatever your Ip address is)
RESTART THE VDR FRONTEND
WegGui > System > System > Restart VDR backend
Change sound settings:
GUI > System > Sound > select relevent one
Change resolution:
GUI > System > Display > select relevent one
If after a reboot the channels are showing (after a short period) and you find a restart of the VDR backend fixes this, there is another fix:
Put a "sleep x" line into /etc/init/vdr.conf right after the line "script". Instead of the x, provide a number (=number of seconds to delay VDR start). Experiment which delay suits your setup.