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

Hallo Lars

Kernel is 3.13.0-35-generic.
Kernel sourcen hab ich installiert, aber nichts weiter getan. Ich meine mich erinnern zu können dass ich die irgendwie in in /usr/src nach linux verlinken muss? bin mir aber nicht sicher und habe im moment keinen Zugriff auf mein System oder irgendein anderes Linux womit ich die Pfade verifizieren könnte.

Habe gerade eine mail von digital-devices bekommen. angeblich ist die ddbridge mittlerweile im stable Branch von v4l angekommen. Werde dieses mal versuchen

Meinen Punkt könnt ihr rausnehmen. Nach gründlichem aufräumen und neuinstallierend er v4l stable treiber geht alles!
Danke für die Hilfe!

Hi,

Zitat von UFO

Falls jemand Probleme mit MSI haben sollte, möge er ddbridge mit msi=0 laden.
(Und natürlich Motherboard-Typ und Chipsatz melden.)

Ohne msi=0 bekomme ich viel Fehler Meldungen wie diese:

Zitat

Oct 3 10:47:00 miepie kernel: [ 92.603135] ddbridge 0000:05:00.0: DDBridge IRS 00000000
Oct 3 10:47:00 miepie kernel: [ 92.603189] drxk: i2c read error at addr 0x2a
Oct 3 10:47:00 miepie kernel: [ 92.603234] drxk: Error -5 on scu_command
Oct 3 10:47:00 miepie kernel: [ 92.603276] drxk: GetQAMLockStatus status = fffffffb
Oct 3 10:47:00 miepie kernel: [ 92.603325] drxk: Error -5 on GetLockStatus

Oft arbeitet den nur noch ein von meine vier Tuner. Mit msi=0 lauft alles gut und stabil.

System information:

Base Board Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z87X-UD5H-CF
(Intel Z87 Express Chipset)

PCI chipset met ddbridge:
Vendor: Intel Corporation
Device: 8 Series/C220 Series Chipset Family PCI Express Root Port #4

dank!

Winfried

Welchen kernel hast du im Einsatz?
Bei mir gibt es mit 3.14.12 keine Probleme mit MSIs. Habe aber ein Gigabyte Board mit H77 Chipset.

Gruss
tec

Zitat von tecfreak

Welchen kernel hast du im Einsatz?

Debian Jesse:

Linux miepie 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux

Mit media build experimental vorgestern gebaut von: http://linuxtv.org/hg/~endriss/media_build_experimental

Winfried

Excuse my English. My German is not very good and this is the only place I found with very recent activity around the ddbridge module for linux...
I tried to compile media_build_experimental against vanilla 3.17.0 this morning and it failed.
I renamed media_build_experimental to media_build_experimental-3.17 because I didn't want to break my working tree.

# make
make -C /usr/src/media_build_experimental-3.17/v4l 
make[1]: Entering directory `/usr/src/media_build_experimental-3.17/v4l'
scripts/make_makefile.pl
make[2]: Entering directory `/usr/src/media_build_experimental-3.17/linux'
Patches for 3.17.0 already applied.
make[2]: Leaving directory `/usr/src/media_build_experimental-3.17/linux'
./scripts/make_kconfig.pl /lib/modules/3.17.0/build /lib/modules/3.17.0/source
Preparing to compile for kernel version 3.17.0
WARNING: This is the V4L/DVB backport tree, with experimental drivers
         backported to run on legacy kernels from the development tree at:
                http://git.linuxtv.org/media-tree.git.
         It is generally safe to use it for testing a new driver or
         feature, but its usage on production environments is risky.
         Don't use it in production. You've been warned.
../experimental/update_kconfig.pl
./scripts/make_myconfig.pl
make[1]: Leaving directory `/usr/src/media_build_experimental-3.17/v4l'
make[1]: Entering directory `/usr/src/media_build_experimental-3.17/v4l'
perl scripts/make_config_compat.pl /lib/modules/3.17.0/source ./.myconfig ./config-compat.h
creating symbolic links...
make -C firmware prep
make[2]: Entering directory `/usr/src/media_build_experimental-3.17/v4l/firmware'
make[2]: Leaving directory `/usr/src/media_build_experimental-3.17/v4l/firmware'
make -C firmware
make[2]: Entering directory `/usr/src/media_build_experimental-3.17/v4l/firmware'
  CC  ihex2fw
Generating vicam/firmware.fw
Generating ttusb-budget/dspbootcode.bin
Generating cpia2/stv0672_vp4.bin
Generating av7110/bootcode.bin
make[2]: Leaving directory `/usr/src/media_build_experimental-3.17/v4l/firmware'
Kernel build directory is /lib/modules/3.17.0/build
make -C ../linux apply_patches
make[2]: Entering directory `/usr/src/media_build_experimental-3.17/linux'
Patches for 3.17.0 already applied.
make[2]: Leaving directory `/usr/src/media_build_experimental-3.17/linux'
make -C /lib/modules/3.17.0/build SUBDIRS=/usr/src/media_build_experimental-3.17/v4l  modules
make[2]: Entering directory `/usr/src/kernel/linux-3.17'
  CC [M]  /usr/src/media_build_experimental-3.17/v4l/mt2131.o
In file included from <command-line>:0:0:
/usr/src/media_build_experimental-3.17/v4l/compat.h: In function 'snd_card_create':
/usr/src/media_build_experimental-3.17/v4l/compat.h:686:2: warning: passing argument 1 of 'snd_card_new' makes pointer from integer without a cast [enabled by default]
  *card = snd_card_new(idx, id, module, extra_size);
  ^
In file included from /usr/src/media_build_experimental-3.17/v4l/compat.h:246:0,
                 from <command-line>:0:
include/sound/core.h:283:5: note: expected 'struct device *' but argument is of type 'int'
 int snd_card_new(struct device *parent, int idx, const char *xid,
     ^
In file included from <command-line>:0:0:
/usr/src/media_build_experimental-3.17/v4l/compat.h:686:2: warning: passing argument 2 of 'snd_card_new' makes integer from pointer without a cast [enabled by default]
  *card = snd_card_new(idx, id, module, extra_size);
  ^
In file included from /usr/src/media_build_experimental-3.17/v4l/compat.h:246:0,
                 from <command-line>:0:
include/sound/core.h:283:5: note: expected 'int' but argument is of type 'const char *'
 int snd_card_new(struct device *parent, int idx, const char *xid,
     ^
In file included from <command-line>:0:0:
/usr/src/media_build_experimental-3.17/v4l/compat.h:686:2: warning: passing argument 3 of 'snd_card_new' from incompatible pointer type [enabled by default]
  *card = snd_card_new(idx, id, module, extra_size);
  ^
In file included from /usr/src/media_build_experimental-3.17/v4l/compat.h:246:0,
                 from <command-line>:0:
include/sound/core.h:283:5: note: expected 'const char *' but argument is of type 'struct module *'
 int snd_card_new(struct device *parent, int idx, const char *xid,
     ^
In file included from <command-line>:0:0:
/usr/src/media_build_experimental-3.17/v4l/compat.h:686:2: warning: passing argument 4 of 'snd_card_new' makes pointer from integer without a cast [enabled by default]
  *card = snd_card_new(idx, id, module, extra_size);
  ^
In file included from /usr/src/media_build_experimental-3.17/v4l/compat.h:246:0,
                 from <command-line>:0:
include/sound/core.h:283:5: note: expected 'struct module *' but argument is of type 'int'
 int snd_card_new(struct device *parent, int idx, const char *xid,
     ^
In file included from <command-line>:0:0:
/usr/src/media_build_experimental-3.17/v4l/compat.h:686:2: error: too few arguments to function 'snd_card_new'
  *card = snd_card_new(idx, id, module, extra_size);
  ^
In file included from /usr/src/media_build_experimental-3.17/v4l/compat.h:246:0,
                 from <command-line>:0:
include/sound/core.h:283:5: note: declared here
 int snd_card_new(struct device *parent, int idx, const char *xid,
     ^
make[3]: *** [/usr/src/media_build_experimental-3.17/v4l/mt2131.o] Error 1
make[2]: *** [_module_/usr/src/media_build_experimental-3.17/v4l] Error 2
make[2]: Leaving directory `/usr/src/kernel/linux-3.17'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/usr/src/media_build_experimental-3.17/v4l'
make: *** [all] Error 2

No problem, the system perfoms quite well against the default ubuntu 14.04 kernel now. I was just looking into completely home built solution. Is there any chance the cine c2/t2 v7 (0006) will ever be supported in the mainline kernel?

With this patch/workaround it is running here on 3.16.3, maybe with 3.17, too.

diff -Naur media_build_experimental.orig/linux/drivers/media/pci/ddbridge/ddbridge.c media_build_experimental/linux/drivers/media/pci/ddbridge/ddbridge.c
--- media_build_experimental.orig/linux/drivers/media/pci/ddbridge/ddbridge.c	2014-08-10 18:35:51.215188043 +0200
+++ media_build_experimental/linux/drivers/media/pci/ddbridge/ddbridge.c	2014-08-10 18:31:00.000000000 +0200
@@ -145,6 +145,7 @@
 
 #ifdef CONFIG_PCI_MSI
    if (msi && pci_msi_enabled()) {
+#define pci_enable_msi_block pci_enable_msi_exact
	stat = pci_enable_msi_block(dev->pdev, 2);
	if (stat == 0) {
	    dev->msi = 1;
diff -Naur media_build_experimental.orig/v4l/compat.h media_build_experimental/v4l/compat.h
--- media_build_experimental.orig/v4l/compat.h	2014-08-10 18:35:51.331186901 +0200
+++ media_build_experimental/v4l/compat.h	2014-08-10 18:37:42.626091523 +0200
@@ -678,17 +678,9 @@
    } while (0)
 #endif
 
-#ifdef NEED_SND_CARD_CREATE
-static inline int snd_card_create(int idx, const char *id,
-			      struct module *module, int extra_size,
-			      struct snd_card **card)
-{
-	*card = snd_card_new(idx, id, module, extra_size);
-
-	if (*card == NULL)
-		return -ENOMEM;
-	return 0;
-}
+#ifdef NEED_SND_CARD_NEW
+#define snd_card_new(p, idx, id, module, extra_size, ret) \
+    	snd_card_create(idx, id, module, extra_size, ret)
 #endif
 
 /* This macro was added in commit v2.6.23-5792-g34c6538 */

Compilation goes a lot further, but ultimately fails on 3.17. See output in attachment.

Vielleicht gehts damit ... ?

diff -r 6b80c0903403 experimental/dddvb/ddbridge/ddbridge-core.c
--- a/experimental/dddvb/ddbridge/ddbridge-core.c       Mon Jun 09 19:34:53 2014 +0200
+++ b/experimental/dddvb/ddbridge/ddbridge-core.c       Wed Oct 08 20:40:32 2014 +0200
@@ -3416,16 +3416,16 @@
        __ATTR_RO(ports),
        __ATTR_RO(ts_irq),
        __ATTR_RO(i2c_irq),
-       __ATTR(gap0, 0666, gap_show, gap_store),
-       __ATTR(gap1, 0666, gap_show, gap_store),
-       __ATTR(gap2, 0666, gap_show, gap_store),
-       __ATTR(gap3, 0666, gap_show, gap_store),
+       __ATTR(gap0, S_IWUGO|S_IRUGO, gap_show, gap_store),
+       __ATTR(gap1, S_IWUGO|S_IRUGO, gap_show, gap_store),
+       __ATTR(gap2, S_IWUGO|S_IRUGO, gap_show, gap_store),
+       __ATTR(gap3, S_IWUGO|S_IRUGO, gap_show, gap_store),
        __ATTR_RO(hwid),
        __ATTR_RO(regmap),
 #if 0
        __ATTR_RO(qam),
 #endif
-       __ATTR(redirect, 0666, redirect_show, redirect_store),
+       __ATTR(redirect, S_IWUGO|S_IRUGO, redirect_show, redirect_store),
        __ATTR_MRO(snr,  bsnr_show),
        __ATTR_NULL,
 };
@@ -3448,21 +3448,21 @@
 };


 static struct device_attribute ddb_attrs_fan[] = {
-       __ATTR(fan, 0666, fan_show, fan_store),
+       __ATTR(fan, S_IWUGO|S_IRUGO, fan_show, fan_store),
 };


 static struct device_attribute ddb_attrs_snr[] = {
-       __ATTR(snr0, 0666, snr_show, snr_store),
-       __ATTR(snr1, 0666, snr_show, snr_store),
-       __ATTR(snr2, 0666, snr_show, snr_store),
-       __ATTR(snr3, 0666, snr_show, snr_store),
+       __ATTR(snr0, S_IWUGO|S_IRUGO, snr_show, snr_store),
+       __ATTR(snr1, S_IWUGO|S_IRUGO, snr_show, snr_store),
+       __ATTR(snr2, S_IWUGO|S_IRUGO, snr_show, snr_store),
+       __ATTR(snr3, S_IWUGO|S_IRUGO, snr_show, snr_store),
 };


 static struct device_attribute ddb_attrs_led[] = {
-       __ATTR(led0, 0666, led_show, led_store),
-       __ATTR(led1, 0666, led_show, led_store),
-       __ATTR(led2, 0666, led_show, led_store),
-       __ATTR(led3, 0666, led_show, led_store),
+       __ATTR(led0, S_IWUGO|S_IRUGO, led_show, led_store),
+       __ATTR(led1, S_IWUGO|S_IRUGO, led_show, led_store),
+       __ATTR(led2, S_IWUGO|S_IRUGO, led_show, led_store),
+       __ATTR(led3, S_IWUGO|S_IRUGO, led_show, led_store),
 };


 static struct class ddb_class = {

The patches didn't apply neatly to the latest media_build_experimental but I managed to apply them manually. I also applied the last patch to v4l/ddbridge-core.c since that had errors as well but still no luck. See attachment.

I installed the latest version using dkms but then my webcam stops working. When I plug it in it looks like it still references to different driver versions:

[    3.043224] videodev: Unknown symbol media_entity_put (err 0)
[    3.043241] videodev: Unknown symbol media_entity_remove_links (err 0)
[    3.043256] videodev: Unknown symbol media_device_register_entity (err 0)
[    3.043287] videodev: Unknown symbol media_entity_get (err 0)
[    3.043293] videodev: Unknown symbol media_device_unregister_entity (err 0)

Anyone knows how to fix this?

Zitat von dvbdvb

Anyone knows how to fix this?

Webcam drivers are not build by the dkms. Some of them made problems in the past and nobody of us needs them.

To fix it rebuild the sources of the dkms package with the needed drivers in the .config activated and add these drivers to the dkms.conf.
If you got it working, you can send patches.

Gerald

Zitat von gda

Webcam drivers are not build by the dkms. Some of them made problems in the past and nobody of us needs them.

To fix it rebuild the sources of the dkms package with the needed drivers in the .config activated and add these drivers to the dkms.conf.
If you got it working, you can send patches.

Gerald

thx. Will take a look but sounds complex, probably have to do without cam then. Regarding patches, the one below does not yet seem to be included but is readily available for quite some time now and would save some manual patching ;-).

Zitat von jeee

Please include the mutex patch

Diff

--- media-build-experimental-dkms-0~20140312.204530.orig/media-build-experimental-0~20140312.204530/linux/drivers/media/dvb-core/dvbdev.c	2014-03-21 10:04:22.306392000 +0100
+++ media-build-experimental-dkms-0~20140312.204530/media-build-experimental-0~20140312.204530/linux/drivers/media/dvb-core/dvbdev.c	2014-03-21 10:08:39.942392000 +0100
@@ -82,7 +82,11 @@
 		file->private_data = dvbdev;
 		replace_fops(file, new_fops);
 		if (file->f_op->open)
+    	{
+        	mutex_unlock(&dvbdev_mutex);
 			err = file->f_op->open(inode,file);
+        	mutex_lock(&dvbdev_mutex);
+    	}
 		up_read(&minor_rwsem);
 		//mutex_unlock(&dvbdev_mutex);
 		return err;

Alles anzeigen

I have seen this patch before and it is ugly. If this patch really is necessary, then there is something wrong in another place and has to be fixed there. Anyway, I don't accept patches to the driver itself, only to the package. This kind of patches have to be implemented by the driver developers.

Gerald

Zitat von gda

I have seen this patch before and it is ugly. If this patch really is necessary, then there is something wrong in another place and has to be fixed there. Anyway, I don't accept patches to the driver itself, only to the package. This kind of patches have to be implemented by the driver developers.

I am no programmer so if you say it is ugly it probably is ;-). If someone has a better way to do it that's even better of course. I think that it is required to be able to create a virtual/loopback device that otherwise get blocked because of the lock. Since the patch is already there since the 2.X kernel if someone can create a solution that is not ugly and can be integrated that be awesome.

thx

mrvanes

Your problem is related to this commit: https://git.kernel.org/cgit/li…9c32b5ae3313a3801cb66adf9
Try replacing all occurrences of 0666 with 0664 in ddbridge-core.c:

sed -i 's/0666/0664/' drivers/media/pci/ddbridge/ddbridge-core.c

EDIT: This way it compiles just fine for me, no idea if it actually works though.

Hi UFO.

Könnte dieses Problem ein Treiber Bug sein?

Gruß Patrick

Zitat von MegaX

Bitteschön

Patch

Diff

--- a/linux/drivers/media/pci/ddbridge/ddbridge.c
+++ b/linux/drivers/media/pci/ddbridge/ddbridge.c
@@ -145,6 +140,7 @@ static int __devinit ddb_probe(struct pci_dev *pdev,
 
 #ifdef CONFIG_PCI_MSI
    	if (msi && pci_msi_enabled()) {
+#define pci_enable_msi_block pci_enable_msi_exact
            	stat = pci_enable_msi_block(dev->pdev, 2);
            	if (stat == 0) {
                    	dev->msi = 1;

Gruß
MegaX

Hi,
habe gerade diesen Patch hier für den neuen Linux Kernel 3,16 gesehen. Habe eine S2-6400 und bin beim compilie auch auf den Fehler gestoßen.
Bin ein wenig unerfahren in Patch einspielen. Die Datei habe ich gefunden, nur wie lautet der Befehl zum einpielen des Patches.
Vielen Dank für Nachsicht
lg Martin