Page MenuHomeSolus

Closing lid gives black screen
Closed, InvalidPublic

Description

I have HP Pavilion g6 series, and whenever I close the lid it gives a black screen after I open the lid again. I have to force shutdown the laptop then I can use it again.

Event Timeline

Botanium created this task.Dec 7 2016, 8:31 AM

Please confirm against a fully-updated system and ensure you have TLP disabled / uninstalled.

TLP is uninstalled and system is fully-updated but I have also switched from the Budgie desktop to the Mate desktop.

So far, the issue has not occured so I believe the fix might have been fixed.

I am facing same issue in ASUS K556UR. Whenever I close the lid or the laptop goes to sleep I get a black screen. Maybe these outputs can help?

botanium@soluspc ~ $ inxi -Fx
System:    Host: soluspc Kernel: 4.13.5-24.current x86_64 bits: 64 gcc: 6.4.0 Desktop: Budgie 10.4
           Distro: Solus 3
Machine:   Device: laptop System: ASUSTeK product: X556URK v: 1.0 serial: N/A
           Mobo: ASUSTeK model: X556URK v: 1.0 serial: N/A
           UEFI: American Megatrends v: X556URK.306 date: 02/27/2017
Battery    BAT0: charge: 35.2 Wh 97.0% condition: 36.3/38.0 Wh (95%) model: ASUSTeK ASUS status: Discharging
CPU:       Dual core Intel Core i7-7500U (-HT-MCP-) arch: Kaby Lake rev.9 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11616
           clock speeds: max: 3500 MHz 1: 2900 MHz 2: 2900 MHz 3: 2900 MHz 4: 2900 MHz
Graphics:  Card-1: Intel HD Graphics 620 bus-ID: 00:02.0
           Card-2: NVIDIA GM108M [GeForce 930MX] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.18.4 ) drivers: modesetting,nvidia Resolution: 1920x1080@60.05hz
           OpenGL: renderer: GeForce 930MX/PCIe/SSE2 version: 4.5.0 NVIDIA 384.90 Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.13.5-24.current
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 02:00.0
           IF: enp2s0 state: down mac: 2c:4d:54:39:89:b0
           Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: 58:00:e3:00:dc:97
Drives:    HDD Total Size: 1000.2GB (12.5% used)
           ID-1: /dev/sda model: ST1000LM035 size: 1000.2GB
Partition: ID-1: / size: 912G used: 117G (14%) fs: ext4 dev: /dev/dm-1
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 221 Uptime: 9 min Memory: 1588.0/7930.7MB Init: systemd Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.3.38

this also

botanium@soluspc ~ $ sudo journalctl -p 3 -xb
Password: 
-- Logs begin at Sun 2017-09-24 13:25:33 +03, end at Sat 2017-10-14 17:14:00 +03. --
Oct 14 17:01:56 soluspc systemd-udevd[503]: specified group 'scanner' unknown
Oct 14 17:02:05 soluspc bluetoothd[655]: Failed to set mode: Blocked through rfkill (0x12)
Oct 14 17:02:23 soluspc lightdm[780]: gkr-pam: couldn't unlock the login keyring.
Oct 14 17:02:23 soluspc systemd-logind[633]: Failed to remove runtime directory /run/user/620: Permission denied
Oct 14 17:02:27 soluspc pulseaudio[1043]: [pulseaudio] pid.c: Daemon already running.
Oct 14 17:02:36 soluspc bluetoothd[655]: Failed to set mode: Blocked through rfkill (0x12)
JoshStrobl moved this task from Backlog to Input on the Hardware board.Oct 26 2017, 2:56 AM

apparently, this doesn't have a solution. I just reinstalled Solus again and I am facing the same issue.

I am also facing the same issue. It seems to only occur after the installation of proprietary Nvidia drivers. Here are some forum posts that seem to talk about the issue:

Is there anything I can do to help advance this issue? This is perhaps one of the few things that is preventing me from using Solus as my daily driver OS.

About a month ago, I found a little workaround/fix for the freezing on wake from suspend, and I made a forum post here: https://solus-project.com/forums/viewtopic.php?f=11&t=12253. I just remembered that I posted in this bug report, so I thought I would add the link for future reference.

Basically the fix is just adding the following to your kernel boot parameters: acpi_osi=! acpi_osi='Windows 2009'. In the forum post, I just go through more details for describing/diagnosing the freezing issue.

DataDrake triaged this task as Needs More Info priority.Oct 16 2018, 10:06 PM
DataDrake added a subscriber: DataDrake.

Is this still an issue?

JoshStrobl closed this task as Invalid.Nov 4 2018, 12:23 PM

Closing due to lack of response.