Autor Thema: TBS5925 einrichten  (Gelesen 7877 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
TBS5925 einrichten
« am: 21.März.2015, 09:09:33 »
Hallo
Ich brauche mal Hilfe
Habe hier ein TBS5925 und moechte es an meinem Laptop zum
Satschuesseleinrichten benutzen.
Bekomme das Ding aber nicht zum laufen.
Kann jemand mir mal dabei helfen ?
]$ uname -a
Linux localhost.localdomain 3.18.1-pclos1 #1 SMP Wed Dec 17 03:45:39 CST 2014 i686 i686 i386 GNU/Linux
FullMonty 2014 12 32 bit
---------------
Bus 002 Device 005: ID 734c:5925 TBS Technologies China
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x734c TBS Technologies China
  idProduct          0x5925
  bcdDevice            0.01
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          171
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           6
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       2
      bNumEndpoints           6
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       3
      bNumEndpoints           6
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)
-------------------
Wenn weitere Angaben notwendig sind , bitte posten

derpurzel
« Letzte Änderung: 21.März.2015, 13:03:29 von Leiche »

Offline Joe

  • Mit PCLinuxOS holt ihr mehr aus eurem Computer/Lappi raus!
  • Beiträge: 900
Re: TBS5925 einrichten
« Antwort #1 am: 21.März.2015, 10:05:55 »
Installier mal Kaffeine und metv und dann schreib mal zurück ;)
« Letzte Änderung: 21.März.2015, 10:09:17 von Joe »

Offline pinguin4488

  • Administrator
  • *
  • Beiträge: 980
  • PCLinuxOS....weil es einfach besser ist.
Re: TBS5925 einrichten
« Antwort #2 am: 21.März.2015, 10:16:13 »
hast du für den TBS5962 ein Linux Treiber installiert?
   

Nur der Fragenden Menschen kann geholfen werden.

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #3 am: 21.März.2015, 11:01:42 »
@Joe
>>Installier mal Kaffeine und metv
Ist automattisch inststalliert bei FullMonty

Scherzmodus an
>>und dann schreib mal zurück
zurück
Scherzmodus aus

Was soll ich schreiben ?

@pinguin4488
>>hast du für den TBS5962 ein Linux Treiber installiert?
Ich habe hier ein TBS5925
Linux Treiber installiert nach Anleitung von TBS versucht.
Habe aber bestimmt einen Fehler gemacht.

TBS5925 readme
I.0 install the TBS 5925 USB firmware file "dvb-usb-tbsqbox-id5925.fw" /lib/firmware/:

mv dvb-usb-tbsqbox-id5925.fw /lib/firmware/

II. refer to README_TBS5921 for further installation instructions
README_TBS5921
README file for TurboSight TBS 5921 DVB-S/S2 USB box Linux drivers

NOTE: this document assumes that all prerequisite packages like kerner headers
and build tools are already installed in your Linux system.

Most of the steps require root access to and basic knowledge of Linux system.

Create directory, for example /root/tbs and copy the following file to it:

- linux-tbs-drivers.tar.bz2 (S2API Linix driver for TurboSight TBS 5921)
- dvb-usb-tbsqbox-id5921.fw (QBOXS3 USB firmware file)
- szap-s2.tar.bz2 (szap tool compatible with new DVB-S2 aware S2 API for Linux)
- scan-s2.tar.bz2 (scan tool compatible with new DVB-S2 aware S2 API for Linux)
- astra_szap-s2.conf (example configuration file for szap-s2)
- astra_scan-s2.conf (example configuration file for scan-s2)
- v4l-cx23885-avcore-01.fw (CX23885 AV core firmware, not needed for USB box)

I.0 install the QBOXS3 USB firmware file "dvb-usb-tbsqbox-id5921.fw" /lib/firmware/:

mv dvb-usb-tbsqbox-id5921.fw /lib/firmware/

I.1 extract linux-tbs-drivers.tar.bz2 archive:

# tar xjvf linux-tbs-drivers.tar.bz2

I.2 go to driver package directory:

# cd linux-tbs-drivers

I.3 depending on your kernel version and if the kernel is x86 or
x86_64 (check output of 'uname -a') do:

- for x86 kernel 3.x (x86 32 bit installations of kernel 3.x):

# ./v4l/tbs-x86_r3.sh

- for x86 kernel 2.6.x (x86 32 bit installations of kernel 2.6.x):

# ./v4l/tbs-x86.sh

- for any x86_64 kernel (x86 64 bit installations of Linux):

# ./v4l/tbs-x86_64.sh

I.4 build and install the driver:

# make && make install

I.5 reboot in order to load the newly installed driver:

# shutdown -r now

I.6 after reboot check that the newly installed driver is loaded correctly:

# dmesg | grep QBOXS3

if everything is OK, the output from the above command should be similar to:

dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in cold state, will try to load a firmware
dvb-usb: found a 'TBS QBOXS3 DVBS2 USB2.0' in warm state.
DVB: registering new adapter (TBS QBOXS3 DVBS2 USB2.0)
QBOXS3: TBS5921FE attached.
dvb-usb: TBS QBOXS3 DVBS2 USB2.0 successfully initialized and connected.

II. some basic instructions how to test locking to transponder with "szap-s2":

II.1 extract "szap-s2.tar.bz2" archive:

# tar xjvf szap-s2.tar.bz2

II.2 go to szap-s2 source code directory:

# cd szap-s2

II.3 build szap-s2:

# make

II.4 szap-s2 uses configuration files (see configuration file "astra_szap-s2.conf"
for example) - they are simple text files and each line of them contains information
about a channel, for example:

BBC:11597:v:0:22000:163:92:10050

this means:

- channel name is BBC, you can choose whatever you want for channel name, it's just
a text string

- channel frequency is 11597 MHz

- transponder polarization is V(ertical)

- 0: use first LNB (if you have only one LNB, it's always 0, if you have DiSEqC switch
and several LNBs connected to that switch it could be number greater than 0 and is showing
which LNB to use, i.e. to which DiSEqC switch port desired LNB is connected)

- 22000: symbol rate

- 163: Video PID (VPID)

- 92: Audio PID

- 10050: Service ID (SID)

the example is for "BBC World" channel on Astra 19.2E satellite.
you can find all those numbers for example here:

http://www.lyngsat.com/astra19.html

II.5 write your szap-s2 configuration files (or create one using S2API compatible
version of the "scan" tool)

II.6 use szap-s2 examples:

- to lock to DVB-S transponder: ./szap-s2 -c astra_szap-s2.conf -p -r -S 0 "BBC"

- to lock to DVB-S2: ./szap-s2 -c sample.conf -p -r -S 1 -M 5 -C 23 "CHAN_NAME"

where "-S 1" is DVB-S2, "-M 5" is 8PSK modulation, "-C 23" is FEC 2/3

III. some basic instructions how to scan transponder with "scan-s2":

III.1 extract "scan-s2.tar.bz2" archive:

# tar xjvf scan-s2.tar.bz2

III.2 go to scan-s2 source code directory:

# cd scan-s2

III.3 build scan-s2:

# make

III.4 scan-s2 uses configuration files (see configuration file "astra_scan-s2.conf"
for example) - they are simple text files and each line of them contains information
about a transponder, for example:

S1 11778000 V 27500000 3/4 35 QPSK
S2 11362000 H 22000000 2/3 35 8PSK

where:

- "S1" or "S2" indicates the delivery system, i.e. either DVB-S or DVB-S2
- second parameter is the frequency, in our example respectively 11778000 kHz or 11362000 kHz
- "V" or "H" indicates that the polarization: V(ertical) or H(orizontal)
- 5th parameter is the FEC value, in our example respectively 3/4 or 2/3
- the next parameter is the Roll-off factor, "35" in our example
- and the last parameter is the modulation, in our example respectively QPSK or 8PSK

DVB-S supports only one Roll-off factor (0.35) and only one modulation (QPSK) and so
for DVB-S transponders Roll-off factor is always 35 and modulation is always QPSK in
the configuration file.

DVB-S2 supports several modulation like QPSK and 8PSK and 3 Roll-off factors: 0.20, 0.25, 0.35
(respectively 20, 25, 35 in the configuration file). TBS 5921 should be able to work even if
AUTO is specified for Roll-off factor, but that will result in slower lock. it's always
recommended to use the correct Roll-off value if you know it.

III.5 write your scan-s2 configuration files

III.6 use scan-s2 to scan a tranposnder

IV. some general notes about using TBS 5921 USB box in Linux:

IV.1 TBS 5921 is single DVB-S/S2 tuner and there is no need to specify which frontend to use:

- use frontend 0:
# szap-s2 -a 0 -c astra_szap-s2.conf -p -r -S 0 "BBC"
# scan-s2 -a 0 astra_scan-s2.conf

IV.2 TBS 5921 frontend is initialized only when it's necessary - this is done for maximum
performance. after power-on of the computer, frontend is in uninitialize state and that's
why after power-on of the computer first lock will be a little slower than ussual, all
subsequent locks are faster. after the frontend is initialized just restarting the
computer should keep it in initialize state.

IV. TBS 5921 frontend driver provides several options:

- reporting signal in dBm instead of percents
- reporting SNR in EsNo instead of percents

for more information you can check the output of 'modinfo tbsfe.ko'

for enable/disable these options you need to create file called for example "tbsfe.conf"
in "/etc/modprobe.d" directory with content similar to:

# cat /etc/modprobe.d/tbsfe.conf
options tbsfe dbm=1
options tbsfe esno=1

respectively "1" means enabled and "0" means disabled. please, note that the new value will
take effect after reload of the kernel module - either with using 'rmmod' and 'modprobe' or
after restart of the computer.
.....................................
Werde nicht schlau aus den readmes
derpurzel
« Letzte Änderung: 21.März.2015, 13:05:37 von Leiche »

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #4 am: 21.März.2015, 13:08:12 »
Hi purzel,

Du schreibst Du hast es versucht zu installieren nach Anleitung und gleichzeitig schreibst Du, Du wirst nicht schlau daraus. Dann mal mit eigenen Worten was Du versucht hast zu installieren um hier den Knoten zum platzen zu kriegen :)

Regards
Daniel

Edit: Ist es das http://www.tbs-technology.de/index.php?id=48 ?
« Letzte Änderung: 21.März.2015, 13:13:42 von Leiche »

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #5 am: 21.März.2015, 13:45:31 »
@Leiche
>>Handelt es sich darum
JA
Na dann werden ich mal berichten
ein verzeichnis tbs im Home_verzeichnis erstellt .
in dieses verzeichnis gewechselt
mit wget den neuesten Linuxtreiber von der TBS Seite geholt
ausgepackt
die readme Datei vom TBS 5925 gelesen (2 post zurueck kann diese gelesen werden )
Verzeichnis /tbs/erstellt (konsole als root)
mit mc (konsole als root) die dateien ,wie in readme tbs5921 beschrieben kopiert,entpackt,installiert, aber als tbs5925 modifiziert.
auch die Datei  in /lib/firmware kopiert (aber als tbs5925 modifiziert)
So nun verstehe ich die Anleitung nicht mehr .
nach einem reboot sollen die Kernelmodule automatisch geladen werden
aber nichts ist
[ich@localhost ~]$ dmesg | grep QBOXS3
[ich@localhost ~]$ dmesg | grep 5925
[ich@localhost ~]$ dmesg | grep TBS
[ich@localhost ~]$
das verstehe ich noch ,denn wie sollen  denn die treiber in das richtige
Kernelverzeichnis kopiert werden ,wenn ich ein beliebiges Verzeichnis erstellen kann  ?
derpurzel

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #6 am: 21.März.2015, 14:02:08 »
Die ./v4l/tbs-x86_r3.sh auch ausgführt?

Zitat
- for x86 kernel 3.x (x86 32 bit installations of kernel 3.x):

# ./v4l/tbs-x86_r3.sh

Die .sh Datei wird bestimmt der make Datei die richtige Installationsorte verraten...
Bei make && make install wurde keine Fehlermeldungen ausgegeben?
Bitte in Tags (Schaltfläche mit # ) angeben...

Ansonsten poste mal den Link zu den Treibers

Regards
Daniel

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #7 am: 22.März.2015, 01:48:17 »
Hi Leiche
>>Die ./v4l/tbs-x86_r3.sh auch ausgführt?
Ja
>>Bei make && make install wurde keine Fehlermeldungen ausgegeben?
nein
Hier mal den Inhalt von tbs-x86_r3.sh
#!/bin/bash

cp ./v4l/tbs6980fe_driver.o.x86_r3 ./v4l/tbs6980fe_driver.o

cp ./v4l/tbs6981fe_driver.o.x86_r3 ./v4l/tbs6981fe_driver.o

cp ./v4l/tbs6921fe_driver.o.x86_r3 ./v4l/tbs6921fe_driver.o

cp ./v4l/tbs8921ctrl.o.x86_r3 ./v4l/tbs8921ctrl.o
cp ./v4l/tbs8921fe_driver.o.x86_r3 ./v4l/tbs8921fe_driver.o

cp ./v4l/tbs5921ctrl.o.x86_r3 ./v4l/tbs5921ctrl.o
cp ./v4l/tbs5921fe_driver.o.x86_r3 ./v4l/tbs5921fe_driver.o

cp ./v4l/tbsctrl.o.x86_r3 ./v4l/tbsctrl.o

cp ./v4l/tbs6925ctrl_driver.o.x86_r3 ./v4l/tbs6925ctrl_driver.o
cp ./v4l/tbs6925cctrl_driver.o.x86_r3 ./v4l/tbs6925cctrl_driver.o

cp ./v4l/tbs62x0fe_driver.o.x86_r3 ./v4l/tbs62x0fe_driver.o

cp ./v4l/tbs6984fe_driver.o.x86_r3 ./v4l/tbs6984fe_driver.o

cp ./v4l/tbs6992_driver.o.x86_r3 ./v4l/tbs6992_driver.o

cp ./v4l/tbs6922fe_driver.o.x86_r3 ./v4l/tbs6922fe_driver.o

cp ./v4l/tbs6928fe_driver.o.x86_r3 ./v4l/tbs6928fe_driver.o
cp ./v4l/tbs6928se_driver.o.x86_r3 ./v4l/tbs6928se_driver.o

cp ./v4l/tbs8922ctrl.o.x86_r3 ./v4l/tbs8922ctrl.o
cp ./v4l/tbs8922fe_driver.o.x86_r3 ./v4l/tbs8922fe_driver.o

cp ./v4l/tbs5922ctrl.o.x86_r3 ./v4l/tbs5922ctrl.o
cp ./v4l/tbs5922fe_driver.o.x86_r3 ./v4l/tbs5922fe_driver.o
cp ./v4l/tbs5922se_driver.o.x86_r3 ./v4l/tbs5922se_driver.o

cp ./v4l/tbs5880ctrl.o.x86_r3 ./v4l/tbs5880ctrl.o
cp ./v4l/tbs5880fe_driver.o.x86_r3 ./v4l/tbs5880fe_driver.o

cp ./v4l/tbs6982fe_driver.o.x86_r3 ./v4l/tbs6982fe_driver.o
cp ./v4l/tbs6991fe_driver.o.x86_r3 ./v4l/tbs6991fe_driver.o

cp ./v4l/tbs5280fe_driver.o.x86_r3 ./v4l/tbs5280fe_driver.o

cp ./v4l/tbs5925ctrl.o.x86_r3 ./v4l/tbs5925ctrl.o
cp ./v4l/tbs5925fe_ctrl_driver.o.x86_r3 ./v4l/tbs5925fe_ctrl_driver.o

cp ./v4l/tbs6618fe_driver.o.x86_r3 ./v4l/tbs6618fe_driver.o

cp ./v4l/tbs6680fe_driver.o.x86_r3 ./v4l/tbs6680fe_driver.o

cp ./v4l/tbs5680ctrl.o.x86_r3 ./v4l/tbs5680ctrl.o
cp ./v4l/tbs5680fe_driver.o.x86_r3 ./v4l/tbs5680fe_driver.o

cp ./v4l/tbsdvbcctrl.o.x86_r3 ./v4l/tbsdvbcctrl.o
cp ./v4l/tbsdvbcfe_driver.o.x86_r3 ./v4l/tbsdvbcfe_driver.o

cp ./v4l/tbs6985fe_driver.o.x86_r3 ./v4l/tbs6985fe_driver.o

cp ./v4l/tbs6926_driver.o.x86_r3 ./v4l/tbs6926_driver.o
cp ./v4l/tbs6926ctrl_driver.o.x86_r3 ./v4l/tbs6926ctrl_driver.o

cp ./v4l/tbs6923fe_driver.o.x86_r3 ./v4l/tbs6923fe_driver.o

cp ./v4l/tbs6982se_driver.o.x86_r3 ./v4l/tbs6982se_driver.o

cp ./v4l/tbs5881ctrl.o.x86_r3 ./v4l/tbs5881ctrl.o
cp ./v4l/tbs5881fe_driver.o.x86_r3 ./v4l/tbs5881fe_driver.o
cp ./v4l/tbs5220ctrl.o.x86_r3 ./v4l/tbs5220ctrl.o
cp ./v4l/tbs5220fe_driver.o.x86_r3 ./v4l/tbs5220fe_driver.o
cp ./v4l/tbs62x1fe_driver.o.x86_r3 ./v4l/tbs62x1fe_driver.o
cp ./v4l/tbs6290fe_driver.o.x86_r3 ./v4l/tbs6290fe_driver.o

cp ./v4l/tbs6985se_driver.o.x86_r3 ./v4l/tbs6985se_driver.o
cp ./v4l/tbs6991se_driver.o.x86_r3 ./v4l/tbs6991se_driver.o

cp ./v4l/tbs5281fe_driver.o.x86_r3 ./v4l/tbs5281fe_driver.o
cp ./v4l/tbs5990fe_driver.o.x86_r3 ./v4l/tbs5990fe_driver.o
cp ./v4l/tbs5926fe_driver.o.x86_r3 ./v4l/tbs5926fe_driver.o

cp ./v4l/tbs6983fe_driver.o.x86_r3 ./v4l/tbs6983fe_driver.o

cp ./v4l/tbsdvbctl.o.x86_r3 ./v4l/tbsdvbctl.o
cp ./v4l/tbs6904fe_driver.o.x86_r3 ./v4l/tbs6904fe_driver.o
cp ./v4l/tbs6908fe_driver.o.x86_r3 ./v4l/tbs6908fe_driver.o
cp ./v4l/tbs6205fe_driver.o.x86_r3 ./v4l/tbs6205fe_driver.o
cp ./v4l/tbs6814fe_driver.o.x86_r3 ./v4l/tbs6814fe_driver.o
cp ./v4l/tbs6704fe_driver.o.x86_r3 ./v4l/tbs6704fe_driver.o

echo "TBS drivers configured for x86_r3 platform."

Ich versuche noch weiteres zu finden
derpurzel

EDIT: das ist jetzt das letzte Mal das ich größere Ausgaben in Tags (Symbol #) setze, noch einmal mach ich das nicht und werde in Zukunft auch nicht mehr drauf Antworten, da mir das zu wider ist, solche Post zu lesen!!!




« Letzte Änderung: 22.März.2015, 09:53:13 von Leiche »

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #8 am: 22.März.2015, 04:42:19 »
@Joe
ich habe gerade festgestellt , wenn man in Synaptic metv eingiebt wird tvtime angezeigt. dieses ist in FullMonty schon installiert.
wenn man in Synaptic me-tv eingiebt wird me-tv angezeigt. Dieses kann noch
installiert werden.
derpurzel

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #9 am: 22.März.2015, 10:00:20 »
Eines vorerst, siehe mein EDIT zwei Post vorher!!!
Siehe dazu auch rogaven's angegebenen Link!

So nun, wenn keine Fehlermeldungen ausgegeben wurde, kannst Du auch mal versuchen, wie folgt vor zu gehen:
Bitte wie gehabt die Quelldateien (Archiv) entpacken.
Schritt eins die ./v4l/tbs-x86_r3.sh Datei ausführen.
Schritt zwei  make
Schritt drei make install
Schritt vier depmod
Schritt fünf reboot

Nun sollten die Treiber installiert sein...

Regards
Daniel
« Letzte Änderung: 28.Dezember.2015, 21:07:52 von Joe »

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #10 am: 22.März.2015, 11:43:07 »
Hallo Leiche nochmal
habe ich wohl wieder falsch gemacht.
ich gelobe besserung

lsmod
Module                  Size  Used by
dvb_usb_tbs5925         6888  0
dvb_usb                12816  1 dvb_usb_tbs5925
dvb_core               66118  1 dvb_usb
rc_core                12624  1 dvb_usb
.
.
.
usbcore               124520  10 dvb_usb_tbs5925,dvb_usb,snd_usb_audio,snd_usbmidi_lib,uvcvideo,ehci_pci,uhci_hcd,ohci_hcd,ehci_hcd,usbhid
usb_common               964  1 usbcore
.
.
.
.
root@localhost ich]# dmesg | grep tbs
[  366.677397] usbcore: registered new interface driver tbs5925
[root@localhost ich]#  dmesg | grep 5925
[  366.651420] usb 2-1.2: New USB device found, idVendor=734c, idProduct=5925
[  366.677397] usbcore: registered new interface driver tbs5925
[root@localhost ich]#  dmesg | grep QBOXS3
[root@localhost ich]#



die module erscheinen ,wenn man eine eingeschaltete tbs5925 in die usb-buchse gesteckt hat.aber ein bild bekomme ich mit keinem Programm. Irgenwas mache ich noch falsch

ist das jetzt so richtig ? ich kann aber die kleine schrift kaum lesen
wie macht man die groesser ?
der purzel
« Letzte Änderung: 22.März.2015, 12:16:59 von Leiche »

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #11 am: 22.März.2015, 12:04:32 »
Hallo Leiche nochmal
habe ich wohl wieder falsch gemacht.
ich gelobe besserung
[code ]

lsmod
Module                  Size  Used by
dvb_usb_tbs5925         6888  0
dvb_usb                12816  1 dvb_usb_tbs5925
dvb_core               66118  1 dvb_usb
rc_core                12624  1 dvb_usb
.
.
.
usbcore               124520  10 dvb_usb_tbs5925,dvb_usb,snd_usb_audio,snd_usbmidi_lib,uvcvideo,ehci_pci,uhci_hcd,ohci_hcd,ehci_hcd,usbhid
usb_common               964  1 usbcore
.
.
.
.
root@localhost ich]# dmesg | grep tbs
[  366.677397] usbcore: registered new interface driver tbs5925
[root@localhost ich]#  dmesg | grep 5925
[  366.651420] usb 2-1.2: New USB device found, idVendor=734c, idProduct=5925
[  366.677397] usbcore: registered new interface driver tbs5925
[root@localhost ich]#  dmesg | grep QBOXS3
[root@localhost ich]#



die module erscheinen ,wenn man eine eingeschaltete tbs5925 in die usb-buchse gesteckt hat.aber ein bild bekomme ich mit keinem Programm. Irgenwas mache ich noch falsch

ist das jetzt so richtig ? ich kann aber die kleine schrift kaum lesen
wie macht man die groesser ?
der purzel

So ist das genau richtig, in erster Linie ist das über sichtlich und außerdem hast Du es ja eh schon gelesen.

Jetzt must du den sendersuchlauf starten, dazu kannst Du auch wscan ( in der repo enthalten) nutzen.  Muss den Rechner starten um genaueres zu finden

Gesendet von nvidia shield

EDIT:
So nun denn hier mal wie man eine Channel conf mit wscan erstellen kann, die Xine lesen kann...
w_scan -f s -s S19E2 > $HOME/.xine/channels.confDen ganzen Beitrag gibt es nur noch hier, da man im Mutterforum zu schnell Threads löscht...

Alternative zu wscan

Regards
Daniel
« Letzte Änderung: 22.März.2015, 12:14:58 von Leiche »

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #12 am: 22.März.2015, 12:15:52 »
Ich sehe gerade fast richtig..., habe es dann noch einmal korrigiert :)

EDIT: um die Schriften allgemein größer zu bekommen, kannst Du die Tasten (Strg) und (+) nutzen...
« Letzte Änderung: 22.März.2015, 12:31:17 von Leiche »

Offline derpurzel

  • Beiträge: 87
  • PCLOS Forum!!
Re: TBS5925 einrichten
« Antwort #13 am: 22.März.2015, 12:52:40 »
Hallo Leiche
Ich nochmal
wscan giebt es nicht, w_scan schon.

Ich bekomme es einfach nicht gebacken
[root@localhost ich]# w_scan -sS105EX  -cPW -k -fs
w_scan version 20101204 (compiled for DVB API 5.1)
using settings for 105.X east AsiaSat 3S
frontend_type DVB-S, channellist 46
output format kaffeine channels.dvb
Info: using DVB adapter auto detection.
main:3023: FATAL: ***** NO USEABLE DVB CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.
[root@localhost ich]#

immer wieder Fehlermeldungen
der purzel

Offline Leiche

  • Global Moderator
  • *
  • Beiträge: 619
  • Gott weiß, ich bin kein Engel
    • Tipps und Tricks
Re: TBS5925 einrichten
« Antwort #14 am: 22.März.2015, 13:08:14 »
Welchen Satelliten wählst Du?
Ist das richtig east AsiaSat 3S

Die Module erscheinen ,wenn man eine eingeschaltete tbs5925 in die usb-buchse gesteckt ist, hast Du dieses auch noch einmal geprüft?

Ansonsten weiter vorgehen, wie in der Readme geschrieben steht, denn es könnte sein das w_scan die Karte nicht über USB erkennt...

Zitat
III. some basic instructions how to scan transponder with "scan-s2":

III.1 extract "scan-s2.tar.bz2" archive:

# tar xjvf scan-s2.tar.bz2

III.2 go to scan-s2 source code directory:

# cd scan-s2

III.3 build scan-s2:

# make

III.4 scan-s2 uses configuration files (see configuration file "astra_scan-s2.conf"
for example) - they are simple text files and each line of them contains information
about a transponder, for example:

S1 11778000 V 27500000 3/4 35 QPSK
S2 11362000 H 22000000 2/3 35 8PSK

where:

- "S1" or "S2" indicates the delivery system, i.e. either DVB-S or DVB-S2
- second parameter is the frequency, in our example respectively 11778000 kHz or 11362000 kHz
- "V" or "H" indicates that the polarization: V(ertical) or H(orizontal)
- 5th parameter is the FEC value, in our example respectively 3/4 or 2/3
- the next parameter is the Roll-off factor, "35" in our example
- and the last parameter is the modulation, in our example respectively QPSK or 8PSK

DVB-S supports only one Roll-off factor (0.35) and only one modulation (QPSK) and so
for DVB-S transponders Roll-off factor is always 35 and modulation is always QPSK in
the configuration file.

DVB-S2 supports several modulation like QPSK and 8PSK and 3 Roll-off factors: 0.20, 0.25, 0.35
(respectively 20, 25, 35 in the configuration file). TBS 5921 should be able to work even if
AUTO is specified for Roll-off factor, but that will result in slower lock. it's always
recommended to use the correct Roll-off value if you know it.

III.5 write your scan-s2 configuration files

III.6 use scan-s2 to scan a tranposnder

IV. some general notes about using TBS 5921 USB box in Linux:

IV.1 TBS 5921 is single DVB-S/S2 tuner and there is no need to specify which frontend to use:

- use frontend 0:
# szap-s2 -a 0 -c astra_szap-s2.conf -p -r -S 0 "BBC"
# scan-s2 -a 0 astra_scan-s2.conf

IV.2 TBS 5921 frontend is initialized only when it's necessary - this is done for maximum
performance. after power-on of the computer, frontend is in uninitialize state and that's
why after power-on of the computer first lock will be a little slower than ussual, all
subsequent locks are faster. after the frontend is initialized just restarting the
computer should keep it in initialize state.

IV. TBS 5921 frontend driver provides several options:

- reporting signal in dBm instead of percents
- reporting SNR in EsNo instead of percents

for more information you can check the output of 'modinfo tbsfe.ko'

for enable/disable these options you need to create file called for example "tbsfe.conf"
in "/etc/modprobe.d" directory with content similar to:

# cat /etc/modprobe.d/tbsfe.conf
options tbsfe dbm=1
options tbsfe esno=1

respectively "1" means enabled and "0" means disabled. please, note that the new value will
take effect after reload of the kernel module - either with using 'rmmod' and 'modprobe' or
after restart of the computer.

Das Problem ist, das ich nichts nachvollziehen kann wegen fehlender Hardware :(

Regards
Daniel

EDIT: laut dieser Post soll es gehen mit w_scan  ::) dort ist aber auch die Rede von szap

Zitat
II. some basic instructions how to test locking to transponder with "szap-s2":

II.1 extract "szap-s2.tar.bz2" archive:

# tar xjvf szap-s2.tar.bz2

II.2 go to szap-s2 source code directory:

# cd szap-s2

II.3 build szap-s2:

# make

II.4 szap-s2 uses configuration files (see configuration file "astra_szap-s2.conf"
for example) - they are simple text files and each line of them contains information
about a channel, for example:

BBC:11597:v:0:22000:163:92:10050

this means:

- channel name is BBC, you can choose whatever you want for channel name, it's just
a text string

- channel frequency is 11597 MHz

- transponder polarization is V(ertical)

- 0: use first LNB (if you have only one LNB, it's always 0, if you have DiSEqC switch
and several LNBs connected to that switch it could be number greater than 0 and is showing
which LNB to use, i.e. to which DiSEqC switch port desired LNB is connected)

- 22000: symbol rate

- 163: Video PID (VPID)

- 92: Audio PID

- 10050: Service ID (SID)

the example is for "BBC World" channel on Astra 19.2E satellite.
you can find all those numbers for example here:

http://www.lyngsat.com/astra19.html

II.5 write your szap-s2 configuration files (or create one using S2API compatible
version of the "scan" tool)

II.6 use szap-s2 examples:

- to lock to DVB-S transponder: ./szap-s2 -c astra_szap-s2.conf -p -r -S 0 "BBC"

- to lock to DVB-S2: ./szap-s2 -c sample.conf -p -r -S 1 -M 5 -C 23 "CHAN_NAME"

where "-S 1" is DVB-S2, "-M 5" is 8PSK modulation, "-C 23" is FEC 2/3

Müsstest Du dann auch erst erstellen...

EDIT II: einen weiteren Link der eventuell helfen könnte
http://www.tbsdtv.com/forum/viewtopic.php?f=77&t=8264
« Letzte Änderung: 22.März.2015, 13:32:08 von Leiche »