Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Samsung Curved Monitor No DDC/CI #140

Closed
FibroJedi opened this issue Aug 17, 2020 · 16 comments
Closed

Samsung Curved Monitor No DDC/CI #140

FibroJedi opened this issue Aug 17, 2020 · 16 comments
Labels
monitor specific problems with particular monitors samsung

Comments

@FibroJedi
Copy link

FibroJedi commented Aug 17, 2020 •
edited
Loading

FibroJedi Samsung CF390 Monitor Interrogate Output.txt
Hey,

So I just switched to Linux and all bar one thing is working fine: DDC/CI.

Monitor: Samsung CF390 (FYI this is attacked by HDMI to my laptop)

In Windows this worked most of the time, had to turn the monitor off and on occasionally to refresh it. But with softMCCS (A windows app) and a DDC/CI app I was able to control the backlight and colour tinting.

However in Linux, ddcutil says the monitor is in the database but DDC/CI is not active. While I agree it's not active, it should be possible to activate it. And in Linux I don't know what I'm doing with this one. Hope you can help. From what little I've managed to follow here's some output.

sudo ddcutil detect        
Invalid display
   I2C bus:             /dev/i2c-3
   EDID synopsis:
      Mfg id:           SAM
      Model:            C24F390
      Serial number:    H4ZM900890
      Manufacture year: 2019
      EDID version:     1.3
   DDC communication failed

Invalid display
   I2C bus:             /dev/i2c-6
   EDID synopsis:
      Mfg id:           CMN
      Model:            
      Serial number:    
      Manufacture year: 2015
      EDID version:     1.4
   DDC communication failed
   This is an eDP laptop display. Laptop displays do not support DDC/CI

Great start, eh?

$ ddcutil getvcp known --bus 6
Most of this returned "Invalid Response"

ddcutil interrogate 2>&1
Attached as a txt file. (Edited as I found how to upload attachments)
If there's anything else you need to help you, let me know. I'm moving house tomorrow but from Wednesday I should be able to reply again, if our ISP does its job.

Thanks in advance.
@rockowitz
Copy link
Owner

rockowitz commented Aug 18, 2020 via email

@FibroJedi
Copy link
Author

Thanks for the explanation, that helps. So, two numpty questions

  1. Which command do I apply the --sleep-multiplier to?
  2. How do I force the monitor to use the discreet NVIDIA chip?

Sadly I don't own another monitor so I can't check that one. I'll have a nosey around to see if I can force NVIDIA on that screen until you have a chance to get back to me. Thanks again!

@rockowitz
Copy link
Owner

rockowitz commented Aug 19, 2020 via email

@FibroJedi
Copy link
Author

Okay thanks, I'll give that a shot. (Sorry for the delay, still getting the new house sorted), I'll get back to you when I've had a brain space to try it :)

@FibroJedi
Copy link
Author

FibroJedi commented Aug 21, 2020 •
edited
Loading

Okay I've managed the first bit

sudo ddcutil detect --sleep-multiplier 3           
Display 1
   I2C bus:             /dev/i2c-2
   EDID synopsis:
      Mfg id:           SAM
      Model:            C24F390
      Serial number:    H4ZM900890
      Manufacture year: 2019
      EDID version:     1.3
   VCP version:         2.0

Does this help? I don't get the "communication failed" error with this one. If it does, do I need to do DDC stuff via the command line only, or can I modify how I launch the ddcutil GUI to let me do it that way?

Thanks!

@rockowitz
Copy link
Owner

rockowitz commented Aug 21, 2020 via email

@FibroJedi
Copy link
Author

FibroJedi commented Aug 22, 2020 •
edited
Loading

the --sleep-multiplier worked 4 out of 5 times, I just tested.

for the other

sudo ddcutil probe --sleep-multiplier=D --stats
Invalid sleep-multiplier

however

sudo ddcutil probe --sleep-multiplier=3 --stats

Mfg id: SAM, model: C24F390, sn: H4ZM900890

Capabilities for display on bus /dev/i2c-3
Unparsed capabilities string: 
MCCS version: not present

May support table reads:   true

Scanning all VCP feature codes for display [i2c: fd=3, busno=3]

that's then followed by a shedload of "invalid response, maximum retries exceeded" errors. I assume this means, in Linux, I can't control this monitor with DDC/CI?

@rockowitz
Copy link
Owner

rockowitz commented Aug 23, 2020 via email

@FibroJedi
Copy link
Author

FibroJedi commented Aug 25, 2020 via email

@rockowitz rockowitz added the monitor specific problems with particular monitors label Oct 8, 2020
@captn3m0
Copy link

I have the same monitor (C24F390) connected to a Intel NUC (with integrated Intel graphics). The second monitor I have (LG) works perfectly with ddcutil. I have so far only managed one single successful detect call:

sudo ddcutil detect
Display 1
   I2C bus:             /dev/i2c-5
   EDID synopsis:
      Mfg id:           SAM
      Model:            C24F390
      Serial number:    HTQK801650
      Manufacture year: 2018
      EDID version:     1.3
   VCP version:         2.0

This was just after I re-plugged the monitor. Every subsequent call has failed, even with sleep multipliers:

sudo ddcutil detect --sleep-multiplier=10
Invalid display
   I2C bus:             /dev/i2c-5
   EDID synopsis:
      Mfg id:           SAM
      Model:            C24F390
      Serial number:    HTQK801650
      Manufacture year: 2018
      EDID version:     1.3
   DDC communication failed

Output for sudo ddcutil --bus 5 interrogate

I'm gonna blame samsung here, but happy to provide more details if they can be of help in maybe a workaround?

Thanks for making ddcutil, I'd been trying to dim my monitors for months via a script, and I was so disappointed when I found out that they didn't support HDMI-CEC. ddcutil worked great for my usecase 🤗 (atleast on one monitor!)

@rockowitz
Copy link
Owner

rockowitz commented Jan 18, 2021 via email

@captn3m0
Copy link

captn3m0 commented Jan 19, 2021 via email

@davidhi7 davidhi7 mentioned this issue Apr 11, 2023
Closed
@pacjo pacjo mentioned this issue Jun 1, 2023
Open
@mirh
Copy link

mirh commented Jun 16, 2024

I'd be really curious to know if even with Samsung's own MagicTune you'd have this unreliability.

@captn3m0
Copy link

I never tried MagicTune - don't run Windows, and the monitor's page at samsung website never listed it as supported.

I can't find a MagicTune listing on the samsung website - is the tool still supported?

@mirh
Copy link

mirh commented Jun 17, 2024

Mhh, right. It's not a recent monitor by any stretch, but it's still 3 years newer than the last version of MT (which may or may not require a bit of legwork to install on W10).
Still, who knows? There's also supposedly a firmware update I think?

@captn3m0
Copy link

Upgrade File(USB type)
ver 1007.0 0.22 MB Dec 05. 2023 All OS

The firmware gets me a .bin file, but the monitor doesn't have a USB socket, and the manual makes no mention of a firmware upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
monitor specific problems with particular monitors samsung
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@captn3m0 @mirh @rockowitz @FibroJedi