SLES12 SP1 to SP2 - ATI ES1000 console video no longer works

SUSE Linux Enterprise Server SLES Install-Boot
1

I’ve just updated for SLES12 SP1 to SP2 and my console video no longer works.

The system starts correctly, grub displays the boot menu correctly in graphics mode and starts.
Then the screen goes blank and the monitor goes to sleep.

However, the system is working since I can use VNC to access it.

The system log is displaying many many copies of the following:
2017-02-13T08:23:31.329803-08:00 FIJI kernel: [ 374.002087] [TTM] radeon 0000:01:06.0: Unable to get page 0
2017-02-13T08:23:31.329804-08:00 FIJI kernel: [ 374.002094] [TTM] radeon 0000:01:06.0: Failed to fill cached dma32 pool (r:-12)!
2017-02-13T08:23:31.329805-08:00 FIJI kernel: [ 374.002118] [drm:radeon_gem_object_create [radeon]] ERROR Failed to allocate GEM object (249856, 2, 4096, -12)

The output from ‘lspci’
/sbin/lspci -nnk | grep VGA -A2
01:06.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02)
Subsystem: Super Micro Computer Inc Device [15d9:1511]
Kernel driver in use: radeon

I’ve tried ‘nomodeset’ and that just gives me the command line console at boot.
The video has been working without problem for all of SLES11 and SLES12 SP1.
Any suggestions on what to try?

Thanks,

Al

Note: output from hwinfo

hwinfo --gfxcard
29: PCI 106.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: zsAr.MprrWRTPK04
Parent ID: H0_h.k+eI0bksT96
SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:01:06.0
SysFS BusID: 0000:01:06.0
Hardware Class: graphics card
Model: “ATI ES1000 515E”
Vendor: pci 0x1002 “ATI Technologies Inc”
Device: pci 0x515e “ES1000 515E”
SubVendor: pci 0x15d9 “Super Micro Computer Inc”
SubDevice: pci 0x1511
Revision: 0x02
Driver: “radeon”
Driver Modules: “drm”
Memory Range: 0xf0000000-0xf7ffffff (ro,non-prefetchable)
I/O Ports: 0xc000-0xcfff (rw)
Memory Range: 0xfe9f0000-0xfe9fffff (rw,non-prefetchable)
Memory Range: 0xfe9c0000-0xfe9dffff (ro,non-prefetchable,disabled)
IRQ: 17 (606 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v00001002d0000515Esv000015D9sd00001511bc03sc00i00”
Driver Info #0:
XFree86 v4 Server Module: radeon
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #12 (PCI bridge)

Primary display adapter: #29

2

Hi
You don’t have a custom /etc/X11/xorg.conf or a custom config in /etc/X11/xorg.conf.d/ directory?

What does /var/log/Xorg.0.log say? If too for the forum big use http://paste.opensuse.org/ (please set to never expire).

Is the system all up to date?

3

Malcom,

There are no customizations at all.
I checked, there is no ‘xorg.conf’
The system is fully up to date as of this morning.

Here is /var/log/Xorg.0.log
http://paste.opensuse.org/84164515

The monitor resolution is 1680x1050

At line 570 of /var/log/Xorg.0.log I see an error that it failed to set the mode.
How would I go about forcing a specific mode?

Thanks,

Al

4

[QUOTE=capekeppel;36536]
The monitor resolution is 1680x1050

At line 570 of /var/log/Xorg.0.log I see an error that it failed to set the mode.
How would I go about forcing a specific mode?

Thanks,

Al[/QUOTE]
I don’t think there is a problem with the display mode set, but your dmesg output suggests a kernel-related problem.

It might be useful to trawl through the log for other radeon-related errors

dmesg|egrep "radeon|drm
5

Sorry, that should have been

dmesg|egrep "radeon|drm"
6

You might try forcing the console video mode as per this openSUSE thread (same ES1000 graphics card)…
https://forums.opensuse.org/showthread.php/494299-OpenSUSE-equivalent-of-Debian-s-update-grub
Hopefully, that will keep the monitor awake?

7

I found a solution, but doesn’t actually address the problem!
I used a different monitor and it now works fine.

First I tried forcing the screen to 1280x1024 in Yast->System->Boot Loader with the original monitor.
I was able to set the same parameters as suggested in the openSUSE thread, but it made no difference.
I also looked through dmesg, but found just the same errors I originally documented.

I then reset everything back to the original settings and put a different monitor on.
It worked immediately without any problem.

I also checked dmesg and Xorg.0.log and all the errors I was getting previously have gone away!

The ‘new’ monitor is an old Viewsonic VX800 with a max resolution of 1280x1024
The original one was a Dell E207WFP with a max resolution of 1680x1050

There’s obviously a bug in the driver, but I’ll just use the other monitor since I usually use VNC to access the system.

Thanks for all your advice.

Al

8

capekeppel wrote:
[color=blue]

There’s obviously a bug in the driver, but I’ll just use the other
monitor since I usually use VNC to access the system.[/color]

If you have maintenance you could still open a Service Request and
upload a Supportconfig to help SUSE diagnose the issue. That way others
could avoid the same problem.

–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.