Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT sowie TT S2-6400 (Teil 1)

Zitat von sbontadi

Hallo Oliver
Du hast noch einige Updates im ddbridge gemacht. Allerdings gab es schon lange keine commits in linux-media, sprich im Kernel.
Was sind deine Pläne. Welcher Kernelversion wird anvisiert. Zeithorizont.

Ich habe derzeit nicht vor, etwas an v4ldvb zu submitten.

Die letzte Aktion war frustrierend. Der Subsystem-Maintainer betrachtet das Master-Directory als seine private Spielwiese. Kaum war der DRXK-Treiber upstream, wurde er so umgemodelt, daß ein Abgleich mit dem Original-Treiber kaum noch möglich ist. Mehrfach wurde der Support für die DD-Karten kaputt gepatcht. D.h. für die Karten, denen die Existenz des Treibers im Kernel überhaupt zu verdanken ist. Einfach inakzeptabel!

Für mich gibt es interessantere Tätigkeiten als zu überwachen, was die Jungs upstream gerade so treiben.

stv0367dd und tda18212dd müßten erst noch an den Kernel-Coding-Style angepaßt werden. Möglicherweise würden sie dennoch nicht akzeptiert, da es bereits Treiber für diese Chips gibt (die allerdings nicht so ohne weiteres verwendet werden können).

Daher bleibt dieser Treiber in nächster Zeit der Referenztreiber.

CU
Oliver

Zitat von tom66

Hallo Leute,

ich sehe gerade im Artikel des Threadstarters, dass man initial

Code

hg clone http://linuxtv.org/hg/~endriss/media_build_experimental

aufrufen soll. Doch da kommt:

Code

WARNING: You're using an obsolete driver! You shouldn't be using it!
         If you want anything new, you can use:
                http://git.linuxtv.org/media_build.git.
         The tree is still here just to preserve the development history.
         You've been warned.

Wann kommt diese Meldung? Bestimmt nicht bei o.g. "hg clone" - jedenfalls nicht bei mir.

Zitat

Kann man den ersten Artikel aktualisieren oder gibt es eine aktuellere Anleitung irgend wo?

Der Artikel _ist_ aktuell.

CU
Oliver

Zitat von kokel

Hallo,

ich habe den aktuellen Treiber für die Digital Devices Cine C/T V6 aus media_build_experimental wie hier beschrieben installiert.
System ist ein Debian Squeeze, Kernel 2.6.32.
VDR aus e-tobi.net Repository.

Leider funktioniert das automatische Umschalten auf DVBT nicht.

# dmesg

Code

[   26.547321] DDBridge 0000:00:06.0: irq 29 for MSI/MSI-X
[   26.800430] Port 0 (TAB 1): DUAL DVB-C/T
[   26.801978] Port 1 (TAB 2): NO MODULE
[   26.802804] Port 2 (TAB 3): NO MODULE
[   26.803005] DVB: registering new adapter (DDBridge)
[   26.803007] DVB: registering new adapter (DDBridge)
[   26.816495] stv0367 found
[   27.093705] tda18212dd: ChipID 4724
[   27.094151] tda18212dd: PowerState 01
[   27.221510] DVB: registering adapter 0 frontend 0 (STV0367 DVB-C DVB-T)...
[   27.222447] stv0367 found
[   27.494426] tda18212dd: ChipID 4724
[   27.494881] tda18212dd: PowerState 00
[   27.780495] DVB: registering adapter 1 frontend 0 (STV0367 DVB-C DVB-T)...

Alles anzeigen

syslog nach start des vdrs:

Code

Feb  7 17:57:23 vdrserver vdr: [1652] VDR version 1.7.23 started
...
Feb  7 17:57:23 vdrserver vdr: [1652] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.1.7.23

Beim Anfordern eines DVB-T Kanals sieht syslog so aus:

Code

Feb  7 17:59:50 vdrserver vdr: [1672] streamdev: No device provides channel 2 (ZDF) at priority 0

Mit dem dvb-fe-tool funktionierts ,wenn ich manuell auf DVBT umschalte, aber der VDR ab v1.7.23 solls doch angeblich nativ können?
Habe ich vllt was übersehen oder mache ich was falsch?

Alles anzeigen

VDR 1.7.23 kann den Tuner umschalten - definitiv.
Für mich sieht es so aus, als ob streamdev es nicht könnte. (Oder es stimmt noch etwas an der Plugin-Schnittstelle nicht.)

CU
Oliver

Zitat von grid

I was hoping someone here could help me.
I have installed mythbuntu 11.10 with 64bit 3.0.0 kernel.
I have Digital Devices mini pcie DVB-S2 installed.
The card was working straight out of the box with mythtv after I had installed the ngene_18.fw

Ok.

Zitat

I could tune the card and watch tv. However mythbackend had a continuous
log of errors including "warning: unsupported fec_inner parameter"

Not very meaningful unless there is more info, which value caused the problem.

Zitat

"frequency ....... out of range"

Attempt to tune to an invalid frequency. Not a driver problem.

Zitat

"cannot count uncorrected blocks"

The kernel driver does not support this function yet.

Zitat

"wrong pmt"

Not a driver problem.

Zitat

and so on. I tried deleting all channels and rescanning them
but the errors continued.
I thought maybe it was a driver error and I
followed the instructions on the first page and then deselected all
modules in the menuconfig except: Media Controller API, Video for Linux,
DVB for Linux, Load and Attach frontend as needed, Micronas ngene
support, Digital devices bridge support, STV0900/STV0903 (A/B),
STV6110/(A) based tuners. Everything else was unselected.

Alles anzeigen

It is a bad idea to deselect "Load and Attach frontend as needed" - unless you know exactly what you are doing.
"LNBP21/LNBH24 SEC controllers" is missing in the list above.

Zitat

After reboot there have been a few changes. Before I had one adaptor with two
frontends. Now my device is listed as two different adaptors. Any
command relating to either adaptor results in a hang. for example an
attempt at scanning for channels with terminal command, I deleted the
devices in mythtv but if I try to create a new one it crashes.

Alles anzeigen

You probably mixed modules from the kernel with modules from this driver.
This will likely cause strange errors or a crash. lnbp21 might be the problem in this case.

Zitat

used to say "ngene: Found Digital Devices Duoflex miniPCIe" now it says
"ngene: Found Digital Devices Duoflex PCIe or miniPCIe"

That's fine.

Zitat

Also there is a very long list of "Modules linked in:" which never used to be there.
lsmod
shows stv6100x, stv090x, ngene, dvb_core, and lnbp21 which I have
realised I did not select as a module from the media build experimental.
What am I missing? I am still new to Linux so learning a lot as I go.
If anyone could help me that would be great.
Is there a way to add modules that I might have forgotten from media build experimental?

Alles anzeigen

Select "Load and Attach frontend as needed", then enable just the bridge driver(s) that you need (in your case "Micronas nGene support"). All dependencies will be enabled automatically.

CU
Oliver

Zitat von grid

Vielen dank Oliver!

So just to make sure,
I need to cd media_build_experimental
make distclean
make untar
and then start again with make menuconfig, make, make install?

Yes, this should work.

Zitat von grid

Ok, I included lnbp21 in the menuconfig, and after rebooting the DVB card no longer crashed, but I could not tune with it. So I instead included all modules in the menuconfig but now card is not recognised.
Dmesg:
ngene: disagrees about version of symbol cxd2099_attach
Unknown symbol cxd2099_attach

I renamed the cxd2099.ko in /lib/modules/3.0.0-12-generic/kernel/drivers/staging/cxd2099/ to cxd2099.old

Has no effect: If you run 3.0.0-15, the 3.0.0-12 directory does not matter.

Zitat

There is now only one in /lib/modules/3.0.0-15-generic/kernel/drivers/staging/cxd2099/

These errors are still there:
ngene: disagrees about version of symbol cxd2099_attach

Unknown symbol cxd2099_attach

You _must_not_use_ an old driver module from the kernel!
Look into the v4l subdirectory and verify that
1. ngene.ko, stv090x.ko etc. were installed under /lib/modules/3.0.0.15/...
2. there are no old versions of these files under /lib/modules/3.0.0.15/...

Did you enable the "CXD2099AR Common Interface driver" under "Staging"?
cxd2099.ko must also come from the driver, not the kernel.

Zitat

How can I revert to vanilla kernel and modules? I'm not having any luck with these treibers. Its probably my fault being a noob and not doing something right.

This depends on your distribution. Re-install the package, which contains the kernel modules.

CU
Oliver

Zitat von mmajoor

Leider gibst ein Problem mit dem USE_API3 definierten Code (also -kein- gemeinsames Frontend) in 'set_parameters', wodurch Tuning für DVB-C (QAM) nicht gelingen wird.
Der Grund dafür ist, dass der Code eine gültige Bandbreite überprüft. Allerdings ist die Bandbreite kein Teil des QAM/DVB-C 'Union', sondern ist Teil des OFDM/DVB-T 'Union'.
Für QAM/DVB-C wird beim überprüfen die Symbolrate (die sich im selben "Raum" als die OFDM/DVB-T-Bandbreite befindet) verwendet, und scheitert.

Code

#ifdef USE_API3
static int set_parameters(struct dvb_frontend *fe,
    	struct dvb_frontend_parameters *p)
{
  int stat;
  struct stv_state *state = fe->demodulator_priv;
  u32 OF = 0;
  u32 IF;


  if (fe->ops.tuner_ops.set_params)
	fe->ops.tuner_ops.set_params(fe, p);


  state->modulation = p->u.qam.modulation;
  state->symbol_rate = p->u.qam.symbol_rate;
  switch(p->u.ofdm.bandwidth) {   <--- For DVB-C/QAM this actually returns the symbolrate (u.qam.symbol_rate)
	case BANDWIDTH_AUTO:
	case BANDWIDTH_8_MHZ:
  	state->bandwidth = 8000000;
  	break;
	case BANDWIDTH_7_MHZ:
  	state->bandwidth = 7000000;
  	break;
	case BANDWIDTH_6_MHZ:
  	state->bandwidth = 6000000;
  	break;
	default:
  	return -EINVAL;         	<--- Error triggered when using DVB-C/QAM
  }
#else

Alles anzeigen

Eine mögliche Lösung ist die folgende:

Code

#ifdef USE_API3
static int set_parameters(struct dvb_frontend *fe,
    	struct dvb_frontend_parameters *p)
{
  int stat;
  struct stv_state *state = fe->demodulator_priv;
  u32 OF = 0;
  u32 IF;


  if (fe->ops.tuner_ops.set_params)
	fe->ops.tuner_ops.set_params(fe, p);


  switch (state->omode) {
	case OM_DVBT:
  	switch(p->u.ofdm.bandwidth) {
    	case BANDWIDTH_AUTO:
    	case BANDWIDTH_8_MHZ:
      	state->bandwidth = 8000000;
      	break;
    	case BANDWIDTH_7_MHZ:
      	state->bandwidth = 7000000;
      	break;
    	case BANDWIDTH_6_MHZ:
      	state->bandwidth = 6000000;
      	break;
    	default:
      	return -EINVAL;
  	}
  	break;
	case OM_DVBC:
	case OM_QAM_ITU_C:
  	state->modulation  = p->u.qam.modulation;
  	state->symbol_rate = p->u.qam.symbol_rate;
  	break;
	default:
  	stat = -EINVAL;
  }
#else

Alles anzeigen

Nach der Anwendung dieser Änderungen konnte ich Tunen.

Alles anzeigen

Danke, da habe ich Mist gebaut. Merkwürdig - hätte ich eigentlich sehen müssen.
Werde es korrigieren.

Nur zur Warnung:
Wenn man das alte Repository http://linuxtv.org/hg/~endriss/ngene-octopus-test direkt verwendet, hat man - bis auf ngene, octopus + Konsorten - keine aktuellen Treiber. dvb-core & Co werden dort nicht mehr aktualisiert.

CU
Oliver

Zitat von grid

Danke Oliver again. You guessed it correctly, I had not included cxd2099 from the staging drivers in menuconfig
I included it and saw that a new cxd2099.ko was created in /lib/modules/3.0.0-15-generic/kernel/drivers/linux/drivers/staging/media/cxd2099
I renamed the old cdx2099.ko in /lib/modules/3.0.0-15-generic/kernel/drivers/staging/cxd2099/ to cxd2099.ko.old and unloaded the cxd2099.ko module.
Modprobe cxd2099 showed a not found error so I moved the new module from /drivers/linux/drivers/staging... to /kernel/drivers/staging/ and this time at boot ngene was loaded without errors:

I guess, a "depmod -a" would have fixed the "not found" error.

Zitat

DVB: registering new adapter (nGene)
DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
DVB: registering new adapter (nGene)
DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...

ngene 0000:03:00.0: PCI INT A -> Link[LN3A] -> GSI 17 (level, low) -> IRQ 17
ngene: Found Digital Devices DuoFlex PCIe or miniPCIe
ngene 0000:03:00.0: setting latency timer to 64
ngene: Device version 1
ngene: Loading firmware file ngene_18.fw.
ngene 0000:03:00.0: irq 47 for MSI/MSI-X

Alles anzeigen

Looks perfect.

Zitat

BUT, there is always a "but" ....
Now the device is half recognised by Mythtv, however the switch, diseq, LNB options are missing when I try to create the new adaptor. Trying to watch or tune channels doesn't work and mythbackend shows the following errors:

New DB connection, total: 2
Connected to database 'mythconverg' at host: localhost
DiSEqCDevTree, Warning: No device tree for cardid 3
New DB connection, total: 3
Connected to database 'mythconverg' at host: localhost
DVBChan(3:/dev/dvb/adapter1/frontend0) Warning: Unsupported fec_inner parameter.
DiSEqCDevTree, Error: No root device tree node!
DVBChan(3:/dev/dvb/adapter1/frontend0) Error: Tune(): Failed to setup DiSEqC devices
DVBChan(3:/dev/dvb/adapter1/frontend0) Error: SetChannelByString(1): Tuning to frequency.
DVBChan(4:/dev/dvb/adapter1/frontend0) Warning: Your frequency setting (12000000) is out of range. (min/max:950000/2150000)
DVBChan(4:/dev/dvb/adapter1/frontend0) Warning: Unsupported fec_inner parameter.
DiSEqCDevTree, Error: No root device tree node!
DVBChan(3:/dev/dvb/adapter1/frontend0) Error: Tune(): Failed to setup DiSEqC devices
DVBChan(4:/dev/dvb/adapter1/frontend0) Error: SetChannelByString(1): Tuning to frequency.
DiSEqCDevTree, Warning: No device tree for cardid 5

These are repeated many times for both tuners, also this is repeated many times:

SignalMonitor: channel change failed

Any ideas as to what I'm missing?
As always your help is much appreciated, thank you!

Alles anzeigen

These error messages do not come from the driver.
I suspect that Myth is not configured correctly.

Frequency 12000000 [kHz] is way too high, 950000..2150000 [kHz] is the allowed range for all DVB-S/DVB-S2 tuners.
Check the LOF (local oscillator frequency) setting: Universal LNBs use 9750 MHz for low band, 10600 MHz for high band.

Sorry, I never used Myth, so I cannot provide much help in this area.

CU
Oliver