Vu+
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Hyperstick Digital Key Usb Terrestre T2/C

Discussion in 'Dispositivi DVB' started by wyzard, Feb 10, 2015.

  1. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    Provato varie volta la pennetta Hyperstick Digital Key Usb Terrestre T2/C come da titolo ma niente non viene riconosciuta è normale e sono previsti aggiornamenti o è un prob mio? grazie
    PS: immagine BH ultima ovviamente
     
  2. Eragon

    Eragon Moderator

    Messages:
    3,041
    A parte i siti (soprattutto italiani) che lo vendono non si trovano molte informazioni su Internet.
    Su Linuxtv con quel nome non si trova nulla.
    Per cui potrebbe essere piu' nota sotto un altro nome...

    Comunque in genere i dati tecnici citati sono in tedesco, per cui potrebbe essere supportata da qualche immagine made in Germany.

    Se trovi le specifiche del chipset interno usato come sintonizzatore si potrebbe sapere di piu' sulla sua compatibilita'.

    hyperstick-digital-key-usb-terrestre-t2-c.jpg
     
  3. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
  4. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    grazie per l'interessamento ma ho difficoltà nel capire cosa scrivere nel putty scusate, non so se il nome opticombo può aiutare cosi è stata chiamata consigliata forse per un optimuss o cose del genere.
    io speravo in un Vu+ Turbo - Il sintonizzatore USB DVB-T2 / C ma vedo dal sito che non è ancora disponibile
     
    Last edited: Feb 10, 2015
  5. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    I comandi da dare dentro putty sono i seguenti:
    appena il box è partito con connesso il dispositivo DVB USB
    Code:
    dmesg
    
    e
    Code:
    lsmod
    
    e
    Code:
    lsusb
    
     
  6. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    ok e una volta fatto tutto come lo faccio diventare un file da poterti inviare.
    se può servire il decoder è un VU+ Solo2
     
    Last edited: Feb 11, 2015
  7. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    Evidenzi il testo e poi lo incolli qui.
     
  8. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    login as: root
    root@192.168.0.101's password:
    root@vusolo2:~# dmesg
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0x10406900 (irq = 65, base_baud = 5062500) is a 16550A
    console [ttyS0] enabled
    bootconsole [early0] disabled
    serial8250.0: ttyS1 at MMIO 0x10406940 (irq = 66, base_baud = 5062500) is a 16550A
    serial8250.0: ttyS2 at MMIO 0x10406980 (irq = 67, base_baud = 5062500) is a 16550A
    loop: module loaded
    ahci strict-ahci.0: can't get clock
    __clk_enable: sata [1]
    bcm40nm_pm_sata_enable 00
    ahci strict-ahci.0: SSS flag set, parallel bus scan disabled
    ahci strict-ahci.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl platform mode
    ahci strict-ahci.0: flags: ncq sntf stag clo slum part
    scsi0 : ahci_platform
    scsi1 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 41
    ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 41
    brcmstb_nand: NAND controller driver is loaded
    __clk_enable: network [1]
    __clk_enable: enet [1]
    bcm40nm_pm_genet_enable 00
    Found PHY at Address 3
    bcmgenet: configuring instance #0 for external RGMII
    __clk_disable: enet [0]
    bcm40nm_pm_genet_disable 00
    __clk_disable: network [0]
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ata1: SATA link down (SStatus 0 SControl 300)
    __clk_enable: usb [1]
    bcm40nm_pm_usb_enable 00
    ehci-brcm ehci-brcm.0: Broadcom STB EHCI
    ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
    ehci-brcm ehci-brcm.0: irq 69, io mem 0x10480300
    ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    ehci-brcm ehci-brcm.1: Broadcom STB EHCI
    ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
    ehci-brcm ehci-brcm.1: irq 70, io mem 0x10480500
    ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    ehci-brcm ehci-brcm.2: Broadcom STB EHCI
    ehci-brcm ehci-brcm.2: new USB bus registered, assigned bus number 3
    ehci-brcm ehci-brcm.2: irq 74, io mem 0x10490300
    ehci-brcm ehci-brcm.2: USB 0.0 started, EHCI 1.00
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 1 port detected
    ehci-brcm ehci-brcm.3: Broadcom STB EHCI
    ehci-brcm ehci-brcm.3: new USB bus registered, assigned bus number 4
    ehci-brcm ehci-brcm.3: irq 75, io mem 0x10490500
    ehci-brcm ehci-brcm.3: USB 0.0 started, EHCI 1.00
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 1 port detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci-brcm ohci-brcm.0: Broadcom STB OHCI
    ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 5
    ohci-brcm ohci-brcm.0: irq 71, io mem 0x10480400
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 1 port detected
    ohci-brcm ohci-brcm.1: Broadcom STB OHCI
    ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
    ohci-brcm ohci-brcm.1: irq 72, io mem 0x10480600
    ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata2.00: ATA-8: Hitachi HTS545016B9A300, PBBOCA0G, max UDMA/100
    ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 1 port detected
    ohci-brcm ohci-brcm.2: Broadcom STB OHCI
    ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
    ohci-brcm ohci-brcm.2: irq 76, io mem 0x10490400
    ata2.00: configured for UDMA/100
    scsi 1:0:0:0: Direct-Access ATA Hitachi HTS54501 PBBO PQ: 0 ANSI: 5
    sd 1:0:0:0: Attached scsi generic sg0 type 0
    sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
    sd 1:0:0:0: [sda] Write Protect is off
    sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1
    sd 1:0:0:0: [sda] Attached SCSI disk
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 1 port detected
    ohci-brcm ohci-brcm.3: Broadcom STB OHCI
    ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
    ohci-brcm ohci-brcm.3: irq 77, io mem 0x10490600
    hub 8-0:1.0: USB hub found
    hub 8-0:1.0: 1 port detected
    usbcore: registered new interface driver usb-storage
    mousedev: PS/2 mouse device common for all mice
    i2c /dev entries driver
    Success! Registering the characther device success with 0
    blackhole initialised
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    sdhci-pltfm: SDHCI platform and OF driver helper
    hidraw: raw HID events driver (C) Jiri Kosina
    usb 1-1: new high-speed USB device number 2 using ehci-brcm
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    TCP: cubic registered
    NET: Registered protocol family 17
    Key type dns_resolver registered
    PM: CP0 COUNT/COMPARE frequency does not depend on divisor
    EBI CS0: setting up NAND flash (primary)
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
    NAND device: 256MiB, SLC, page size: 2048, OOB size: 64
    brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
    Bad block table found at page 131008, version 0x01
    Bad block table found at page 130944, version 0x01
    nand_read_bbt: bad block at 0x0000006e0000
    nand_read_bbt: bad block at 0x000002500000
    nand_read_bbt: bad block at 0x0000025e0000
    nand_read_bbt: bad block at 0x000006200000
    nand_read_bbt: bad block at 0x000006fc0000
    nand_read_bbt: bad block at 0x000009ae0000
    nand_read_bbt: bad block at 0x00000a100000
    nand_read_bbt: bad block at 0x00000c4a0000
    nand_read_bbt: bad block at 0x00000fd60000
    Creating 4 MTD partitions on "brcmnand.0":
    0x000001f00000-0x000010000000 : "rootfs"
    0x000001f00000-0x000010000000 : "rootfs(redundant)"
    0x000000200000-0x000000900000 : "kernel"
    0x000000900000-0x000000a00000 : "mac"
    UBI: attaching mtd0 to ubi0
    random: nonblocking pool is initialized
    UBI: scanning is finished
    UBI: attached mtd0 (name "rootfs", size 225 MiB) to ubi0
    UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
    UBI: good PEBs: 1788, bad PEBs: 12, corrupted PEBs: 0
    UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
    UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1813821734
    UBI: available PEBs: 0, total reserved PEBs: 1788, PEBs reserved for bad PEB handling: 28
    UBI: background thread "ubi_bgt0d" started, PID 53
    ALSA device list:
    No soundcards found.
    UBIFS: parse sync
    UBIFS: background thread "ubifs_bgt0_0" started, PID 56
    UBIFS: recovery needed
    UBIFS: recovery completed
    UBIFS: mounted UBI device 0, volume 0, name "rootfs"
    UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
    UBIFS: FS size: 221573120 bytes (211 MiB, 1745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
    UBIFS: reserved for root: 0 bytes (0 KiB)
    UBIFS: media format: w4/r0 (latest is w4/r0), UUID ABEB7A6F-B070-4EA1-9CB8-4DFAD6F00F9A, small LPT model
    VFS: Mounted root (ubifs filesystem) on device 0:12.
    devtmpfs: mounted
    Freeing unused kernel memory: 208K (8074c000 - 80780000)
    NET: Registered protocol family 10
    procmk_init
    dvb_bcm7356: module license 'Proprietary' taints kernel.
    Disabling lock debugging due to kernel taint
    DVB: registering new adapter (vusolo2)
    bcm7356: hotplug_callback():
    Hotplug - status.connected 1:0:0
    bcm7356: hotplug_callback():
    Hotplug - connecting HDMI to display 0xe
    [GP]:brcm_pwm_init
    bcm7356: hotplug_callback():
    Hotplug - status.connected 1:1:0
    brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
    [MPVR]: >> misc_pvr_init
    [VID]: 6bcm7335_video_init
    [AUD]: 6bcm7335_audio_init
    BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (BCM7346 FE)...
    BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (BCM7346 FE)...
    BKNI_P_GetTrackAllocEntry_resize: resizing from 5376->8704
    BKNI_Malloc(linuxkernel) top users:
    blocks, bytes, filename:line
    1024, 176128, portinginterface/hsm/src/common/bhsm.c:500
    684, 157560, BSEAV/lib/utils/balloc.c:31
    385, 24640, magnum/commonutils/mrc/src/bmrc_monitor.c:666
    input: dreambox advanced remote control (native) as /devices/virtual/input/input0
    [LCD]: registered
    0:0
    [CI]: registered ci0
    [DFP]: registered dbox fp
    [DFP]: Scart 9597 is found 4
    [SC]: registered sci0
    [SC]: registered sci1
    system_time_set wakeup mode get
    system_time_set wakeup mode get 0xc4
    fpga update driver loaded
    udevd (119): /proc/119/oom_adj is deprecated, please use /proc/119/oom_score_adj instead.
    [VID]: VIDEO_SET_STREAMTYPE 0
    [VID]: VIDEO_SELECT_SOURCE 1 0
    [VID]: VIDEO_PLAY 1 2 0
    [VID]: VIDEO_CONTINUE 1 1
    [VID]: VIDEO_CLEAR_BUFFER 1 1 0
    EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
    EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (244)
    EXT4-fs (sda1): recovery complete
    EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    [VID]: VIDEO_STOP 0 1
    [VID]: VIDEO_SELECT_SOURCE 0 0
    __clk_enable: network [1]
    __clk_enable: enet [1]
    bcm40nm_pm_genet_enable 00
    IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    bcmgenet bcmgenet.0 eth0: link up, 100 Mbps, full duplex
    IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    svc: failed to register lockdv1 RPC service (errno 124).
    [VID]: VIDEO_SET_STREAMTYPE 0
    [VID]: VIDEO_SELECT_SOURCE 1 0
    [VID]: VIDEO_PLAY 1 2 0
    [VID]: VIDEO_CONTINUE 1 1
    [VID]: VIDEO_CLEAR_BUFFER 1 1 0
    [VID]: VIDEO_STOP 0 1
    [VID]: VIDEO_SELECT_SOURCE 0 0
    [LCD]: unknown cmd 0x1015
    [CI]: CI interface initialised
    UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
    [AUD]: AUDIO_SET_MUTE 0
    [AUD]: AUDIO_SET_MIXER -862102048
    [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
    [AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
    [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    [AUD]: AUDIO_SET_MIXER -862102048
    [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
    [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
    root@vusolo2:~# lsmod
    Module Size Used by Tainted: P
    ext2 56975 0
    fpga_directc 493 0
    brcmfb 1254 4
    dvb_bcm7356 8401873 10 brcmfb
    procmk 1668 1 dvb_bcm7356
    ipv6 326329 12 [permanent]
    root@vusolo2:~# lsusb
    Bus 001 Device 002: ID 0572:0320
    Bus 001 Device 001: ID 1d6b:0002
    Bus 002 Device 001: ID 1d6b:0002
    Bus 003 Device 001: ID 1d6b:0002
    Bus 004 Device 001: ID 1d6b:0002
    Bus 005 Device 001: ID 1d6b:0001
    Bus 006 Device 001: ID 1d6b:0001
    Bus 007 Device 001: ID 1d6b:0001
    Bus 008 Device 001: ID 1d6b:0001
    root@vusolo2:~#
     
  9. Eragon

    Eragon Moderator

    Messages:
    3,041
    Non mi pare che nel log ci sia traccia del tuner USB... era collegato in quel momento?
     
  10. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    Sì. Gli USB ID 0572:0320 lo confermano come una veloce ricerca su Google ha tirato fuori il driver incriminato ... DVBSky .....
     
    Eragon likes this.
  11. Eragon

    Eragon Moderator

    Messages:
    3,041
    Quindi e' questo:
    DVBSky T330 DVB-T2/T/C USB Stick

    T330.jpg
    Code:
    http://www.dvbsky.net/Products_T330.html
     
  12. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    Molto probabile.
     
  13. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    l'estetica diciamo cosi è quella della foto di eragon, è previsto qualche aggiornamento o altro :)
     
  14. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    Devo vedere se il driver è disponibile tra quelli non inclusi nella BH.
     
  15. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    ok grazie
     
  16. angelofsky1980

    angelofsky1980 BlackHole Driver Specialist

    Messages:
    16,854
    Da quanto ho potuto vedere, il driver DVBSky non è ancora incluso nel set di driver che la BH utilizza.
    Verifico se per caso è incluso nel set da cui derivano i driver usati nelle immagini BH.... ok almeno nelle ultime versioni di driver (non ancora implementati in BH) il driver esiste ... al prossimo aggiornamento dei driver DVB USB, il tuo device dovrebbe quanto meno essere riconosciuto e se siamo fortunati, funzionerà anche.
    Tempi di implementazione attualmente non noti.
     
  17. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    grazie di tutto
     
  18. kapoaug

    kapoaug Vu+ Newbie

    Messages:
    23
    echo qui il driver per questa chiavetta.. provalo e facci sappere.. credo che lo devi installare manualmente.. ciao
     

    Attached Files:

  19. wyzard

    wyzard Vu+ Newbie

    Messages:
    20
    grazie nell'attesa preso un duo2 e ora sono in attesa che il server torni funzionante per gli ipk appena mi torna la provo anzora grazie
     
  20. kapoaug

    kapoaug Vu+ Newbie

    Messages:
    23
    che centra il server.. questo file lo metti con DCC nella cartella tmp e poi tasto verde + tasto giallo, installazione manuale ipk.. e faccile..
     

Share This Page