Arch Linux

kflak

Member

Registered: 2017-09-23

Posts: 52

[SOLVED] Black screen after lid close

Hi all,

I installed the linux-rt-bfq kernel and now I am having trouble with power management. When opening the lid the screen is completely black (no backlight, no nothing), and it doesn't respond to any keyboard presses. I have tried disabling xfce4-powermanager, i3lock as well as caffeine, but to no avail. I am using nouevau drivers on a MacBook Pro mid-2013. The only way to "solve" this is by way of power button and reboot. Where should I start looking for a fix for this? I have 0 failed systemctl units. journalctl -xe output is:
https://pastebin.com/E5cFpD74

Grateful in advance,
K

Last edited by kflak (2017-12-02 18:48:48)

lo1

Member

Registered: 2017-09-25

Posts: 584

Re: [SOLVED] Black screen after lid close

As a good start, I'd try editing your /etc/systemd/logind.conf: uncomment and set

HandleLidSwitch=ignore

and see if this is a waking up thing rather than a backlight issue.

P.S. probably you'd need to reboot/login again to apply this change.
EDIT: nope, for future reference, to apply changes just run

systemctl restart systemd-logind

Last edited by lo1 (2017-11-22 16:46:19)

---

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

kflak

Member

Registered: 2017-09-23

Posts: 52

Re: [SOLVED] Black screen after lid close

Thanks for that. Didn't change anything, so I suppose it is a wake-up issue then?

lo1

Member

Registered: 2017-09-25

Posts: 584

Re: [SOLVED] Black screen after lid close

Thanks for that. Didn't change anything, so I suppose it is a wake-up issue then?

Not really, this means the issue is with nouveau driver/backlight.
Let's see

lspci -k
ls /etc/modprobe.d
cat /etc/mkinitcpio.conf
cat /var/log/Xorg.0.log

---

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

kflak

Member

Registered: 2017-09-23

Posts: 52

Re: [SOLVED] Black screen after lid close

Here it is! Forgive the lack of code tags, I can't find any documentation on how to do them...

EDIT: now I know :-)

lspci -k 

https://pastebin.com/AzP9jrqV

ls /etc/modprobe.d 

bcwc-pcie.conf  hid_apple.conf

cat /etc/mkinitcpio.conf 

https://pastebin.com/pDJfK1iy

cat /var/log/Xorg.0.log 

https://pastebin.com/apMyk3Qq

Last edited by kflak (2017-11-22 20:00:08)

lo1

Member

Registered: 2017-09-25

Posts: 584

Re: [SOLVED] Black screen after lid close

Mmh, try adding

nouveau

under MODULES, in your mkinitcpio.conf, then run

mkinitcpio -p linux

and reboot.
Also, see https://wiki.archlinux.org/index.php/Ma … d.2FResume
P.S. before rebooting, undo the logind.conf change I suggested you in post #2
P.P.S. regarding code tags, see help. It's ok to use pastebin (just do not write code as plain text in your posts

---

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

kflak

Member

Registered: 2017-09-23

Posts: 52

Re: [SOLVED] Black screen after lid close

Thanks on all three counts! Placing nouveau in the mkinitcpio.conf did the trick! Will mark as solved and prettify my previous offending plain text :-)

kflak

Member

Registered: 2017-09-23

Posts: 52

Re: [SOLVED] Black screen after lid close

Terribly sorry to reopen this thread, but the monster is back. I have followed all the steps above, but no way to get the screen back online after suspend. Additionally I tried installing https://aur.archlinux.org/packages/mba6x_bl-dkms/, but this doesn't seem to help either.

Output of

cat /var/log/Xorg.0.log

is https://pastebin.com/367ts92r

/etc/mkinitcpio.conf

looks like this:

# 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=(nouveau)

# 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 filesystems keyboard 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=()

Any help greatly appreciated!

Running linux-rt-bfq kernel.

lo1

Member

Registered: 2017-09-25

Posts: 584

Re: [SOLVED] Black screen after lid close

Damn, it really doesn't work?
Try placing 20-nouveau.conf in /etc/X11/xorg.conf.d containing

Section "Device"
    Identifier "Nvidia card"
    Driver "nouveau"
EndSection

and restart Xorg.
(if this works, you may need to add some options later, like vsync, accelmethod and such according to your preferences)

---

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

kflak

Member

Registered: 2017-09-23

Posts: 52

Re: [SOLVED] Black screen after lid close

Hi lo1,

Thanks for keeping looking into this with me :-)
So, I tried to do this, and obviously I pasted verbatim what you wrote, which didn't work and I realize is very stupid, now that I think about it, but I am not sure what I would put into the card identifier? I tried

Section "Device"
    Identifier "GeForce GT 750M Mac Edition"
    Driver "nouveau"
EndSection

also without much luck.

The output of

lspci 

is

00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
00:01.0 PCI bridge: Intel Corporation Crystal Well PCI Express x16 Controller (rev 08)
00:01.1 PCI bridge: Intel Corporation Crystal Well PCI Express x8 Controller (rev 08)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03)
04:00.0 Multimedia controller: Broadcom Limited 720p FaceTime HD Camera
05:00.0 SATA controller: Samsung Electronics Co Ltd Apple PCIe SSD (rev 01)
06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
08:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI [Falcon Ridge 4C 2013]

EDIT: A bit more info: it seems this is connected with the kernel, somehow. When I start up from linux-rt-lts suspend seems to work as expected, whereas when I start from linux-rt-bfq it doesn't... I suppose I should lob this ball to the maintainers of that particular package. In the meanwhile I will remark this thread as solved and hope that it will be resolved in a future upgrade of rt-bfq...

Last edited by kflak (2017-12-02 18:48:31)