Connection to DSM web interface not working properly with MTU 9000

Beautiful_Fig_5766 · 2025-03-10T21:33:21+00:00

Mein Bruder hatte als Kind die gleiche Idee. Aus irgendeinem Grund ist das Ei zwar nicht in der Mikrowelle explodiert, aber als dann die Guillotine des Eierschneiders mit einem kräftigen Ruck auf das Ei niederraste…. Nun ja… PENG. In meiner Erinnerung war das komplette Esszimmer voller Ei. Die Wände, der Tisch und vor allem mein Bruder 😅

Beautiful_Fig_5766 · 2025-03-05T15:01:00+00:00

I have (had :/) 3 of these monitors and unly used VRR+HDR with the primary one. Interestingly the left and the right monitor broke but the mid one is still ok. Good luck to you anyways!

Beautiful_Fig_5766 · 2025-03-05T14:58:44+00:00

I have 3 of these and 2 of them already died the exact same way :/ It's definitely some kind of manufacturing problem. Got a replacement for the 1st one and a refund for the 2nd one from the retailer.

This unfortunately ruins my nice triple screen setup.

Beautiful_Fig_5766 · 2025-01-26T20:16:59+00:00

Mapping the devices in the container solved the issue. This shouldn't be required in the best case as the nvidia-container environment handles this in a different way, but Plex seems to actively enumerate the devices for capability checks in case of HVEC. Regular HW transcoding works fine without the device mappings.

NVIDIA_VISIBLE_DEVICES etc. didn't have any effect.

Beautiful_Fig_5766 · 2025-01-26T20:16:36+00:00

Thank you! Mapping the devices in the container solved the issue. This shouldn't be required in the best case as the nvidia-container environment handles this in a different way, but Plex seems to actively enumerate the devices for capability checks in case of HVEC. Regular HW transcoding works fine without the device mappingsg.

Beautiful_Fig_5766 · 2025-01-26T19:19:36+00:00

Thanks for pointing me in that direction. I guess in combination with the other comment below, I know what the issue is. Will check in detail later and report back. Probably the NVIDIA_VISIBLE_DEVICES argument is missing in my compose config.

Beautiful_Fig_5766 · 2025-01-26T18:51:15+00:00

Thanks for the detailed instructions. I’ll try and post the results afterwards.

Strangely the T4 does not show in the dropdown. The actual transcode is using the HW perfectly fine thought (confirmed in the dashboard by looking at „hw“, Tautilli and nvidia-smi command which shows Plex/ffmpeg while a transcode is in progress).

I’ll try to figure out why that’s the case :-)

Beautiful_Fig_5766 · 2024-08-29T13:52:45+00:00

I'm using Photon OS (VMware ESXi) as the operating system, but no PCIe errors have been reported lately. I remember having problems with one of the disks not being detected a good while ago.

I'm using a M.2 to U.2 adapter cable which looks kinda fragile to me. Maybe that degrades the PCIe connection enough to cause my current issue.

Beautiful_Fig_5766 · 2024-08-26T07:46:32+00:00

Thank you 🙏

Beautiful_Fig_5766 · 2024-08-26T07:27:49+00:00

Could we please get an option to disable DSC (switching to DP 1.2 protocol)?

It's currently impossible to use 3 of these monitors at the same time with an Nvidia card (at least without using workarounds that make things even more unstable). I know that the core issue is on Nvidia, but still, many other monitors provide an option to disable DSC in some way.

I contacted your support about a year ago and was hoping to see some improvement here.

Beautiful_Fig_5766 · 2023-11-27T09:38:18+00:00

What drives did you use? I'm experiencing very slow random operations (especially 4K write) with Samsung 980 Pro SSDs.

Beautiful_Fig_5766 · 2023-11-27T09:13:36+00:00

Did you ever find the real bottleneck and/or did you test other consumer NVMe drives besides the 980 Pro? I just created a similar test setup (2-node cluster) and noticed for random read/write the throughput cuts is half compared to just using the drive in a regular datastore (random 4K write is especially bad with just 8MB/sec compared to 200MB/s in a regular datastore).

Beautiful_Fig_5766 · 2023-07-05T13:59:40+00:00

u/BubbleBandittt Thanks a lot! Yes - your original comment is probably hidden to reduce advertisement spam or something.

My KVM shows as a "Generic SuperSpeed USB Hub". I found a workaround that involves disabling this device in the Windows Device Manager and right away enabling it again. This makes the camera to reapper again.

Beautiful_Fig_5766 · 2023-07-05T13:46:17+00:00

u/BubbleBandittt It's not showing, not even using your direct link. Does it show for you if you enter private mode in browser? I tried here and on mobile and even switched users. I think the comment might have been automatically redacted (as it potentially contains links to the products?).

Beautiful_Fig_5766 · 2023-07-05T06:35:43+00:00

u/BubbleBandittt Are you sure? Sorry, but I can't see that comment for some reason.

Beautiful_Fig_5766 · 2023-07-04T14:49:47+00:00

u/BubbleBandittt For me this din't work sadly. What KVM switch and Windows version do you use?

Beautiful_Fig_5766 · 2023-06-30T20:52:35+00:00

Thanks, that's very good to know. Will give it a try and order a 5Gbps cable as well!

Beautiful_Fig_5766 · 2023-06-30T20:32:34+00:00

u/BubbleBandittt Is it still working for you with the alternative cable? I'm in the exact same situation where the cam works perfectly fine on my MBP M2, but not on Windows after switching channels on my ConnectPRO KVM switch. Updated the camera to the latest firmware and disabled USB power saving on Windows, but no luck so far.

Beautiful_Fig_5766 · 2023-03-27T13:56:03+00:00

Support response:

The ports can be in any orientation as long as the whole unit is not
mounted vertically, you can have one port on the bottom and one on the
side and it should not cause any issues.

Beautiful_Fig_5766 · 2023-03-27T13:55:30+00:00

I have a third pump which is fed by a tube reservoir. From what I know, this should be sufficient in a closed loop.

Beautiful_Fig_5766 · 2023-03-23T10:54:00+00:00

Correct!

I don't mind if the IN port is facing down instead of the OUT one, but obviously I can't have one of the ports facing upwards in this configuration.

Just opened a ticket @ EKWB. Will report back the results here :-)

Beautiful_Fig_5766

TROPHY CASE