Bug #1060
TVHeadend GUI thinks Duoflex DVB-C/DVB-T Turner is a DVB-S Device
| Status: | Invalid | Start date: | 07/27/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Hein Rigolo | % Done: | 0% | |
| Category: | DVB | |||
| Target version: | - | |||
| Found in version: | 0.90.0.5265.ga257d | Affected Versions: |
Description
Strange behaviour encountered with latest OpenELEC TVHeadend-Version:
(START: HTS Tvheadend version 0.90.0.5265.ga257d started)
Card is a Dual DVB-C/DVB-T Tuner and recognized as...
dvb: Found adapter /dev/dvb/adapter1 (DRXK DVB-C DVB-T) via PCI
So appearing in under http://localhost:9981 / Settings/Adapters.
The card is connected to a DVB-C signal.
When trying to provide Channel frequency & Modulation Params(eg. 410000, 6900000, QUAM256..) or try to load presets one finds all the parameters a DVB-S (!!) Card needs.
When now in XBMC the AddON for TVHeadend is deaktived and reactived, the TVHeadend GUI Provides all the Params for a DVB-T (!!!) Signal.
BTW TVHeadend running on an Ubunto 12.04 systems works fine (but its a completely different tvheadend version)
dmes on startup recognizes the card fine.
Any Ideas in which direction to look?
dmesg_GEHT_NICHTOPENELEC.txt 
(108 KB)
History
#1
Updated by Hein Rigolo 10 months ago
tvheadend does not yet support single adapters with dual frontends via de dvb-api v5 interface. So please use kernel module settings to have both frontend appear as separate adapters (so in your case /dev/dvb/adapter1 and /dev/dvb/adapter2)
Hein
#2
Updated by Adam Sutton 10 months ago
It may well be that the xbmc plugin is using an very out of date version of tvh. 2.12 probably.
It may be that latest build on ubuntu will work.
I hope to address the out of date packages in coming weeks.
Adam
#3
Updated by Adam Sutton 10 months ago
If this is working with latest TVH on Ubuntu and not with TVH OpenELEC plugin can you contact the OpenELEC maintainer. I spoke to him tonight to let him know about some TVH structural changes and he did a build for his system, so there might be a new release available shortly.
He might be able to provide something more up to date. If it genuinely is a problem with DVB API, then we'll need to investigate.
#4
Updated by Adam Sutton 10 months ago
- Category changed from WEB UI to DVB
- Status changed from New to Need feedback
#5
Updated by Adam Sutton 9 months ago
- Status changed from Need feedback to Invalid
No update in a month and the evidence tends to suggest that this is specific to an older version of TVH (namely the OE addon build).
Please try contacting the author of the addon, I've spoken to him several times recently and I know he has more recent builds that he's been testing.
#6
Updated by Pim Zandbergen 4 months ago
I have the exact same problem with brand new Tvheadend 3.3.200~ga420c83 and brand new kernel 3.7.1.
This is a vanilla kernel running on Fedora 17 x86_64.
Kernel 3.3.8 is the last that runs fine for this card.
Kernel versions in between don't work at all because of firmware loading problems.
I have two ngene-based cards, one dual DVB-S2 and one dual DVB-C/DVB-T card that defaults to DVB-C.
The real DVB-S2 card works, but the DVB-C/DVB-T card is shown as if it's a DVB-S2 card as well.
The syslog shows a DVBv3-emulated ioctl has failed without Tvheadend noticing or reporting.
Jan 13 23:27:58 moog tvheadend[3749]: charset: 71 entries loaded Jan 13 23:27:58 moog tvheadend[3749]: dvb: Found adapter /dev/dvb/adapter0 (STV090x Multistandard) via PCI Jan 13 23:27:58 moog tvheadend[3749]: dvb: Found adapter /dev/dvb/adapter1 (STV090x Multistandard) via PCI Jan 13 23:27:58 moog kernel: [ 250.216234] ngene 0000:04:00.0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0 Jan 13 23:27:58 moog tvheadend[3749]: dvb: Found adapter /dev/dvb/adapter2 (DRXK DVB-C DVB-T) via PCI Jan 13 23:27:58 moog kernel: [ 250.217652] ngene 0000:04:00.0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0 Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:charset: 71 entries loaded Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:dvb: Found adapter /dev/dvb/adapter0 (STV090x Multistandard) via PCI Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:dvb: Found adapter /dev/dvb/adapter1 (STV090x Multistandard) via PCI Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:dvb: Found adapter /dev/dvb/adapter2 (DRXK DVB-C DVB-T) via PCI Jan 13 23:27:58 moog tvheadend[3749]: dvb: Found adapter /dev/dvb/adapter3 (DRXK DVB-C DVB-T) via PCI Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:dvb: Found adapter /dev/dvb/adapter3 (DRXK DVB-C DVB-T) via PCI Jan 13 23:27:58 moog tvheadend[3749]: dvb: Adapter /dev/dvb/adapter0 will run in full mux mode Jan 13 23:27:58 moog tvheadend[3749]: Jan 13 23:27:58 [INFO]:dvb: Adapter /dev/dvb/adapter0 will run in full mux mode
Pim
#7
Updated by Pim Zandbergen 4 months ago
Correction: this was this Tvheadend 3.3.345~g687d047
Pim