Black screen after system update

jondion · 2018-06-23 19:06:09

Hi,

I spent a week on Arch and everything was working as expected but yesterday I upgraded my system using "pacman -Syu" and rebooted. The update included a kernel update (4.16.13-2 to 4.17.2-1)

Now, when I boot I have a blackscreen but the computer seems to run in the background. I think it's due to my graphics card or xorg...

I was able to use the TTY login and create some logs to debug.

journalctl logs:
https://pastebin.com/raw/5y06P0i2

Xorg logs:
https://pastebin.com/raw/eXG6nFrD

Full logs (~10 000 lines)
https://www.dropbox.com/s/vm5buedhkwcbjep/text.txt?dl=0

As you can see from the logs I'm using the KMS options:
xdriver=intel modprobe.blacklist=nouveau nomodeset nouveau.modset=0

How can I prevent this in the future?

Thanks and your help is appreciated.

Last edited by jondion (2018-06-23 19:10:21)

V1del · 2018-06-23 20:31:06

These options don't make much sense where did you get them from? xdriver doesn't exist as a parameter and you will definitely not want to disable modeset for every driver. if you want to blacklist nouveau then keep that parameter, especially remove the general nomodeset, that is a likely cause. You might also want to try and get your hand on an updated xorg log the one you posted is from a old log.

seth · 2018-06-23 20:31:22

The xorg log is old, also why do you blacklist nouveau - is this an optimus system at all?

Can you boot into the multi-user.target? (w/o nomodeset)?
https://wiki.archlinux.org/index.php/Sy … _boot_into

In case, please elaborate on your GUI target (DM or xinit; which display server)

jondion · 2018-06-23 20:57:05

V1del wrote:

These options don't make much sense where did you get them from? xdriver doesn't exist as a parameter and you will definitely not want to disable modeset for every driver. if you want to blacklist nouveau then keep that parameter, especially remove the general nomodeset, that is a likely cause. You might also want to try and get your hand on an updated xorg log the one you posted is from a old log.

Thanks my computer is a Dell XPS 15 9570. I want to use Intel video drive instead of the Nvidia GTX 1050 Ti.

So I just need this to update my KMS to "modprobe.blacklist=nouveau" ?

I'm using xinit with i3 for my display manager

here my .xinit https://pastebin.com/raw/RhrKSPJM

Should I follow this https://wiki.archlinux.org/index.php/De … screte_GPU

Last edited by jondion (2018-06-23 21:04:00)

seth · 2018-06-23 21:02:29

Yes. Then see whether you can boot the multi-user.target, then whether you can run xinit/startx from there. Watch for error messages and try to provide an recent xorg log.

jondion · 2018-06-24 02:45:38

I disabled the discrete GPU from the guide.

I also updated my KMS to "modprobe.blacklist=nouveau acpi_rev_override=1" and ran > $ systemctl set-default multi-user.target

I'm still on black screen even without "nomodeset".

I looked at my Xorg logs and the date is still "... 10 June 2018".

I'm not sure how multi-user.target works. I guess I need to change the KMS settings (w/o nomodeset) ? How can I boot selecting the good target? I will like to have more details.

Thanks Seth.

EDIT: There is the Xorg logs https://pastebin.com/raw/k90bCSQ6

Last edited by jondion (2018-06-24 03:14:21)

seth · 2018-06-24 07:41:46

That looks more like the stdout than the log file, but I assume it's from a "nomodeset" boot? (X will not start if you boot "nomodeset")

The acpi_rev_override=1 parameter only allows you to disable the GPU using bbswitch
I would however suggest that you stall all attempts to disable the GPU until we figured what's going on here, so neither blacklist nouveau, nor try to disable the GPU in any way else.

jondion · 2018-06-24 12:55:44

seth wrote:

That looks more like the stdout than the log file, but I assume it's from a "nomodeset" boot? (X will not start if you boot "nomodeset")

Yes.

seth wrote:

The acpi_rev_override=1 parameter only allows you to disable the GPU using bbswitch

For "acpi_rev_override=1" yes It's from the instructions.

I can disable the bumblebeed.service for now and on tty1 it's not running

seth wrote:

would however suggest that you stall all attempts to disable the GPU until we figured what's going on here, so neither blacklist nouveau, nor try to disable the GPU in any way else.

When my computer was working I had "nomodeset"

Why my Xorg logs date are so old? "Build Date: 18 June 2018 03:12:37PM". My system date is set correctly. I did $data.

The logs have 2 locations "/var/logs" and "$HOME/.local/share/xorg/" but none of them seems updated.

Thanks.

Last edited by jondion (2018-06-24 12:57:53)

loqs · 2018-06-24 13:02:28

Remove all the boot options you have set such as acpi_rev_override=1 nomodeset etc and any module blasklisting you have done then perform a clean boot.
Does that boot to a console? If it does post the dmesg then try startx and post an updated Xorg.0.log.

seth · 2018-06-24 13:05:54

I can disable the bumblebeed.service for now

Why do you have it itfp? Bumblebee only makes sense along the nouveau or nvidia module. You've neither.

When my computer was working I had "nomodeset"

That's unlikely. Output of

pacman -Qi xf86-video-vesa

Why my Xorg logs date are so old? "Build Date: 18 June 2018 03:12:37PM".

The build date is the date when Xorg was build, the actual log date is

(==) Log file: "/home/jon/.local/share/xorg/Xorg.1.log", Time: Sat Jun 23 23:07:24 2018

loqs · 2018-06-24 13:20:03

Also the output of `lspci -nn | grep -e 3D -e VGA` please

jondion · 2018-06-25 14:53:24

loqs wrote:

Also the output of `lspci -nn | grep -e 3D -e VGA` please

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e9b]
01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1)

seth wrote:

That's unlikely. Output of
pacman -Qi xf86-video-vesa

https://pastebin.com/raw/DYjqYWvH

Using i915

Startx ouput:
https://pastebin.com/raw/fKGvu89T

Here the updated X.Org X Server logs:
https://pastebin.com/raw/aysEzA0t

Last edited by jondion (2018-06-25 16:23:06)

seth · 2018-06-25 14:59:54

NOT "xf86-video-intel", "xf86-video-vesa" - if the package isn't installed, there is simply no way that you had a GUI w/ the nomodeset paramter.

loqs · 2018-06-25 16:22:15

Jondio the system has hybrid graphics how is it intended to be configured? Use the intel GPU only, use the nvidia GPU only, optimus or bumblebee?
How is the X server started? Please also provide the output of

dmesg
pacman -Qs nvidia
pacman -Qs xf86

jondion · 2018-06-25 16:48:19

loqs wrote:

Jondio the system has hybrid graphics how is it intended to be configured? Use the intel GPU only, use the nvidia GPU only, optimus or bumblebee?
How is the X server started? Please also provide the output of
dmesg
pacman -Qs nvidia
pacman -Qs xf86

dmesg
https://pastebin.com/raw/kGmtDViU

$ pacman -Qs nvidia

local/bumblebee 3.2.1-17
    NVIDIA Optimus support for Linux through VirtualGL
local/libvdpau 1.1.1+3+ga21bf7a-1
    Nvidia VDPAU library

$ pacman -Qs xf86

local/lib32-libxxf86vm 1.1.4-2
    X11 XFree86 video mode extension library (32-bit)
local/libxxf86dga 1.1.4-2
    X11 Direct Graphics Access extension library
local/libxxf86misc 1.0.3-3
    X11 XFree86 misc extension library
local/libxxf86vm 1.1.4-2
    X11 XFree86 video mode extension library
local/xf86-input-libinput 0.27.1-1 (xorg-drivers)
    Generic input driver for the X.Org server based on libinput
local/xf86-video-fbdev 0.5.0-1 (xorg-drivers)
    X.org framebuffer video driver
local/xf86-video-intel 1:2.99.917+831+ge7bfc906-1 (xorg-drivers)
    X.org Intel i810/i830/i915/945G/G965+ video drivers
local/xf86-video-vesa 2.4.0-2 (xorg-drivers xorg)
    X.org vesa video driver
local/xorgproto 2018.4-1
    combined X.Org X11 Protocol headers

I would like to use my Intel card only.

seth wrote:

NOT "xf86-video-intel", "xf86-video-vesa" - if the package isn't installed, there is simply no way that you had a GUI w/ the nomodeset paramter.

Sorry for that

Name            : xf86-video-vesa
Version         : 2.4.0-2
Description     : X.org vesa video driver
Architecture    : x86_64
URL             : https://xorg.freedesktop.org/
Licenses        : custom
Groups          : xorg-drivers  xorg
Provides        : None
Depends On      : glibc
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : xorg-server<1.20  X-ABI-VIDEODRV_VERSION<24  X-ABI-VIDEODRV_VERSION>=25
Replaces        : None
Installed Size  : 74.00 KiB
Packager        : Andreas Radke <andyrtr@archlinux.org>
Build Date      : Fri 11 May 2018 10:50:51 AM EDT
Install Date    : Sat 16 Jun 2018 05:07:37 PM EDT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum

extra/xf86-video-fbdev 0.5.0-1 (xorg-drivers) [installed]
    X.org framebuffer video driver
extra/xf86-video-intel 1:2.99.917+831+ge7bfc906-1 (xorg-drivers) [installed]
    X.org Intel i810/i830/i915/945G/G965+ video drivers
    X.org SiS USB video driver
extra/xf86-video-vesa 2.4.0-2 (xorg-drivers xorg) [installed]
    X.org vesa video driver

Last edited by jondion (2018-06-25 16:56:22)

loqs · 2018-06-25 16:55:28

If you want to use exclusively the intel GPU and that is the GPU the display output is connected to or routed by firmware then remove bumblebee.
This does means the nvidia GPU will never be used. Also remove the boot options 'acpi_rev_override=1 modprobe.blacklist=nouveau nomodeset nouveau.modset=0'
Unless you want to use an unaccelerated X server in which case you can keep nomodeset. Then please provide details of how you start the X server.

jondion · 2018-06-25 17:03:07

loqs wrote:

If you want to use exclusively the intel GPU and that is the GPU the display output is connected to or routed by firmware then remove bumblebee.

Yes, you are right I should not use bumblebee if I only want Intel.

loqs wrote:

This does means the nvidia GPU will never be used. Also remove the boot options 'acpi_rev_override=1 modprobe.blacklist=nouveau nomodeset nouveau.modset=0'

I edit the KMS on each boot with grub. I'm using none of these options.

loqs wrote:

Unless you want to use an unaccelerated X server in which case you can keep nomodeset. Then please provide details of how you start the X server.

I'm using a custom .xinitrc file.

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
  fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

setxkbmap -layout us
setxkbmap -option ctrl:nocaps,altwin:swap_alt_win
xset r rate 250 35
xinput set-prop 14 "libinput Accel Speed" 0.5

xautolock -time 5 -locker "$DOTFILES_PATH/lock"

exec i3

Last edited by jondion (2018-06-25 17:04:14)

loqs · 2018-06-25 17:11:17

jondion wrote:

loqs wrote:
This does means the nvidia GPU will never be used. Also remove the boot options 'acpi_rev_override=1 modprobe.blacklist=nouveau nomodeset nouveau.modset=0'
I edit the KMS on each boot with grub. I'm using none of these options.

The grub editing is not working as the options still show in the dmesg.
Fix those options then try startx again when they are not in dmesg. If the issue still appears please provide an updated Xorg.0.log from ~/.local/share/xorg/

jondion · 2018-06-25 17:38:15

loqs wrote:

jondion wrote:
loqs wrote:
This does means the nvidia GPU will never be used. Also remove the boot options 'acpi_rev_override=1 modprobe.blacklist=nouveau nomodeset nouveau.modset=0'
I edit the KMS on each boot with grub. I'm using none of these options.
The grub editing is not working as the options still show in the dmesg.
Fix those options then try startx again when they are not in dmesg. If the issue still appears please provide an updated Xorg.0.log from ~/.local/share/xorg/

Sounds good. My grub file inside "/etc/default/grub" is now empty... is that normal? Is that because I changed to multi-user.target?

Thanks for the quick feedback. I appreciate.

seth · 2018-06-25 17:42:34

No, that's not normal and not necessarily good either. It's however certainly not because you changed the default target.

loqs · 2018-06-25 18:32:41

This will replace /etc/default/grub with the default supplied by the package (please be careful copying this command)

cd /
sudo bsdtar -xvf /var/cache/pacman/pkg/grub-2\:2.02-6-x86_64.pkg.tar.xz etc/default/grub

Kernel_parameters#GRUB

jondion · 2018-06-26 01:41:51

loqs wrote:

This will replace /etc/default/grub with the default supplied by the package (please be careful copying this command)
cd /
sudo bsdtar -xvf /var/cache/pacman/pkg/grub-2\:2.02-6-x86_64.pkg.tar.xz etc/default/grub
Kernel_parameters#GRUB

Is there a way with Arch USB iso to install a package to my arch installation? I saw this: https://wiki.archlinux.org/index.php/of … f_packages

The thing is, I have access to the internet with the live iso terminal but not on my installation anymore.

Thanks.

Last edited by jondion (2018-06-26 01:59:44)

seth · 2018-06-26 06:19:38

You're not supposed to install the package but to extract a file from a package that you probably still have in cache. Even if not you could copy it w/ a usb key…
However, you can just mount the installed systems root filesystem from the iso boot and copy the file into the mounted path.

Overmore this explains how to install packages (mkinitcpio systemd linux) from the iso boot: https://wiki.archlinux.org/index.php/Pa … an_upgrade

The 5s interval of the network connection in your pasted dmesg suggests you're running concurrent network managing services…

Arch Linux

#1 2018-06-23 19:06:09

Black screen after system update

#2 2018-06-23 20:31:06

Re: Black screen after system update

#3 2018-06-23 20:31:22

Re: Black screen after system update

#4 2018-06-23 20:57:05

Re: Black screen after system update

#5 2018-06-23 21:02:29

Re: Black screen after system update

#6 2018-06-24 02:45:38

Re: Black screen after system update

#7 2018-06-24 07:41:46

Re: Black screen after system update

#8 2018-06-24 12:55:44

Re: Black screen after system update

#9 2018-06-24 13:02:28

Re: Black screen after system update

#10 2018-06-24 13:05:54

Re: Black screen after system update

#11 2018-06-24 13:20:03

Re: Black screen after system update

#12 2018-06-25 14:53:24

Re: Black screen after system update

#13 2018-06-25 14:59:54

Re: Black screen after system update

#14 2018-06-25 16:22:15

Re: Black screen after system update

#15 2018-06-25 16:48:19

Re: Black screen after system update

#16 2018-06-25 16:55:28

Re: Black screen after system update

#17 2018-06-25 17:03:07

Re: Black screen after system update

#18 2018-06-25 17:11:17

Re: Black screen after system update

#19 2018-06-25 17:38:15

Re: Black screen after system update

#20 2018-06-25 17:42:34

Re: Black screen after system update

#21 2018-06-25 18:32:41

Re: Black screen after system update

#22 2018-06-26 01:41:51

Re: Black screen after system update

#23 2018-06-26 06:19:38

Re: Black screen after system update

Board footer