ich777

Your issue seems to be different since power well is something completely differnt, have you yet tried to disable power well? You can do that by adding this to your syslinux.config i915.disable_power_well=1 If the options do nothing for you (as you've previously mentioned the option enable_dc=0 in your case), you can always blacklist the module so that Unraid doesn't load it automatically on boot and enabling it in the go file like mentioned in my previous post with the line: modprobe i915 disable_power_well=1 or: modprobe i915 disable_power_well=1 enable_dc=0 Attention: If you have my Intel GPU TOP plugin installed it will also activate the iGPU so I would recommend that you uninstall it first before trying these options.

Just one since both the adapter and also the physical interface is PCIe x1, otherwise you would need a PCIe x2 or better speaking a x4 interface (I don't know a motherboard with a PCIe x2 interface. This one: Click Please note that this adapter is meant for Wifi cards but if it's enough for you to use one TPU it will work fine, please don't connect the USB Adapter since most Wifi/Bluetooth combo cards are using PCIe for Wifi and USB for Bluetooth and no, you won't be able to get the second TPU to work over USB. ATTENTION: You know that you have to make your own custom heat spreader for the Dual Edge TPU? If you don't do that this card will be a serious fire hazard <- this is also mentioned in the documentation (not the chip itself, the power regulation is most of the time the issue). You can create your own heat spreader from something like a M2 NVME heat spreader and a few thermal pads. I just wanted to point that out because this is very important!

First of all, I completely missed that you've mentioned me here. Can you please test this: Remove the iGPU from the bus with: echo "1" > /sys/devices/pci0000\:00/0000\:00\:02.0/remove (in this case I'm assuming that the iGPU is on the PCI bus on: 00:02.0) After that unload the module with: rmmod i915 Load the module again with enable_dc=0 with: modprobe i915 enable_dc=0 Then rescan the PCIe bus to again get your iGPU into the system with: echo "1" > /sys/bus/pci/rescan After that issue: cat /sys/module/i915/parameters/enable_dc And enable_dc should be at 0 again Please not that none of these command should print an error, rmmod for example should display nothing and modprobe also doesn't display anything. Please let me know if that is working on your platform. Maybe also try to play around with different power states for you iGPU and if enable_dc=2 is maybe working, even enabled_dc=3 can work:

Still the wrong thread. Please just reply in the support thread. No further support here.

You should reply in the support thread (you've even posted a screenshot where it is visible... ) : I said that already twice in my previous responses to your posts. Anyways, then your Steam Guard is not fully disabled. I have a account where it works fine, but you also have to disable Email codes so to speak Steam Guard entirely.

For now this is a permanent requirement, I can't tell why it isn't detected by the plugin, maybe the device is initialized to late. It won't hurt if you let this line in the go file, even when the card isn't installed anymore so to speak if you forget to remove it at some point.

Please don't start a new topic, you have to reply in the support thread. I have already posted an answer here and said that we should carry on in the appropriate support thread:

(this is the initial resolution for the container) BTW, the container also supports remote resizing, this means if you resize the browser window the container will also resize the Firefox application running inside the container to fill the browser window, to enable this: Click on the little arrow on the left side to open up the noVNC menu Click on the gear icon At scaling select "Server side scaling" Hope that helps.

I've took a quick look at this but I can't extend the plugin since this is basically a completely different chip. However I've looked at the linked repository and your board listed as upstreamed (this means basically that a patch was sent to the Kernel team to be implemented directly into the Kernel). Have you yet tried to add: acpi_enforce_resources=lax to your syslinux.conf? I'm not a huge fan from this option but at least you can try.

Please double check: Anyways, your problem is pretty obvious: Please read the description from the variables: and also the description from the container itself: If you have any further questions, please use the support thread.

I would recommend that you put the line: modprobe em28xx in your go file (/boot/config/go) so that it looks like this: #!/bin/bash # Load DVB drivers modprobe em28xx # Start the Management Utility /usr/local/sbin/emhttp & This is just a example but make sure to do it before emhttp starts to ensure that you load the driver before the Docker containers are starting. BTW, your Plex container should now start since the driver now loads from what I see in your syslog: Jun 7 00:56:20 catNAS kernel: mc: Linux media interface: v0.10 Jun 7 00:56:20 catNAS kernel: videodev: Linux video capture interface: v2.00 Jun 7 00:56:20 catNAS kernel: em28xx 1-12.1:1.0: New device HCW quadHD-A @ 480 Mbps (2040:846d, interface 0, class 0) Jun 7 00:56:20 catNAS kernel: em28xx 1-12.1:1.0: DVB interface 0 found: bulk Jun 7 00:56:20 catNAS kernel: em28xx 1-12.1:1.0: chip ID is em28174 Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xbd798474 Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: EEPROM info: Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: microcode start address = 0x0004, boot configuration = 0x01 Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: AC97 audio (5 sample rates) Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: 300mA max power Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: Table at offset 0x27, strings=0x126a, 0x1688, 0x087e Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: Identified as Hauppauge USB QuadHD ATSC (card=106) Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: dvb set to bulk mode. Jun 7 00:56:21 catNAS kernel: em28xx 1-12.1:1.0: chip ID is em28174 Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xbd798474 Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: EEPROM info: Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: microcode start address = 0x0004, boot configuration = 0x01 Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: AC97 audio (5 sample rates) Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: 300mA max power Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: Table at offset 0x27, strings=0x126a, 0x1688, 0x087e Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: Identified as Hauppauge USB QuadHD ATSC (card=106) Jun 7 00:56:22 catNAS kernel: em28xx 1-12.1:1.0: dvb ts2 set to bulk mode. Jun 7 00:56:22 catNAS kernel: em28xx 1-12.3:1.0: New device HCW quadHD-A @ 480 Mbps (2040:846d, interface 0, class 0) Jun 7 00:56:22 catNAS kernel: em28xx 1-12.3:1.0: DVB interface 0 found: bulk Jun 7 00:56:23 catNAS kernel: em28xx 1-12.3:1.0: chip ID is em28174 Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xc7798474 Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: EEPROM info: Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: microcode start address = 0x0004, boot configuration = 0x01 Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: AC97 audio (5 sample rates) Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: 300mA max power Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: Table at offset 0x27, strings=0x126a, 0x1688, 0x087e Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: Identified as Hauppauge USB QuadHD ATSC (card=106) Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: dvb set to bulk mode. Jun 7 00:56:24 catNAS kernel: em28xx 1-12.3:1.0: chip ID is em28174 Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xc7798474 Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: EEPROM info: Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: microcode start address = 0x0004, boot configuration = 0x01 Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: AC97 audio (5 sample rates) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: 300mA max power Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: Table at offset 0x27, strings=0x126a, 0x1688, 0x087e Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: Identified as Hauppauge USB QuadHD ATSC (card=106) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: dvb ts2 set to bulk mode. Jun 7 00:56:25 catNAS kernel: usbcore: registered new interface driver em28xx Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: Binding DVB extension Jun 7 00:56:25 catNAS kernel: mxl692 8-0060: MaxLinear mxl692 successfully attached Jun 7 00:56:25 catNAS kernel: dvbdev: DVB: registering new adapter (1-12.1:1.0) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: DVB: registering adapter 0 frontend 0 (MaxLinear MxL692 VSB tuner-demodulator)... Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'MaxLinear MxL692 VSB tuner-demodulator' registered. Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: DVB extension successfully initialized Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: Binding DVB extension Jun 7 00:56:25 catNAS kernel: mxl692 10-0063: MaxLinear mxl692 successfully attached Jun 7 00:56:25 catNAS kernel: dvbdev: DVB: registering new adapter (1-12.1:1.0) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: DVB: registering adapter 1 frontend 0 (MaxLinear MxL692 VSB tuner-demodulator)... Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'MaxLinear MxL692 VSB tuner-demodulator' registered. Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. Jun 7 00:56:25 catNAS kernel: em28xx 1-12.1:1.0: DVB extension successfully initialized Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: Binding DVB extension Jun 7 00:56:25 catNAS kernel: mxl692 12-0060: MaxLinear mxl692 successfully attached Jun 7 00:56:25 catNAS kernel: dvbdev: DVB: registering new adapter (1-12.3:1.0) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: DVB: registering adapter 2 frontend 0 (MaxLinear MxL692 VSB tuner-demodulator)... Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'MaxLinear MxL692 VSB tuner-demodulator' registered. Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: DVB extension successfully initialized Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: Binding DVB extension Jun 7 00:56:25 catNAS kernel: mxl692 14-0063: MaxLinear mxl692 successfully attached Jun 7 00:56:25 catNAS kernel: dvbdev: DVB: registering new adapter (1-12.3:1.0) Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: DVB: registering adapter 3 frontend 0 (MaxLinear MxL692 VSB tuner-demodulator)... Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'MaxLinear MxL692 VSB tuner-demodulator' registered. Jun 7 00:56:25 catNAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. Jun 7 00:56:25 catNAS kernel: em28xx 1-12.3:1.0: DVB extension successfully initialized Jun 7 00:56:25 catNAS kernel: em28xx: Registered (Em28xx dvb Extension) extension

Please open up a Unraid terminal and issue: modprobe em28xx_dvb or modprobe em28xx (please note that if you get no output then it was successful, please post your Diagnostics after you issued the commands, at least if one was successful) I think the second one should work for you fine and load the driver.

Please post your Diagnostics again.

I don't see the card in lspci, this could be because it hung up (didn't properly reset). Please try the following: Shut down the server Pull the power cord from the wall or flip the power switch at the power supply Press the power/reset button a few times (to empty the caps) Wait for at least 30 seconds Put power back to your server Power the server back on

I wonder where you have that information from, even if you search for FileIO latency and/or FileIO speeds (on your favorite search engine) you'll find multiple reports that it of course introduces some additional latency and in some cases really bad write/read performance. Sure, but that depends always on how it's set up. In case for Unraid it is maybe the case that this was a BTRFS RAID1 which adds a additional layer of complexity, Unraid is also using a FUSE file system, which BTW wasn't used as how the user was setting it up. Jumbo Frames shouldn't matter much when the right adapter is used, even on my Mellanox/Nvidia ConnectX3 card I can saturate the full 10Gbit/s with the default MTU from 1500. Exactly, but it is always my recommendation to use a single Block Device for the usage with iSCSI since I've seen users with really bad performance (<10MB/s) on FileIO and troubleshooting them in every single case can be very tedious since there are so many variables, even with Write-Back enabled. I haven't had any issues with FileIO back then but my use case shifted also to use only a single Block Device with Write Through. Agreed.

Please use the support thread for that, click on the container icon and select Support:

Please post your Diagnostics. Are you sure that the Plugin is still installed and not in the Plugins Error tab?

Please reboot, the driver is already modified and should work. Let me know if everything is working after you rebooted.

Can you describe a bit more in depth when the URLs should open or do you do this on a schedule with user scripts? If you are doing that with user scripts be careful since you can easily end up with many tabs open when you don‘t be careful. What I can tell for sure is that you are missing: su $USER right at the beginning.

I don‘t know if you can set up Authy in Authelia, I always thought that Authy is to manage your already existing 2FAs or am I wrong? This is also a thing you could/should look up in the documentation from Authelia.

Authy is completly different from Authelia. Authy is for accessing your 2FA tokens for logins to web apps Authelia is for securing web apps and putting it infront of you web apps I‘ve never said to avoid Authy, I pointed it out because it is for a completely different use case. Authelia was meant in this specific use case to secure the WebGUI and you simply can‘t do that with Authy because of above reasons, you can login to a website with your token but you can‘t secure a web site with Authy.

I'm not entirely sure, IIRC you should always, or at least it is recommended to use include and exclude if you want to sync only certain folders with a wildcard.

I can't reproduce this on my end, as said above I haven't tested if it also syncs the sub folders but it should. Please make sure that you create for exclude: /* And for include: /[p-zP-Z]*/ This makes sure to first exclude everything from the source directory and then look only for files/folder which start with letters from p-z (upper and lower case). Please also note that I have checked "Do NOT create extra directory".

I've now tried it on my own (sorry btw, I've wrote this from the top of my head and haven't tried it) and here is the solution: These are my test directories before the sync: and here they are after the sync: EDIT: Please note that I haven't tried it with files in the subfolders, but this pattern should work.

Do you also have the exclude pattern applied? Without it it won't work. Are you sure that you have the lower case letters first and the upper case ones after the lower case?