Adjust Display Resolution

SUSE Product Topics SLES Install-Boot
1

Installing SLES12 on a physical server. After the install using the defaults, I have no x system to login with. The screen goes black. After reinstalling again, I look in the hardware settings just before the install and the resolution is set to 1680x1050. My monitor will handle that but I don’t think the server grapics will. How do I change the resolution to something else?

2

H
What is the output from;

/sbin/lspci -nnk |grep -A2 VGA

If it goes black, then you would need to turn kms (kernel mode setting
off) temporarily at the grub menu. Press esc then e, in the line with
kernel on it, you can append the word nomodeset before the quiet entry.
Press from memory F10 to then boot.

If you get the GUI desktop, then should be able to check the modes
available via the command xrandr. You can then use YaST bootloader to
set the screen size.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.2 (Harlequin) (x86_64) GNOME 3.14.0 Kernel 3.16.7-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

3

[QUOTE=malcolmlewis;26125]H
What is the output from;

/sbin/lspci -nnk |grep -A2 VGA [/quote]

0e:0d.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD]
Subsystem: Dell Device [1028:01b3]
Kernel modes: radeon

[quote]If it goes black, then you would need to turn kms (kernel mode setting
off) temporarily at the grub menu. Press esc then e, in the line with
kernel on it, you can append the word nomodeset before the quiet entry.
Press from memory F10 to then boot.

If you get the GUI desktop, then should be able to check the modes
available via the command xrandr. You can then use YaST bootloader to
set the screen size.[/quote]

xrandr results in :failed to get size of gamma for output default screen0: minimum 1280x1024+0+0 0mm x 0mm
1280x1024 77.0*

4

I still need a fix for this. Anybody know how to drop the resolution down on a monitor? You use to be able to use sax(2) but that doesnt seem to exist in SLES12.

5

Hi
Sax is deprecated… so radeon driver, what screen and do you have a
edid file for it? Are you using the GNOME DE?

You could try xrandr -s <some_resolution> but if the entries aren’t in
the xorg.conf files…

You could try the frglrx driver from the ati repository?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

6

[QUOTE=malcolmlewis;26607]Hi
Sax is deprecated… so radeon driver, what screen[/quote]

Asus VW220S

[quote]and do you have a
edid file for it?[/quote]

I would say no unless it comes with the default SLES12 install

Yes

[quote]You could try xrandr -s <some_resolution> but if the entries aren’t in
the xorg.conf files…[/quote]

Not going to try this as i bet i will not be able to login afterwards

Can i use the repo from opensuse or do i have to use a SLE 12 specific repo? If SLE 12, do you have a link or can i get it from their site?

7

Hi
The xrandr command is a onshot deal, as in doesn’t survive a
logout/login reboot and not saved anywhere…

The edid file is part of the monitor, not OS related, did it come with a
CD with drivers etc, if so the file will be on that.

The fglrx repo is part of SLE setup and should be activated by default,
check the output from zypper lr. Else check via SCC
https://scc.suse.com/dashboard for your url and credentials needed to
manually add.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

8

[QUOTE=malcolmlewis;26613]Hi
The xrandr command is a onshot deal, as in doesn’t survive a
logout/login reboot and not saved anywhere…

The edid file is part of the monitor, not OS related, did it come with a
CD with drivers etc, if so the file will be on that.[/quote]

Dont have a disc for this monitor

[quote]The fglrx repo is part of SLE setup and should be activated by default,
check the output from zypper lr.[/quote]

zypper lr shows only debug and pool, and updates and web scripting module

[quote]Else check via SCC
https://scc.suse.com/dashboard for your url and credentials needed to
manually add.[/QUOTE]

I have had the hardest time with activation/eval and now cant remember my login info. Scc wants a username and the customer center in SLES12 wants an email address? Either way, cant login…

9

Hi
This should add the repo;

zypper ar -f http://www2.ati.com/suse/sle12 "SLE-12-GA-Desktop-AMD-Driver (x86_64)"

You can grab a SLE 12 version of read-edid from here to see what the monitor info is;
http://download.opensuse.org/repositories/home:/aevseev/SLE-12/x86_64/read-edid-3.0.1-1.1.x86_64.rpm

10

[QUOTE=malcolmlewis;26615]Hi
This should add the repo;

zypper ar -f http://www2.ati.com/suse/sle12 "SLE-12-GA-Desktop-AMD-Driver (x86_64)" [/quote]

Added. Which one to install?

[quote]You can grab a SLE 12 version of read-edid from here to see what the monitor info is;
http://download.opensuse.org/repositories/home:/aevseev/SLE-12/x86_64/read-edid-3.0.1-1.1.x86_64.rpm[/QUOTE]

get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface

Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful

VBE version 200
VBE string at 0x11100 "ATI ES1000"

VBE/DDC service about to be called
Report DDC capabilities

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful

Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
Read EDID

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful

Checksum Correct

Looks like VBE was successful. Have a good day.
Section “Monitor”
Identifier “ASUS VW220”
ModelName “ASUS VW220”
VendorName “ACI”
# Monitor Manufactured week 41 of 2008
# EDID version 1.3
# Analog Display
Option “SyncOnGreen” “true”
DisplaySize 430 270
Gamma 2.20
Option “DPMS” “true”
Horizsync 30-82
VertRefresh 50-75
# Maximum pixel clock is 210MHz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1152x864, 75Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1280x800, 60Hz
#Not giving standard mode: 1680x1050, 75Hz
#Not giving standard mode: 1280x720, 60Hz
Modeline “Mode 0” -hsync +vsync
EndSection

11

Hi
So it’s an ATI ES1000, so unfortunately your stuck with the radeon
driver, so might as well remove the ati repo.

Not sure why it won’t read the modelines… do you have a different
monitor you can try and see if it changes.

Can you look at the file /var/log/Xorg.0.log are there any entries that
indicate “Validating Mode”?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

12

[QUOTE=malcolmlewis;26634]Hi
So it’s an ATI ES1000, so unfortunately your stuck with the radeon
driver, so might as well remove the ati repo.

Not sure why it won’t read the modelines… do you have a different
monitor you can try and see if it changes.

Can you look at the file /var/log/Xorg.0.log are there any entries that
indicate “Validating Mode”?[/QUOTE]

This may not mean anything:

32.606] (II) LoadModule: “glx”
[ 32.606] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 32.608] (II) Module glx: vendor=“X.Org Foundation”
[ 32.608] compiled for 1.15.2, module version = 1.0.0
[ 32.608] ABI class: X.Org Server Extension, version 8.0
[ 32.608] (==) AIGLX enabled
[ 32.608] Loading extension GLX
[ 32.608] (==) Matched fglrx as autoconfigured driver 0
[ 32.608] (==) Matched ati as autoconfigured driver 1
[ 32.608] (==) Matched modesetting as autoconfigured driver 2
[ 32.608] (==) Matched fbdev as autoconfigured driver 3
[ 32.608] (==) Matched vesa as autoconfigured driver 4
[ 32.608] (==) Assigned the driver to the xf86ConfigLayout
[ 32.608] (II) LoadModule: “fglrx”
[ 32.756] (WW) Warning, couldn’t open module fglrx
[ 32.756] (II) UnloadModule: “fglrx”
[ 32.756] (II) Unloading fglrx
[ 32.756] (EE) Failed to load module “fglrx” (module does not exist, 0)
[ 32.756] (II) LoadModule: “ati”

Dont see anything about validating mode in the xorg log

According to this thread:

http://ubuntuforums.org/showthread.php?t=1981168&p=11941129#post11941129

Will fglrx work?

13

Hi
A lot happens in two-three years… AFAIK, no due to kernel changes etc
the legacy driver won’t build. Does the system have a PCI-E x16 slot,
use the dmidecode command to see?

Any luck with trying a different screen?

The other thing we can look at is if glamor is enabled, again look
through the xorg log.

I will get one of my openSUSE colleagues to look at this thread to see
if we can configure the modelines.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

14

Xrandr provides the best means to adding and testing new display modes. Once you have a working modeline (compatible with your graphics card and monitor), you can move on to making it persistent via an Xorg configuration file.

For example, 1280x1024@60Hz:

[CODE]gtf 1280 1024 60

1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

Modeline “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
[/CODE]

xrandr --newmode "1280x1024_60.00"  108.88  1280 1360 1496 1712  1024 1025 1028 1060  -HSync +Vsync
xrandr --newmode VGA-0 "1280x1024_60.00"

Then test it by invoking it with

xrandr -s 1280x1024_60.00

That’s the general approach, and it may take a bit of trial and error to get a working display mode with suitable timings. The ‘cvt’ utility can also be used to generate modelines. (Refer to the man pages for more info on using these utilities.)

15

[QUOTE=malcolmlewis;26646]Hi
A lot happens in two-three years… AFAIK, no due to kernel changes etc
the legacy driver won’t build. Does the system have a PCI-E x16 slot,
use the dmidecode command to see?[/quote]

It does not look to have a pci-e x16, does have pci-e 8x:

[code]Handle 0x0900, DMI type 9, 17 bytes
System Slot Information
Designation: PCI1
Type: x8 PCI Express
Current Usage: Available
Length: Long
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported

Handle 0x0901, DMI type 9, 17 bytes
System Slot Information
Designation: PCI2
Type: x8 PCI Express
Current Usage: Available
Length: Long
ID: 2
Characteristics:
3.3 V is provided
PME signal is supported[/code]

Will have to reboot the server after hooking up screen so that will need to happen after hours. I will report back with the results

[quote]The other thing we can look at is if glamor is enabled, again look
through the xorg log.[/quote]

No mention of glamor in the xorg log file

[quote]I will get one of my openSUSE colleagues to look at this thread to see
if we can configure the modelines.[/QUOTE]

Great!

16

[QUOTE=deano_ferrari;26650]Xrandr provides the best means to adding and testing new display modes. Once you have a working modeline (compatible with your graphics card and monitor), you can move on to making it persistent via an Xorg configuration file.

For example, 1280x1024@60Hz:

[CODE]gtf 1280 1024 60

1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

Modeline “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
[/CODE]

xrandr --newmode "1280x1024_60.00"  108.88  1280 1360 1496 1712  1024 1025 1028 1060  -HSync +Vsync
xrandr --newmode VGA-0 "1280x1024_60.00"

Then test it by invoking it with

xrandr -s 1280x1024_60.00

That’s the general approach, and it may take a bit of trial and error to get a working display mode with suitable timings. The ‘cvt’ utility can also be used to generate modelines. (Refer to the man pages for more info on using these utilities.)[/QUOTE]

gtf 1280 1024 60

1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

Modeline “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync

When i ran:
xrandr --newmode “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync

resulted in this:
xrandr: Failed to get size of gamma for output default

Remember, in order for me to get a screen, at boot i have to enter nomodeset just before the quiet text of the grub menu.
And when i boot the server normal without entering the nomodeset text and VNC into the server, the xrandr result are according to the VNC window. Could i SSH to the server and run xrandr? I will try that… and from SSH results in “cant open display”

17

[QUOTE=carnold6;26652]
When i ran:
xrandr --newmode “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync

resulted in this:
xrandr: Failed to get size of gamma for output default

Remember, in order for me to get a screen, at boot i have to enter nomodeset just before the quiet text of the grub menu.
And when i boot the server normal without entering the nomodeset text and VNC into the server, the xrandr result are according to the VNC window.[/QUOTE]
Okay, using ‘nomodeset’ results in a basic framebuffer driver being used, so you can’t ‘xrandr’ to change display resolution. The radeon driver needs to be active first.

18

So, in yast->bootloader, there is a sopt to set resolution:

Shall i try the selection that is highlighted in the above image?

19

OK, i got the server booted without using nomodeset. i run gtf:

[code]gtf 1280 1024 60

1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

Modeline “1280x1024_60.00” 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync[/code]

Then i run xrandr --newmode "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync

Then xrandr --newmode VGA-0 "1280x1024_60.00" and get:

xrandr: failed to parse ‘VGA-0’ as a mode specification
Try ‘xrandr --help’ for more information.

So i looked through --help and the xorg.log file and do see:
[ 74244.709] (II) RADEON(0): Output VGA-0 has no monitor section
[ 74244.742] (II) RADEON(0): EDID for output VGA-0

So i am not sure why that command failed. Any ideas?