Posts by tmn505

    That xlogin addition, as I described, is precisely for not starting X server manually or even logging user in, it handles everything for You (not much magic, everything in that project is plaintext, see for Yourself).

    Today I've tested X11+softhddevice on i3-3220T with Debian 12, that's 3rd gen, any 3rd gen i3 or i5 intel is dirt cheap and should work with Your mainboard (check compatibility), worked like charm with AVC broadcasts. The -v switch of softhddevice was va-api-egl (plain one has given me "video/vaapi: vaPutSurface failed: unknown libva error", while glx "video/glx: vaCopySurfaceGLX failed", probably I missed some dev dependency). No stuttering or hiccups. But before buying anything check if changing to va-api-egl helps with Your CPU.

    According to https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video Your CPU has hardware decoder for AVC, if that is what they broadcast, it should be fine. For it to work make sure to compile softhddevice with libva (VA-API), check https://wiki.debian.org/HardwareVideoAcceleration to familiarize Yourself what's needed (Arch Linux wiki also has good article about it). Just as reminder You'll probably need to set this "LIBVA_DRI3_DISABLE=1" as global variable for the decoding to work. As alternative to X11+softhddevice You could also try to use softhdcuvid's (https://github.com/jojo61/vdr-plugin-softhdcuvid) DRM plugin variant which doesn't use X11 at all, simply run with the plugin enabled and there should be image on TV (remember to shutdown X11 before).

    I personally use X11+softhddevice as an output, since that's been most stable and performant on my systems. As I use Arch Linux as base, I'll describe the setup only briefly, since some details might differ.

    There's this nice project called xlogin (https://github.com/joukewitteveen/xlogin), install it in Debian appropriate places, no need to start or enable its service. Download https://raw.githubusercontent.com/VDR4Arch/vdr4a…g/vdr-xorg.conf to /etc/systemd/system/vdr.service.d and that's it. Now each time You'll run vdr.service it'll pull xlogin as a dependency which will start X server to which softhddevice will be able to connect to. Remember to adjust -v option of the plugin, I use va-api-egl, You might find va-api to work better on Your hardware.

    If You're talking about devices in Your footer, then I'm using the same ones, except DuoFlexS2, and they work flawless with 6.6 kernel without any additional drivers or patches.

    It probably broke after this https://git.kernel.org/pub/scm/linux/…656c0b67e53cc80 which comes right after https://git.kernel.org/pub/scm/linux/…6d2b4e4cad703de. So revert 026ea897cb0731e29324536bae019512fa3dc13e and add "#include <linux/vmalloc.h>" to vtunerc_main.c. Compiles on my side, albeit with one warning:

    Code
    /srv/local/tomek/vtuner-ng/kernel/vtunerc_proxyfe.c:38:6: warning: no previous prototype for ‘dvb_proxyfe_set_stat’ [-Wmissing-prototypes]
       38 | void dvb_proxyfe_set_stat(struct vtuner_dtv_fe_stats *vtuner_stats, struct dtv_fe_stats *dvb_stats)
          |      ^~~~~~~~~~~~~~~~~~~~

    but should work nonetheless.

    I tried it today on both devices I have and they booted initramfs by default from either of USB ports to which the drive was connected. Maybe U-Boot on Yours does not recognize USB drive or initramfs file, try different USB stick. Do You have the newer device version with one USB port? Best option to troubleshoot is connect to UART port and attach console to it to see all messages or interact with U-Boot.

    For a quick test I uploaded my old initramfs image: https://www.mediafire.com/file/9ditdza0x…Boot_Image/file

    MD5 sum of the file: 934cc093dc20f733db9763c217078728

    To know if You booted from it, check available applications (double TAB), there should be minisatip and some others.

    Ich wollte das nachvollziehen, bin aber drüber gestolpert, dass das satip Binary noch kein DVBT(2) unterstützt: https://github.com/joed74/vtuner-…p_vtuner.c#L173 ff. - ist etwas überraschend, weil das Programm im Hilfetext anbietet die unterstützten Formate auf DVBT2 einzuschränken:

    Code
    May 16 10:34:00 [2996 satip_vtuner.c:230] debug: MSG_SET_PIDLIST:
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 0
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 16
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 17
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 18
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 19
    May 16 10:34:00 [2996 satip_vtuner.c:233] debug: 20
    May 16 10:34:21 [2996 satip_vtuner.c:175] debug: MSG_SET_FRONTEND
    May 16 10:34:21 [2996 satip_vtuner.c:206] error: unsupported delsys 16

    Found the same, some time ago when I tried it. I had to add small patch (in attachment) for DVB-T2(only) for it to work. Fortunately only msys and freq is needed for minisatip or SATPI to work, otherwise it would be impossible for me.

    Continued because of 10000 character limit.

    P.S. for anyone wanting to play with Tombea these are more-or-less ordered strings from the app (there is some "devmode" which I don't know how to activate):

    Bislang ist es mir nicht gelungen die Firmware-Version zu ändern, wird scheinbar irgendwo intern ausgelesen.

    Rename the firmware to "Elgato_UAB_Boot_Image" and place it on a FAT32 formatted USB stick. Plug it in to USB port and reboot. The device should boot firmware from USB stick. This won't leave any permanent changes to NAND flash, so if You want to go back, simply remove the stick and reboot.

    I would suggest connecting UART<->USB adapter to UART pins which are populated on J24, (I have the first version with 2 USB ports, might be different for newer one with single USB port), don't connect the first pin:

    Code
    ZIM-1900 VER:1.0
    
    J24: 1. VCC 3.3V, 2. TX, 3. RX, 4. GND
         ^

    After connecting terminal You'll see also messages from bootloader. If USB is inserted there are these messages:

    Code
    ***** USB AUTO FLASH *****
    SPI image Elgato_UAF_SPI not found
    SPI image Elgato_UAF_OTP not found
    Partition image Elgato_UAF_Boot_FW1 not found
    Partition image Elgato_UAF_Boot_Loader_0 not found
    Partition image Elgato_UAF_Boot_Loader_1 not found
    Partition image Elgato_UAF_UBoot_Env not found
    Partition image Elgato_UAF_Linux_Kernel_0 not found
    Partition image Elgato_UAF_Linux_Kernel_1 not found
    Partition image Elgato_UAF_AppFS_0 not found

    I didn't test these yet, but I assume each will replace corresponding partition contents on NAND flash.

    When I fiddled with the device, my goal was to put Tombea on different ports and block external access to them with iptables, then add minisatip as a client and use that as a server. Unfortunately I had limited time and with none sat cable available (have to change my sat installation) I had to postpone it indefinitely. Along the way I created a very crude build system, which would create a full firmware initramfs ready to be copied to USB stick. The build system needs rpm<=4.15.x, yum and yumbootstrap to create Fedora 8 chroot. The scripts are in attachment. Maybe You'll find some inspiration out of it. The flow of execution is:

    1. prepare-source.sh, 2. sudo prepare-chroot.sh, 3. build-firmware.sh

    Yess.. Jetzt hat's geklappt! ...Ich glaub ich hab vorher die tar als root entpackt, vllt. lag es daran ^^

    Good that's finally working.

    The issue is that kernel 6.1 introduced CONFIG_STAGING_MEDIA_DEPRECATED and it guards all the deprecated drivers. Although Debian enables staging media drivers for x86 arch, when config was refreshed for 6.1, maintainer either overlooked this or simply discarded. So if anyone wants these drivers in "bookworm", You'll need to submit a bug report.

    Btw the Debian kernel recipe is tracked in this repo: https://salsa.debian.org/kernel-team/linux (check respective branches for a particular release).

    So, I tried to reproduce Your error (had only systems with Debian 10 and 11) but the modules are found without issues by depmod and also load without issues. So You probably compiled against wrong kernel headers or loading modules against wrong kernel. Did You update system (kernel) in-between? For reference this is output of depmod:

    Code
    root@debian12:/lib/modules/6.1.0-10-amd64/updates# depmod -a -v | grep 'updates/'
    
    /lib/modules/6.1.0-10-amd64/updates/budget-core.ko needs "dvb_dmxdev_init": /lib/modules/6.1.0-10-amd64/kernel/drivers/media/dvb-core/dvb-core.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-core.ko needs "saa7146_wait_for_debi_done": /lib/modules/6.1.0-10-amd64/updates/saa7146.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-core.ko needs "ttpci_eeprom_parse_mac": /lib/modules/6.1.0-10-amd64/kernel/drivers/media/common/ttpci-eeprom.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-ci.ko needs "saa7146_unregister_extension": /lib/modules/6.1.0-10-amd64/updates/saa7146.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-ci.ko needs "dvb_ca_en50221_init": /lib/modules/6.1.0-10-amd64/kernel/drivers/media/dvb-core/dvb-core.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-ci.ko needs "ttpci_budget_debiwrite": /lib/modules/6.1.0-10-amd64/updates/budget-core.ko
    /lib/modules/6.1.0-10-amd64/updates/budget-ci.ko needs "rc_register_device": /lib/modules/6.1.0-10-amd64/kernel/drivers/media/rc/rc-core.ko

    and dmesg after loading budget-ci:

    Code
    [  996.902270] mc: Linux media interface: v0.10
    [  996.914926] saa7146: loading out-of-tree module taints kernel.
    [  996.914990] saa7146: module verification failed: signature and/or required key missing - tainting kernel
    [  996.917448] saa7146: register extension 'budget_ci dvb'