pokerdog

I installed the latest driver, 21.4.1, re-connected to displayport overnight and returned to not find the resolution changed or evidence that windows had resized at all. Requires more time to test but I'm hoping it's been resolved.

This is unfortunately an issue where each company will end up just pointing the finger at the other, especially knowing it worked fine with an older driver stack. LG is just ignoring reports of the issue.

Thanks for this VidKo, it's somewhat assuring I'm not the only one experiencing this but also annoying that AMD seems relatively silent on the issue. Will just have to keep submitted bug reports while it's in the problem state to try to force their hand.

I've been experiencing a very weird issue and googling isn't turning up anything. I've reported the behavior to AMD multiple times but got no response. What will happen, is that sometimes when waking my monitor from sleep Windows will have changed from my monitor's native resolution and refresh rate to 1280*1024 60Hz. It will not change back unless I disconnect the monitor from the computer or reset the driver. Even times when I wake the monitor and it is still proper resolution, open windows have been moved around and resized. Other times I've walked by my computer while idle, the screen has turned on staying blank and going back to sleep. I suspect this is related. I first started to notice this with my previous AMD card beginning with driver stack 20.11.2 (November WHQL release for 6000 series). I rolled back and had no issue. Eventually I acquired the 6800 and had no choice but to use 20.11.2 stack. Ever since then with each new driver revision the problem persists and I'm not sure what I can do. Environment: Windows 10 20H2 AMD Reference 6800 LG 34GK950F (Native 3440*1440 144Hz connected over DisplayPort) If anyone has any suggestions it would be very appreciated.

PSA: You may want to hold back on updating Pixel devices to 11, numerous reported issues. Myself and my spouse having noticeable performance issues, including his freaking out and entering a recovery mode after a hard crash. Issues with the Plex app, etc.

Please do more content like this! I agree that something with either you or Anthony would be quite interesting, but there's a more pressing matter. Did you recover the CD??

Have you eliminated the possibility it may be a physical issue? For instance something may have happened to the cable or switch-port. If you're able, try a different cable or such. Do you have other Ethernet devices that are unaffected?

You may need to capture what you're seeing, otherwise stating "can't configure the switch" is very ambiguous.

There is a potential benefit from a redundancy perspective, but no reason "not" to have 2. It just depends on how you wish to use them.

As long as round-trip traffic is possible between the host and DNS, it can be anywhere. In that regard you don't need multiple DNS servers unless other restrictions prevent it. ie 8.8.8.8 isn't in your network but it can be reached.

Theoretically, some ISP's do support this and would likely require another modem. Yours may not, it doesn't hurt to inquire with them. Alternatively if there's another ISP in your area you can consider them for your secondary connection.