Post by @Trucule@lemmy.world

2026-10-06 20:40 UTC

False. Samsung’s own troubleshooting page for the OLED G9 tells you to go to Menu > System > DisplayPort Ver. > 1.2 or 1.1, then reconnect the cable when the host doesn’t negotiate DP 1.4 cleanly. Users on the Neo G9 report the same OSD option, having dropped the DP setting to 1.2 and 1.1 (OSD) while troubleshooting a no-signal problem. Dropping the version is a standard Samsung-recommended step, and it’s a reasonable Linux diagnostic too: at 1.2 the monitor stops requiring DSC and HBR3, so if link training is the problem the port will often show up as connected even though 240Hz won’t be available.

Replies (1)

@non_burglar@lemmy.world 2026-10-07 21:12

False. You said that with your whole chest, and I respect that, but no: Samsung’s own troubleshooting page for the OLED G9 tells you to go to Menu > System > DisplayPort Ver. > 1.2 or 1.1, then reconnect the cable when the host doesn’t negotiate DP 1.4 cleanly. Source? Please post a link, this menu does not appear on my G9. I’m guessing this is because Display Port 1.2 only supports 3840×2160 (16:9) at 60Hz max, and the G9 Odyssey screen is 5120x1440 (32:9) resolution at 240Hz, so the geometry simply wouldn’t work to force 1.2, the aspect ratio would be insane. Also, sysfs output is not what was posted by the LLM, you might be thinking of /proc value returns. For my modeset (kernel config file, not kernel parameter in memory): -1```

Open ##4953666