Booting kernel 4.3.3-2 results in blackscreen

reedts · 2016-01-01 18:05:46

I own a Schenker XMG P706 Notebook with Intel Skylake 6700HQ (with HD 530) and an discrete NVIDIA GTX 980M. I'm using bumblebee to make use of my discrete graphics card and installed

xf86-video-intel bumblebee nvidia

Which worked quite well with kernel 4.2.5-1 except a few minor issues (see also this post)

With kernel 4.3.3-2 the boot process results in a blackscreen nearly instantly after "triggering uevents".

If I append

i915.modeset=0

to the kernel parameters, the system will boot up but Xorg is unable to start.
Xorg.0.log:

[   567.206] 
X.Org X Server 1.18.0
Release Date: 2015-11-09
[   567.207] X Protocol Version 11, Revision 0
[   567.208] Build Operating System: Linux 4.2.3-1-ARCH x86_64 
[   567.209] Current Operating System: Linux pharyx 4.3.3-2-ARCH #1 SMP PREEMPT Wed Dec 23 20:09:18 CET 2015 x86_64
[   567.209] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=f532cd42-9d9d-434f-a3b3-8081bf3ac707 rw verbose i915.preliminary_hw_support=1 i915.modeset=0
[   567.210] Build Date: 18 November 2015  08:07:09AM
[   567.211]  
[   567.211] Current version of pixman: 0.32.8
[   567.213] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   567.213] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   567.215] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan  1 18:37:08 2016
[   567.216] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   567.217] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   567.219] (==) No Layout section.  Using the first Screen section.
[   567.219] (==) No screen section available. Using defaults.
[   567.219] (**) |-->Screen "Default Screen Section" (0)
[   567.219] (**) |   |-->Monitor "<default monitor>"
[   567.219] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[   567.219] (**) |   |-->Device "Intel Graphics"
[   567.219] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   567.219] (==) Automatically adding devices
[   567.219] (==) Automatically enabling devices
[   567.219] (==) Automatically adding GPU devices
[   567.219] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   567.219] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   567.219] 	Entry deleted from font path.
[   567.219] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   567.219] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   567.219] 	Entry deleted from font path.
[   567.219] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   567.219] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/,
	/usr/share/fonts/Type1/
[   567.219] (==) ModulePath set to "/usr/lib/xorg/modules"
[   567.219] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   567.219] (II) Loader magic: 0x819d40
[   567.219] (II) Module ABI versions:
[   567.219] 	X.Org ANSI C Emulation: 0.4
[   567.219] 	X.Org Video Driver: 20.0
[   567.219] 	X.Org XInput driver : 22.1
[   567.219] 	X.Org Server Extension : 9.0
[   567.220] (++) using VT number 1

[   567.220] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   567.221] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[   567.222] (--) PCI:*(0:0:2:0) 8086:191b:1558:6540 rev 6, Mem @ 0xdd000000/16777216, 0xa0000000/536870912, I/O @ 0x0000f000/64
[   567.222] (--) PCI: (0:1:0:0) 10de:1617:1558:6783 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[   567.222] (II) Open ACPI successful (/var/run/acpid.socket)
[   567.222] (II) LoadModule: "glx"
[   567.222] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   567.223] (II) Module glx: vendor="X.Org Foundation"
[   567.223] 	compiled for 1.18.0, module version = 1.0.0
[   567.223] 	ABI class: X.Org Server Extension, version 9.0
[   567.223] (==) AIGLX enabled
[   567.223] (II) LoadModule: "intel"
[   567.223] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[   567.223] (II) Module intel: vendor="X.Org Foundation"
[   567.223] 	compiled for 1.18.0, module version = 2.99.917
[   567.223] 	Module class: X.Org Video Driver
[   567.223] 	ABI class: X.Org Video Driver, version 20.0
[   567.223] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[   567.223] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[   567.223] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[   567.223] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[   567.225] (EE) No devices detected.
[   567.225] (EE) 
Fatal server error:
[   567.225] (EE) no screens found(EE) 
[   567.225] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   567.225] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   567.225] (EE)

I'm also using the i915 Module in my mkinitcpio.conf. Tried to remove it and rebuild the kernel image: same problem.
I also have got this configuration in my xorg.conf.d for the integrated intel gpu:

Section "Device"
	Identifier	"Intel Graphics"
	Driver		"intel"
	Option		"DRI"		"3"
	Option		"AccelMethod"	"sna"
	Option		"TearFree"	"true"
EndSection

Removing that file did not change anything either.

I'm thankful for any input!
reedts

slytux · 2016-01-01 18:35:03

There is a problem with the nvidia package. I am running on -lts kernel for now.

reedts · 2016-01-01 18:47:33

LTS-Kernel makes the system boot up here too. Just tried out. Thanks for the advice. Hope the problems are fixed soon though.

leuchtturm · 2016-01-01 19:59:22

Doesn't seem to be a sole nvidia problem: https://bbs.archlinux.org/viewtopic.php?id=206970

jasonwryan · 2016-01-01 20:34:16

The nvidia issue is well known: https://bugs.archlinux.org/task/47092

loqs · 2016-01-01 20:52:19

As the NVIDIA GTX 980M is not supported by the nvidia-304xx series it should not be 47092 but the OP does not explicitly state which nvidia packages they are using.

reedts · 2016-01-01 21:48:29

Installed are following nvidia packages (output of pacman -Q nvidia):

nvidia 358.16-3

EDIT: @leuchtturm: tried the "workaround" with your more or less random xrandr commands from the discussion you linked in your post. Confirm they work for me too. But as you said yourself: not quite satisfying.

Last edited by reedts (2016-01-01 21:57:59)

loqs · 2016-01-01 22:03:59

reedts wrote:

With kernel 4.3.3-2 the boot process results in a blackscreen nearly instantly after "triggering uevents".

Were you trying to boot directly into X11 or was the blackscreen in place of where you would expect a console?
In your journal from the blackscreen boot are seeing similar to leuchtturmcharli3

Dec 31 23:59:10 charlie_cpu kernel: WARNING: CPU: 2 PID: 121 at drivers/gpu/drm/i915/intel_dp.c:854 inte
Dec 31 23:59:10 charlie_cpu kernel: dp_aux_ch not started status 0xad40001f

Also would you be willing to try the 4.4-rc7 kernel to see if it is already fixed upstream?
Edit:
The dmesg lines are from charli3 the original poster in the thread leuchtturm linked to.
Sorry for the miss attribution to leuchtturm

Last edited by loqs (2016-01-01 22:10:02)

reedts · 2016-01-01 22:19:39

Blackscreen would occur where normally systemd would report the passed/failed units on startup (as I have verbose output enabled by kernel parameter). Blackscreen will persist from here on, no matter if lightdm should appear or I try to switch to TTY-X.

@loqs: Kernel 4.4-rc7 is available through the AUR-package

linux-git

right? Never tried to install an kernel under Arch that is not in the official repositories. But I'm willing to try it out.

Edit:
@loqs: Had to read your question twice.

loqs wrote:

Were you trying to boot directly into X11 or was the blackscreen in place of where you would expect a console?

Disabled lightdm.service in systemctl to boot to plain console. Blackscreen anyway, just as booting directly to lightdm/X11.

Last edited by reedts (2016-01-01 22:25:06)

loqs · 2016-01-01 22:43:55

linux-git will get your the current master branch of the kernel ( currentily about 20 committs beyond rc7 )
If you want exactily v4.4-rc7 append #tag=v4.4-rc7 to the source line eg

source=('git+https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git#tag=v4.4-rc7'

Building and installing linux-git should add an additional kernel and corresponding initrd's into /boot and you just need to add a new bootloader entry for them leaving the existing kernel package alone.
There is an issue with the nvidia kernel module as that will be built for 4.3 or not 4.4

reedts · 2016-01-01 22:54:05

Cloning the repository now, just as you instructed. Definitely will take some time. I will report back ASAP.

Edit:
@loqs: Would the AUR-package linux-mainline do the trick, too? Seems to provide 4.4-rc7-1 but seems to build much faster, as the cloning of the git-repo takes ages..

Last edited by reedts (2016-01-01 23:04:05)

loqs · 2016-01-01 23:10:24

reedts wrote:

Cloning the repository now, just as you instructed. Definitely will take some time. I will report back ASAP.
Edit:
@loqs: Would the AUR-package linux-mainline do the trick, too? Seems to provide 4.4-rc7-1 but seems to build much faster, as the cloning of the git-repo takes ages..

Looks like it should but I personally have never used that package.

reedts · 2016-01-02 09:41:27

So, built and installed kernel 4.4-rc7-1 throught AUR-package linux-mainline. Machine is booting up fine, no errors so far.

killvanrea · 2016-01-02 11:14:36

HI all,
I have the same problem on my laptop Asus ROG with Intel 6700HQ and GTX960M. I was installed only the Intel driver and don`t have any Nvidia package installed. This morning I update to 4.3.3 and reboot my system and the result was blank screen.
My kernel parameters are:

 acpi_backlight=vendor i915.preliminary_hw_support=1 intel_pstate=disable reboot=pci

I tried with no parameters with all of acpi_backlight option (video/nativ/none), also i add "i915.modeset=0" but the screen only display

::running early hook [udev]
starting vesrion 228
::running hook [udev]
::Triggering uevents....

Someone any suggestions ?

p.P.: I also hooked up external display but it also stays blank
Also tried to boot using usb stick with arch linux 2016.01.01 with kernel 4.3.3 and downgrade the kernel but without any luck, blank screen also with the usb img

Last edited by killvanrea (2016-01-02 11:48:30)

leuchtturm · 2016-01-02 12:11:13

killvanrea wrote:

My kernel parameters are:
 acpi_backlight=vendor i915.preliminary_hw_support=1 intel_pstate=disable reboot=pci 
I tried with no parameters with all of acpi_backlight option (video/nativ/none), also i add "i915.modeset=0" but the screen only display

What happens when you only disable preliminary_hw_support?

Linux-mainline solves the problem for me. Works just fine

killvanrea · 2016-01-02 12:29:07

I remove "i915.preliminary_hw_support=1" but nothing happens. What is "Linux-mainline" ?!?

reedts · 2016-01-02 14:10:35

"linux-mainline" is a package maintained in the AUR (see here) which lets you install the newer version of the linux kernel in addition to the version in the Arch Linux core repository.
This version of the linux kernel (4.4-rc-7-1) fixes the blackscreen for me.

Last edited by reedts (2016-01-02 14:11:18)

killvanrea · 2016-01-02 17:27:13

I made a bootable usb stick with the old arch linux kernel (img dec 2015) and install the "linux-mainline" from AUR but nothing, again blank screen
Can someone help me, I wont wanna install the whole linux from ground end

p.P.: Is it normal "uname -r" to return me 4.2.5-1-ARCH when I'm login using arch-chroot, but I've already update the kernel to 4.3.3 and installed linux-mainline pkg from AUR ?

Last edited by killvanrea (2016-01-02 17:44:26)

loqs · 2016-01-02 18:09:25

killvanrea wrote:

I made a bootable usb stick with the old arch linux kernel (img dec 2015) and install the "linux-mainline" from AUR but nothing, again blank screen
Can someone help me, I wont wanna install the whole linux from ground end
p.P.: Is it normal "uname -r" to return me 4.2.5-1-ARCH when I'm login using arch-chroot, but I've already update the kernel to 4.3.3 and installed linux-mainline pkg from AUR ?

Depending on which bootloader/boormanager you are using you may need to manually create an entry for the linux-mainline kernel which you should then select instead of the orginal entry for arch linux.

uname

Should give you information on the currently booted kernel. 4.2.5-1-ARCH seems like it could be the kernel when booting off the usb stick.
Edit additionally while you have chrooted into the install you could check the journal.

journalctl -b -3

For example would show messages from 3 boots ago.
The kernel used should recorded as one of the first few entries in the journal for that boot.

Last edited by loqs (2016-01-02 18:40:25)

killvanrea · 2016-01-02 19:14:59

Hi again,
so

 uname

return only

 Linux

I've tried :

 journalctl -b -3

return entries only from Dec 29, I've tried only journaltcl but without luck, no entries for Jan.
About bootloader, I've used "bootctl install" for dual-boot with Windows 10.
When I check for update with "pacman -Suy" it return "there is nothing to do".
Any other suggestions ?

Last edited by killvanrea (2016-01-02 19:19:27)

loqs · 2016-01-02 19:40:32

Systemd-boot#Standard_root_installations
Did you create for instance $esp/loader/entries/arch-mainline.conf?
Check in the /boot of your arch install would expect to see:

vmlinuz-linux
initramfs-linux-fallback.img
initramfs-linux.img

the above kernel + ramdisks from the linux package

vmlinuz-linux-mainline
initramfs-linux-mainline-fallback.img
initramfs-linux-mainline.img

from the linux-mainline package you built from AUR.

killvanrea · 2016-01-02 23:03:15

No luck with this blank screen again.
Here are some outputs:
arch.conf

title 	Arch Linux
linux	/vmlinuz-linux-mainline
initrd	/initramfs-linux-mainline.img
options	root=/dev/sdb5 rw acpi_backlight=vendor i915.preliminary_hw_support=1 intel_pstate=disable reboot=pci

ls -la /boot/

total 54701
    1 drwxr-xr-x 4 root root     1024 Oct 20 19:05 boot-sav
    1 drwxr-xr-x 5 root root     1024 Oct 25 02:53 EFI
18699 -rwxr-xr-x 1 root root 19147276 Jan  2 21:47 initramfs-linux-fallback.img
 4361 -rwxr-xr-x 1 root root  4465369 Jan  2 21:47 initramfs-linux.img
18706 -rwxr-xr-x 1 root root 19154127 Jan  2 22:58 initramfs-linux-mainline-fallback.img
 4465 -rwxr-xr-x 1 root root  4571297 Jan  2 22:58 initramfs-linux-mainline.img
    1 drwxr-xr-x 3 root root     1024 Dec 17 11:38 loader
    1 drwxr-xr-x 2 root root     1024 Mar 26  2015 syslinux
 4226 -rwxr-xr-x 1 root root  4327248 Dec 23 21:10 vmlinuz-linux
 4240 -rwxr-xr-x 1 root root  4341200 Jan  2 22:56 vmlinuz-linux-mainline

and pacman -Q linux

linux 4.3.3-2

I've also tried with linux-mainline and without any boot parameters
e.g.

options	root=/dev/sdb5 rw

and with each one independently, but still blank screen

loqs · 2016-01-02 23:29:55

@killvanrea if you downgrade the kernel packagge to 4.2 but leave arch.conf unchanged it should still give you a blank screen but will prove that config is being used.
Then just to make sure alter arch.conf back to its previous values ie remove references to mainline and it should work as before the 4.3 upgrade.
If that then works as expected it would appear you have a seperate issue that affects both 4.3 and 4.4 and needs more investigation.

bnahill · 2016-01-03 03:14:26

Hey all,
I experienced what I think was this problem when I upgraded to 4.3.3-2 today on a Skylake laptop using the i915 driver. I got the following message on boot when the screen went black (I booted with i915.modeset=0 and systemd.unit=rescue to see the messages).

WARNING: CPU: 1 PID: 238 at drivers/gpu/drm/i915/intel_dp.c:854 intel_dp_aux_ch+0x114/0x690 [i915]()
dp_aux_ch not started status 0xad40001f
Modules linked in: joydev mousedev hid_multitouch arc4 i2c_designware_platform i2c_designware_core intel_rapl x86_pkg_temp_thermal intel_powerclamp dell_wmi bnep sparse_keymap dell_l
battery hid rfkill pinctrl_sunrisepoint video pinctrl_intel intel_lpss_acpi intel_lpss int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad ac button fjes 
CPU: 1 PID: 238 Comm: kworker/u8:4 Not tainted 4.3.3-2-ARCH #1
Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.0.0 09/10/2015
Workqueue: events_unbound async_run_entry_fn
0000000000000000 00000000096169be ffff8802b4f935e0 ffffffff812c0dc9
ffff8802b4f93628 ffff8802b4f93618 ffffffff81074f42 00000000ad40001f
0000000000064010 0000000000064014 ffff8802b0040000 0000000000000005
...(stack trace)...

I switched to linux-mainline and it works now. To switch to mainline, I installed linux-mainline from AUR and added a bootloader entry in /boot/loader/entries. The above kernel options will get you to a functioning prompt to install linux-mainline without having to USB boot.
I haven't the time to figure out what changed in the 4.3.3-2 release, but maybe this is of use to somebody.

killvanrea · 2016-01-03 20:29:27

Hi all,
I've try with i915.modeset=0 and systemd.unit=rescue and linux-mainline but blank screen again.
So I boot using usb stick go in chroot and downgrade linux and linux-header and now everything is fine. Hope soon their will be fix
Thanks to all of you for the help!

Arch Linux

#1 2016-01-01 18:05:46

Booting kernel 4.3.3-2 results in blackscreen

#2 2016-01-01 18:35:03

Re: Booting kernel 4.3.3-2 results in blackscreen

#3 2016-01-01 18:47:33

Re: Booting kernel 4.3.3-2 results in blackscreen

#4 2016-01-01 19:59:22

Re: Booting kernel 4.3.3-2 results in blackscreen

#5 2016-01-01 20:34:16

Re: Booting kernel 4.3.3-2 results in blackscreen

#6 2016-01-01 20:52:19

Re: Booting kernel 4.3.3-2 results in blackscreen

#7 2016-01-01 21:48:29

Re: Booting kernel 4.3.3-2 results in blackscreen

#8 2016-01-01 22:03:59

Re: Booting kernel 4.3.3-2 results in blackscreen

#9 2016-01-01 22:19:39

Re: Booting kernel 4.3.3-2 results in blackscreen

#10 2016-01-01 22:43:55

Re: Booting kernel 4.3.3-2 results in blackscreen

#11 2016-01-01 22:54:05

Re: Booting kernel 4.3.3-2 results in blackscreen

#12 2016-01-01 23:10:24

Re: Booting kernel 4.3.3-2 results in blackscreen

#13 2016-01-02 09:41:27

Re: Booting kernel 4.3.3-2 results in blackscreen

#14 2016-01-02 11:14:36

Re: Booting kernel 4.3.3-2 results in blackscreen

#15 2016-01-02 12:11:13

Re: Booting kernel 4.3.3-2 results in blackscreen

#16 2016-01-02 12:29:07

Re: Booting kernel 4.3.3-2 results in blackscreen

#17 2016-01-02 14:10:35

Re: Booting kernel 4.3.3-2 results in blackscreen

#18 2016-01-02 17:27:13

Re: Booting kernel 4.3.3-2 results in blackscreen

#19 2016-01-02 18:09:25

Re: Booting kernel 4.3.3-2 results in blackscreen

#20 2016-01-02 19:14:59

Re: Booting kernel 4.3.3-2 results in blackscreen

#21 2016-01-02 19:40:32

Re: Booting kernel 4.3.3-2 results in blackscreen

#22 2016-01-02 23:03:15

Re: Booting kernel 4.3.3-2 results in blackscreen

#23 2016-01-02 23:29:55

Re: Booting kernel 4.3.3-2 results in blackscreen

#24 2016-01-03 03:14:26

Re: Booting kernel 4.3.3-2 results in blackscreen

#25 2016-01-03 20:29:27

Re: Booting kernel 4.3.3-2 results in blackscreen

Board footer