Probleme mit dem erstellen der v4l Treiber für ein ARM System

SvenGWK · 11. Juli 2015

EDIT: Ein make modules_prepare im Kernelsourcenverzeichnis hatte ich vergessen. Nun klappt´s auch mit dem bauen.

Ich spiele derzeit in jeder freien Minute weiter mit dem Cubieboard herum, da ich die Hoffnung noch nicht aufgegeben habe selbst etwas hin zu bekommen.
Mittlerweile habe ich ein lauffähiges Trusty Ubuntu mit dem Mainline Kernel 4.2.0-rc1-00062-gc4b5fd3 auf dem Board.
Um die v4l zu kompilieren benötigt man ja die Kernelsourcen, ich will die Treiber auf dem Cubieboard selbst kompilieren.
Ich habe daher das Quellverzeichniss des Kernels vom Entwicklungsrechner nach /usr/src/4.2.0-rc1-00062-gc4b5fd3 verschoben.
Unter /lib/modules/4.2.0-rc1-00062-gc4b5fd3 liegen die beim kompilieren gebauten Kernelmodule.
Die in dem Ordner befindlichen Symlinks build und source habe ich nach /usr/src/linux-4.2.0 verlinkt.
So weit so gut (?).

Wenn ich die Treiber bauen lassen will schlägt dies jedoch recht schnell fehl:

Code

make[2]: Entering directory `/usr/src/4.2.0-rc1-00062-gc4b5fd3'
  CC [M]  /root/media_build/v4l/msp3400-driver.o
scripts/basic/fixdep: 1: scripts/basic/fixdep: Syntax error: "(" unexpected
make[3]: *** [/root/media_build/v4l/msp3400-driver.o] Error 2
make[2]: *** [_module_/root/media_build/v4l] Error 2
make[2]: Leaving directory `/usr/src/4.2.0-rc1-00062-gc4b5fd3'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/root/media_build/v4l'
make: *** [all] Error 2
build failed at ./build line 491.

Die Datei fixdep ist eine Binärdatei. Oder meint er die fixdep.c?
Ich weiss nicht wo ich anfangen könnte mit dem Fehlersuchen...
Oder ist der Kernel zu neu und damit inkompatibel?
Ich habe mir ausserdem testweise das Paket
linux-headers-4.2.0-040200rc1_4.2.0-040200rc1.201507051635_all
installiert und die Links mal dahin gebogen, funktioniert allerdings genau so wenig.

gda · 11. Juli 2015

Durch das fehlende make modules_prepare wurde fixdep nicht neu gebaut und hatte sicherlich eine falsche Architektur.

Gerald

SvenGWK · 11. Juli 2015

Ich habe im allgemeinen wohl aber ein Problem mit den gebauten Modulen. Sie lassen sich nicht laden.
es kommt immer die Meldung modprobe:

Code

ERROR: could not insert '[i]jeweiliger Modulname[/i]' : Exec format error

Ich versuche jetzt noch einmal alles sauber von vorn zu beginnen, war zum Ende doch recht chaotisch und ich war mir nicht mehr sicher ob das die Kernelsourcen aus dem heruntergeladenen Paket waren oder die mit denen der Kernel gebaut wurde.
Oder hat dieser Fehler eine andere Ursache?

dmesg sagt nach dem versuchten laden:

Code

si2157: version magic '4.2.0-rc1-00062-gc4b5fd3-dirty SMP ARMv7 p2v8 ' should be '4.2.0-rc1-00062-gc4b5fd3 SMP ARMv7 p2v8 '

Der hier beschriebene Workaround fnktioniert nicht, nach modprobe finde ich nach wie vor den gleichen Fehler vor.

Ich habe auf einer Seite gelesen, dass zur Verwendung der v4l Treiber vor dem kompilieren des Kernels alles was mit DVB zu tun hat deaktiviert werden muss. Ist dem so?

wirbel · 11. Juli 2015

Bau doch kernel, module und v4l direkt auf dem ARM ohne cross compiler - der kann in aller Ruhe in der Nacht werkeln.
Zum Vergleich: Kernel bauen braucht auf einem banana (dual core) etwa 2-2,5h. Dann sollte das cubie doch in vier das gleiche schaffen.

SvenGWK · 11. Juli 2015

Ich habe mir damit geholfen, dass ich den Kernel noch einmal kompiliert habe.
Allerdings habe ich vorher unter scripts/setlocalversion die Versionskontrolle entschärft.
Mein neuer alter Kernel ist jetzt nicht mehr "dirty" und die (ebenfalls noch einmal gebauten) Module werden geladen.

Code

WARNING: You are using an experimental version of the media stack.
        As the driver is backported to an older kernel, it doesn't offer
        enough quality for its usage in production.
        Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
        8783b9c50400c6279d7c3b716637b98e83d3c933 [media] SMI PCIe IR driver for DVBSky cards
        f459aec2bc81a46b674901424295f8ffe5e29ad0 [media] lmedm04: NEC scancode cleanup
        275ddb40bcf686d210d86c6718e42425a6a0bc76 [media] rc-core: remove the LIRC protocol
WARNING: You are using an experimental version of the media stack.
        As the driver is backported to an older kernel, it doesn't offer
        enough quality for its usage in production.
        Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
        8783b9c50400c6279d7c3b716637b98e83d3c933 [media] SMI PCIe IR driver for DVBSky cards
        f459aec2bc81a46b674901424295f8ffe5e29ad0 [media] lmedm04: NEC scancode cleanup
        275ddb40bcf686d210d86c6718e42425a6a0bc76 [media] rc-core: remove the LIRC protocol
dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
axp20x 0-0034: uevent
axp20x 0-0034: uevent
axp20x 0-0034: uevent
i2c-dev: adapter [Mygica T230 DVB-T/T2/C] registered as minor 2
i2c i2c-2: adapter [Mygica T230 DVB-T/T2/C] registered
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Mygica T230 DVB-T/T2/C)
i2c-core: driver [si2168] registered
i2c 2-0064: uevent
si2168 2-0064: probe
i2c-dev: adapter [i2c-2-mux (chan_id 0)] registered as minor 3
i2c i2c-3: adapter [i2c-2-mux (chan_id 0)] registered
i2c i2c-2: Added multiplexed i2c bus 3
si2168 2-0064: Silicon Labs Si2168 successfully attached
i2c i2c-2: client [si2168] registered with bus id 2-0064
i2c-core: driver [si2157] registered
i2c 3-0060: uevent
si2157 3-0060: probe
i2c i2c-3: master_xfer[0] R, addr=0x60, len=1
si2157 3-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
i2c i2c-3: client [si2157] registered with bus id 3-0060
usb 2-1.1: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
input: IR-receiver inside an USB DVB receiver as /devices/platform/soc@01c00000/1c1c000.usb/usb2/2-1/2-1.1/input/input3
dvb-usb: schedule remote query interval to 100 msecs.
dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_cxusb

Alles anzeigen

Sieht meines Erachtens erstmal gut aus.
Werde mich mal an den VDR machen...

wirbel · 11. Juli 2015

Wenn jetzt noch die fw passt, wird die Karte funzen.

SvenGWK · 11. Juli 2015

Funktioniert.
Einige wichtige Plugins funktionieren noch nicht, aber ich denke mein "Projekt" ist auf einem guten Weg.

Laut syslog funktioniert alles, ich kann jedoch nicht streamen. Kommt nichts an.

SvenGWK · 12. Juli 2015

Ich habe mich da anscheinend zu früh gefreut.
Mit der channels.conf von meinem anderen VDR empfange ich EPG Daten, sehe ich im kive plugin.
Der Versuch einen Sender zu streamen schlägt jedoch fehl.
w_scan scheint etwas zu finden, jedoch hinterlässt es dann doch eine leere channels.conf:

Code

root@minivdr:~# w_scan -fc -c DE >> channels.conf
w_scan version 20130331 (compiled for DVB API 5.10)
using settings for GERMANY
DVB cable
DVB-C
scan type CABLE, channellist 7
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> CABLE "Silicon Labs Si2168": very good :-))


Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.a
frontend 'Silicon Labs Si2168' supports
INVERSION_AUTO
QAM_AUTO
FEC_AUTO
FREQ (55.00MHz ... 862.00MHz)
SRATE (1.000MSym/s ... 7.200MSym/s)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
73000: sr6900 (time: 00:00) sr6875 (time: 00:03)
81000: sr6900 (time: 00:05) sr6875 (time: 00:08)
113000: sr6900 (time: 00:11) sr6875 (time: 00:13)
121000: sr6900 (time: 00:16) sr6875 (time: 00:18)
129000: sr6900 (time: 00:21) sr6875 (time: 00:23)
137000: sr6900 (time: 00:26) sr6875 (time: 00:28)
145000: sr6900 (time: 00:31) sr6875 (time: 00:33)
153000: sr6900 (time: 00:36) sr6875 (time: 00:38) (time: 00:40)
161000: sr6900 (time: 00:41) sr6875 (time: 00:44)
169000: sr6900 (time: 00:46) (time: 00:48)
sr6875 (time: 00:49)
314000: sr6900 (time: 00:51) (time: 00:53)
sr6875 (time: 00:54) (time: 00:56)
322000: sr6900 (time: 00:57) sr6875 (time: 01:00) (time: 01:02)
330000: sr6900 (time: 01:03) (time: 01:04) signal ok:
        QAM_AUTO f = 330000 kHz S6900C999
Info: no data from NIT(actual)
338000: sr6900 (time: 01:16) (time: 01:17) signal ok:
        QAM_AUTO f = 338000 kHz S6900C999
Info: no data from NIT(actual)
346000: sr6900 (time: 01:29) (time: 01:30) signal ok:
        QAM_AUTO f = 346000 kHz S6900C999
Info: no data from NIT(actual)
354000: sr6900 (time: 01:42) (time: 01:43) signal ok:
        QAM_AUTO f = 354000 kHz S6900C999
Info: no data from NIT(actual)
362000: sr6900 (time: 01:55) (time: 01:56) signal ok:
        QAM_AUTO f = 362000 kHz S6900C999
Info: no data from NIT(actual)
370000: sr6900 (time: 02:09) (time: 02:10) signal ok:
        QAM_AUTO f = 370000 kHz S6900C999
Info: no data from NIT(actual)
378000: sr6900 (time: 02:22) (time: 02:23) signal ok:
        QAM_AUTO f = 378000 kHz S6900C999
Info: no data from NIT(actual)
386000: sr6900 (time: 02:35) (time: 02:36) signal ok:
        QAM_AUTO f = 386000 kHz S6900C999
Info: no data from NIT(actual)
394000: sr6900 (time: 02:48) (time: 02:49) signal ok:
        QAM_AUTO f = 394000 kHz S6900C999
Info: no data from NIT(actual)
402000: sr6900 (time: 03:02) (time: 03:03) signal ok:
        QAM_AUTO f = 402000 kHz S6900C999
Info: no data from NIT(actual)
410000: sr6900 (time: 03:15) (time: 03:16) signal ok:
        QAM_AUTO f = 410000 kHz S6900C999
Info: no data from NIT(actual)
418000: sr6900 (time: 03:28) sr6875 (time: 03:31)
426000: sr6900 (time: 03:33) (time: 03:34) signal ok:
        QAM_AUTO f = 426000 kHz S6900C999
Info: no data from NIT(actual)
434000: sr6900 (time: 03:46) (time: 03:47) signal ok:
        QAM_AUTO f = 434000 kHz S6900C999
Info: no data from NIT(actual)
442000: sr6900 (time: 03:59) (time: 04:00) signal ok:
        QAM_AUTO f = 442000 kHz S6900C999






..
..
..
..
..




        QAM_AUTO f = 714000 kHz S6900C999
Info: no data from NIT(actual)
722000: sr6900 (time: 24:15) sr6875 (time: 24:17)
730000: sr6900 (time: 24:20) (time: 24:21) signal ok:
        QAM_AUTO f = 730000 kHz S6900C999
Info: no data from NIT(actual)
738000: sr6900 (time: 24:33) (time: 24:34) signal ok:
        QAM_AUTO f = 738000 kHz S6900C999
Info: no data from NIT(actual)
746000: sr6900 (time: 24:46) (time: 24:47) signal ok:
        QAM_AUTO f = 746000 kHz S6900C999
Info: no data from NIT(actual)
754000: sr6900 (time: 24:59) sr6875 (time: 25:02)
762000: sr6900 (time: 25:04) sr6875 (time: 25:07)
770000: sr6900 (time: 25:09) sr6875 (time: 25:12)
778000: sr6900 (time: 25:14) sr6875 (time: 25:17)
786000: sr6900 (time: 25:19) sr6875 (time: 25:22)
794000: sr6900 (time: 25:24) sr6875 (time: 25:27)
802000: sr6900 (time: 25:29) sr6875 (time: 25:32)
810000: sr6900 (time: 25:35) sr6875 (time: 25:37)
818000: sr6900 (time: 25:40) sr6875 (time: 25:42)
826000: sr6900 (time: 25:45) (time: 25:46) signal ok:
        QAM_AUTO f = 826000 kHz S6900C999
Info: no data from NIT(actual)
834000: sr6900 (time: 25:58) sr6875 (time: 26:00)
842000: sr6900 (time: 26:03) sr6875 (time: 26:05)
850000: sr6900 (time: 26:08) sr6875 (time: 26:10)
858000: sr6900 (time: 26:13) sr6875 (time: 26:15)
tune to: QAM_AUTO f = 330000 kHz S6900C999
(time: 26:18) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 338000 kHz S6900C999
(time: 26:30) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 346000 kHz S6900C999
(time: 26:42) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 354000 kHz S6900C999
(time: 26:55) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 362000 kHz S6900C999
(time: 27:07) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 370000 kHz S6900C999
(time: 27:19) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 378000 kHz S6900C999
(time: 27:31) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 386000 kHz S6900C999
(time: 27:43) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 394000 kHz S6900C999
(time: 27:56) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 402000 kHz S6900C999
(time: 28:08) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 410000 kHz S6900C999
(time: 28:20) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 418000 kHz S6900C999
(time: 28:32) ----------no signal----------
tune to: QAM_AUTO f = 418000 kHz S6900C999  (no signal)
(time: 28:33) ----------no signal----------
tune to: QAM_AUTO f = 426000 kHz S6900C999
(time: 28:34) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 434000 kHz S6900C999
(time: 28:47) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 442000 kHz S6900C999
(time: 28:59) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 450000 kHz S6900C999
(time: 29:11) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 458000 kHz S6900C999
(time: 29:23) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 466000 kHz S6900C999
(time: 29:35) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 498000 kHz S6900C999
(time: 29:48) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 522000 kHz S6900C999
(time: 30:00) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 530000 kHz S6900C999
(time: 30:12) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 538000 kHz S6900C999
(time: 30:24) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 546000 kHz S6900C999
(time: 30:37) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 554000 kHz S6900C999
(time: 30:49) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 562000 kHz S6900C999
(time: 31:02) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 570000 kHz S6900C999
(time: 31:14) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 578000 kHz S6900C999
(time: 31:27) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 586000 kHz S6900C999
(time: 31:39) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 594000 kHz S6900C999
(time: 31:52) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 602000 kHz S6900C999
(time: 32:04) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 610000 kHz S6900C999
(time: 32:17) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 618000 kHz S6900C999
(time: 32:29) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 626000 kHz S6900C999
(time: 32:41) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 642000 kHz S6900C999
(time: 32:53) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 650000 kHz S6900C999
(time: 33:05) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 658000 kHz S6900C999
(time: 33:18) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 666000 kHz S6900C999
(time: 33:30) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 674000 kHz S6900C999
(time: 33:43) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 682000 kHz S6900C999
(time: 33:55) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 690000 kHz S6900C999
(time: 34:07) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 698000 kHz S6900C999
(time: 34:20) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 706000 kHz S6900C999
(time: 34:33) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 714000 kHz S6900C999
(time: 34:45) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 722000 kHz S6900C999
(time: 34:58) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 730000 kHz S6900C999
(time: 35:11) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 738000 kHz S6900C999
(time: 35:23) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 746000 kHz S6900C999
(time: 35:35) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
tune to: QAM_AUTO f = 826000 kHz S6900C999
(time: 35:47) Info: no data from PAT
Info: no data from SDT(actual)
Info: no data from NIT(actual)
dumping lists (0 services)
Done.

Alles anzeigen

Woran kann sowas liegen?

wirbel · 12. Juli 2015

Zitat von SvenGWK

Ich habe mich da anscheinend zu früh gefreut.
(..)
Woran kann sowas liegen?

Zitat

Wenn jetzt noch die fw passt, wird die Karte funzen.

SvenGWK · 12. Juli 2015

Das war es zum Glück nicht. Scheint sich um eine Art Hardwareproblem zu handeln.
Wenn ich den Hub und alles andere entferne, funktioniert es.
Bin mir nur noch nicht recht schlüssig ob es die Stromversorgung oder die "Peripheriegeräte" sind die da Probleme machen.

Probleme mit dem erstellen der v4l Treiber für ein ARM System

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema