[gr4vity]

Hello,

Where i can find linux-headers-5.3.5.202.31?
As i want to install a module that i use frequently on pc (for ex. vtuner) on MLD distro but i can't because it won't work (error message invalid module format).

I was thinking about using my pc kernel on MLD then copied the modules directory and some of the boot files then ended up with boot failure.

I restored the boot files however MLD HD screen will hang up for 3-4 minutes then it will start booting normally, how i can solve that issue?

Best regards.

[clausmuus]

Why du you want to build the vtuner modul? If you use the VDR, you can use the satip plugin and do not need the vtuner modul.

The problem with the vtuner and the 5.3 kernel ist, that I don't know about vtuner sources for that.
But if you realy want to build the modul, you can find a documentation on how to set up a MLD development enviroment and how to build MLD packages in the MLD wiki.

[gr4vity]

Thanks clausmuus for replying,
I have a problem with VDR satip, it doesn't work properly with diseqc although it works fine when i compiled it on Raspberry pi using raspbian not MLD.

Actually, i want to use my custom kernel which supports blindscan.
It's not just a module i want to build.
MLD kernel 5.3 shows SNR like this
Lock   (0x1f) Signal= 58.00% C/N= 27.40% postBER= 0
Lock   (0x1f) Signal= 58.00% C/N= 27.20% postBER= 0
Lock   (0x1f) Signal= 58.00% C/N= 27.00% postBER= 0

Which is not correct, it should be 70%
In fact it should be shown in dB not %
My custom kernel supports showing SNR in dB as well.

Is it possible to build the whole kernel for MLD?

[gr4vity]

I restored the boot files however MLD HD screen will hang up for 3-4 minutes then it will start booting normally, how i can solve that issue?

What about that problem?
MLD HD screen will be displayed for 3-4 minutes no matter if i selected quiet, verbose or snapshots.
Then it will continue booting normally.
Is there anyway to fix that?
I reinstalled syslinux but the problem wasn't solved.


There is another issue i want to report,
grab shows screenshots in negative colors as in the attachment.
Is that a known issue?

[clausmuus]

It is necessary to aktivate some kernel settings for the MLD. Fer example you must build in the btrfs file system. Also the kernel must support lzma kompressed initramfs. A full list of special settings is here: http://minidvblinux.de/git/?a=viewblob&p=kernel&h=ea3261971571e0820cf5d1b90aebedea066da131&hb=dfe88b033d796c5a60390f5c1dcf054a2f81297a&f=src/README
Also you can find the MLD kernel konfig file here: http://minidvblinux.de/git/?a=viewblob&p=kernel&h=c5ebcda89324a8bd212458b63a0570cf822b232b&hb=dfe88b033d796c5a60390f5c1dcf054a2f81297a&f=src/linux.config.x86

The problem with the colors are known. This is an issue of some grafic cards.

I don't know the problem of your restored MLD kernel. But you sould be able to boot the snapshot boot option and than restore an older version. Also you can boot an MLD USB Image and select there the snapsoh tool in the bootloader and also in the web interface.

[gr4vity]

Okay, i think i need time to learn about compiling MLD kernel 

What about building MLD module, regarding this tutorial:
http://www.minidvblinux.de/wiki/mld/entwicklung/54_entwicklungsumgebung

MLD 5.4 x64 is installed on USB 2.0 stick, if i followed that tutorial, it will take ages to compile right?

- i already tried to restore an older version however the problem wasn't solved.
The problem is i deleted the files in the fat16 partition then after i got a boot failure i copied them manually.

Perhaps there are some permissions i need to adjust?

- I think grab works fine using Nvidia graphic cards, the attachment is for Intel card although it works fine on my ubuntu pc.

[clausmuus]

You are right. That is the description, how to compile (or create) MLD packages (also the kernel package). The MLD development enviroment is a docker container that also can run on a MLD system.
You can follow all steps up to capture 3. At step 2.5 you needn't do the call "make" in the "MLD" folder. At that step enter the kernel folder (cd kernel) and there call "make" to build only the MLD kernel. To change the kernel config simple do a "make menuconfig" in the kernel folder. After the first "make" you will found the kernel sources in the folder src/linux/

The MLD do not use the grub boot loader. We are using the syslinux boot loader. The original MLD boot files are not only placed at the first partition. They are also stored on the second partition in the boot folder. To see them, you must unmount the first partition, whitch is mounted also to the /boot folder and so hide the files on the second partition.

[gr4vity]

make -C src/linux-5.3.5 menuconfig 
make[1]: Entering directory '/MLD/kernel/src/linux-5.3.5'
  UPD     scripts/kconfig/mconf-cfg
  HOSTCC  scripts/kconfig/mconf.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf  Kconfig


*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

make[1]: Leaving directory '/MLD/kernel/src/linux-5.3.5'
cp src/linux-5.3.5/.config src/linux.config.x86
touch src/linux-5.3.5/.config
root@92bafaf276d7:/MLD/kernel#


Hi Claus,
I followed the tutorial successfully but i run out of space.
Please check the attachments.
Is it possible to delete /dev/sdb3 then resize /dev/sdb2 to gain more space?
Or do i have to buy a new SSD and start the whole process again?

Now i want to compile the kernel in the below link
https://gitlab.com/updatelee/v4l-updatelee

How i can do that?


* i will discuss the boot problem later.

[gr4vity]

dpkg: error processing archive /tmp/apt-dpkg-install-MLu7TN/6-iptables_1.6.0-3+5.3.5.202.31_amd64.deb (--unpack):
 trying to overwrite '/lib/modules/5.3.5.202.31/kernel/net/802/stp.ko', which is also in package network-wireless-drivers 0-10.2+5.3.5.202.31
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

By the way, i had to remove the network wireless drivers to be able to install docker.

[clausmuus]

Thank you for the info. I have fix the network-wireless-drivers package. You should get an update until the next half hour.

[clausmuus]

It is possible to use the space of the sdb3 device by resizing the root partition.
Therefor you must first remove the mount of the sdb3 device from the /etc/fstab . There sould be some lines that contain the device. One line by device id and some bind mounts of the /mnt/... device mount point. If you do not have any data on the partition it sould be secure to do so. After that change you must reboot the system. Be award, to add a new data device, if you plan to make any recordings.
Now you can remove the sdb3 partition with fdisk and expand the sdb2 partition. After a second reboot you can use the btrfs tool to resize the sdb2 partition to use the new space.

I never have test this, but I think it should be work.

It is also possible to start the MLD development docker container on any other PC witch can run docker container. Maybe that's a more simple way if you have one with more free space.

[gr4vity]

Okay, i have 7.1GB free space instead of 1.7GB  on sdb2 partition. 
I already tried that many times on Android SD cards distros but i had to ask you 1st just to make sure.

It's my 1st time to use that docker container so i'm still learning about it.
I had installed it by access MLD from my Raspberry pi 3 via ssh.
Now, when i start docker container i can see MLD folder via ssh but i can't access it using samba on the Raspberry pi.

- How i can paste the module source folder inside docker container in order to compile it?
- Do i have to modify the module Makefile because it points to /usr/src/linux-headers-5.3.5.202.31

[clausmuus]

You do not need to change the dockerfile. You have a full linux (debian) system inside the docker container. So you can inside install packages, call a "git clone", use scp to copy files,...
You can also install and start a samba server if you want. You must only know, that no init scripts will be start automatically inside the docker container.
After you have build the new kernel, you can copy it by scp to outside (after you have installed it).

[gr4vity]

You do not need to change the dockerfile. You have a full linux (debian) system inside the docker container.

If you tried the application in the above screenshot, you will not say that 
You can read about it here
https://www.linuxtv.org/wiki/index.php/UpdateDVB
In order to make the application work, you must install the kernel in the link i posted.
I don't understand why you are against it, maybe there is something i should know so please tell me.

Beim ersten “make” wird nach dem Namen und der E-Mail-Adresse gefragt. Dies wird insbesondere benötigt, wenn man Änderungen einchecken möchte. Dann werden diese Informationen ins Logfile geschrieben.

I was not asked about any name or email, why?

[clausmuus]

You do not have a physical PC inside the docker container, but you can use all functions of a linux system (debian) inside it. If you want to access the hardware of the host, you must make that available by additional docker create options.

By the way:
If you want to build a driver for the MLD system, you must give the build tool the path to the MLD kernel sources. You can find examples for that in some of the dvb-... packages (e.g. the dvb-dddvb package).

It is no problem to use an other kernel for the MLD. But the kernel must support some features as I describe before.

You will only be ask for you name and email if you build the whole MLD system. Since you build only one package, you will not asked.