Reply to thread

Message

<blockquote data-quote="deeptho" data-source="post: 1119139" data-attributes="member: 215446">You could try to figure it out in multiple ways, such as lspci -vvv|less02:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card&nbsp; &nbsp; &nbsp; &nbsp; Subsystem: Device 6909:0010&nbsp; &nbsp; &nbsp; &nbsp; Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+&nbsp; &nbsp; &nbsp; &nbsp; Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast &gt;TAbort- &lt;TAbort- &lt;MAbort- &gt;SERR- &lt;PERR- INTx-&nbsp; &nbsp; &nbsp; &nbsp; Latency: 0&nbsp; &nbsp; &nbsp; &nbsp; Interrupt: pin A routed to IRQ 149&nbsp; &nbsp; &nbsp; &nbsp; IOMMU group: 13&nbsp; &nbsp; &nbsp; &nbsp; Region 0: Memory at df400000 (32-bit, non-prefetchable) [size=256K]&nbsp; &nbsp; &nbsp; &nbsp; Capabilities: &lt;access denied&gt;&nbsp; &nbsp; &nbsp; &nbsp; Kernel driver in use: TBSECP3 driver&nbsp; &nbsp; &nbsp; &nbsp; Kernel modules: tbsecp302:00.0 is the PCI address which is also shown somehwere in the frontend list of neumodvb (the long number in the &quot;cards&quot; column starts with it)The adapters are numbered sequentially, so if adapter0 is for the tbs6909x then adapter9 is for tbs6090.&nbsp; Using this information, you can guess a number.Normally you should also get a working result on tbs6909, but spectrum scan will probably not work and there maybe some crashes because the code is alpha. You can always restart and try again.One important thing:assuming you have a normal lnb attached and not a multiswitch, it is important to have a file /etc/modprobe.d/stid135.confwith contentoptions stid135 mode=1THis is the same as for the regular drivers. If the file is newly created you will need to reboot</blockquote>

[QUOTE="deeptho, post: 1119139, member: 215446"] You could try to figure it out in multiple ways, such as lspci -vvv|less 02:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card Subsystem: Device 6909:0010 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 Interrupt: pin A routed to IRQ 149 IOMMU group: 13 Region 0: Memory at df400000 (32-bit, non-prefetchable) [size=256K] Capabilities: <access denied> Kernel driver in use: TBSECP3 driver Kernel modules: tbsecp3 02:00.0 is the PCI address which is also shown somehwere in the frontend list of neumodvb (the long number in the "cards" column starts with it) The adapters are numbered sequentially, so if adapter0 is for the tbs6909x then adapter9 is for tbs6090. Using this information, you can guess a number. Normally you should also get a working result on tbs6909, but spectrum scan will probably not work and there may be some crashes because the code is alpha. You can always restart and try again. One important thing: assuming you have a normal lnb attached and not a multiswitch, it is important to have a file /etc/modprobe.d/stid135.conf with content options stid135 mode=1 THis is the same as for the regular drivers. If the file is newly created you will need to reboot [/QUOTE]

Verification