Samsung UN40MU6300 in 4K with Intel® Core™ i5-7200U

[windyweather]

On LM 18.3 and now LM 19 I can't get a 4K display to work on a Gigabyte BRIX GB-KBi5HA-7200.
This is the processor:
https://ark.intel.com/products/95443/In ... -3-10-GHz-

The video section for the 7200U says:
4K Support Yes, at 60Hz [ I assume this means with HDMI 2.0 or later]
Max Resolution (HDMI 1.4)‡ 4096x2304@24Hz [ I assume this means that if your display is only HDMI 1.4 you don't get 60Hz]
Max Resolution (DP)‡ 4096x2304@60Hz

Here is the Gigabyte BRIX page:
https://www.gigabyte.com/Mini-PcBarebon ... -rev-10#ov

The TV is Samsung UN40MU6300 and here's the page:
https://www.samsung.com/us/televisions- ... u6300fxza/

Video
Screen Size 39.9" Measured Diagonally
Resolution 3,840 × 2,160
Motion Rate 120
Color 4K Color Drive HDR (High-Dynamic Range) 4K HDR Pro
Picture Engine UHD Up-Scaling UHD Upscaling Yes

This shows sliced video in 4K mode. 1920x1080 works great.
https://imgur.com/a/8QI6BOj

I've tried different cables and I've tried using an adapter to the MiniDisplayport connection. The MiniDisplayport gives me only 1920x1080 choice in display settings, oddly.

This behavior did not change when I upgraded to LM 19 from LM 18.3. Same non-working 4K behavior on both.

Any suggestions to get 4K working? All specs seem to say it should work fine.

Thanks. ww

[AndyMH]

I'd start by using get-edid to find out what the monitor is telling mint about screen resolutions. Have a look at my post here on what I had to do to get mint 19 to work with my ultrawide monitor (it's quite long):

viewtopic.php?f=46&t=280143

[windyweather]

So I installed read-edid and ran it and this is what I got:

Code: Select all

@GBLM19:~$ sudo get-edid  | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
2 potential busses found: 0 5
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one.
Bus 0 doesn't really have an EDID...
256-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
	Identifier "SAMSUNG"
	ModelName "SAMSUNG"
	VendorName "SAM"
	# Monitor Manufactured week 1 of 2017
	# EDID version 1.3
	# Digital Display
	DisplaySize 890 500
	Gamma 2.20
	Option "DPMS" "false"
	Horizsync 15-81
	VertRefresh 24-75
	# Maximum pixel clock is 300MHz
	#Not giving standard mode: 1152x864, 75Hz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x800, 60Hz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1440x900, 60Hz
	#Not giving standard mode: 1600x900, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz

	#Extension block found. Parsing...
#WARNING: I may have missed a mode (CEA mode 95)
#DOUBLE WARNING: It's your first mode, too, so this may actually be important.
#WARNING: I may have missed a mode (CEA mode 93)
#WARNING: I may have missed a mode (CEA mode 94)
#WARNING: I may have missed a mode (CEA mode 98)
#WARNING: I may have missed a mode (CEA mode 99)
#WARNING: I may have missed a mode (CEA mode 100)
Segmentation fault (core dumped)

So that's strange. I don't see any modes we expect, like 1920x1080 or 3840x2160 and the Seg Fault also seems odd.
Can you make anything from this?

I see in the post that you reference that you appear to follow this step with typing some new modes into a settings file. Anyway, let's keep track of the fact that the two modes SHOW UP in the display settings panel - 4096x2160 and 3840x2160 both show up when I use the HDMI cable. They just don't work. Like I mentioned the display is vertical strips repeated horizontally across the screen. Is there a setting for 60hz vs 120hz or something that I can't see in the Display settings? That I need to edit a settings file to change? Are the vertical strips caused by some refresh frequency being wrong?

One more piece of data. I have plugged this TV into a Windows 10 system with a GFX 1060 card and it worked like a charm. Showed up next to my 2K monitor and I could wave the mouse back and forth across between them. No muss no fuss.I'm not sure if this says anything about the state of Intel graphics drivers for Linux or the surrounding software, but this seems like brain surgery by comparison. Just say'n.
Thanks.

[AndyMH]

Strange, it seems to have found the right monitor (samsung), but can't read the edid (the extension block). Googling cea mode 93 hasn't turned up anything useful. Best I found was https://bugs.launchpad.net/ubuntu/+sour ... ug/1702827, but simply reports a v similar problem to yours. Most other hits on cea refer to a raspberry pi and the use of a tvservice command that seems unique to the pi.

If, somehow, you can get the right modelines for the monitor you can force the mode with xrandr. I wonder if there is a way of getting this in win10 as it works?

Hoping someone else comes along with a bit more expertise than me!

You could try using cvt or gtf to get the modelines, but I suspect that what they tell you will be wrong.

My only other thought is to try different kernels, but this is grasping at straws.

[roblm]

Post the output of xrandr --prop

Also post the Xorg.0.log file. Use this command to open it: xed /var/log/Xorg.0.log

If there is a problem posting that long file, then it can be uploaded to pastebin.
First install pastebinit with this command: apt install pastebinit

Then use this command to upload the file to pastebin: pastebinit /var/log/Xorg.0.log
Post the URL link that displays in the Terminal window.

If, somehow, you can get the right modelines for the monitor you can force the mode with xrandr. I wonder if there is a way of getting this in win10 as it works?

Yes there is using the PowerStrip or other programs and that could be explored if there is no useful info from the outputs above.

[windyweather]

Here ya go. I assume that I didn't need to do this in 4K mode. It's done with LM using 1920x1080.

Thanks a ton

[roblm]

Here is the data extracted from the TV’s EDID using edid-decode:

Code: Select all

Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   4c 2d f6 0d 00 0e 00 01 01 1b
version:         01 03
basic params:    80 59 32 78 0a
chroma info:     23 ad a4 54 4d 99 26 0f 47 4a
established:     bd ef 80
standard:        71 4f 81 c0 81 00 81 80 95 00 a9 c0 b3 00 01 01
descriptor 1:    04 74 00 30 f2 70 5a 80 b0 58 8a 00 50 1d 74 00 00 1e
descriptor 2:    02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74 00 00 1e
descriptor 3:    00 00 00 fd 00 18 4b 0f 51 1e 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20
extensions:      01
checksum:        64

Manufacturer: SAM Model df6 Serial Number 16780800
Made week 1 of 2017
EDID version: 1.3
Digital display
Maximum image size: 89 cm x 50 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
  1152x870@75Hz
Standard timings supported:
  1152x864@75Hz
  1280x720@60Hz
  1280x800@60Hz
  1280x1024@60Hz
  1440x900@60Hz
  1600x900@60Hz
  1680x1050@60Hz
Detailed mode: Clock 297.000 MHz, 1872 mm x 1053 mm
               3840 4016 4104 4400 hborder 0
               2160 2168 2178 2250 vborder 0
               +hsync +vsync 
Detailed mode: Clock 148.500 MHz, 1872 mm x 1053 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync 
Monitor ranges (GTF): 24-75Hz V, 15-81kHz H, max dotclock 300MHz
Monitor name: SAMSUNG
Has 1 extension blocks
Checksum: 0x64 (valid)

CEA extension block
Extension version: 3
69 bytes of CEA data
  Video data block
    VIC 95 Unknown mode 
    VIC 16 1920x1080@60Hz 
    VIC 31 1920x1080@50Hz 
    VIC 04 1280x720@60Hz 
    VIC 19 1280x720@50Hz 
    VIC 05 1920x1080i@60Hz 
    VIC 20 1920x1080i@50Hz 
    VIC 32 1920x1080@24Hz 
    VIC 33 1920x1080@25Hz 
    VIC 34 1920x1080@30Hz 
    VIC 93 Unknown mode 
    VIC 94 Unknown mode 
    VIC 98 Unknown mode 
    VIC 99 Unknown mode 
    VIC 100 Unknown mode 
    VIC 07 1440x480i@60Hz 
    VIC 22 1440x576i@50Hz 
    VIC 03 720x480@60Hz 
    VIC 18 720x576@50Hz 
  Audio data block
    Linear PCM, max channels 1
    Supported sample rates (kHz): 48 44.1 32
    Supported sample sizes (bits): 24 20 16
    AC-3, max channels 5
    Supported sample rates (kHz): 48 44.1 32
    Maximum bit rate: 56 kHz
    DTS, max channels 5
    Supported sample rates (kHz): 48
    Maximum bit rate: 56 kHz
    Dolby Digital+, max channels 7
    Supported sample rates (kHz): 48 44.1 32
  Speaker allocation data block
  Extended tag: video capability data block
    YCbCr quantization: No Data (0)
    RGB quantization: No Data (0)
    PT scan behaviour: No Data (0)
    IT scan behaviour: Support both over- and underscan (3)
    CE scan behaviour: Support both over- and underscan (3)
  Extended tag: Colorimetry data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
    Supports_AI
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 300MHz
    Extended HDMI video details:
      HDMI VIC 0 3840x2160@30Hz
      HDMI VIC 1 3840x2160@25Hz
      HDMI VIC 2 3840x2160@24Hz
      HDMI VIC 3 4096x2160@24Hz
  Extended tag: Reserved video block (06)
  Extended tag: Reserved video block (0e)
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
0 native detailed modes
Detailed mode: Clock 74.250 MHz, 1872 mm x 1053 mm
               1920 2448 2492 2640 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced 
Detailed mode: Clock 85.500 MHz, 1872 mm x 1053 mm
               1366 1436 1579 1792 hborder 0
                768  771  774  798 vborder 0
               +hsync +vsync 
Checksum: 0x69 (valid)

The 3840x2160 mode is listed but not the refresh rate:

Code: Select all

Detailed mode: Clock 297.000 MHz, 1872 mm x 1053 mm
               3840 4016 4104 4400 hborder 0
               2160 2168 2178 2250 vborder 0
               +hsync +vsync

This modeline from the Xorg.0.log shows the same mode and lists the refresh rate as 30 Hz:

Code: Select all

Printing probed modes for output DP-2
Modeline "3840x2160"x30.0  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz eP)

Note that the pixel clock (dot clock) is 297.00 MHz

The problem is that the maximum pixel clock is listed as only 300 MHz:

Code: Select all

Monitor ranges (GTF): 24-75Hz V, 15-81kHz H, max dotclock 300MHz

The same result from using sudo get-edid | parse-edid:

Code: Select all

# Maximum pixel clock is 300MHz

Using cvt to generate a standard modeline at 60 Hz shows a 712 MHz pixel clock:

Code: Select all

cvt 3840 2160 
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz
Modeline "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 2168 2237 -hsync +vsync

Using cvt to generate a reduced blanking mode at 60 Hz shows a 533 MHz pixel clock:

Code: Select all

cvt 3840 2160 -r
# 3840x2160 59.97 Hz (CVT 8.29M9-R) hsync: 133.25 kHz; pclk: 533.00 MHz
Modeline "3840x2160R"  533.00  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync

For whatever reason, it appears that the TV may be reporting the wrong maximum pixel clock from the EDID.

The TV’s specs say: Picture Engine UHD Up-Scaling
Does this mean that the TV can use a lower resolution at 60 Hz and upscale it to 3840x2160?

Your options as of now are:
You can use 3840x2160 at 30 Hz

Unless the 3840x2160 at 60 Hz mode is listed in the xrandr --prop output or Xorg.0.log when using the
MiniDisplayport connection.

Or if a Windows PC is available with an HDMI 2.0 supported port, then the TV can be connected to it to see if 3840x2160 at 60 Hz is possible. If it is, then the EDID can be obtained and transferred to the Mint installation.

[AndyMH]

Ahh... several modelines in the xorg output of potential interest:

Code: Select all

[     5.901] (II) modeset(0): Printing probed modes for output DP-2
[     5.901] (II) modeset(0): Modeline "3840x2160"x30.0  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync
[     5.901] (II) modeset(0): Modeline "4096x2160"x30.0  297.00  4096 4184 4272 4400  2160 2168 2178 2250 +hsync +vsync

As per my original post try using either of the following:

Code: Select all

xrandr --newmode "3840x2160x30"  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync
xrandr --newmode "4096x2160x30"  297.00  4096 4184 4272 4400  2160 2168 2178 2250 +hsync +vsync

and then addmode:

Code: Select all

xrandr --addmode DP-2 "2560x1080x30"

or

Code: Select all

xrandr --addmode DP-2 "4096x2160x30"

Note, I've added x30 into the titles to distinguish them from whatever xorg is automatically finding. They then should appear in menu > preferences > display. What happens if you select either (I suspect that it won't work as I think you already have these resolutions in display but they don't work)?

If it does work (pretty please ) then you can follow my original post on how to make it permanent.

EDIT: Had a quick look at powerstrip, think it's this: https://www.entechtaiwan.com/util/ps.shtm, if the above fails, try installing it in win10 and see if it can tell you anything useful - like the modelines.

[windyweather]

roblm: You ask:

Unless the 3840x2160 at 60 Hz mode is listed in the xrandr --prop output or Xorg.0.log when using the
MiniDisplayport connection.

When using the MiniDP <> HDMI adapter, neither "4k" mode appears in the LM Display settings. The maximum rez reported is 1920x1080. Since the display is sliced up, its a real problem to obtain any data. It's possible to switch back using the display settings to 1920x1080, but that's about all.

also you suggest:

Or if a Windows PC is available with an HDMI 2.0 supported port, then the TV can be connected to it to see if 3840x2160 at 60 Hz is possible. If it is, then the EDID can be obtained and transferred to the Mint installation.

This was done a while ago. And the TV showed 4K without issue using a GTX 1060 card. Both a ASUS 2K monitor and the Samsung 4K tv were connected at the time and they both worked fine. So you suggest getting the edid info using a windows 10 system. I could try to do that but have no idea how. I have a long hdmi cable and could try that again to gather the info if you can point me to how.

Re AndyMH
You suggest adding some modes. The TV specs say 3840x2160 as it's resolution and a "Motion Rate" of 120.
The processor chip specs are here:
https://ark.intel.com/products/95443/In ... -3-10-GHz-
and say that the following in the video section:

4K Support Yes, at 60Hz
Max Resolution (HDMI 1.4)‡ 4096x2304@24Hz
Max Resolution (DP)‡ 4096x2304@60Hz

So why do we think we should set things to 30Hz refresh?

I'll give the 3840 choices a try and see what happens.

I have no idea what you are trying to accomplish with this:

Code: Select all

xrandr --addmode DP-2 "2560x1080x30"

That sounds like a 2K not a 4K display, right?

Thanks. Looks like we are making progress.

[windyweather]

With the long HDMI cable I connected the TV to the Windows 10 / GTX 1060 card. It came right up in 4K.
At first the display settings on Win 10 showed 3840x2160 30Hz, but the deeper dive showed "List All Modes" and 60Hz was there.
On setting 3840x2160x60 hz the TV is quite happy and Win 10 settings now shows 60Hz.

on LM 19 I tried the xrandr commands and nothing new appeared in the list of the Display settings panel.

Code: Select all

xrandr --newmode "3840x2160x30"  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync
xrandr --addmode DP-2 "3840x2160x30"

One sec. I'll ltry x60 and see if that changes anything.
Nope. Still nothing new in the list of the Display settings panel.

[windyweather]

I'm a long time Linux Mint lover. For 8 or 10 years now I've been building LM systems and using LM in VMs for safer internet usage.

But, it's too much work to get this going. I installed Windows 10 from a stick on this system and it came up with a 1024x768 display, and then loaded the right driver in the background and switched over to 3840x2160 automatically. Works great. Yep, gonna cost me $100 for an Win 10 OEM license I guess. But it doesn't say it's gonna expire, just won't update I guess.

So, I don't know what's up with Ubuntu/LM. I would guess that Intel or whoever supports the driver for these on-chip graphics engines needs a kick in the pants to get them fixed. This is a core i-5 7200 as I've said, so it's not like its an old model - 2 generations back.

Maybe someone knows who to notify that there is a problem. Or, if we think it would help, I could submit a bug to the database.

Thanks for all your efforts. You folks spent a lot of time with me to try to solve this.
I look forward to trying LM again sometime on this system.
Cheers, ww

[AndyMH]

I got win10 professional off amazon for £8 ~ $10. Was surprised it worked but it did. There are somethings where life is too short, but if you are minded, when you get win up and running you might try https://www.entechtaiwan.com/util/ps.shtm and see if you can get a modeline that works for xrandr. My problem was getting an ultrawide monitor to work, managed to fix it by getting the modeline with edid and using xrandr to define a new mode and add it. Eventually tracked to problem down to the kernel - anything before 4.5.7 was okay, anything later wouldn't work. This was third gen intel integrated graphics (i5-3320 and i7-3632).