Good day everyone,
I performed a clean install of opensuse Leap 15 on my laptop (just trying to revive my old lenovo x230), but connecting the external ultrawide monitor through mDP-HDMI cable cannot give me the resolution of 2560x1080 @60
Maximum is 1920x1080.
I am new in Linux and would like to ask for some instructions how to set up manually the resolution.
Thank you in advance.
You may need to provide/post here what graphic card is in your machine.
Please post the output of the following Terminal (CLI) command – use a normal user – there’s no need to use the user “root”:
> xrandr --query
If you wish to see more detail, use “xrandr --query --verbose” but, there shouldn’t be any need to post the detail that option provides …
What we need is at least the following lines: “Screen 0:” and the connector with the status “connected primary”.
What year was that LG manufactured? What model? Does it have a DisplayPort? A DVI port? If my experience with a 21:9 Dell made in 2016 is any guide, you’re going to need to use the LG’s DisplayPort or DVI input instead of HDMI, and/or a newer PC or laptop. Only my newest GPUs with HDMI outputs will produce 2560x1080 on my Dell. Using the Dell’s DVI and DisplayPort inputs, 2560x1080 is no problem. With my older HDMI outputs, the Dell produces 1152x864 or 1400x1050 by default, and needs manual Xorg configuration to reach as much as 1920x1080.
Thank you for the reply, please see the output below:
oleks@linux-5rh2:~> xrandr --query
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected (normal left inverted right x axis y axis)
1366x768 60.00 +
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
700x525 59.98
800x450 59.95 59.82
640x512 60.02
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
640x400 59.88 59.98
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm
1920x1080 60.00* 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
oleks@linux-5rh2:~>
The monitor has only 2 HDMI ports, the laptop has only VGA and mDP. I am connected through mDP to HDMI cable.
Same laptop with the same cable arrangment with windows 10 installed before was working automatically with 2560x1080 resolution. The graphics card is Intel HD 4000
This is LG 29UM58 from 2016 with 2 HDMI ports only. I am connected through mDP port (laptop) to HDMI (monitor) - tried both ports.
I tried some advise from Ubuntu user (with cvt, xrandr --newmode, etc) - it gave me the option in Display settings for 2560x1080, but whenever I click on it, it returns the 1920 x 1080 without any message.
I have Intel HD 4000 graphics and mDP to HDMI connection.
In the future, when you paste, please wrap what you paste with the Code ( # ]) icon above the input window.
Does /etc/X11/xorg.conf exist? If it does, please paste its content here.
Do /etc/X11/xorg.conf.d/50-device.conf or 50-screen.conf exist and contain uncommented lines? If either does, please paste its content here.
This may be a case of bad EDID from the LG that can be solved with a config file. Save the following to /etc/X11/xorg.conf.d/50-monitor.conf:
Section "Monitor"
Identifier "DefaultMonitor"
Identifier "DefaultMonitor"
VendorName "LG"
ModelName "29UM58"
HorizSync 29-94
VertRefresh 49-86
Option "PreferredMode" "2560x1080"
EndSection
LG’s online pdf omits the specs required to do this perfectly, so the following should be run:
hwinfo --monitor
and then the HorizSync and VertRefresh values above be replaced with those provided by the hwinfo command: Vert. Sync Range: and Hor. Sync Range.
If 50-monitor.conf already exists, examine it. If it only contains comments, delete or replace it. If it contains anything more than comments, please paste its entire content here.
/etc/X11/xorg.conf - does not exist in the folder X11
50-monitor.conf - i had it only with comments. I edited it as you mentioned, putting correct HorizSync and VertRefresh. After reboot I didnt have GUI, only command line. I navigated to its location and deleted it and GUI restarted.
I am really feeling myself as a complete “0” in Linux, trying to start learning it, but I didnt expect it will be the start with immediate issue like that.
My prior reply neglected to take into account that there are two displays, so couldn’t be expected to work. 
Instead of the previous suggestion to save /etc/X11/xorg.conf.d/50-monitor.conf, save the following as /etc/X11/xorg.conf:
Section "Device"
Identifier "Intel4000"
Option "Monitor-LVDS-1" "internal"
Option "Monitor-HDMI-1" "external"
EndSection
Section "Monitor"
Identifier "lvds"
EndSection
Section "Monitor"
Identifier "hdmi"
VendorName "LG"
ModelName "29UM58"
HorizSync 29-94
VertRefresh 49-86
Option "PreferredMode" "2560x1080"
EndSection
Section "Screen"
Identifier "internal"
Device "Intel4000"
Monitor "lvds"
EndSection
Section "Screen"
Identifier "external"
Device "Intel4000"
Monitor "hdmi"
EndSection
Substitute the values from hwinfo --monitor for HorizSync and VertRefresh.
This xorg.conf could be divided into parts to be saved in xorg.conf.d/, but with multiple displays I find keeping everything in one file easier to work with when trying to debug.
If this fails, please do:
susepaste -n kassinni -e 10080 /var/log/Xorg.0.log
and paste here the link it provides. If you get a command not found response, install susepaste with zypper or yast2 and try again.
xorg.conf was created as advised, but nothing changed.
“susepaste” gave me 2 links:
http://susepaste.org/13516758
SUSE Paste
From the log:
No Layout section. Using the first Screen section.
I believe is saying in need to debug xorg.conf by including a missing layout section. Including a layout section is something that has been on my todo list for quite some time. Up until around a year or so ago it wasn’t necessary. Hopefully I can get to figuring it out later or tomorrow. Using xrandr to add a missing mode should be another option, but that is something I’ve always avoided a need for, and so have never tried.
What you can try before then is a slight rearranging of the xorg.conf previously suggested, making the later ‘Section “Screen”’ the earlier, and the earlier the later, having the first scanned point to the HDMI screen instead of the internal.
The graphics hardware (GPU) for the Laptop screen supports a maximum resolution of 1366x768 at a refresh rate of 60 Hz.
The graphics hardware (GPU) for the HDMI-1 port supports a maximum resolution of 1920x1080 at a refresh rate of 60 Hz.
[HR][/HR]Regardless of what the Monitor is capable of, more than what the GPU is capable of, is not possible …
Please, upon what authority is this assertion based? All I see in the man page is
a ‘+’ after the preferred modes and a ‘*’ after the current mode
Up to now it’s always been my understanding that modes reported by xrandr are (current state) modes roughly corresponding to modes reported in output from ‘hwinfo --monitor’, which have nothing to do with what the GPU supports.
IME, xrandr is capable of lies. Today I tried to match OP’s environment with my oldest Intel GPU with multiple outputs, a slightly newer (Tick) HD Graphics 4400 (i3-4150T Haswell) rather than OP’s HD Graphics 4000 (i5-3320M Ivy Bridge), and Dell 2560x1080 display instead of LG. Never having plugged the Dell into the Haswell before, I simply plugged in the Dell’s HDMI cable to this more than a week of uptime Haswell on Samsung 1920x1200. Not liking what I saw, I cycled the power on the Samsung, then checked xrandr:
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 59.95*+
1600x1200 60.00
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 74.98 59.98 59.90...
HDMI-2 connected (normal left inverted right x axis y axis) # black screen
2560x1080 60.00 +
1920x1080 60.00 60.00 50.00 59.94 24.00 23.98
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 59.98...
The Dell 2560x1080 was black, the Samsung 1920x1200 was running in 1600x1200, and all open windows on my 8 virtual desktops that had been flush with top of screen now had had their titlebars relocated above the screen, and the upper portions of their main menus relocated above the screen as well. This mispositioning of windows survived rebooting, both with both displays connected, as well as with only the Samsung connected. It took me a while to rediscover Alt-F3 to recover those window positions without losing their content, even though the reboot made both displays work as expected, 1920x1200 and 2560x1080.
Could OP’s limitation be a limitation of his mDP-to-HDMI cable? I’ve never run across any DisplayPort incapable of outputting more than 1920x1200.
Yes, “xrandr” seems to have some issues with “the truth” – especially with respect to “maximum” …
For example, an ASUS R7240-SL-2GD3-L card (AMD Radeon R7 240 – OLAND):
> xrandr --query
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
1920x1080 60.00*+ 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
VGA-0 disconnected (normal left inverted right x axis y axis)
>
Considering the refresh rates: 75 Hz means a maximum resolution of 1280x1024; a resolution of 1920x1080 means a refresh rate of 60 Hz.
The maximum resolution of 16384x16384 is a myth …
[HR][/HR]Bottom line:
That’s not an issue with xrandr though. It derives that information from the graphics driver, which interrogates the attached hardware to get the display EDID,
Looking into the Intel HD 4000 information I noticed that:
For 2nd and 3rd Generation Intel® Core™ Processors the maximum supported resolutions are:
- DisplayPort 1.1 = 2560x1600 at 60 Hz
- HDMI 1.4 = 1920x1200 at 60 Hz
- DVI (Single-link) = 1920x1200 at 60 Hz
- VGA = 2048x1536 at 75 Hz
Could it be that, the Linux driver, because of the Display Port to HDMI cable and, the HDMI at the monitor, is setting up for a HDMI scenario – the xrandr output seems to be indicating this.
This is what I had in mind when I mentioned the DP-to-HDMI cable in post #14. ISTR that it was a relatively recent HDMI bandwidth specification (in 2.0?) that enabled more than 1920x1200 via HDMI. This was greatly puzzling me when I got my 2560x1080 28 months ago. Eventually I deduced that HDMI outputs that were too old just could not support it, since I could never find an explanation of differences between specs that translated bandwidth to resolution. Wikipedia’s description of v1.3 seems to describe the OP’s problem, except that it’s hard to believe a GPU as new as HD 4000 wouldn’t support a specification so old. It was only after Ivy Bridge that Intel started including supported resolutions on their CPU spec pages, e.g. mine (Haswell) vs. OP’s (Ivy Bridge).
Since my last post I tried an adapter here. First, using the DP-to-HDMI adapter:
# inxi -GxxxS
System: Host: gx78b Kernel: 4.12.14-lp150.12.58-default x86_64 bits: 64 compiler: gcc v: 7.3.1 Desktop: Trinity R14.0.6
tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: startx Distro: openSUSE Leap 15.0
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] vendor: Dell
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6779
Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa alternate: ati resolution: 1400x1050~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.12.14-lp150.12.58-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 compat-v: 3.0
direct render: Yes
# xrandr # DP output on Radeon to adapter to HDMI input on 2560x1080 Dell display
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 16384 x 16384
DP-1 connected primary 1400x1050+0+0 (normal left inverted right x axis y axis) 673mm x 284mm
1920x1080 59.96 60.00 60.00 50.00 59.94 59.93 24.00 23.98
1920x1080i 60.00 50.00 59.94
1680x1050 59.95 59.88
1400x1050 74.76 59.98*
1600x900 59.94 59.95 59.82...
DVI-I-1 connected 1400x1050+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
1920x1200 59.95 +
1920x1080 59.96 59.93
1600x1200 60.00
1680x1050 59.95 59.88
1400x1050 59.98* 59.95
1600x900 59.95 59.82...
Unsettling that it falls down to 1400x1050 on both. I then shut down, changed nothing except to DP-to-DP cable, and rebooted:
# inxi -GxxxS
System: Host: gx78b Kernel: 4.12.14-lp150.12.58-default x86_64 bits: 64 compiler: gcc v: 7.3.1 Desktop: Trinity R14.0.6
tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: startx Distro: openSUSE Leap 15.0
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] vendor: Dell
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6779
Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa alternate: ati
resolution: 2560x1080~60Hz, 1920x1200~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.12.14-lp150.12.58-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 compat-v: 3.0
direct render: Yes
# xrandr # DP output on Radeon straight to DP input on 2560x1080 Dell display
Screen 0: minimum 320 x 200, current 4480 x 1200, maximum 16384 x 16384
DP-1 connected primary 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm
2560x1080 60.00*+
1920x1080 59.96 60.00 60.00 50.00 59.94 59.93 24.00 23.98
1920x1080i 60.00 50.00 59.94
1680x1050 59.95 59.88
1400x1050 74.76 59.98
1600x900 59.94 59.95 59.82...
DVI-I-1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis) 519mm x 324mm
1920x1200 59.95*+
1920x1080 59.96 59.93
1600x1200 60.00
1680x1050 59.95 59.88
1400x1050 59.98 59.95
1600x900 59.95 59.82...
- With the same hardware, it was OK when Windows 10 was executing – possibly due to the recognition of the Display Port …
My guess is the Windows video driver runs outside HDMI specification, but well within DisplayPort’s, something FOSS DDX writers probably don’t have practical means to both accomplish and confidently QA before releasing to the public.
IMO OP got a bad bargain buying a display with no DisplayPorts for a slightly too old laptop. It would be nice if he still has time to exchange it or return it, cheaper than a new laptop. Looks like a more sophisticated DP-to-HDMI adapter might get this job done. There is a huge range of prices in a search for same on Newegg. Passive and active both exist among descriptions.
Other thoughts within this overall context:
Hi Guys,
Got an interesting update with this struggle. You might be able to explain it to me.
I have 2 hard drives, so on second I installed Debian 9.9.
of course, it had same issue with monitor, but with few commands:
cvt 2560 1080 50
then
xrandr --addmode and --newmode I got the resolution working.
But it was 50Hz,
In UBUNTU it doesnt work, the mode appears as an option, but cannot switch on it, it returns back.
Got it working right now, but only 2560x1080_40 with same cable and setup.