Bug 1314492 - Black screen and no tty after updating to kernel 4.4.2-301 (4.3.5-300 or lower works)
Summary: Black screen and no tty after updating to kernel 4.4.2-301 (4.3.5-300 or lowe...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 18:31 UTC by Basic Six
Modified: 2016-11-22 10:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:57:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
sysinfo (16.02 KB, text/plain)
2016-03-03 18:52 UTC, Basic Six
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1609436 0 None None None 2016-08-10 13:29:11 UTC

Description Basic Six 2016-03-03 18:31:10 UTC
Description of problem:

After updating to kernel 4.4.2-301, the screen goes black on boot and the system is not usable except via SSH. After the Grub menu goes away, the Fedora boot screen is visible for about one second, then the screen goes black. It's not X that doesn't work because switching to another tty (Ctrl + Alt + F2) is not possible either.

Luckily, Fedora always keeps a couple of older kernels installed, so instead of manually downgrading the kernel package, simply booting 4.3.5-300 is enough to get a working system.



Version-Release number of selected component (if applicable):

Kernel 4.4.2-301 or higher makes the screen go black.
Kernel 4.3.5-300 (or lower) works.



How reproducible:

100%, screen black with 4.4, screen works with 4.3.



Steps to Reproduce:
1. dnf upgrade
2. screen black after reboot



Actual results:

Screen black, system unusable.



Expected results:

Screen should work as it did before.

A software bug should never break the functionality of the screen. Some sort of fallback mode, maybe to a lower resolution, might be acceptable in case of a severe bug. But the screen suddenly not working anymore after a routine update is unacceptable under any circumstances.



Additional info:

No Nvidia driver installed:

# rpm -qa | grep -ci nvidia 
0

# lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

Comment 1 Basic Six 2016-03-03 18:52:44 UTC
Created attachment 1132893 [details]
sysinfo

Attached sysinfo.

Ran another update, same issue with kernel 4.4.3-300.

Comment 2 Laura Abbott 2016-03-04 21:43:40 UTC

*** This bug has been marked as a duplicate of bug 1313013 ***

Comment 3 Basic Six 2016-08-03 14:02:52 UTC
The screen is still not working. No Fedora system with kernel 4.4 or newer has been working on this computer. It has been broken for over 4 months now! This is ridiculous.

On every boot, the old kernel 4.3 must be selected manually or else there is no video output.

A full system update cannot be performed, because every new kernel version seems to be broken as well.
Also, when updating the system (for example using apper or clicking on the update notifications in the tray), the working kernel could be uninstalled because Fedora only retains 3 kernel versions by default. So clicking on a software update notification by accident can render the whole system completely useless without any working kernel left.

According to bug 1313013, it's supposedly fixed in kernel 4.5.5. If this is the case, then these are two different bugs because it is still happening with 4.5.5.

The Fedora 24 live system also does not work - same issue:
5aa184c9377046a5e281402c4cee1a8a  Fedora-Workstation-Live-x86_64-24-1.2.iso

Comment 4 Basic Six 2016-08-09 10:05:49 UTC
Black screen means "no video input", so it seems like the monitor is not even getting a signal.

When the "nomodeset" option is specified for the boot process, switching to another tty (Ctrl + Alt + F2) not only makes the screen go black in the same way, but also freezes the system completely.

Comment 5 Basic Six 2016-08-10 11:14:42 UTC
I have tried this Fedora live system - same bug, system won't boot, no video:
1b410e9889132274ed256d9966cd6538  Media/F24-x86_64-KDE-20160808.iso

Unlike Ubuntu (tested: ubuntu-16.04.1-desktop-amd64.iso), where the "nomodeset" boot option seems to be a good workaround, switching to another tty does not work (black screen, system frozen, including keyboard leds) on Fedora when using this option.
But using this option (Fedora live system boot menu, TAB, append "nomodeset", Enter), the system will at least boot and the login screen shows up. Apart from other issues that might arise because of this option, it seems to fix the boot process and the monitor won't go black until Ctrl + Alt + FX is pressed.

I feel like this bug should receive a bit more attention. After all, one of the most commonly used Linux distributions has stopped working (on this particular hardware) almost half a year ago.

In other words: Fedora Linux does not work on this computer anymore.

Comment 6 Basic Six 2016-08-10 13:47:14 UTC
$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)

Motherboard: Asus Z87-PRO

Comment 7 Laura Abbott 2016-09-23 19:18:31 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

Comment 8 Laura Abbott 2016-10-26 16:57:37 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 9 Basic Six 2016-11-22 10:49:56 UTC
I replaced the hardware because Fedora Linux would not work on the old hardware anymore. Probably still broken, but can't check.


Note You need to log in before you can comment on or make changes to this bug.