[baltic]

Hi gr4vity,

well, the combination of actual kernel and legacy-driver works now, but the problem with the black screen after returning to F7 persists.

I have a prob on a workstation, witch looks a bit similar: The screensaver is set to "empty screen" and sometimes I only see the mouse pointer after activating the system. But there are two sensible differences:
- it's an intel-graphic and
- it happens infrequent on the ws, but it's 100% reproducible on the MLD

Greets
baltic

[gr4vity]

Hi baltic,

Please wait till Claus releases a newer nvidia legacy package tomorrow, i will try it myself as well because i have swtiched to intel driver and can't look further into that issue.

Claus, if you could tell me the exact steps you do to build crazycat media_build i will build it myself then will try to build vtuner and see if i can make it work.

Regards.

[baltic]

Hi gr4vity,

thanks for the info.
As I wrote earlier, it's not a prob for me, 'cause I use the keyboard with the vdr very rarely. So it will be very easy for me to stay patient. 

Greetings
baltic

[clausmuus]

You will find the Build rules in the Makefile of this package: http://minidvblinux.de/git/?a=tree&p=dvb-mb

[gr4vity]

Hi baltic,

That issue doesn't bother me either because i mostly use Tvheadend but it will be fine if it's fixed for all 

Hi Claus,

I have already checked that makefile since this reply of yours

cd /MLD
make checkout name=dvb-mb
cd dvb-mb
cat Makefile

Please understand that i use a slow pc at the moment so i don't want to spend hours building kernels then it fails then i start over and over again 
I need a simple step by step guide just like the wiki guide which is very simple to follow.

I have reached the following point

Code: [Select]

ln -fs ../.packages/kernel_5.3.11.202.34-202.35+root_amd64.deb package.deb
test -n "" || make -C $(test -e ../libs && echo ../libs || echo ..) libs
make[2]: Entering directory '/MLD/libs'
make[3]: Entering directory '/MLD/libs/libc6'
      libc6:
make[4]: Entering directory '/MLD/libs/libc6'
        Build package: libc6
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[6]: Entering directory '/MLD/libs/libc6'
make[6]: Leaving directory '/MLD/libs/libc6'
make[6]: Entering directory '/MLD/libs/libc6'
make[6]: Leaving directory '/MLD/libs/libc6'
make[6]: Entering directory '/MLD/libs/libc6'
make[6]: Leaving directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[5]: Entering directory '/MLD/libs/libc6'
make[5]: Leaving directory '/MLD/libs/libc6'
make[4]: Leaving directory '/MLD/libs/libc6'
        libc6_2.24-~1+root_amd64.deb is ready
make[3]: Leaving directory '/MLD/libs/libc6'
make[2]: Leaving directory '/MLD/libs'
make[1]: Leaving directory '/MLD/kernel'
  kernel_5.3.11.202.34-202.35+root_amd64.deb is ready
test ! -e .git || git checkout
M src/linux.config.x86
Your branch is up-to-date with 'origin/master'.
test -z "$(git log origin/master..HEAD --pretty=format: 2>&1)" || echo -e "P\tNot all commits are pushed"
Now, what i should do?
cd /MLD
git clone https://bitbucket.org/CrazyCat/media_build.git
./build

Then?
I need an already made makefile, i don't want to keep testing.

Regards.

[clausmuus]

After you enter the dvb-mb folder, you can simple call "make". The kernel will build only one time, not every time you made changes on the dvb-mb package (config,...)
The "make" in the dvb-mb folder will build this package and all depended packages (like the kernel) if they not already build.

[gr4vity]

To clean the docker cache, you must remove the Images you want to rebuild. Docker build only that pats new, thhat has chanded.

You can find the dvb-mb Makefile by this:

Code: [Select]

cd /MLD
make checkout name=dvb-mb
cd dvb-mb
cat Makefile
But maybe, you should took a look at the Makefile of the dvb-dddvb package. It's a bit simpler.

I already did that since the above reply but it failed

Code: [Select]

test -n "$deps" && echo -e "Sie können es durch folgende Eingabe installieren:"; \
test -n "$deps" && echo -e "sudo apt-get install$deps\n"; \
test -n "$deps" -a -n "" && (apt-get install -sqq libproc-processtable-perl firmware-linux-free firmware-zd1211 firmware-libertas atmel-firmware firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-linux firmware-myricom firmware-netxen firmware-qlogic firmware-misc-nonfree firmware-realtek midisport-firmware dahdi-firmware-nonfree bluez-firmware >/dev/null 2>&1 || echo -e "\n"); \
test -n "$deps" && rm -f Makefile.version; \
test -n "$deps" && (grep -q "^dvb-mb$" ../broken_packages.lst || echo dvb-mb >> ../broken_packages.lst); \
test -z "$deps"
Das für dvb-mb benötigtes Debian Paket libproc-processtable-perl fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-linux-free fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-zd1211 fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-libertas fehlt.
Das für dvb-mb benötigtes Debian Paket atmel-firmware fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-atheros fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-bnx2 fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-bnx2x fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-brcm80211 fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-intelwimax fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-ipw2x00 fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-ivtv fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-iwlwifi fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-linux fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-myricom fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-netxen fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-qlogic fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-misc-nonfree fehlt.
Das für dvb-mb benötigtes Debian Paket firmware-realtek fehlt.
Das für dvb-mb benötigtes Debian Paket midisport-firmware fehlt.
Das für dvb-mb benötigtes Debian Paket dahdi-firmware-nonfree fehlt.
Das für dvb-mb benötigtes Debian Paket bluez-firmware fehlt.
Sie können es durch folgende Eingabe installieren:
sudo apt-get install libproc-processtable-perl firmware-linux-free firmware-zd1211 firmware-libertas atmel-firmware firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-linux firmware-myricom firmware-netxen firmware-qlogic firmware-misc-nonfree firmware-realtek midisport-firmware dahdi-firmware-nonfree bluez-firmware

grep: ../broken_packages.lst: No such file or directory
../Makefile.tools:742: recipe for target 'dep' failed
make: *** [dep] Error 1
apt-get install libproc-processtable-perl firmware-linux-free firmware-zd1211 firmware-libertas atmel-firmware firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-linux firmware-myricom firmware-netxen firmware-qlogic firmware-misc-nonfree firmware-realtek midisport-firmware dahdi-firmware-nonfree bluez-firmware

Code: [Select]

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package firmware-bnx2 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package firmware-ipw2x00 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package firmware-iwlwifi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package firmware-qlogic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package midisport-firmware is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package firmware-linux is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package firmware-zd1211
E: Unable to locate package firmware-libertas
E: Unable to locate package atmel-firmware
E: Unable to locate package firmware-atheros
E: Package 'firmware-bnx2' has no installation candidate
E: Unable to locate package firmware-bnx2x
E: Unable to locate package firmware-brcm80211
E: Unable to locate package firmware-intelwimax
E: Package 'firmware-ipw2x00' has no installation candidate
E: Unable to locate package firmware-ivtv
E: Package 'firmware-iwlwifi' has no installation candidate
E: Package 'firmware-linux' has no installation candidate
E: Unable to locate package firmware-myricom
E: Unable to locate package firmware-netxen
E: Package 'firmware-qlogic' has no installation candidate
E: Unable to locate package firmware-misc-nonfree
E: Unable to locate package firmware-realtek
E: Package 'midisport-firmware' has no installation candidate
E: Unable to locate package dahdi-firmware-nonfree
E: Unable to locate package bluez-firmware


[clausmuus]

You can remove the line "deps = ..." in the Makefile and then try it again. Otherwise you musst add the needed debian package repositories to your docker installation to install the firmware packages.

[gr4vity]

Hi Claus,

1st option did the trick .. thank you.

I had to build i2c package too.

Code: [Select]

make[2]: Leaving directory '/MLD/dvb-mb'
grep -q ^Description: package/control/control || dpkg -s dvb-mb | grep ^Description: >> package/control/control
grep -q "Multi-Arch:" package/control/control || sed "/^Architecture:/aMulti-Arch: foreign" -i package/control/control
test "" || grep -q "Installed-Size:" package/control/control || sed "/^Description:/iInstalled-Size: $(du -s package/data | cut -f1)" -i package/control/control
find package/data -type f -exec md5sum {} \; | sed 's|package/data/||' > package/control/md5sums
cd package/control; tar -czf ../control.tar.gz ./*
cd package/data; tar --owner=root --group=root -czf ../data.tar.gz ./*
cd package; ar -r ../../.packages/dvb-mb_2019.11.20-29.4+5.3.11.202.34+root_amd64.deb debian-binary control.tar.gz data.tar.gz 2>/dev/null
ln -fs ../.packages/dvb-mb_2019.11.20-29.4+5.3.11.202.34+root_amd64.deb package.deb
test -n "" || make -C $(test -e ../libs && echo ../libs || echo ..) libs
make[2]: Entering directory '/MLD/libs'
make[2]: Leaving directory '/MLD/libs'
make[1]: Leaving directory '/MLD/dvb-mb'
  dvb-mb_2019.11.20-29.4+5.3.11.202.34+root_amd64.deb is ready
test ! -e .git || git checkout
M Makefile
Your branch is up-to-date with 'origin/master'.
test -z "$(git log origin/master..HEAD --pretty=format: 2>&1)" || echo -e "P\tNot all commits are pushed

One step left then game over. 

dvb-mb kernel modules are installed under /MLD/dvb-mb/lib/modules/5.3.11.202.34/kernel/drivers/media

If i want to build vtuner against dvb-mb i should edit makefile to what path?

/MLD/dvb-mb/src/dvb/linux
?
If i do that i receive an error no rule to make target modules

[gr4vity]

i think it's better if you can make dvb-mb-vtuner package so i simple run make to reproduce the error.

You said it's enabled already but i can't find it.

[clausmuus]

I think it's not possible to build the vtuner against the dvb-mb drivers. If it's possible, it's to complicated.
But the dvb-mb sources contains the vtuner. I only don't know why it would not be build. So, if you find the reason, you will get it

[gr4vity]

It sounds like a good deal 
But i need to reproduce the error, if i'm able to build dvb-mb package then there was no errors right?

#
# Tools to develop new frontends
#
CONFIG_DVB_DUMMY_FE=m
CONFIG_DVB_VTUNERC=m
# CONFIG_AUDIO_SUPPORT is not set
CONFIG_FRAME_VECTOR=m
CONFIG_MISC_DEVICES=y

It's true that vtunerc is enabled but there is no sign of vtuner files anywhere.

I even build dvb_dummy_fe module because it looks similar to vtuner but i don't know how it works.

dvb_dummy_fe files are in dvb-frontends folder however i don't know where are vtuner files .... any idea?

[clausmuus]

You can have a look in the init script of the satip package. there will be enable the vtuner. Maybe it's equal to the dvb-dummy-fe

[gr4vity]

Guten Morgen Claus,

I have successfully build dvb-mb package that contains vtuner module 
vtuner is inside dvb-frontends folder.
Thank you very much for being so patient answering my questions.
I have sent you the download link in pm.
Only problem is i have to start satip-client manually because vtuner will not work if satip-client started automatically.

Please check it and see if you can make dvb-mb-vtuner seperate package in order to work with satip-client.


 

[clausmuus]

What do you have changed to build the dvb-mb vtuner? Dou you have used the vtuner that is inside the dvb-mb sources, or do you have used the external vtuner sources?
Can you please send me a diff.