MLD-5.x > General
(MLD 5.4 testing) kernel 5.3.5.202.31 amd64
gr4vity:
Hello Claus,
Thank you very much, i already compiled vtuner module by changing the path in Makefile.
The funny thing is after i did all that i noticed that vtuner is already included in MLD 5.3.5 kernel sources :D :D
root@92bafaf276d7:/MLD/kernel/src/linux-5.3.5/drivers/media/vtuner# ls
Kconfig vtunerc.ko vtunerc.o vtunerc_main.o
Makefile vtunerc.mod vtunerc_ctrldev.c vtunerc_priv.h
modules.order vtunerc.mod.c vtunerc_ctrldev.o vtunerc_proxyfe.c
vtuner.h vtunerc.mod.o vtunerc_main.c vtunerc_proxyfe.o
So why you don't make it available for download in MLD 5.4 testing branch?
MLD> apt search vtuner
Sorting... Done
Full Text Search... Done
I think docker containers are similar to virtual machines in windows, i'm still learning about it though.
For ex.,
MLD> docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
mld/devel 5.4 cd043bf25c68 2 days ago 967MB
<none> <none> 01e85ee1f011 2 days ago 582MB
<none> <none> 220f8b9d5448 2 days ago 539MB
<none> <none> da6238eec7e8 2 days ago 101MB
<none> <none> 28e0fb4d2e31 2 days ago 101MB
debian stretch 4f5edfdf153f 6 days ago 101MB
MLD> docker rmi 01e85ee1f011
Error response from daemon: conflict: unable to delete 01e85ee1f011 (cannot be forced) - image has dependent child images
I don't know what are those images with <none> tag which i'm unable to delete :-\
Any idea?
I was playing around then installed an image called dperson/samba then deleted it so it's not one of those images.
Secondly,
docker network inspect bridge
"IPv4Address": "172.17.0.2/16",
What i can do with the container ip address?
clausmuus:
I'm not sure, but until my last tests with the vtuner module, it don't work. That's the reason why we disable the vtuner package. The vtuner module is added by a patch to the MLD kernel.
The docker image with tag <none> are layers, that are used by other images. In you case by the mld/devel image. Every block in the docker file create a layer. That's the normal way it works.
If you want to access the docker container from outside e.g. by ssh or scp, you must forward a port of the host to the internal used port. This is only possible on container creation time. But you can do a ssh connection from inside the container to outside without any problems. You must only install the ssh client package inside the container.
On our MLD development server we are running sometimes the develserver. This tool start a simple apt repository server that allow to install packages direct from the MLD docker container. But for this you must also configure a port forwarding into the container. you can find some info about it in the MLD wiki.
gr4vity:
I think i know why the vtuner module you tested didn't work because of this.
DEVICE:0 ADAPTER:1 FRONTEND:0 (vTuner proxyFE DVB-S2)
FE_QPSK Fmin=0MHz Fmax=2MHz
It should be FE_QPSK Fmin=950MHz Fmax=2150MHz
The vtuner module which i build yesterday works fine,
Do you want that i upload it here?
By the way i wanted to compile crazycat media_build in order to fix my SNR measurement problem but it failed.
Do you know how to fix that?
* Start building *
******************
make -C /MLD/media_build/v4l allyesconfig
make[1]: Entering directory '/MLD/media_build/v4l'
No version yet, using 5.3.5.202.31
make[2]: Entering directory '/MLD/media_build/linux'
Applying patches for kernel 5.3.5.202.31
patch -s -f -N -p1 -i ../backports/api_version.patch
patch -s -f -N -p1 -i ../backports/pr_fmt.patch
patch -s -f -N -p1 -i ../backports/debug.patch
patch -s -f -N -p1 -i ../backports/drx39xxj.patch
Patched drivers/media/dvb-core/dvbdev.c
Patched drivers/media/v4l2-core/v4l2-dev.c
Patched drivers/media/rc/rc-main.c
make[2]: Leaving directory '/MLD/media_build/linux'
./scripts/make_kconfig.pl /lib/modules/5.3.5.202.31/build /lib/modules/5.3.5.202.31/build 1
Preparing to compile for kernel version 5.3.5
File not found: /lib/modules/5.3.5.202.31/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4.
Makefile:387: recipe for target 'allyesconfig' failed
make[1]: *** [allyesconfig] Error 2
make[1]: Leaving directory '/MLD/media_build/v4l'
Makefile:26: recipe for target 'allyesconfig' failed
make: *** [allyesconfig] Error 2
can't select all drivers at ./build line 545
root@92bafaf276d7:/MLD/media_build#
File not found: /lib/modules/5.3.5.202.31/build/.config
Should i change the path in make_kconfig.pl ?
clausmuus:
Thank you for the test with the vtuner. Can you please post a diff to fix it.
Until your media_build build there is an absolute path "/lib/modules/5.3.5.202.31/...". I think this must be the path to the mld kernel.
Dou you have take a look to our dvb-mb package. That is our old media_build package. If you want to use it as template, you mut check it out "make checkout name=dvb-mb" and than remove the first line of the Makefile because that disable the package.
clausmuus:
Please test the "dvb-vtuner" package of MLD unstable.
You can use the "satip" package to configure and activate the vtuner connection.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version