Tvheadend

https://linuxtv.org/wiki/index.php/TBS6922
just compare

domenic ciciarelli wrote:

This is the second motherboard
Only with windows works this card, Could it be the version of ubuntu?
Or the card has been damaged, but I have never used it before now

Not sure this applies with the driver you're using, but some TBS cards have issues with some motherboards. You may want to see if the driver has support for MSI interrupts.

I'm not 100% sure of the correct module here, but what does.

sudo modinfo saa716x

Output?

Mark Clarkstone wrote:

domenic ciciarelli wrote:

This is the second motherboard
Only with windows works this card, Could it be the version of ubuntu?
Or the card has been damaged, but I have never used it before now

Not sure this applies with the driver you're using, but some TBS cards have issues with some motherboards. You may want to see if the driver has support for MSI interrupts.

I'm not 100% sure of the correct module here, but what does.

[...]

Output?

hi thanks
i have this error

root@server:~# sudo modinfo saa716x
modinfo: ERROR: Module saa716x not found.

domenic ciciarelli wrote:

Mark Clarkstone wrote:

domenic ciciarelli wrote:

This is the second motherboard
Only with windows works this card, Could it be the version of ubuntu?
Or the card has been damaged, but I have never used it before now

Not sure this applies with the driver you're using, but some TBS cards have issues with some motherboards. You may want to see if the driver has support for MSI interrupts.

I'm not 100% sure of the correct module here, but what does.

[...]

Output?

hi thanks
i have this error

root@server:~# sudo modinfo saa716x
modinfo: ERROR: Module saa716x not found.

Like I said I wasn't even sure of the module used by that card so took a stab in the dark and assumed saa716x. @saen acro might have an idea though.

If all fails, e-mail tbs support, they should be able to advise further.

Mark Hunting Clarkstone if device exist dmesg and lspci will show it with or without enabled module

https://bitbucket.org/updatelee/v4l-updatelee
to compile Philips module

why not test LibreElec it have all modules build in

There is a verry rare chance, this card to use 5V data bus but mobo to have only 3.3V

saen acro wrote:

Mark Hunting Clarkstone if device exist dmesg and lspci will show it with or without enabled module

Yeah, you're right.

https://bitbucket.org/updatelee/v4l-updatelee
to compile Philips module

why not test LibreElec it have all modules build in

There is a verry rare chance, this card to use 5V data bus but mobo to have only 3.3V

On two motherboards though? O.o

This is a real head scratcher..

Thank you very much for your response
Then I followed the help from @saen acro but I did not succeed
I received a response from TBS assistance and they told me to use it

Lspci -vvv

hi i see this in ubuntu 14.04
http://prntscr.com/eyocfh

I'm sure I downloaded the file for linux, I do not understand
http://prntscr.com/eyocy7

$lspci vvvnn
01:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7160 [1131:7160] (rev 03)
Subsystem: Device [6922:0001]
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-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fea00000 (64-bit, non-prefetchable) [disabled] [size=1M]
Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [50] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, 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 128 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [74] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Vendor Specific Information: Len=50
Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=088

domenic ciciarelli wrote:

I received a response from TBS assistance and they told me to use it

Lspci -vvv

it is same as lspci but more detailed

but on this picture

there is no device on channel
01:00.0

it is available now and need to compile module/driver to work /read from beginning/

hi, thanks now i have this
http://prntscr.com/eypccp

Do you think the law is now?
Which command is needed now to make it run?

These drives are horrible and tbs service is the same, i have to throw the card there is no way to get it started, would you recommend a good alternative a TBS?

All are same, when Linux is far away from you
learn how to compile source code.
Or install https://libreelec.tv
there is all installed, just need configuration.

Tbs team is horrible as Intel one.
No DKMS no specified modules installer.
media_build compile modules for web cam's WTF

How do I fill in a fill out this file?
After I followed the guide

this guide no work
sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/
1.wget http://www.tbsiptv.com/download/common/tbs-linux-drivers_v170330.zip
2.unzip tbs-linux-drivers_v170330.zip
3. tar jxvf linux-tbs-drivers.tar.bz2
4. cd linux-tbs-drivers
5. ./v4l/tbs-x86_64.sh
6. make -j4
7.make install
8.reboot

what should I do?
How can I fill in?
Please help

I don't know why they are telling you to do sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/ - that seems very wrong, and I have never had to do that.

I think maybe you are not using sudo when building your drivers.

The instructions I have used in the past, which are no longer online, go like this (I have added a few comments in bold):

Go to https://www.tbsdtv.com/download/ and find the latest Linux drivers for your card. Right click the download link and copy the link location. Then from your Linux command prompt:

mkdir driver
cd driver
wget http://www.tbsiptv.com/download/common/tbs-linux-drivers_v170330.zip (use the driver link you just copied)
unzip tbs-linux-drivers_v170330.zip (use the filename of the file you just downloaded)
tar xjvf linux-tbs-drivers.tar.bz2
cd linux-tbs-drivers

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 (this is probably the one you want on any modern system, so do this:)

sudo ./v4l/tbs-x86_64.sh (note use of sudo!!)

sudo make && sudo make install (note use of sudo!!)

Reboot in order to load the newly installed driver:

sudo shutdown -r now (or sudo reboot on Ubuntu/Debian type systems)

After reboot check that the newly installed driver is loaded correctly:

(NOTE THIS PART IS FOR A DIFFERENT CARD, SO IT MAY NOT WORK UNLESS YOU CHANGE THE grep STRING. I USE DIFFERENT TESTS, SPECIFICALLY

dmesg | grep -i dvb

and/or

ls -l /dev/dvb

WHICH SEEM TO WORK FOR MOST TBS CARDS)

dmesg | grep cx23885

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

[ 13.190399] cx23885 driver version 0.0.3 loaded
[ 13.190430] cx23885 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 13.190612] CORE cx23885⁰: subsystem: 6921:8888, board: TurboSight TBS 6921 [card=34,autodetected]
[ 13.946229] cx25840 2-0044: cx23885 A/V decoder found @ 0x88 (cx23885⁰)
[ 14.647274] cx25840 2-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
[ 14.654933] cx23885_dvb_register() allocating 1 frontend(s)
[ 14.654935] cx23885⁰: cx23885 based dvb card
[ 14.813362] DVB: registering new adapter (cx23885⁰)
[ 14.840282] cx23885_dev_checkrevision() Hardware revision = 0xb0
[ 14.840286] cx23885⁰/0: found at 0000:06:00.0, rev: 2, irq: 16, latency: 0, mmio: 0xfb600000
[ 14.840292] cx23885 0000:06:00.0: setting latency timer to 64
[ 14.898554] input: cx23885 IR (TurboSight TBS 6921) as /devices/pci0000:00/0000:00:09.0/0000:06:00.0/rc/rc0/input10
[ 14.902061] rc0: cx23885 IR (TurboSight TBS 6921) as /devices/pci0000:00/0000:00:09.0/0000:06:00.0/rc/rc0
[ 14.902183] input: MCE IR Keyboard/Mouse (cx23885) as /devices/virtual/input/input11
[ 14.902268] rc rc0: lirc_dev: driver ir-lirc-codec (cx23885) registered at minor = 0

Also keep in mind that every time you do a Linux kernel update you'll need to rebuild the drivers. If you still have problems I'd start over with a fresh install of the operating system, and DO NOT do the sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/ step from whatever instructions you are reading now.

ONCE YOU GET IT WORKING, you will want to make sure it's not sharing an interrupt (see https://freetoairamerica.wordpress.com/2014/11/08/do-you-run-one-or-more-tbs-pcie-cards-under-linux-check-your-irqs/ and you may want to look at some of the other articles on that site that address other TBS card quirks).

To follow up on my previous post: TVHeadend runs as user "hts", not as your default Linux user. So it will not be able to see or use any drivers your build as a normal user because it doesn't have permission to do so. And actually I think the operating system would ignore them as well, if you don't build them using sudo.

One thing to keep in mind about Linux is when things don't work as expected, about 50% of the time it's a permissions issue (or ownership issue, which is essentially also a permissions issue). And also, there are very few instances where a driver would not be installed by the root user (which is what sudo does, in effect it makes you the root user for that one command. I know it's a bit more nuanced than that, but that is effectively what it does for all practical purposes). When you install a driver as root it sort of becomes part of the operating system, and any application can use it. When you don't install it as root, it's pretty much a big blob of useless dead code lying there that neither the operating system nor any application will use.

I'm not a linux expert surely but I have never had so much trouble installing anything, even with the avermedia pennas that eventually work, these tbs files are horrible

Thought apart

I installed it from header ubuntu server 14.04
I followed the retail guide as shown by Sean Sean Micklem
The outcome is always the same, the card works on windows, on Ubuntu - tvh no!
To install everything I have always used root permissions sudo - root@server:~#

Ps: for security I tried 2 times....no work!!!!

https://bitbucket.org/updatelee/v4l-updatelee
Are you test with this?
or
https://github.com/ljalves/linux_media/wiki
or
https://github.com/crazycat69/linux_media

To saen acro, if he can't get the standard TBS drivers to work, it may be even more difficult messing with third party drivers. You have to be even more well-versed in Linux to get those installed and working.

To domenic ciciarelli, I just don't get why you are having issues. I run TVHeadend 4.0.9 (the stable version) on Ubuntu Server 14.04 and it has no problems detecting and using the TBS cards. What happens when you run

dmesg | grep -i dvb

and

ls -l /dev/dvb

Both of those should in some way show your TBS card tuners. If they don't then that means the card is not being detected by your motherboard and/or by Linux, and therefore TVHeadend will not be able to use it. It may be that you need to tweak some bios setting, but I can't begin to suggest which one. Or it may be that a different motherboard would help; I use a MSI model and I do remember that I had to replace a Gigabyte motherboard with the MSI because the TBS cards wouldn't work with the Gigabyte board that I had.

Keep in mind that if you install the drivers and then do a kernel update you'll need to rebuild the drivers again or there is no hope of them working.

Alternately, if you simply can't get the card to work under Linux but as you say it has no problem working under Windows, then you may want to try a Windows-based program such as MediaPortal or NextPVR. I hate to adopt a defeatist attitude but it sounds like you are bashing your head against the proverbial wall and getting nowhere, and I'm not really sure why because other than the specific TBS card model and possibly the motherboard, you appear to have an almost identical setup to what I've been running for over two years now. I would say maybe the card is defective but you say it works under windows, so I don't know what else to tell you to try.

I will say to be careful of conflicting interrupts; I've seen Linux shut down an IRQ completely when it is shared with more than one device and one of the other devices acts up. I sent you a link to an article in my previous post that explains how to fix that with at least some TBS cards, though I don't know if it applies to yours.

However you choose to proceed, I wish you good luck. I'm not a Linux expert by any stretch of the imagination, so I don't really have any more suggestions for you.

OMG your linux knowledge is worst
If there is not module loaded there is no chance to see any dvb messages
or devices /module create them/

hardware > Kernel > module > kernel > device communication
aka to work device first bios need to see hardware device
then kernel to to take this info and base on it to see is there a module to load
module itself create software layer to communicate to device
then if previous are satisfied any software will work with device
with version and type of software this is other question

saen acro wrote:

OMG your linux knowledge is worst
If there is not module loaded there is no chance to see any dvb messages
or devices /module create them/

hardware > Kernel > module > kernel > device communication
aka to work device first bios need to see hardware device
then kernel to to take this info and base on it to see is there a module to load
module itself create software layer to communicate to device
then if previous are satisfied any software will work with device
with version and type of software this is other question

I don't know who you were directing that to, but that is the most poorly written post I have ever read in my life. No part of it made the slightest bit of sense.

Maybe this is intelligible to other Linux users, or maybe you were writing complete gibberish, I don't know and I don't care. But whether you were writing to me or to the OP or to some mystical leprechaun, I doubt anyone in this thread has the slightest idea what you are babbling on about.

Sean Micklem wrote:

saen acro wrote:

OMG your linux knowledge is worst
If there is not module loaded there is no chance to see any dvb messages
or devices /module create them/

hardware > Kernel > module > kernel > device communication
aka to work device first bios need to see hardware device
then kernel to to take this info and base on it to see is there a module to load
module itself create software layer to communicate to device
then if previous are satisfied any software will work with device
with version and type of software this is other question

I don't know who you were directing that to, but that is the most poorly written post I have ever read in my life. No part of it made the slightest bit of sense.

Maybe this is intelligible to other Linux users, or maybe you were writing complete gibberish, I don't know and I don't care. But whether you were writing to me or to the OP or to some mystical leprechaun, I doubt anyone in this thread has the slightest idea what you are babbling on about.

Chill! He's trying & English isn't his first language.

What he's saying is that for the device to work with any software the kernel first needs to be able to see the hardware, it then uses the device info to determine what driver/module is required.

Thank you very much Sean Sean Micklem your intervention was very constructive, to say the least out of place, but back to the friends who gave me a hand, I did help this restart restart tbs 6922 worked perfectly, only fixing a problem here is another ready ready Vision stalls continually I can not have fluid vision

Sorry I followed this guide I said
Https://bitbucket.org/updatelee/v4l-updatelee

Not all motherboards are compatible with this sat board
Asus with this guide works the first time
Asrock still does not work with over 10 tests done

Upgrade bios to latest hope it help.