ich777

proc hat nichts mit der HDD led zu tuhen. Ich vermute eher das es das BTRFS Dateisystem ist oder hast du kein BTRFS?

Ah okay, got it, then the installation needs to be done in the Docker container. If you want to I can write a plugin which actually takes care of the creation from the dummy adapters and the mknod.

Please read the first recommend post on top of this thread.

As @Sundtek already pointed out not the whole installation, the creation from the dummy devices on the host should go to the go file and the installation in the TVH container is a one time thing as far as I understand it since the drivers are installed in the /config directory in the container.

Exactly, because the go file is executed every time the server boots and with this you ensure they are there. But what would be ultimately be my goal is to install everything on the host and then pass the "devices" /dev/dvbX to the container as usual (this should also work like if you pass through any other DVB card to a container or am I wrong?) and also check if eg: /dev/dvb0 is already there and create a new device for at the next free /dev/dvbX slot.

Server, in the syslog, maybe post the Diagnostics or send it via PM if you don't want to post it publicly.

Trust me I've been there, I tried it for about 3 days and did a lot of research... Even tried it with the Linux version but can't that get to work either.

Done, also skipped the gift card.

Jup I know, still no dice... In my WINE containers WINE32 and WINE64 is installed by default and I've tried it with both (also keep in mind that this post is from 2018...).

Please read the comment carefully it mentions to do this in on line and not as two separate commands: modprobe it87 ignore_resource_conflict=1 Please post the output again after issuing the command and also the output from: lsmod EDIT: Please forget that, you have a NCT chip on your Motherboard, so this driver won't help. You can however pass: acpi_enforce_resources=lax to your syslinux.config, but please be aware that this command can damage your hardware in very rare cases and I'm not a big fan from it. Should look like this: Please reboot afterwards and see if it changes anything.

I've now tried to create a container for Golden Eye: Source but can't get it to work. First of all you have to use WINE because on newer Linux distributions it won't work and even if I'm using WINE I still can't get it to work. Maybe that's also a reason why the other container that you've tried isn't working for you.

Then it would be best to simply put the creation from the dummy devices in the go file at the end (/boot/config/go). Anyways, I will try to get the one tuner from our local used market and see if I can create a plugin, will keep you updated.

Das ist leider eine gute Frage die ich dir nicht beantworten kann... Ich bin bei so propietären Server geschichten immer sehr sehr vorsichtig...

Can you also do the things that I've mentioned here:

Do you have AER errors in your syslog?

@Bcy please update the plugin to version 2022.11.02 and remove all custom options from your syslinux.config, go file and also from the modprobe.d folder since I've added a check if the modules is already enabled, if not it will enable it now automatically. Please reboot after you've disabled all modifications to syslinux.config, go file and also from the modprobe.d folder and updated the plugin Let me know if the module was loaded successful after the reboot.

What works best for you. Maybe go with your route with the modprobe.d folder and see if this works for you.

If you do it like that you have to create the file: /boot/config/modprobe.d/it87.conf with the contents: options it87 ignore_resource_conflict=1

I don't know... Please add the line: modprobe it87 ignore_resource_conflict=1 to your go file so that it looks something like this: #!/bin/bash # Enable unsupported IT87 modprobe it87 ignore_resource_conflict=1 # Start the Management Utility /usr/local/sbin/emhttp & You then can also remove: it87.ignore_resource_conflict=1 from your syslinux.config

Yes.

Please remove this from your syslinux.config: it87.force_id=0x8689 and try to reboot your server and see if it is working afterwards.

This is fine since it loaded the driver correctly and you can see it now also in the output from lsmod. Does it now show up in your Dashboard if you click detect again?

May I ask why you need Nerd Tools? Perl is now part from Unraid and doesn't need to be installed. BTW Perl was only needed if you clicked on Detect in the plugin, it was safe on older versions to uninstall it afterwards. Please remove that part, it shouldn't be necessary if you are using: it87.ignore_resource_conflict=1 What does happen when you issue: modprobe it87 ignore_resource_conflict=1 from a Unraid terminal? Can you post the output from: lsmod after you issued the command from above?

@pika & @knex666 & @tknz & @Marolo & @fireplex & @pk1057 Good news for all TBS users! I just asked Tom to include some necessary Kernel modules to Unraid which are needed to compile the TBS drivers and hopefully they make it into Unraid 6.11.2 so this basically means that the TBS driver package should be working again when Unraid 6.11.2 is released.

That was already clear to me but everything on the host is not persistent across reboots. You have to add that somewhere in /boot/config and run: bash /boot/config/sundtek_netinst.sh -dockerhost on every reboot, you can put that for example in the go file (/boot/config/go <- but please be careful with it since it basically starts the WebUI and everything else from Unraid at the end of the boot process, preferably I would put that before emhttp starts). What does the -dockerhost option exactly? Does it need to download something from the Internet or does it simply create the devices? As mentioned above, the easiest solution would be to create a plugin for that because then the users can download it from the CA App <- all applications for Unraid (Docker templates and Plugins) and don't have to worry about anything, then I think it would be also possible to install the driver on the host and the users can pass through the /dev/dvbX devices to the container as usual. I will maybe pick up the DVB-C adapter that is available on the used market near me.