It doesn't, but would be nice to have such capability.
Beiträge von tmn505
-
-
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
Alles anzeigenURI 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
Alles anzeigenUsage ### 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.
-
The issue is that Debian 12 has kernel 6.1. There budget-ci driver got moved to 'staging/media/deprecated' and Debian maintainer didn't notice it or discarded the driver from kernel config. So You'll need to install driver like mentioned in post #2 or try to compile this single module (and dependencies) from kernel sources. Something like this:
1. apt install linux-headers-$(uname -r) linux-source-6.1.
2. unpack tarball with kernel source from /usr/src to Your home directory (we don't want to compile as root)
3. enter source directory in Your home dir and run (this is one-liner):
make -C /lib/modules/$(uname -r)/build M=$(pwd)/drivers/staging/media/deprecated/saa7146 NOSTDINC_FLAGS="-I$(pwd)/drivers/media/common -I$(pwd)/drivers/media/dvb-frontends -I$(pwd)/drivers/media/tuners" CONFIG_VIDEO_SAA7146=m CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET_CI=m modules
4. copy all kernel modules (.ko extension) from 'drivers/staging/media/deprecated/saa7146' dir and its subdirs to '/lib/modules/$(uname -r)/updates'
5. run depmod -a
6. now You should be able to run modprobe budget-ci
Btw. report the lack of driver to the kernel maintainer in Debian, so it gets included.
Edit.
forgot to refresh the site, SHF said it all
-
biggsmann save this as a file with xspf extension:
XML
Alles anzeigen<?xml version="1.0" encoding="UTF-8"?> <playlist xmlns="http://xspf.org/ns/0/" xmlns:vlc="http://www.videolan.org/vlc/playlist/ns/0/" version="1"> <title>Playlist</title> <trackList> <track> <location>dvb-s2://frequency=10802750</location> <extension application="http://www.videolan.org/vlc/playlist/0"> <vlc:id>0</vlc:id> <vlc:option>dvb-polarization=H</vlc:option> <vlc:option>dvb-srate=22000000</vlc:option> <vlc:option>dvb-fec=3/4</vlc:option> <vlc:option>dvb-ts-id=1055</vlc:option> <vlc:option>program=5501</vlc:option> </extension> </track> </trackList> </playlist>
Open it in VLC, it should display HSE24 Extra HD channel. Naturally don't forget to stop VDR before.
For the TürkmenÄlem/MonacoSat test use this one:
XML
Alles anzeigen<?xml version="1.0" encoding="UTF-8"?> <playlist xmlns="http://xspf.org/ns/0/" xmlns:vlc="http://www.videolan.org/vlc/playlist/ns/0/" version="1"> <title>Playlist</title> <trackList> <track> <location>dvb-s://frequency=10804000</location> <extension application="http://www.videolan.org/vlc/playlist/0"> <vlc:id>0</vlc:id> <vlc:option>dvb-polarization=H</vlc:option> <vlc:option>dvb-srate=27500000</vlc:option> <vlc:option>dvb-fec=2/3</vlc:option> <vlc:option>dvb-ts-id=7478</vlc:option> <vlc:option>program=1</vlc:option> </extension> </track> </trackList> </playlist>
Should display Persiana Family HD.
-
The vb2 conversion patches have been posted: saa7146: please test the vb2 conversion!
Anyone having such hardware, please test them (and review if anyone is capable) and post feedback in this thread: [PATCHv2 00/19] saa7146: convert to vb2
-
Thanks for testing, now I know that my remote VDR with NVS 310, which I occasionally update, won't need hw update for now
-
Are You using softhddevice as output? I reported one bug w.r.t. glibc update: https://github.com/ua0lnj/vdr-plugin-softhddevice/issues/53. That's related to VAAPI, maybe VDPAU also triggers similar problem in different place.
-
Thanks lnj for posting this. I checked if there's something two days before the patch was sent.
Anyway, as already stated, Hans will work on striping analog video parts from the drivers. This will move it from staging back to maintained area. Should be at least easier to bring back the analog capabilities, when the driver is still in tree, if someone wants to do it. Sadly the OSD part of DVB API will go away and I don't think it'll ever come back.
After Hans will post changes to ML, it would be good to see some test feedback. One doesn't need to be subscribed to the ML, You can download raw message from kernel lore (https://lore.kernel.org/linux-media), example: https://lore.kernel.org/linux-…rkuil-cisco@xs4all.nl/raw. Open it in Your mail client, hit reply. To not break threading, fill 'In-Reply-To' field with 'Message-Id' of downloaded message (view the source of message to get it). That way it'll show the popularity of the driver.
If I'll be Cc-ed to the patch, I'll notify it here.
-
I doubt that that is possible.
I'm not sure, but Videobuf seems to be used to transfer the DVB-Data too.
Sorry, I should be more specific, I meant the budget cards supported by ttpci driver (didn't realize that saa7146 also support particular budget cards). From brief look at the source, only ttpci/budget-av.c contains videobuf references.
Btw. when zoran driver was removed and Corentin stepped-up to convert the driver, Hans responded with small check list: https://lore.kernel.org/linux-…c6-ea9036afac3d@xs4all.nl. Hope this helps, for me that's way over my head.
Falls das Anfang 2023 raus fliegt, ist es dann zuletzt in Kernel 6.1 als deprecated und in 6.0 regulär.
Wahrscheinlich wird 6.1 oder vielleicht 6.0 LTS Support bekommen.
Mit etwas Glück hält das bis Ende 2028, mindestens jedoch bis Ende 2025.
The 6.1 seem to be next LTS candidate.
Ich würde mir im Kernel aktuelle und gepflegte Treiber für Budget Karten wünschen.
As already mentioned, the videobuf code should be easily stripped from the ttpci driver. That would cause issues for someone wanting to also convert saa7146 driver, since both drivers currently are entangled with each other, and I personally don't want to do that until last moment.
Das scheint aber nicht möglich zu sein, bei dem derzeitigen Maintener (?).
Well, nobody asked or complained yet on the mailing list or #linux-media IRC channel on OFTC. I'll do that somewhere after Christmas (unless someone beats me to it), just want to give time for anyone wanting to convert saa7146 as well as the ttpci driver to videobuf2, so I don't thwart his/hers efforts.
-
Regarding the budget cards, aside from converting the driver to vb2, there's also possibility to simply strip the video input capabilities from the driver. We could probably convince Hans to do this himself, as apparently the vendor of Omnicom S2 PCI card is still selling it (https://www.omicom.info/PayPal_Omicom_S2_PCIr3.html, personally didn't try to order it). But as that would create not good position for full-featured cards, I won't post any request to Media ML until someone posts patches for removal of the driver.
-
As I'm not subscribed to linux-media@vger.kernel.org mailing list, just recently got aware that most part of drivers using videobuf version 1, have been moved to staging/media/depreciated area. This means that at some point these drivers could be removed if not converted to videobuf version 2 (maintainers wrote "some time next year"). The move started with https://lore.kernel.org/linux-…1455527ece2a@xs4all.nl/#t followed by https://lore.kernel.org/linux-…-hverkuil-cisco@xs4all.nl and https://lore.kernel.org/linux-…59-43c0b7f56486@xs4all.nl which in result landed in 6.1 kernel.
This post is to raise some awareness about it, as I don't have skills to do the driver conversion myself. Hope someone in VDR community can step-up and do the task.
-
Sorry, but that seems to be a made-up issue. Pacman will always complain if package is installed first time and the file, tracked by this package, already exists. Aside from the issue, putting the files to backup array is good idea. If the file has changed the new version will be installed as '.pacnew'.