search

ljalves / linux_media

TBS linux open source drivers
https://github.com/ljalves/linux_media/wiki
Other
88 stars 153 forks source link

TBS6285 no signal #64

Closed ghost closed 9 years ago

ghost commented 9 years ago

Hi,

With a bit of effort I managed to get the drivers built for the TBS 6285. However, when I start TVHeadend 3.4.27 I can see all the adapters and it will appear to tune to a frequency, but it doesn't find any channels. I've tried both int_type=0 and int_type=1 without success.

The firmware is in /lib/firmware and is taken from bas-t's repository.

I'm using the latest commit from both repositories.

Using the official drivers I can get scan successfully, but they cause my server to crash after a day or so even using int_type=1 (MSI).

I can attach dmesg output if this would be any use?

Any ideas?

RayCic commented 9 years ago

Unfortunately it looks driver is incapable to correctly initialize some versions (all?) of card.

I had same problem and I fixed it by addiding following commands to boot scripts:

/usr/bin/dvb-fe-tool -a 0 -d DVBT
/usr/bin/dvb-fe-tool -a 1 -d DVBT
/usr/bin/dvb-fe-tool -a 2 -d DVBT
/usr/bin/dvb-fe-tool -a 3 -d DVBT

You should change numbers with your adapters numbers

Theoretically you can use any program capable of FULL initialization of card, for example w_scan.

BTW for statistics can you post you revision of card (mine is V21, it is written on front side of card)

750430 commented 9 years ago

Hi, sorry for the thread hijack, what distro did you use to successfully build the drivers? When you run a : lspci -v | grep --after-context=10 7160 do you see 'kernel module' loaded?

ljalves commented 9 years ago

@epon You can paste dmesg. Are you sure the firmware is located in the right place and you have the correct versions? The ideia of having to do a "full initialization of the card" is weird and should not be necessary.

ghost commented 9 years ago

Since issue #66 describes the same problem I'm seeing in this issue, I think we should close this one down and mark it as a duplicate of #66 if that's possible. Better to keep the information in one place.

ljalves commented 9 years ago

Closing and marking duplicate of #66