[yavdr 4] Cannot "see" tuner: TechnoTrend S2-3600

  • Hi,


    After sucessfulll upgrade mine yavdr installation i've plugged in this tuner and .... lsusb can recognize it:

    Code
    root@htpc64:~# lsusb | grep TechnoTrend
    Bus 001 Device 004: ID 0b48:3007 TechnoTrend AG TT-connect S2-3600


    But dmesg not :(

    Code
    root@htpc64:~# dmesg | grep dvb
    [   12.781342] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
    [   12.782678] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    [   14.528252] dvb-usb: schedule remote query interval to 500 msecs.
    [   14.528265] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
    [   14.538246] usbcore: registered new interface driver dvb_usb_af9015


    I've did reconfiguration of linux-media drivers - without any resoult. Could you halp me with this?


    Code
    root@htpc64:~# ls /dev/dvb/adapter0/
    demux0 	dvr0   	frontend0  net0
  • After sucessfulll upgrade mine yavdr installation


    What do you mean with update?


    I've did reconfiguration of linux-media drivers


    Do you have already installed the new driver?


    Code
    apt-get install linux-media-dkms


    Albert

  • I had some problems with do-distro-upgrade - with help of other foum coleuages i was albe to make proper update ;)


    I had only linux-media-tbs-dkms package installed, now i will instal version proposed by u :)


    M.

  • I had some problems with do-distro-upgrade


    Code
    sudo apt-get update && apt-get dist-upgrade


    I had only linux-media-tbs-dkms package installed, now i will instal version proposed by u


    What for a DVB device do you have? The linux-media-tbs-dkms is correct for TBS cards. For every else is the linux-media-dkms the newest driver package.


    Albert

  • Alber, i have device mantioned in topic. After installing package u proposed dmesg is showing the card, but:

    Code
    Apr 28 21:29:50 htpc64 kernel: [  300.050478] pctv452e: I2C error -121; AA C4  CC 00 01 -> 55 C4  CC 00 00.
    Apr 28 21:29:50 htpc64 kernel: [  300.065752] pctv452e: I2C error -121; AA DB  CC 00 01 -> 55 DB  CC 00 00.
    Apr 28 21:29:50 htpc64 kernel: [  300.150402] pctv452e: I2C error -121; AA F7  CC 00 01 -> 55 F7  CC 00 00.
    Apr 28 21:29:50 htpc64 kernel: [  300.570386] pctv452e: I2C error -121; AA A1  CC 00 01 -> 55 A1  CC 00 00.
    Apr 28 21:29:50 htpc64 kernel: [  300.790483] pctv452e: I2C error -121; AA EF  CC 00 01 -> 55 EF  CC 00 00.


    I've read that this error is appering on 3.x kernels, but currently I have:

    Code
    root@htpc64:~# uname -a
    Linux htpc64 2.6.38-14-generic #58-Ubuntu SMP Tue Mar 27 20:04:55 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
  • What for a DVB device do you have?


    Fu*k. Sorry Miszka. :wand


    Code
    2.6.38-14-generic


    is ok.


    Code
    sudo -s
    apt-get update && apt-get dist-upgrade
    apt-get remove linux-media-tbs-dkms
    apt-get install linux-media-dkms


    Showtime. :D


    Albert

  • :)


    Thanks for the replay. I've mentioned after sucessfull upgrade ..... so I'm after this steps ;)


    Code
    Reading state information... Done
    Package linux-media-tbs-dkms is not installed, so not removed


    So .... this is not the reason :(


    M.

  • Code
    apt-get install linux-media-dkms


    And this? ;)


    Albert

  • Yup, after this card was accessable in dmesg....


    What else? ;)


    Albert

  • Yup, after this card was accessable in dmesg....


    If it works, then set the thread to solved.


    Albert

  • To be honest i'm able to see only log messages - as mine new htpc is standing next to old one and it is connected only to network to copy all movies ;)
    So till now I was not able to "see" picture - but this error logs was upsetting me - that's why I was asking about them....

  • HD channels sometimes scrach


    Then post the log.


    Albert

  • Only bothering thing is this buffering in logs - that's why I was asking about buffering stream on hdd.


    Code
    May  1 08:05:48 htpc64 vdr: [2149] ERROR: 1 ring buffer overflow (89 bytes dropped)
    May  1 08:05:50 htpc64 vdr: [2149] buffer usage: 40% (tid=2148)
    May  1 08:05:51 htpc64 vdr: [2149] buffer usage: 70% (tid=2148)
    May  1 08:05:51 htpc64 vdr: [2149] buffer usage: 80% (tid=2148)
    May  1 08:05:51 htpc64 vdr: [2149] buffer usage: 90% (tid=2148)
    May  1 08:05:51 htpc64 vdr: [2149] buffer usage: 100% (tid=2148)
    May  1 08:05:52 htpc64 vdr: [2149] buffer usage: 10% (tid=2148)
    May  1 08:05:56 htpc64 vdr: [2149] buffer usage: 70% (tid=2148)
    May  1 08:05:56 htpc64 vdr: [2149] buffer usage: 40% (tid=2148)


    I slso get I2C errors:


  • Code
    May  1 08:08:06 htpc64 vdr: [2149] buffer usage: 0% (tid=2148)
    May  1 08:08:46 htpc64 vdr: [2149] buffer usage: 70% (tid=2148)
    May  1 08:08:46 htpc64 vdr: [2149] buffer usage: 80% (tid=2148)
    May  1 08:08:46 htpc64 vdr: [2149] buffer usage: 90% (tid=2148)
    May  1 08:08:47 htpc64 vdr: [2149] buffer usage: 100% (tid=2148)
    May  1 08:08:47 htpc64 vdr: [2149] ERROR: 18059 ring buffer overflows (3394988 bytes dropped)
    May  1 08:08:47 htpc64 vdr: [2149] buffer usage: 0% (tid=2148)
  • Yup, scraches showing when this error appears:

    Code
    May  1 08:14:18 htpc64 vdr: [2149] buffer usage: 100% (tid=2148)
    May  1 08:14:18 htpc64 vdr: [2149] ERROR: 240 ring buffer overflows (45021 bytes dropped)
    May  1 08:14:18 htpc64 vdr: [2149] buffer usage: 0% (tid=2148)
  • Code
    ERROR: 240 ring buffer overflows


    Please post "vdr -V"


    Albert

  • Code
    buffer usage: 100%


    It I seem to know. My workmate had the same thing. Fault was the plasma TV, or settings.


    - Let yaVDR recognize the TV again. (WFE)
    - Point only 50 Hz refresh rate.
    - Set from Xine to vdr-sxfe and then back.
    - Point a sound over HDMI only.


    After each step, do not forget to save. ;)


    Place all your hardware in the signature. We do not want to puzzle. :ausheck


    vdr -V is clean.


    Albert

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!