[SOLVED] Black screen after screenlock, cannot unlock and have to REISUB - what could be causing it?

Lysander666 · 01-19-2018, 04:34 AM

Quote:

Originally Posted by Didier Spaier

as root:

Code:

nmtui-connect

To know more:

Code:

man nmtui
man nmcli

Very helpful, thank you. Just taken a look at the man page.

Quote:

Originally Posted by Didier Spaier

But insure that your $HOME and all the files in it are owned by yourself i.e. $USER.

So this is something to do with chown, as far as I can tell.

As root

Code:

chown -R lysander /home

is, I think, the answer

Didier Spaier · 01-19-2018, 04:54 AM

Quote:

Originally Posted by Lysander666

Code:

chown -R lysander /home

is, I think, the answer

Instead:

Code:

chown -R lysander /home/lysander

Here:

Code:

didier[~]$ echo $USER $HOME
didier /home/didier
didier[~]$

Tip: run the command as regular user. If some files are not owned by lysander, you will be warned. If that is the case, find out who owns these files and why, then take the appropriate measures as root (like moving the file elsewhere or deleting it or changing its ownership).

Lysander666 · 01-19-2018, 02:19 PM

Well, I'm just amazed and quite happy with how this went. I am now able to boot to desktop. Thanks to Didier Spaier for all the help. The steps I took were:

1. chown -R lysander /home/lysander - this was unproblematic, done as my user name.

2. Linking up with my router though nmtui-connect - a very useful thing to know.

3. I had to download lxsession (0.5.3) through wget since for some reason lftp -c "mirror https://slackbuilds.org/repository/14.2/system/lxsession/" didn't work. Maybe I just wasn't connected properly at that point. I used wget to get the lxsession from Slackbuilds but I also had to download the dependencies vala and libunique [references via my main box].

4. Built all packages and installed using ugpradepkg --reinstall

Here is the moment of success.

That was a great learning experience and one of my most successful pieces of Linux schooling so far. Great community effort!

xscreensaver and waking from sleep seem to be working well too now.

ChuangTzu · 01-19-2018, 02:39 PM

make a note of the /home/[user] permissions tip, if you ever share /home with other distros (ahem openSUSE/Gecko) they can screw up permissions.

and yes LQ/Slackware is a great resource for *nix schooling.

Lysander666 · 01-31-2018, 02:34 PM

I'm having to resuscitate this topic - I thought the issue had been sorted out but it unfortunately hasn't been.

On opening my netbook in a tutorial tonight [waking it from sleep], I again got a black screen and had to do a hard reset to reboot [REISUB didn't work].

I have since done some experiments and if I invoke physlock, unlock and then try to lock it again a few seconds later, I'm back with a black screen. I tried this several times with different DEs/WMs - Xfce, LXDE, Fluxbox and Blackbox, and always the second time I got a black screen and had to REISUB. I tried the huge kernel instead of generic, same issue.

So I know that it's not LXsession that was causing the issue. I wonder what it could be. Can anyone shed any more light on the possible causes for this?

brobr · 02-01-2018, 04:10 AM

Hi Lysander, do you have hibernating or sleep set up? I am just wondering whether upon resuspend the computer cannot find the stuff to revive the screen.
Also, the graphics card that are you using might affect sleep/resuspend (or do you have onboard graphics?)

PS I do not think xscreensaver is essential; there is also another one that, as you noticed, kicks in and is fine. I leave xscreensaver off my system as it always gave me trouble and I was not interested in figuring out why; black is fine to me

Lysander666 · 02-01-2018, 04:21 AM

Quote:

Originally Posted by brobr

Hi Lysander, do you have hibernating or sleep set up? I am just wondering whether upon resuspend the computer cannot find the stuff to revive the screen.
Also, the graphics card that are you using might affect sleep/resuspend (or do you have onboard graphics?)

When you say 'set up', do you mean in the power manager? This is where I enabled the settings yes, in the XFCE power manager [I am using LXDE, does LXDE have its own power manager?].

The more I think about this, yes, the more I think it could be to do with the graphics. The reason for this idea are:

Quote:

Usually problems occur when resuming, and normally the culprit is a device driver that does not recover from a powered down state. If your computer successfully performs a suspend, then it is quite likely any resume problems are due to another device driver and not the ACPI subsystem.

https://wiki.ubuntu.com/DebuggingKernelSuspend

For more debugging:

Quote:

Which part of the process does the issue occur with, the suspend to ram, or resuming from?
Please advise how you suspended specifically. For example: Executing at a terminal pm-suspend Shutting the lid of your laptop, which is set to suspend on close [it also happens after trying to resume from physlock
Please advise how you resumed specifically. For example: Pressed the power button, Lifted the lid, Clicked a key on the keyboard

I'm using onboard graphics, specifically Intel 945GME. Now, I imagine the driver is installed by default. However, it is probably just glitchy on resume. Here is an old post about 945GME on Slackware and configuring xorg

http://kuntoaji.blogspot.co.uk/2009/...are-linux.html

Now another theory is to do with SWAP, but I don't think this is the problem since I have a SWAP partition. Still, this user managed to fix a resume problem by creating a SWAP file on Slack

https://unix.stackexchange.com/quest...leep-mode?rq=1

brobr · 02-01-2018, 04:58 AM

Hi Lysander, I have onboard intel graphics as well, for years (and for the same duration no xscreensaver);

I also use xfce's power-manager (note the handy tick-box "presentation-mode" if you use the power-manager-plugin in a desktop-panel (on xfce); when ticked; it keeps your screen alive when doing presentations)

I hibernate to swap and suspend to ram

In my /etc/mkinitrd.conf I have "RESUMEDEV="/dev/<LUKS-partition>/swap" needed for hibernation; but mostly I use suspend to ram (I have a lot of ram and not so much swap-space).

Also I think xfce uses pm-suspend: check out man pm-suspend and /etc/pm. In /etc/pm/sleep.d/ I placed this simple script (10_disconnect) as I often need to rush away from work to catch a train...(note that for Network-manager to accept this script, only user root has rwx, group root and others have only r permission)

Code:

#!/bin/bash
#
# want to disconnect internet stuff when going to sleep
# kill wifi/eth0 connection; unmount networked folders
# like nm does after losing connection
#

case $1 in
    hibernate)
        /usr/bin/nmcli networking off
    ;;
    suspend)
        /usr/bin/nmcli networking off
    ;;
    thaw)
    ;;
    resume)
        /usr/bin/nmcli networking on 
        # maybe not to save battery when opening on train    
    ;;
    *) 
    ;;
esac

hth

PS In the /etc/Network-Manager/dispatcher.d I put a script that organizes mounting of networked folders etc. I basically use nm to sort connected stuff out

Lysander666 · 02-01-2018, 05:55 AM

Thanks for the script, looks very useful, I'll give it a go.

Historically, it looks like this has been a problem for a few people in Slack. A few people have posted on this forum saying they have the same issue as me - sleeps fine, on resume the screen is black and the computer doesn't respond to key presses. This looked interesting though

https://www.linuxquestions.org/quest...ml#post3767147

Quote:

Ok, found it out myself. I had to create following file:

Code:

vladimir@darkstar:~$ cat /etc/pm/config.d/unload_modules
SUSPEND_MODULES="video"

So to summarize. I do not have any quirks.

Code:

vladimir@darkstar:~$ lshal |grep quirk
  power_management.quirk.s3_bios = false  (bool)
  power_management.quirk.s3_mode = false  (bool)

I just have to remove acpi video module (see above).

brobr · 02-01-2018, 08:40 AM

Quote:

Originally Posted by Lysander666

Thanks for the script, looks very useful, I'll give it a go.

Historically, it looks like this has been a problem for a few people in Slack. A few people have posted on this forum saying they have the same issue as me - sleeps fine, on resume the screen is black and the computer doesn't respond to key presses. This looked interesting though

https://www.linuxquestions.org/quest...ml#post3767147

Hi, the script by itself doesn't do much as networking will be halted by lack of connection; it only helps to get scripts in the nm-dispatcher called and executed before everything is put into suspension. I needed the networked folders unmounted as otherwise; when at home and no longer networked at work, Thunar would hang in search for these work-space-specific folders.

Further, Slackware does not put more in place than some sensible defaults but mostly things need setting up using config files in /etc. Your config.d/unload_modules is an addition that did not come with pm-suspend (my config.d is empty) and such additions will mostly not be 'catered for' by the distribution. There are simply too many variables to take into account. The way around is reading man-pages and having an idea about the source of the problem (graphics card) might help. That's not easy and that's why this forum is so great; one learns a lot by following posts or searching it when having a problem and starting a post of course (and preferentially in that order ;-).

If the issue is solved, please mark the thread as such (in 'Thread tools at the top right of the page): you will see that will bump readership ;-)

Lysander666 · 02-01-2018, 01:59 PM

I thought that since Slack was using framebuffer rather than the gfx driver, I should amend xorg.conf-vesa since it may not be using the acutal driver. I changed

Code:

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

to

Code:

Section "Device"
    Identifier "Card"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "Mobile 945GSE Express Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "VBERestore" "true"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

Section "Screen"
Identifier "Screen 1"
Device "Card"
Monitor "My Monitor"

Output of lsmod | grep video and glxinfo | grep render

Code:

uvcvideo               70035  0
videobuf2_vmalloc       4288  1 uvcvideo
videobuf2_memops        1523  1 videobuf2_vmalloc
videobuf2_v4l2         17941  1 uvcvideo
videobuf2_core         21658  2 uvcvideo,videobuf2_v4l2
v4l2_common             3714  1 videobuf2_v4l2
videodev              132108  4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
video                  27356  2 i915,samsung_laptop
i2c_core               41745  9 drm,i915,i2c_i801,i2c_dev,i2c_hid,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev

lysander@lysurfer_viii:/etc/X11$ glxinfo | grep render
direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
    GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer,

But still no difference. I may even be barking up the wrong tree with the graphics theory but I feel I'm running out of options.

EDIT: I may be on the wrong track after all. If I lock the screen using the LXDE Logout menu, and unlock, it's fine. Also, if I suspend using the LXDE Logout menu [rather than just closing the lid], not only does it suspend a lot quicker, but waking up and displaying the screen as normal is no issue. Both processes use xscreensaver. Physlock does not use xscreensaver and waking from sleep does not [as far as I remember from my configuration].

So the problem seems to be rooted in the fact that physlock/suspend XFCE power manager do not use xscreensaver. When I do everything through the LXDE Logout menu, it's fine. Which is a perfectly acceptable workaround for now.

I suppose I should keep my xorg configs?

brobr · 02-01-2018, 02:35 PM

note that the xorg.conf-vesa is for the vesa-driver but not used as xorg.conf because of the '-vesa' end.

Currently a xorf.conf is hardly needed and if changes/additions are to be made (as you tried to do in the xorg.conf-vesa) just add a small file describing that section in /etc/X11/xorg.conf.d/ according to man xorg.conf. Also additions for specific keyboards, input devices etc can be put there -as I used to- but I no longer need to as the hardware gets detected fairly well (at least on current). See attached for an example (omit .txt and replace last _ for .) which would live in /etc/X11/xorg.conf.d/) when used.

I actually changed the mentioned driver in that file for the modesetting driver as that worked better (at the time, but I still use it by having only that intel-driver installed) with the onboard graphics of the intel-chip I have in my laptop. I had similar files for other stuff (evdev, synaptics, keyboard-layout) but they are no longer needed as said, but maybe on 14.2 it might be different (can't remember).

hth

Lysander666 · 02-01-2018, 02:46 PM

Ah, so what I did was actually redundant unless I use nomodeset in lilo.conf

https://www.linuxquestions.org/quest...3-37-a-878827/

Thanks for the text file - I'll take a look at the proper xorg.conf.d, and the man page - may need to add Option "VBERestore" "true".

brobr · 02-01-2018, 04:40 PM

Quote:

Ah, so what I did was actually redundant ...

the file would never have been used if '-vesa' was still attached to its name; independent of:

Quote:

unless I use nomodeset in lilo.conf

Best to stick to the driver for your card which is delivered by package xf86-video-intel-git_20160601_b617f80-....txz (note that there have been patches released for x, xorg and xscreensaver for 14.2; did you apply them after installing 14.2?)

I don't think anything needs to be set in lilo other than vga=normal as a boot option; the system will load the appropriate driver during the second stage of booting.

Advice for 13.37, which yielded a great t-shirt but is fairly outdated compared to 14.2, might not be directly transferable......

Maybe don't make too many changes at the same time and try to make them in a consistent way: if the comp is booting fine without problem; lilo is doing its job, so no need to touch it.

Your resume from suspend problem seems to be linked to desktop (LXDE) using other desktops' (XFCE) functionality which might not completely work (as you found out), so don't mix that and the problem is then solved; and the thread can be closed.

If something in pm-suspend needs to be set to make it work (better) you can do that;

If something for xorg.conf needs to be set to make your graphics better you can do that.

Still, I do not think that your original problem is related to xorg.conf (as you did not report a black screen after a normal boot only after resume from suspend/hibernation).

hth

Lysander666 · 02-02-2018, 08:21 AM

Quote:

Originally Posted by brobr

(note that there have been patches released for x, xorg and xscreensaver for 14.2; did you apply them after installing 14.2?)

Every patch through slackpkg upgrade-all has been applied. However, I've blacklisted Seamonkey and Thunderbird since I have no interest in using those. In fact I uninstalled xscreensaver a few weeks back but I reinstalled it through slackpkg, I think I am now using version 5.38. It works great.

Quote:

Originally Posted by brobr

Maybe don't make too many changes at the same time and try to make them in a consistent way: if the comp is booting fine without problem; lilo is doing its job, so no need to touch it.

OK, thank you.

Quote:

Originally Posted by brobr

Your resume from suspend problem seems to be linked to desktop (LXDE) using other desktops' (XFCE) functionality which might not completely work

There is something in what you say. If everything is done natively in LXDE it's fine [i.e. using LXDE stock applications] but if I use third-party applications [e.g. physlock] or Xfce Power Manager to do the job of suspend/lock, it can create issues. This is unusual since in Debian I was using LXDE with Xfce Power Manager and I never had an issue on this netbook. However, Debian has an official version of LXDE, Slackware does not [even though ponce's version of LXDE is excellent].

Quote:

Originally Posted by brobr

Still, I do not think that your original problem is related to xorg.conf (as you did not report a black screen after a normal boot only after resume from suspend/hibernation).

hth

It does help, yes. I'm not quite ready to mark this as solved since the original issue is not solved as such, I have just found a workaround. For now I will leave this as is, and if I come to a solution I will post it.