• Blank black screen after suspension/hibernation


    Hey Guys,

    unfortunately, suspension/hibernation does not work. If I activate one a black screen appears and I only can see and move my mouse, a login is not possible. Only a reset solves this issue. I’m using Gnome 3.24 on a Asus K52JC.

    Someone else had the same problem as mentioned here:
    link
    But the link to the solution is down.

  • @Slenx said in Blank black screen after suspension/hibernation:

    Someone else had the same problem as mentioned here:
    link
    But the link to the solution is down.

    Hi there and welcome to Antergos!

    It appears their link had an incorrect URL:disappointed:. Here’s the correct one:
    https://forum.antergos.com/topic/3172/display-is-black-after-waking-from-suspend-and-unlocking/2

    Hope this helps and good luck.

    Keep trying, never give up. In the end, you will find that it was all worth it

    Community ISO: https://antergoscommunityeditions.wordpress.com
    Linux Basics: https://linuxbasicssite.wordpress.com

  • Unfortunately, the trick does not work for me. As I change to gdm and do a restart after starting gdm I only get a black screen with the cursor.
    As I do not know what output exactly is needed I post the same mentioned in the thread above.
    Please let me know if something else is necessary.

    cat /etc/mkinitcpio.conf:

    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run.  Advanced users may wish to specify all system modules
    # in this array.  For instance:
    #     MODULES="piix ide_disk reiserfs"
    MODULES=""
    
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image.  This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way.  This is useful for config files.
    FILES=""
    
    # HOOKS
    # This is the most important setting in this file.  The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ##   This setup specifies all modules in the MODULES setting above.
    ##   No raid, lvm2, or encrypted root is needed.
    #    HOOKS="base"
    #
    ##   This setup will autodetect all modules for your system and should
    ##   work as a sane default
    #    HOOKS="base udev autodetect block filesystems"
    #
    ##   This setup will generate a 'full' image which supports most systems.
    ##   No autodetection is done.
    #    HOOKS="base udev block filesystems"
    #
    ##   This setup assembles a pata mdadm array with an encrypted root FS.
    ##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    #    HOOKS="base udev block mdadm encrypt filesystems"
    #
    ##   This setup loads an lvm2 volume group on a usb device.
    #    HOOKS="base udev block lvm2 filesystems"
    #
    ##   NOTE: If you have /usr on a separate partition, you MUST include the
    #    usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"
    
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    
    

    uname -r

    4.13.3-1-ARCH
    

    /usr/share/X11/xorg.conf.d

    10-nvidia-drm-outputclass.conf  10-quirks.conf  40-libinput.conf  70-synaptics.conf
    

    lspci | grep -e VGA -e 3D

    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
    01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)
    

    loginctl list-sessions

    SESSION        UID USER             SEAT             TTY             
            c1       1000 tim              seat0                            
    
    1 sessions listed.
    

    Can’t find neither pm-utils nor xf86-video.

  • @Slenx said

    As I change to gdm and do a restart after starting gdm I only get a black screen with the cursor.

    You mean after logging in? If so, this could be because your card doesn t support *wayland. You should use the *gnome on xorg option in this case.

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • @anarch said in Blank black screen after suspension/hibernation:

    You mean after logging in? If so, this could be because your card doesn t support *wayland. You should use the *gnome on xorg option in this case.

    No, the whole time my display stays black. No login window appears. It’s only possible to login with ctrl+alt+f2 without a graphic interface.

  • @Slenx said in Blank black screen after suspension/hibernation:

    lspci | grep -e VGA -e 3D
    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
    01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)

    so optimus/bumblebee is configured or not?
    https://antergos.com/wiki/hardware/bumblebee-for-nvidia-optimus/

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Neither nouveau nor bumblebee are installed yet.
    Installed are:

    • mesa
    • xf86-video-intel
    • nvidia-340xx
    • nvidia-340xx-utils
    • lib32-nvidia-340xx-utils

    Is it possible to install bumblebee afterwards without setting up a fresh antergos?

  • sure his is the way to install it ;)

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Ok, but which graphic card is currently in use?
    What bumblebee does is to manage (or switch?) these two cards in order to achieve the best performance regarding graphic power and power consumption, right?
    So would there be a noticeable improvement when switching to bumblebee?
    Could bumblebee solve the black screen error?

  • as you write that you have both drivers installed black screen can be caused by unconfigured bumblebee yes sure… it is possible to disable discrete card also and only use nvidia card also, as far as i know…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • @Slenx

    If you use only the Intel graphics card, does the problem persist? You can test it by blacklisting nouveau and nvidia drivers.
    You can see what modules you are currently using with:

    lsmod | grep -i intel
    lsmod | grep -i nouveau
    lsmod | grep -i nvidia
    

    and this gives also some more information:

    lspci -k | grep -i vga
    
blank13 black44 Posts 11Views 238
Log in to reply