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.
Posts by tmn505
-
-
Not yet. When introduced I didn't want to bother with additional library, but since it's packaged now I'll try it in few days.
-
From the ones failing I only use suspendoutput and sometime femon. These are not managed in vdr-projects and I'm not author of these patches. I'll carry them in my fork.
-
So we did overlap: https://github.com/tmn505/vdr4arch/commits/tmn505. Check the "vdr: bump version to 2.7.3" commit, I did import some patches from forum and seahawk1986, which resulted in only burn and dfatmo plugins not building.
-
Please tag the release.
-
AFAIK it's not maintained anymore, so looking around the forum is the the main course, see [ANNOUNCE] VDR Version 2.7.1 freigegeben.
seahawk1986 maintains Ubuntu ppa https://launchpad.net/~seahawk1986-hotmail and he's very prompt on the updates. You can find patches there for some of the unmaintained plugins.
-
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 have only one USB port
So You've got the newer version. I don't have any experience with that one. They probably removed first-boot from USB.
Please post output of "cat /proc/mtd" and upload copies of first two partitions (bootloader and its environment). Maybe I can figure out from strings what changes they made.
-
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:
CodeMay 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.
-
It doesn't, but would be nice to have such capability.
-
Do you know the Password for expert mode?
Don't know that yet, will try to figure it out once I get back to it (probably in spring).
As a side note You can test if command is valid, for example run "Tombea --color ?; echo$?", if output is 0 command is available.
-
There is a litescan patch for EPG scan floating around the forum: RE: [Gelöst] WinTV dualHD - Moduloption um nur einen Tuner zu nutzen? , which is modernized patch from this post: RE: minisatip für Server und Client
BTW if You measured, how much of power consumption difference is there?
-
Continued because of 10000 character limit.
Code
Display MoreURI expertmode.html /stream= /jsonrpc /jsonrpc? /fwupload /dfupload /rootfsupgrade /shell /putfile /getfile/ /reboot /transcoding /scanlist /storage? /view? /status /service /expertmode /enable? /disable? /set /set? /get? /syslog /version /tuninglog /tuninglog?clear /satippresets /stationlist /stationlist?clear /stationlist?start /stationlist?stop /stationlist?edit /stationlist?add /signalquality?bar /signalquality?line /signalquality /signalstrength?bar /signalstrength?line /signalstrength /signalquality /signalstrength?bar /signalstrength?line /signalstrength /signalerrorrate?bar /signalerrorrate?line /signalerrorrate /signalcwerrors?bar /signalcwerrors?line /signalcwerrors /signalmpegerrors?bar /signalmpegerrors?line /signalmpegerrors /signalhistory /signalhistory? /tunerstatus /dvbctune? /dataforward?bar /dataforward?line /dataforward :12345/executecommand /reportdestination /dbgcommand /debugvariables /setdebugvariable /cachedproperties /properties /getcachedproperty /getproperty /setproperty /executecommand /tune /pids /startreceiving /stopreceiving /channellist/channellistdownload.xml /channellist/SatelliteDetection.zip Examples /dbgcommand: calls dbgcommand() with value of 'Command' curl -d "{\"Command\":\"syslog _IP_ADDRESS_\"}" _IP_ADDRESS_:12345/dbgcommand /reportdestination: sets the device report UDP destination to 'Host' and 'Port' curl -d "{\"Host\":\"_IP_ADDRESS_\",\"Port\":12345}" _IP_ADDRESS_:12345/reportdestination /properties: returns all device properties curl _IP_ADDRESS_:12345/properties /cachedproperties: returns all cached properties curl _IP_ADDRESS_:12345/cachedproperties /getcachedproperty: gets one cached property curl -d "{ \"ID\": \"lock\"}" _IP_ADDRESS_:12345/getcachedproperty /getproperty: gets one device property curl -d "{ \"ID\": \"lock\"}" _IP_ADDRESS_:12345/getproperty /setproperty: sets one device property curl -d "{ \"ID\":\"init\", \"Type\":1, \"Value\":999 }" _IP_ADDRESS_:12345/setproperty /debugvariables: gets the debug variables curl _IP_ADDRESS_:12345/debugvariables /setdebugvariable: sets a debug variable with 'Name' and 'Value' curl -d "{\"Name\":\"DisableEIT\",\"Value\":1}" _IP_ADDRESS_:12345/setdebugvariable /tune: Executes a Tune command curl -d "{\"BandwidthKhz\":8000,\"FrequencyKhz\":474000,\"Type\":1}" _IP_ADDRESS_:12345/tune /pids: Executes a pid command. Allowed are 'Set', 'Add' and 'Remove' with an array of integers curl -d "{\"Add\":[17,18,20,101,102,103,104,105,108,201,1501,2101,3101,3201,3301]}" _IP_ADDRESS_:12345/pids /startreceiving: Start receiving data and send it via UDP to 'Address' and 'Port'. If nothing is specified then data is not sent curl -d "{\"Address\":\"_IP_ADDRESS_\",\"Port\":5000}" _IP_ADDRESS_:12345/startreceiving /startreceiving: Start receiving data and send it via TCP to 'Port'. If nothing is specified then data is not sent curl -d "{\"Port\":5000,\"TCP\":true}" _IP_ADDRESS_:12345/startreceiving /stopreceiving: Stop receiving data curl _IP_ADDRESS_:12345/stopreceiving /executecommand: Executes a JSON command curl -d "{\"Command\":\"PowerOff\"}" _IP_ADDRESS_:12345/executecommand
-
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):
Code
Display MoreUsage ### Normal output ### You can query the program whether an option is supported or not, by appending a question mark immediately after the option name. The program will terminate and return exit code 0 if the option is supported, or exit code 1 otherwise. -D, --no-fork do not fork into background -F, --fork fork into background -i <board_id> use <board_id> -l <license_file> use <license_file> --port-rtsp <port> use port <port> instead of 554 for RTSP --port-http <port> use port <port> instead of 80 for HTTP --port-ext-http <port> use port <port> instead of 8080 for HTTP redirect --netstream <ip_addr> use netstream at <ip_addr> --tuners <n> use max <n> tuners, default is use all --tuners-start <n> start with tuner <n>, default is 1 --short-version print version number, then exit (for script usage) --long-version print banner and version number only, then exit --version same as --long-version --show-ip show MAC and IP address of this machine --show-ports show RTSP and HTTP ports used --verbose verbose console output --show-commandline print command line before starting the program --help print this help (same as -?) --standby go to standby mode when idle (default) --no-standby do not go to standby mode --standby-delay <sec> set standby delay to <sec> seconds, default is 10 --no-streaming-led do not use blue streaming LED --watchdog use watchdog timer --no-watchdog do not use watchdog timer --watchdog-delay <msec> set watchdog delay to <msec> ms, default is 1000 --reboot-on-exit do not terminate watchdog, will cause reboot on exit --xcode-check check XCode version for compatibility --no-xcode-check do not check XCode version for compatibility --phy-reconfig reprogram GMAC PHY for compatibility --no-phy-reconfig do not reprogram GMAC PHY for compatibility --xcode-version print Vixs XCode version numbers, then exit --alternate-discovery use alternate non-Sat-IP discovery for DVB-C --no-alternate-discovery use Sat-IP discovery for DVB-C ### Hidden options? ### --convert-tftp convert firmware to TFTP format? --tftp alias to convert-tftp? --convert-usb convert firmware to USB format? --usb alias to convert-usb? --port alias to one of port options? --dump-rtsp ? --dump-http ? --dump-jsonrpc ? --update update system with new firmware? --reboot reboot after flashing new firmware? --enable ? --disable ? --set ? --defaults ? --ovewrite ? ### Devmode options? ### --emulate-satip DVB-C: emulate SAT>IP protocol --remove-cabletable DVB-C: clear SAT>IP to DVB-C station cache --erase-satip-presets DVB-C: erase SAT>IP to DVB-C station cache --debug-vixsdevice setting 'vixsdevice' debug level to 0x%02X --log-tunes logging all tune commands, collapsing duplicates --log-dupe-tunes logging all tune commands, allow duplicates --csv-tunes logging and dumping all tune commands (.csv) --html-tunes logging and dumping all tune commands (.html) --create-station-list creating station list --csv-station-list creating and dumping station list (.csv) --html-station-list creating and dumping station list (.html) --keep-station-list creating and keeping persistent station list --idle-scan running background channel scan during standby --no-idle-scan disabling background channel scan during standby --idle-scan-now start idle scan right after system boot --idle-scan-later start idle scan after first interval is elapsed --idle-scan-interval setting idle scan interval to <num> seconds --log-signal-history logging signal quality history, depth = <seconds?> --csv-signal-history logging and dumping signal quality history (.csv) --html-signal-history logging and dumping signal quality history (.html) --wrong-inversion coping with wrong inversion parameter --detect DVB-S: run regular LNB detection in background --multiswitch DVB-S: set FrontEnd to Standard Multiswitch Mode --quattro Quattro Mode (internal multiswitch) --modulator Modulator Mode ('Sat1' input only, no LNB power) --demo Demo Mode (only 'Sat1' input active) --straight Straight Multiswitch Mode (1:1 tuner to LNB map) --record-program <p> <f> record program number <p> to file <f> --audio1 <a1> record audio track <a1> as first audio --audio2 <a2> record audio track <a2> as second audio --duration <min> record for maximum <min> minutes --signal-stats DVB-C: collect signal quality data in background --no-signal-stats DVB-C: don't collect signal data in background --auto-reset-ber DVB-C: auto reset BER when no change --no-auto-reset-ber DVB-C: don't auto reset BER when no change --colors using colors for debug output --signal-stats collecting regular signal statistics --no-signal-stats not collecting regular signal statistics --auto-reset-ber auto resetting signal BER statistics when no change --no-auto-reset-ber not auto resetting signal BER statistics when no change --detect running regular LNB detection in background --recvbufsize setting XCode Receive Buffer Size to %u (0x%x) --debug-vixshal setting 'vixshal' debug level to 0x%02X --debug-xcode setting 'xcode' debug level to 0x%02X --dump-program dumping xcode parameters for program %d --fake-emergency fake emergency pending, countdown is %u --hardwait DVB-S FrontEnd: setting HardWait to TRUE --softwait DVB-S FrontEnd: setting HardWait to FALSE --hmrfilter DVB-S FrontEnd: using HMR filter for STV6120 tuner --no-hmrfilter DVB-S FrontEnd: not using HMR filter for STV6120 tuner (NOT recommended!) --debug-wait DVB-S FrontEnd: setting DebugWait --i2c-bustimeout DVB-S FrontEnd: setting Vixs I2C bus timeout to %d I2C clocks --i2c-busclock DVB-S FrontEnd: setting Vixs I2C bus clock to %dkHz --i2c-readtimeout DVB-S FrontEnd: setting Vixs I2C read timeout to %dms --i2c-writetimeout DVB-S FrontEnd: setting Vixs I2C write timeout to %dms --debug-frontend DVB-S FrontEnd: setting 'frontend' debug level to 0x%02X --debug-gpio DVB-S FrontEnd: setting 'gpio' debug level to 0x%02X --debug-i2c DVB-S FrontEnd: setting 'i2c' debug level to 0x%02X --resetfrontendonerror DVB-C FrontEnd: enabling automatic tuner reset --no-resetfrontendonerror DVB-C FrontEnd: disabling automatic tuner reset --enhancedtune DVB-C FrontEnd: enabling enhanced tuning algorithm --no-enhancedtune DVB-C FrontEnd: disabling enhanced tuning algorithm --et alias to enhancedtune? --no-et alias to no-enhancedtune? --autospectruminversion DVB-C FrontEnd: enabling automatic spectrum inversion --no-autospectruminversion DVB-C FrontEnd: disabling automatic spectrum inversion --asi alias to autospectruminversion? --no-asi alias to no-autospectruminversion? --trackspectruminversion DVB-C FrontEnd: enabling tracking of spectrum inversion --no-trackspectruminversion DVB-C FrontEnd: disabling tracking of spectrum inversion --tsi alias to trackspectruminversion? --no-tsi alias to no-trackspectruminversion? --extendedcarriersearch DVB-C FrontEnd: enabling extended carrier search --no-extendedcarriersearch DVB-C FrontEnd: disabling extended carrier search --ecs alias to extendedcarriersearch? --no-ecs alias to no-extendedcarriersearch? --alwaysrestartdemod DVB-C FrontEnd: generally restart demod at every tune --no-alwaysrestartdemod DVB-C FrontEnd: don't restart demod at every tune --ard alias to alwaysrestartdemod? --no-ard alias to no-alwaysrestartdemod? --restartsondemodreset DVB-C FrontEnd: setting max number of restarts on demod reset to %dms --no-restartsondemodreset DVB-C FrontEnd: disabling restarts on demod reset --rdr alias to restartsondemodreset? --no-rdr alias to no-restartsondemodreset? --enable-7mhzbandwidth DVB-C FrontEnd: enabling 7MHz bandwidth support for DVB-C --disable-7mhzbandwidth DVB-C FrontEnd: disabling 7MHz bandwidth support for DVB-C --tuningsettletime DVB-C FrontEnd: setting tuning settle time to %dms --tst alias to tuningsettletime? --demodresetdelay DVB-C FrontEnd: setting demod reset delay to %dms --drd alias to demodresetdelay? --i2c-readdelay DVB-C FrontEnd: setting MaxLinear I2C read delay to %dms --hardware-revision DVB-C FrontEnd: setting hardware revision to v0.1 or v0.2
-
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:
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.
Ich habe inzwischen auch Buildlogs gefunden:
6.3.11-1 (bookworm)
6.1.38-1 (sid)
Leider sind die nicht wirklich hilfreich.
Beim 6.3.11 findet man die SAA7146-Header erwähnt, beim 6.1.38 nicht.
Das wars eigentlich schon an Info. Kann aber auch sein, dass ich was übersehen habe.
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:
Coderoot@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:
-
I get this error: insmod: ERROR: could not insert module budget-core.ko: Unknown symbol in module.
What's dmesg output after You try to insmod the drivers? Might be there's some config symbol that is needed.
-
That warning should be harmless. Put a file '/etc/depmod.d/updates.conf' with content search updates (for details check man page for depmod.d), then run depmod and after that You should be able to load the driver.