Posts by suheyl

    I have an ASRock 890GX Extreme 3


    http://www.asrock.nl/mb/AMD/890GX%20Extreme3/



    If you look at the picture in the link up, I´ve installed my first card in the left blue slot. In the right blue slot I have my videocard. The second one I´ve installed in the second from left white slot.
    I´ve just pulled out the first one to see if the second one is recognized alone. It isn´t. Putting the second one in the blue slot still not recognized. Then I put the first one on it´s original place, and that one works.


    So I thought the card may be broken. I´ve put the second one in another PC, and figure out, it does work!


    Now I really stuck...

    What does this mean at the end of installation:


    make -C firmware install
    make[2]: Entering directory `/home/suheyl/dvb/media_build_experimental/v4l/firmware'
    Installing firmwares at /lib/firmware: vicam/firmware.fw dabusb/firmware.fw cp: cannot stat `dabusb/firmware.fw': No such file or directory
    dabusb/bitstream.bin cp: cannot stat `dabusb/bitstream.bin': No such file or directory


    See attachment of installation

    Hi all,


    I've tried a clean install after updating the BIOS once again. I still get the same result when I do i2cdetect -y 0.


    I've read about manually setting these things.
    http://www.lm-sensors.org/wiki/i2cToolsDocumentation


    What I understand is that I can use the i2cset command. Correct me if I'm wrong.
    i2cset <bus> <chip> <register> <value>


    So can I use the command like this?


    sudo i2cset 0 ddbridge 0x1e 1e
    sudo i2cset 0 ddbridge 0x1f 1f
    sudo i2cset 1 ddbridge 0x40 40


    I found these values in thedon´s post.

    Hi thedon!


    Thank you for your efforts!


    Here are the outputs:


    suheyl@mediacenter:~$ sudo lspci -vvnn -s 04:00
    04:00.0 Multimedia controller [0480]: Digital Devices GmbH Octopus LE DVB adapter [dd01:0003]
    Subsystem: Digital Devices GmbH Device [dd01:0030]
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 52
    Region 0: Memory at fcff0000 (64-bit, non-prefetchable)
    Capabilities: [50] Power Management version 3
    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
    Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [70] MSI: Enable+ Count=1/2 Maskable- 64bit+
    Address: 00000000fee3f00c Data: 41b9
    Capabilities: [90] Express (v2) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
    ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
    RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
    MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 <1us
    ClockPM- Surprise- LLActRep- BwNot-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
    ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive - BWMgmt- ABWMgmt-
    DevCap2: Completion Timeout: Range A, TimeoutDis+
    DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
    LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
    LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
    EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
    Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=00 c <?>
    Kernel driver in use: DDBridge
    Kernel modules: ddbridge


    dmesg | less


    8.408901] Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH
    [ 8.408943] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
    [ 8.408962] HW 0001000d REG 00010004
    [ 8.409019] DDBridge 0000:04:00.0: irq 52 for MSI/MSI-X
    [ 8.409171] Port 0 (TAB 1): NO MODULE
    [ 8.409859] Port 1 (TAB 2): NO MODULE
    [ 8.410698] Port 2 (TAB 3): NO MODULE
    [ 8.606679] microcode: CPU0: patch_level=0x010000bf
    [ 8.652157] device-mapper: multipath: version 1.4.0 loaded


    sudo i2cdetect -l
    i2c-0 smbus ddbridge SMBus adapter
    i2c-1 smbus ddbridge SMBus adapter
    i2c-2 smbus ddbridge SMBus adapter
    i2c-3 i2c NVIDIA i2c adapter 0 at 5:00.0 I2C adapter
    i2c-4 i2c NVIDIA i2c adapter 1 at 5:00.0 I2C adapter
    i2c-5 i2c NVIDIA i2c adapter 2 at 5:00.0 I2C adapter
    i2c-6 i2c NVIDIA i2c adapter 6 at 5:00.0 I2C adapter


    sudo i2cdetect -y 0
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    sudo i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    sudo i2cdetect -y 2
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    sudo i2cdetect -y 3
    Error: Can't use SMBus Quick Write command on this bus


    sudo i2cdetect -y 4
    Error: Can't use SMBus Quick Write command on this bus


    sudo i2cdetect -y 5
    Error: Can't use SMBus Quick Write command on this bus


    sudo i2cdetect -y 6
    Error: Can't use SMBus Quick Write command on this bus


    I think something went wrong with the NVIDIA driver.... I'm reinstalling it now.


    But no change at all...


    Is there a possibility that I have to install Ubuntu completely? I mean not the XBMCUbuntu version but Ubuntu itself?
    I'm going to start all over after work. A clean and fresh install. Let's see what happens then.

    Hi Oliver!


    Thanx for your efforts man! I really do appreciate this!


    I've first installed this card on the same PC but on WIN7. The card was detected then and I had 67 channels found. But they were, of course, encrytped. I've decided to use XBCMUbuntu because it runs much smoother. More efficient. Except for the tuner :)


    I've installed i2c and here are the results:
    As a noob, I find all those "--" kind of alarming... Am I right?


    i2cdetect -l


    i2c-0 smbus ddbridge SMBus adapter
    i2c-1 smbus ddbridge SMBus adapter
    i2c-2 smbus ddbridge SMBus adapter


    i2cdetect -y


    Bus 0


    i2cdetect -y 0
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    Bus 1


    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    Bus 2


    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    Because I was curious about the other used buses:
    4 buses for my videocard:
    i2c-3 i2c NVIDIA i2c adapter 0 at 5:00.0 I2C adapter


    result:


    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --


    Isn't that weird? That same result is for all four buses. That card is running fine. Or do I misinterpret this?


    Cheers man

    Hi Oliver,


    I'm sorry. I didn't want to offend you.
    I'm just frustrated it's still not working. As I'm a total noob in Linux I don't know where to begin. I just hoped for some official support from the producer.

    Looks like tha card is broken.
    Could you re-test it on a different system, if possible on a Windows machine?

    Hi Oliver,


    I've already tried that. The card works fine on Windows 7... It's a brand new card.
    I've first installed it on a Windows machine. This did not perform well. I could not get everything intergrated in XBMC on Windows. That's why I reverted to Linux.

    Is anything else connected to the ports of the card?


    Please provide the output of 'lspci -vnn'.

    Hi. No there is nothing else connected to the card. I have the lspci attached. Thank you for your help!





    Falls jemand mich helfen kann, aber nur auf Deutsch, Ich verstehe Deutsch, aber Englisch ist mir einfacher ;) Ich lebe nähe Deutschland auf die Grenze.

    Hi,


    I'm new into Linux and DVB-cards. Now I understand why people shy away from Linux :rolleyes:


    I have installed the newest version of XBMCUbuntu. I have everything working except for the Digital Devices Cine CT card. I have been trying a lot and still not managed to get it working.
    I came across a lot of sites, none of them with a working sollution. This one caught my eyes as it was recenty updated


    http://www.linuxtv.org/wiki/in…tal_Devices_DuoFlex_C%26T

    And it did made me mad! :§$% After so many hours working, dissapointment.
    Maybe somebody can help me here to get this card running.


    I followed this steps:

    http://support.digital-devices…ledgebase.php?article=124


    But when I'm doing step "sudo make" I get the next error:


    LD [M] /usr/src/media_build_experimental/v4l/zr364xx.ko
    make[2]: Leaving directory `/usr/src/linux-headers-3.5.0-22-generic'
    ./scripts/rmmod.pl check
    Can't locate Proc/ProcessTable.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at ./scripts/rmmod.pl line 4.
    BEGIN failed--compilation aborted at ./scripts/rmmod.pl line 4.
    make[1]: *** [default] Error 2
    make[1]: Leaving directory `/usr/src/media_build_experimental/v4l'
    make: *** [all] Error 2


    Hope someone can help me. In the attachment I have some additional info.



    info.txt