Bladeinger

I don't know, if it's the right place to post this, but I'll give it a try. A few weeks ago I stumbled upon MeshCentral and I am deeply impressed. The functionality is awesome! Now, that the number of my agents is reaching 100, I want to change the database to an external one, as recommended. Should be very easy, you start MeshCentral with the parameter "--dbexport", change the database in the config and start MeshCentral with the parameter "--dbimport". But how do I do this in unraid? I searched the web and tried several things in the terminal, but nothing works. Any suggestions on that? Any help is greatly appreciated! Edit: Found the answer by myself! It has to be done in the running Docker Container via terminal. If anyone needs to know how, feel free to contact me.

I think, that would be nice, especially according to upcoming unraid updates. With the right Hardware-ID, there would be no need to build special drivers for any new unraid version. I am on a business trip until Monday, so if anyone gives me instructions how to do it, I am willing to flash the firmware next week.

I just had a Phone Call with TBS distibution in Germany to clarify what the problem with this card is. And indeed, they already knew about the issue. There has been a mistake in the firmware flashing with the last productions series of theese cards. As the very friendly guy at TBS could see by the serial number of my card, my card was the second in this series of cards with the wrong hardware-id. He told me, that there will be a new driver with this hardware-id included. Perhaps there will be also a firmware update, that corrects the id. But this is not sure atm.

It's a few days ago and I tried a lot of things to get this running, PLUS I am an old guy 😉, but as far as I can remember, the driver did not install automatically. I think, I had an "unknown device" in device manager and installed via "Get driver", pointing to the directory of the unpacked driver. After this, it installed without any problem. But this behaviour is not that uncommon to me, regarding windows driver installations...

Is this what you mean?:

Great!

It just worked, no additional steps needed.

This is finally working! Question is, why this card throws the wrong id... And everytime a new unraid vewrsion comes out, the driver file would have to be modified again? Here are the information you requested: And thanks again! unraid-test-diagnostics-20211102-0627.zip

Thank you very much for your effords and your patience. Will definitely buy you some beers...

Yes, still no /dev/dvb. Also tried with lower case letters. Same result.

As requested: root@UNRAID-Test:~# modprobe -vvv tbsecp3 modprobe: INFO: custom logging function 0x40be50 registered insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/mc/mc.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/v4l2-core/videodev.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/common/videobuf2/videobuf2-common.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/common/videobuf2/videobuf2-memops.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/common/videobuf2/videobuf2-vmalloc.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/dvb-core/dvb-core.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/i2c/i2c-mux.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/dvb-frontends/tas2101.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/dvb-frontends/gx1133.ko.xz insmod /lib/modules/5.10.28-Unraid/kernel/drivers/media/pci/tbsecp3/tbsecp3.ko.xz modprobe: INFO: context 0x427500 released root@UNRAID-Test:~#

Sure. Please stand by...

With capital letters, it fails, with lowercase letters it throws no error message, but is still not loading the card:

I took a look in the uncompiled driver package and found this: Could this be the hint we were searching for?

Ok, here we go: root@UNRAID-Test:~# modprobe dvb_core root@UNRAID-Test:~# lsmod Module Size Used by dvb_core 106496 0 videobuf2_vmalloc 16384 1 dvb_core videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_common 49152 3 videobuf2_vmalloc,dvb_core,videobuf2_memops videodev 184320 1 videobuf2_common mc 32768 3 videodev,dvb_core,videobuf2_common md4 16384 0 sha512_ssse3 45056 1 sha512_generic 16384 1 sha512_ssse3 cmac 16384 1 cifs 528384 3 libarc4 16384 1 cifs xt_nat 16384 6 xt_CHECKSUM 16384 1 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT veth 24576 0 xt_tcpudp 16384 27 ip6table_mangle 16384 1 ip6table_nat 16384 1 iptable_mangle 16384 1 nf_tables 180224 0 vhost_net 24576 1 tun 45056 4 vhost_net vhost 28672 1 vhost_net vhost_iotlb 16384 1 vhost tap 24576 1 vhost_net xt_conntrack 16384 2 xt_MASQUERADE 16384 10 nf_conntrack_netlink 45056 0 nfnetlink 16384 3 nf_conntrack_netlink,nf_tables xt_addrtype 16384 2 iptable_nat 16384 1 nf_nat 40960 4 ip6table_nat,xt_nat,iptable_nat,xt_MASQUERADE nf_conntrack 110592 5 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_MASQUERADE nf_defrag_ipv6 16384 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack br_netfilter 24576 0 md_mod 45056 10 nct6775 53248 0 hwmon_vid 16384 1 nct6775 ip6table_filter 16384 1 ip6_tables 28672 3 ip6table_filter,ip6table_nat,ip6table_mangle iptable_filter 16384 1 ip_tables 28672 3 iptable_filter,iptable_nat,iptable_mangle x_tables 28672 13 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle atlantic 155648 0 igb 176128 0 i2c_algo_bit 16384 1 igb dm_mod 102400 4 dax 36864 1 dm_mod edac_mce_amd 32768 0 kvm_amd 90112 6 kvm 421888 1 kvm_amd mpt3sas 237568 10 crct10dif_pclmul 16384 1 crc32_pclmul 16384 0 crc32c_intel 24576 13 ghash_clmulni_intel 16384 0 aesni_intel 364544 1 crypto_simd 16384 1 aesni_intel cryptd 16384 2 crypto_simd,ghash_clmulni_intel nvme 36864 2 raid_class 16384 1 mpt3sas scsi_transport_sas 32768 1 mpt3sas nvme_core 53248 5 nvme i2c_piix4 24576 0 mxm_wmi 16384 0 glue_helper 16384 1 aesni_intel wmi_bmof 16384 0 rapl 16384 0 ccp 69632 1 kvm_amd wmi 24576 2 wmi_bmof,mxm_wmi i2c_core 45056 5 videodev,i2c_algo_bit,igb,dvb_core,i2c_piix4 ahci 40960 4 k10temp 16384 0 libahci 28672 1 ahci button 16384 0 acpi_cpufreq 16384 0 root@UNRAID-Test:~#

Hi ich777. Do you see any chance to get this card working? I am sure that the card is ok and recognized by the mainboard correctly, as I can pass it through to a Windows VM and there it works fine. Yesterday i tried to switch the card to another PCIe-Slot. Didn't make any difference. What about forcing the driver to load via modprobe? Unfortunately I couldn't find out on which chip this card is based. Thank you for your help in advance.

I disabled the PCIe ACS override now and switched back to the TBS OS drivers. Rebooted - Card still not recognized.

Changed the drivers, still no luck:

Thank you for your quick answer. Yes, I read the first thread before installation, installed the plugin according to the instructions given there and changed the driver to TBS. Attached you find the Diagnostics file, as requested. unraid-test-diagnostics-20211030-0618.zip

Thank you very much for your work for the community! May I ask a question, please? I am running unraid 6.9.2 and installed today a TBS6903X. The card is shown under "System Devices": [544d:6178] 07:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card But the Plugin doesn't recognized it. To check, if everything is ok, I passed the controller through to a windows VM in unraid and it works fine. What can I do to make the Plugin see the Card? Any help is highly appreciated.