LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Black screen when returning from suspend mode on 14.2 (https://www.linuxquestions.org/questions/slackware-14/black-screen-when-returning-from-suspend-mode-on-14-2-a-4175617834/)

ctrondheim 11-17-2017 03:13 PM

Black screen when returning from suspend mode on 14.2
 
I've installed Slackware for the first time. Everything went well, and I'm liking 14.2 very much. I haven't done much except setup and configuring so far.

I've run into a problem when returning from suspend mode. the screen is black, but if I do a ctrl-alt-del laptop reboots eventually ( btw hibernation works fine). There are 2 video chipsets: intel and nvidia.
Currently cannot get nvidia to work (more about this in another posting), so am using the intel.

This is the command I use to suspend/sleep:
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

Can someone help me resolve the black screen problem?
Thanks.

Not sure what specs to include, but here are some:
Asus laptop with
intel core i7-7700HQ @ 2.8Ghz
intel HD graphics 630
nvidia GeForce GTX 1050 Ti
intel dual band wireless AC-7265

lspci output:
00:00.0 Host bridge: Intel Corporation Device 5910 (rev 05)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1)
00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation Device 1c8c (rev a1)
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)

brobr 11-19-2017 11:43 AM

Quote:

Originally Posted by ctrondheim (Post 5781856)
This is the command I use to suspend/sleep:
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

Hi,with the same cpu on board, running xfce, suspend/resume from the DE is fine at my end though I need my screen to get alive with a mouse click, some key-press or other form of activity. Maybe because my screen gets locked (power-manager setting in xfce) on suspend. Or is set to blank on inactivity for a short while.


Why are you not using the command pm-suspend? Maybe worth a try:
From "man pm-suspend"
Quote:

On some hardware putting the video card in the suspend state and
recovering from it needs some special quirk handling.

hth

ctrondheim 11-19-2017 12:39 PM

Quote:

Originally Posted by brobr (Post 5782539)
Hi,with the same cpu on board, running xfce, suspend/resume from the DE is fine at my end though I need my screen to get alive with a mouse click, some key-press or other form of activity. Maybe because my screen gets locked (power-manager setting in xfce) on suspend. Or is set to blank on inactivity for a short while.


Why are you not using the command pm-suspend? Maybe worth a try:
From "man pm-suspend"



hth

I did not know about pm-utils. Thanks for pointing it out. So I did a man pm-suspend and then tried it with
--quirk-dpms-suspend with the same results, black screen. It is only the video that is messed up because I can do a
reboot to get back into laptop. I'm not sure about the other quirks options.

Do you have same video chips as me? if so do you have to blacklist anythings and / or have you been able to get
the nvidia to work?

I'm still learning about Linux so I dont know what to configure or not.

brobr 11-19-2017 01:44 PM

No I only have the intel on-board graphics;

[rant]
since nvidia produced graphics chips that were 'melting' along route and reduced a whole generation of laptops to the scrapheap just after a year's usage without taking any responsibility I do not spend my money on their products. This was followed by their linux-unfriendly 'optimus' hybrid stuff (for which the bumblebee project gave some respite) that AMD also implemented but by then I decided to stay away from extra graphics cards that basically caused my battery not to outlast my commute...
[/rant]

As sleep/resume can hang on graphics (I had an ATI card for a while, also in an Asus, and had run in problems around resume after kernel upgrades etc) fat chance it is something to do with your extra graphics card that is not picked up on resume.

Did you (re-)install the nvidia blurp after the linux install (otherwise the mesa and other bits are not those the nvidia card needs) or are you using nouveau (if the card is very recent possibly the nouveau doesn't cope, but I am just guessing here)?

Best to search the forum for (recent) posts on this card ....

EDIt:

PS: 'man pm-suspend' shows you the info about the command 'pm-suspend'; always good to check the man pages to understand what commands are up to and how

EDIT2:

As Ztcoracat advised here, check https://docs.slackware.com/howtos:ha...aphics_drivers

ctrondheim 11-22-2017 04:18 PM

Quote:

Originally Posted by brobr (Post 5782572)
No I only have the intel on-board graphics;

[rant]
since nvidia produced graphics chips that were 'melting' along route and reduced a whole generation of laptops to the scrapheap just after a year's usage without taking any responsibility I do not spend my money on their products. This was followed by their linux-unfriendly 'optimus' hybrid stuff (for which the bumblebee project gave some respite) that AMD also implemented but by then I decided to stay away from extra graphics cards that basically caused my battery not to outlast my commute...
[/rant]

As sleep/resume can hang on graphics (I had an ATI card for a while, also in an Asus, and had run in problems around resume after kernel upgrades etc) fat chance it is something to do with your extra graphics card that is not picked up on resume.

Did you (re-)install the nvidia blurp after the linux install (otherwise the mesa and other bits are not those the nvidia card needs) or are you using nouveau (if the card is very recent possibly the nouveau doesn't cope, but I am just guessing here)?

Best to search the forum for (recent) posts on this card ....

EDIt:

PS: 'man pm-suspend' shows you the info about the command 'pm-suspend'; always good to check the man pages to understand what commands are up to and how

EDIT2:

As Ztcoracat advised here, check https://docs.slackware.com/howtos:ha...aphics_drivers

Ok I've installed Slackware 14.2 on another asus (x555b) which uses Radeon R5 chipset and I get same behavior as on laptop using nvidia. I also get other weired console behavior as posted in another thread.
I'll keep investigating. Thanks

brobr 11-23-2017 06:12 AM

just a an observation: when I run pm-suspend from the command-line my comp goes 'more asleep' than when doing this from within the DE (xfce). For the latter a mouse-click is enough to re-awaken the screen. In case of the command-line suspend I have to press the on/off button (not too long) to get the same result (i.e. resume completing); almost as if the comp had been hibernating.

Because of your new hardware you need to use a fairly recent kernel for the cpu; I used up from 4.10.x to get proper support for the graphics.
Note that the i7 is a kabylake processor , not a Skylake. For comparison this is what I get on 4.14.1 with lspci on my intel core i7-7700HQ @ 2.8Ghz, intel HD graphics 630 box for the processor:
Code:

bash-4.4# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
..

Pre-compiled kernel-images (the bleeding-edge 4.14.x in -current seems to give many problems) can also be found here with explanation here

Also make sure to upgrade with updates for 14.2-packages in the patches-folder.

Further, as both systems have different external chips (nvidia and amd) but the problems appear comparable I would look into the general set-up.
1) What do you use to start the boxes, elilo (if eufi, as could be expected on such a new box), grub or lilo? Do you need kernel/graphics info for the resume (in grub???)
2) the general (with mkinitrd) or huge kernel?


It might help to search this forum for threads with more info that could give you clues. Make sure that you check whether remarks are relevant (i.e. for your card/cpu); eg. with "intel graphics" (but also try 'hybrid graphics', 'bumblebee' etc:)
slackware64-and-kaby-lake
slackware-14-2-and-latest-stable-mesa
slackware64-14-2-intel-iris-640-integrated-graphics-drm
black-screen-after-installing-nvidia-on-slackware-14-2
slackware-14-2-muxless-ati-intel-laptop-and-amdgpu-non-pro-installation


Also check out whether the proprietary drivers (if you use them) have any know issues; e.g. here for radeon 5

ctrondheim 11-23-2017 09:46 AM

Quote:

Originally Posted by brobr (Post 5784230)

Because of your new hardware you need to use a fairly recent kernel for the cpu; I used up from 4.10.x to get proper support for the graphics.
Note that the i7 is a kabylake processor , not a Skylake. For comparison this is what I get on 4.14.1 with lspci on my intel core i7-7700HQ @ 2.8Ghz, intel HD graphics 630 box for the processor:

Pre-compiled kernel-images (the bleeding-edge 4.14.x in -current seems to give many problems) can also be found here with explanation here

Also make sure to upgrade with updates for 14.2-packages in the patches-folder.

Further, as both systems have different external chips (nvidia and amd) but the problems appear comparable I would look into the general set-up.
1) What do you use to start the boxes, elilo (if eufi, as could be expected on such a new box), grub or lilo? Do you need kernel/graphics info for the resume (in grub???)
2) the general (with mkinitrd) or huge kernel?


It might help to search this forum for threads with more info that could give you clues. Make sure that you check whether remarks are relevant (i.e. for your card/cpu); eg. with "intel graphics" (but also try 'hybrid graphics', 'bumblebee' etc:)
slackware64-and-kaby-lake
slackware-14-2-and-latest-stable-mesa
slackware64-14-2-intel-iris-640-integrated-graphics-drm
black-screen-after-installing-nvidia-on-slackware-14-2
slackware-14-2-muxless-ati-intel-laptop-and-amdgpu-non-pro-installation


Also check out whether the proprietary drivers (if you use them) have any know issues; e.g. here for radeon 5

Great links thanks!
I've actually tried the 4.14.1 kernel. I compiled it my self but used Slackware config as a starter. I did some minor changes like excluded some filesystems but included xfs. 4.14 was fine except it would not reboot. then tried 4.14.1 and this caused freeze when doing startx. So am back to Slackware's stock generic.

I do not know how to interpret the xorg log file. I need to understand whether xorg is using intel, nouveau, or vesa driver. I'll keep digging and report back. On the radeon machine I can see that radeon is used.
I have not installed any propriety drivers yet as I need to understand how to do it first.

brobr 11-23-2017 11:15 AM

Quote:

Originally Posted by ctrondheim (Post 5784286)
Great links thanks!
I've actually tried the 4.14.1 kernel. I compiled it my self but used Slackware config as a starter. I did some minor changes like excluded some filesystems but included xfs. 4.14 was fine except it would not reboot. then tried 4.14.1 and this caused freeze when doing startx. So am back to Slackware's stock generic.

Please correct me, but I assume you are using slackware64; efi, elilo bootloader (or grub? ; if so I cannot really help you), huge kernel

The problem with 14.4, if you are using the huge version is that it is too big for the version of elilo (if you use that) shipped with 14.2.
Also it might need an initrd.gz (which will be different from the one installed with the stock kernel); so possibly two reasons the reboot did not work.

With bleeding edge stuff keep track of the posts on current in this forum; many problems will relate to trying the latest kernel etc.

Still when using eufi and the 'BIOS' already has an entry for Slackware, you can mount the /boot/efi-partition and copy over the kernel and its initrd.gz from /boot to where the current kernel and initrd.gz are on the efi-partition (using mc makes this fairly straightforward). Note that you have to edit the (elilo).config to get the new kernel and image loaded. Unmount the efi before rebooting (to keep the fat filesystem in order)

You could try the more tested (higher version) kernel-4.13.15 from Dave Spencer (https://dusk.idlemoor.tk/ mentioned earlier). For me that works fine.
The only drawback for you might be that that only comes as a generic kernel and for that you have to create an initrd.gz using mkinitrd. The initrd contains modules that are needed during boot like for the filesystem of your root partition.

There is a Readme in /boot for mkinitrd and in /etc/ a config-file that you would call with the -F parameter when running the command when in /boot; making it quite easy to recreate an image for any installed kernel: "mkinitrd -c -k 4.13.15 -F"; You have to edit this /etc/mkinitrd.config file as it needs values specific for your set-up for root partition, root filesystem etc. (see that file)

It's best to give each initrd.gz a kernel-related name (e.g. initrd-4.13.15.gz) and copy that with the kernel from the boot folder to the EFI partition. Include xfs as a module if that is the fs for the / partition (and possibly other modules that have to be loaded during boot, say drivers for the drive (nvme for example) that contains the root partition; or modules to unlock an encrypted disk with the /home folder etc.;) graphics cards get used at a later stage:
Quote:

bash-4.4# dmesg | grep -i 'frame buffer'
[ 0.533764] Console: switching to colour frame buffer device 240x67
[ 0.536992] fb0: EFI VGA frame buffer device
[ 18.418570] Console: switching to colour frame buffer device 240x67
[ 18.451995] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Quote:


I do not know how to interpret the xorg log file. I need to understand whether xorg is using intel, nouveau, or vesa driver. I'll keep digging and report back. On the radeon machine I can see that radeon is used.
I have not installed any propriety drivers yet as I need to understand how to do it first.
The top gives nice information about the system (you can see that for me it is an EFI system)
Quote:

bash-4.4# less /var/log/Xorg.0.log

[ 36.359]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[ 36.367] X Protocol Version 11, Revision 0
[ 36.370] Build Operating System: Slackware 14.2 Slackware Linux Project
[ 36.373] Current Operating System: Linux knotsUL 4.14.1 #1 SMP Tue Nov 21 22:50:27 CST 2017 x86_64
[ 36.373] Kernel command line: \EFI\Slackware\vmlinuz-generic-4.14.1 initrd=EFI\Slackware\initrd-4.14.1.gz
further look out for 'module', 'nouveau', 'intel' (e.g. 'less /var/log/Xorg.0.log | grep 'intel')

other good control is trying (f)glxgears (the f included for the nvidia driver)

hth

eduardomiller 01-13-2020 12:12 AM

I am interested in knowing Slackware. Can anyone give me a link to know it in more detail?

TracyTiger 01-13-2020 11:51 AM

Quote:

Originally Posted by eduardomiller (Post 6077731)
I am interested in knowing Slackware. Can anyone give me a link to know it in more detail?

You may want to look at this sticky thread in this forum. You can browse it forward from 2008 or browse it in reverse order to get more recent stuff first.

so-you-want-to-be-a-slacker-what-do-i-do-next

Note that members post links to informational sites in their signatures.

EDIT: The last post from this month has a significant number of links to current information.

bassmadrigal 01-13-2020 06:52 PM

Quote:

Originally Posted by eduardomiller (Post 6077731)
I am interested in knowing Slackware. Can anyone give me a link to know it in more detail?

I would say the better thing than that thread is to check out http://docs.slackware.com/

The thread mentioned above is one person's vision on what might be beneficial to Slackware and has a lot of pages to dig through for information that may or may not be beneficial to your current level/usage of Slackware. The SlackDocs project is a wiki and will hopefully give you a great start on what you need to do to use Slackware the way you want it used.

Of course, if you have any questions or get stuck, feel free to create a new thread and we'd be happy to help.


All times are GMT -5. The time now is 12:35 AM.