You are not logged in.
Recently I got a second Monitor (C49RG9* by Samsung) in addition to a regular 16:9 1440p Monitor.
The first couple of days I only used the 49" Ultrawide on my Windows Install, which is on a different hard drive but shares the same hardware as the Arch install, without any issues.
The Monitor showed BIOS info and worked perfectly fine for a couple days.
I then plugged in my second Monitor and booted up Arch, configured the two monitors using arandr and again the second monitor worked fine for a couple of days.
I then switched back to Windows.
The Ultrawide stopped showing boot info, and showed only a black screen with backlight on. Even the on screen display of the Monitor stopped working.
The Monitor was detected however.
After trying different Cables and resolution settings under Windows, I switch back to Arch since it worked there just a couple of Minutes ago.
The same behaviour is now present with the Arch install aswell, Black screen with backlight and no OSD on the Monitor. Again, however, it gets detected by arandr just fine.
The only difference I notice is that now my GRUB boot screen as well as the tty have their resolutions reset.
I had configured the resolution of them with the
/etc/default/grub
file, adding
GRUB_GFXMODE="2560x1440x32,2560x1440x16,1920x1080x32,1920x1080x16,auto".
However now the resolution of the tty was the same as it had been before I added the GRUB_GFX line.
Additionally the Custom GRUB Background was scaled wrong and the Text in it was way to large aswell.
I update the Arch System fully but failing to solve the issue I shutdown the System and leave it for a couple of hours.
Coming back I boot up the Arch Installation again and the tty resolution is still wrong, but both monitors work after setting them up in arandr.
Both Monitors work for the entire day without any sign of flickering etc.
Thinking the Issue resolved itself, I again boot into Windows. Ultrawide stops working again on both Windows and Linux.
The OSD on the Ultrawide didn't show up, however the Buttons on the Monitor did work, like enabling Eye Saving Mode lead to a significant change in the Backlight of the Monitor.
I again leave the monitor off for the day and turn of the entire system for the next night.
However this time the power cycle didn't change anything and now the Ultrawide seems bricked, as the OSD doesn't even show up if anything is plugged in.
The buttons have also stopped working.
This may well be the Monitor breaking, since Samsung Ultrawides have the Black screen with missing OSD Issue well documented.
I would like to rule out any Software Issues before I try and get the Monitor replaced.
Thanks in advance for your Help.
Offline
Check the cable and/or connector first. That's always the weakest link.
Perhaps also check with a graphical live ISO image, grml is good for that as long as you're not one of those NVIDIA using heathens.
Jin, Jîyan, Azadî
Offline
I've tried the monitor with a completely separate machine, running an integrated intel videocard, same issues.
I suspect it has something to do with the monitors HDR functionality, maybe?
Though it could be any other thing aswell, Samsung Monitors have been known for that kind of behaviour
Offline