Activy 300 eindeutig per SW identifizieren - wie?

  • Hi,


    und hier die Ausgabe von biosinfo bei einer Activy350 (zum Gegencheck):


    Following DMI entries found:
    - Mainboard vendor: "FUJITSU SIEMENS"
    - Mainboard type: "D1636"
    - Mainboard revision: "S26361-D1636"
    - BIOS vendor: "FUJITSU SIEMENS // Phoenix Technologies Ltd."
    - BIOS version: "4.06 Rev. 1.01.1636"
    - BIOS release: "12/10/2003"


    Gruß
    Zwickel

    yavdr 0.2, POV 330, Cine S2 Dual DVB-S2 (V5.5), OriginAE M10, mit HDMI an Samsung UE32B7090

  • Anbei die Infos der 300.



    Auszug


    Ich denk der System Product Name könnte passen :).



    arghgra

  • hello


    I have a little problem with activy and malhzeit iso beta2.
    on one activy (A), no problem with installation and em84xx pluging
    on 2 other one (B and C), when I want to intall em84xx plugin, the message "kein activy , no output overlay" appear. the end of install work but no tv image on scart, only ALTF10 menu. audio is ok.
    previously B was working (em84xx plugin installed) with vdr but I try to install a special xp embeded image from siemens. after that the install iso beta2 don't detect activy anymore. even with a swap of activy(A) HDD give error.
    I have done a bios reset without success
    what info install program use to detect activy ? (I have not understood all the thead)
    which command can I use to show the difference ? (i'm a linux biginner)


    thanks


    Jean-Christophe

  • The both logs seem to be ok ...


    In both cases em84xx-plugin is started and activated - I think the only missing (functional) part is switching of the tdk5002c-tool here ...


    Maybe you can send the source of the script which says "No activy ..." ... otherwise it's only guessing.


    arghgra

  • hello arghgra


    Zitat

    Originally posted by arghgra
    Maybe you can send the source of the script which says "No activy ..." ... otherwise it's only guessing.


    well, I really don't know how to do that


    Zitat

    Originally posted by arghgra
    The both logs seem to be ok ...


    In both cases em84xx-plugin is started and activated - I think the only missing (functional) part is switching of the tdk5002c-tool here ...


    is there a tools to switch it manualy ?


    thanks


    jc

  • hello


    first, I have upgraded the bios to 109
    I have make a debuginfotrace after
    I still have the message when I select EM84xx plugin in setup
    I didn't find a log error message about that


    I have tryed the your tdk5002cct program
    it give same result on both activy
    may be the default parameter are not correct ?



    mahlzeit:/usr/bin# ./tdk5002cctl -s 2
    Will use sequence 2
    TDK5002c read register settings:
    AUX ycout: sync pulse present
    TV ycout: sync pulse present
    TV_Fnc or AUX_Fnc pin level = _UNKNOWN_ Level - Whats this?
    About to write (0-4): 0 30 0 1 0
    Error while writing data to tdk
    mahlzeit:/usr/bin#



    I have not other idea, maybe I will try to put windows and use siemens wideowizard to switch


    jc

  • i2c 0 is used by bvb card
    i2c 1 is maybe the TDK chip
    the cmd is accepted but the screen doesn't switch, it just flash and remain with alt f10 console msg


    any idea ?


    mahlzeit:~# i2cdetect
    Error: No i2c-bus specified!
    Syntax: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
    i2cdetect -l
    i2cdetect -V
    I2CBUS is an integer
    With -a, probe all addresses (NOT RECOMMENDED)
    With -q, uses only quick write commands for probing (NOT RECOMMENDED)
    With -r, uses only read byte commands for probing (NOT RECOMMENDED)
    If provided, FIRST and LAST limit the probing range.
    With -l, lists installed busses only
    Installed I2C busses:
    i2c-1 unknown SMBus I801 adapter at 1400 Algorithm unavailable
    i2c-0 unknown Fujitsu Siemens Activy Budget-T PCI (rev GR/Grundig frontend) Algorithm unavailable



    mahlzeit:/usr/bin# ./tdk5002cctl -i 1 -s 2
    Will use sequence 2
    TDK5002c read register settings:
    AUX ycout: sync pulse present
    TV ycout: sync pulse present
    TV_Fnc or AUX_Fnc pin level =Level 0 .~0V
    About to write (0-4): 0 30 0 1 0
    Succ. written data to tdk
    mahlzeit:/usr/bin#

  • Zitat

    Original von jc.maquet
    i2c 0 is used by bvb card
    i2c 1 is maybe the TDK chip
    the cmd is accepted but the screen doesn't switch, it just flash and remain with alt f10 console msg


    any idea ?


    Hello,
    yes seem s ok to me, don't know why it is the 2. i2c dev on your system.
    At my activy it looks like this:
    i2cdetect -l
    i2c-2 i2c TT-Budget/WinTV-NOVA-C PCI I2C adapter
    i2c-1 i2c TT-Budget/WinTV-NOVA-C PCI I2C adapter
    i2c-0 smbus SMBus I801 adapter at 1400 SMBus adapter


    Maybe your DVB-Driver is loading bevor the mainboard parts?



    This looks very ok,
    maybe your vdr is not running, there is some info in your debuginfo about trouble with the dvb-t card:
    [ 38.353387] DVB: frontend 0 frequency limits undefined - fix the driver


    One question:
    Your Activys are all normal Europe Activys with 2 Scart connectors, and you always use the lower one?


    (Because there is a US-Version with S-Video and a Activy 200 with only one Scart.)


    Regards Ulf


    Ps:
    Please be very carefull with writing to the i2c because if you write to some wrong device you can damage it very fast.

    Samsung UE43RU7479U, Antec Fusion Black, Prime A320m-k, Ryzen3 3200G, 2* DVB-T2,
    Yavdr-ansible auf Ubuntu Server 22.04

    2 Mal editiert, zuletzt von Ulf ()


  • hello


    vdr is running, I have audio, I can zap beetween channel
    the frequency limit is just a warning message, I have another activy working with this message wihout problem.


    I have 2 scart, I use the upper one labelled TV


    mahlzeit:/usr/bin# i2cdetect -l
    i2c-1 unknown SMBus I801 adapter at 1400 Algorithm unavailable
    i2c-0 unknown Fujitsu Siemens Activy Budget-T PCI (rev GR/Grundig frontend) Algorithm unavailable


    it's a little bit different, I have "unknow" instead I2C


    strange problem, isn't it ?


  • you right
    I have removed the dvb card and I have now the output of EM84 on the tv
    something is conflicting with dvb card


    edit:


    I have putted back again the dvb card in another slot => everything work now !!!!????
    sorry for that
    the I2c bus order remain the same...


    thanks for helping


    Jean Christophe

  • Zitat

    Original von jc.maquet
    a) I have 2 scart, I use the upper one labelled TV
    b) strange problem, isn't it ?


    a) To use the upper one you will need the tiva_overlay , at first it is easyer to check the lower one


    b) Yes it is ;)


    Regards Ulf

    Samsung UE43RU7479U, Antec Fusion Black, Prime A320m-k, Ryzen3 3200G, 2* DVB-T2,
    Yavdr-ansible auf Ubuntu Server 22.04

Jetzt mitmachen!

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