graphics card – After waking GNU/Linux up from suspend display stays turned off

Hello everyone,

I am trying to solve an annoying problem which happened to me, when I migrated one of my boxes (computers:) from Ubuntu to it’s fully FSF compliant equivalent called Trisquel. Both of these two platforms are actually based on Ubuntu distros, however Trisquel is free of all proprietary libraries and other software.

The source of the problem which, I believe, is the result of my migrating to Trisquel, is that Trisquel no longer properly recognizes my graphic hardware, i.e, my graphic board that is recognized as (ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350 by lspci CLI command, as well as by whatever is the default fall back graphical driver, when the hardware is not properly identified during X-initialization process. Which you could see in the /var/log/Xorg.o.log, but which, together with my xorg.conf file, due to some rather dark, unexplained issues StackExchange trolls, hiding behind moderators and “bots”, have, I am prevented to publish here:(

Nevertheless, in this Xorg.o.log file, one can see, that my graphical board should require the open radeon driver to be loaded, which actually starts out to be the case, but is in the then further down the initialization process rejected and replaced with a default graphic driver, which I believe is the true culprit eventually even causing the suspend to exhibit its fatal flaw, of not waking up the display monitor. I believe that either or both of the two hardware pieces (my graphic board and/or the display monitor) are not EDID (Extended Display Identification Data compliant, which is actually accounted for in Ubuntu’s close radeon driver, but not in GNU/Linux FSF variant which uses open radeon graphic driver.

I was hoping, that reverting back to the good old Xorg.conf configuration file would solve the problem. Unfortunately, I was not able to accomplish that. Indeed I’ve tried to fix both approaches, the contemporary auto config, which utilizes external utilities, like xrandr, gtf, cvt, xvattr, etc, as well as the manual Xorg.conf configuration, that in the distant past would almost always work, providing, you supplied the correct hardware specifications in the configuration sections for your hardware.

And finally, regardless of whether we are able to solve “Xorg/suspend/monitor wake-up” problem, I would like to be able, indeed with some certainty, to identify what really the problem is. Primarily I wish to know it the problem is related to a graphic card, or a driver, and whether it would be possible to bypass the troubles, by replacing a graphic board with a different one. And last but not list, how can one learn which graphic cards are supported. As I have already pointed out, the list of supported hardware found in the Xorg.0.log file, can not be considered a reliable source!


1. Trying to see if auto config coukd be fixed

Short of posting my xorg related files, lets look at how does my “Xorg/suspend” problem on Trisquel manifests itself?


When I the CPU (computer) exits the suspend state it fails to turn on the monitor. After searching the Internet for posts describing similar problems, some suggested the problem might be in some settings in GRUB. As suggested, I tweaked the line GRUB_CMDLINE_LINUX=”” as shown undeer 1.1.1, and 1.1.2 by doing the following:

        $> sudo vi /etc/default/grub
        #> sudo uodate-grub


 GRUB_CMDLINE_LINUX="" >>>> GRUB_CMDLINE_LINUX="nouveau.modest=0"

Run sudo uodate-grub and tested if waking up the computer from suspend also wakes up the display monitor.

It does not!

Changing this line to


      GRUB_CMDLINE_LINUX="" >>>> GRUB_CMDLINE_LINUX="amdgpu.modest=0

Also does not have any effect!


Next, I checked xrandr output which consistently, always, displayed the same output. In particular I could never really got rid of the following xrandr: Failed to get size of gamma for output default message:

    $> xrandr
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 1600 x 1200, current 1600 x 1200,     \s
        maximum 1600 x 1200
    default connected primary 1600x1200+0+0 0mm x 0mm
       1600x1200     77.00* 


Changing –gamma value to 1.0 seems to fail with the resulting gamma value 0, as shown here:

        $> xrandr --output default --gamma 1.0:1.0:1.0
        xrandr: Gamma size is 0.


I could never get System -> Preferences -> Hardware -> Display to reflect any changes I make by running xrandr‘s –newmode, –addmode, though a subsequent query by running xrandr without any arguments (see 1.4.4) does show the new added mode:


        $> gtf 1920 1200 59.95
        # 1920x1200 @ 59.95 Hz (GTF) hsync: 74.46 kHz; pclk: 192.99 MHz
        Modeline "1920x1200_59.95"                                  \s
                       192.99   1920 2048 2256 2592                 \s
                                1200 1201 1204 1242  -HSync +Vsync


        $> xrandr --newmode "1920x1200_60.00"                       \s
                       193.25   1920 2056 2256 2592                 \s
                                1200 1203 1209 1245  -hsync +vsync


        $> xrandr --addmode VGA1 1920x1200_60.00


        $> xrandr
        xrandr: Failed to get size of gamma for output default
        Screen 0: minimum 1600 x 1200,                              \s
                       current 1600 x 1200,  maximum 1600 x 1200
        default connected primary 1600x1200+0+0 0mm x 0mm
         1600x1200     77.00* 
         1920x1200_60.00 (0x2bf) 193.250MHz -HSync +VSync
         h: width  1920 start 2056 end 2256 total 2592 skew 0 clock 74.56KHz
         v: height 1200 start 1203 end 1209 total 1245        clock 59.88Hz

None of the above has no effect, whatsoever, on the waking up of the display monitor when the computer wakes up from the suspend state.



I created ~/.xprofile and added the following to it:

    xrandr --output default --gamma 1.0:1.0:1.0
    xrandr --newmode "1920x1200_60.00" 193.25                   \s
                            1920 2056 2256 2592                 \s
                            1200 1203 1209 1245  -hsync +vsync

This ~/.xprofile also had no effect on SUSPEND problem, and Display app from the main Trisquel menu also did mot show the newly added mode!


1.6 Conclusion of manual settings using {{ xrandr )) command

In all of the above attempts, in many different combinations, when selecting System -> Preferences -> Hardware -> Display I was never able to get whichever resolution I managed to set by running xrandr commands. Also note that –gamma setting finally always failed and had an erroneous value 0.

But most importantly, I was never able to wake up my screen when waking up the computer from the suspend state!


2. Falling back to xorg.conf configuration file

This is the part, in which corporate culprits hiding between us in the open source community, are trying to prevent us to discuss in fear we could actually achieve, that their proprietary crap may actually became useless in maintaining their monopolies.


So, first is my xord.conf file. I created a new xorg.conf file (which you can see under (2.2), and copied it in its palace as shown in the folowing code segment:

    $> sudo cp /etc/X11/xorg.conf   /etc/X11/xorg.conf.$(date +%y%m%d-%H%M)
    $> sudo cp xorg.conf-NN         /etc/X11/xorg.conf


Due to the above sabotage, I am prevented to share with you my xorg.conf file.

And the following should be my partial /var/log/Xorg.0.log file, which just like the xorg.conf may be dangerous to corporate monopolies, and which effectively they prevented me from showing it to you!

Please note,

ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350

is my graphic card, as identified by

      $> sudo lspci |grep -y VGA
      01:00.0 VGA compatible controller:              \s
              Advanced Micro Devices, Inc. (AMD/ATI)  \s
              RV710 (Radeon HD 4350/4550)

as well as printed in the Xorg.0.log file. Also note how the header in the above output becomes the BusID, I created in the Devices section in my xorg.conf file.

        BusID    "PCI:1:0:0"

Needless to say, none of the above fixed the monitor wake up problem.

Any help or suggestions would be greatly appreciated.
Thank you in advance.