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?