| Summary: | Intel NUC dead console i915 modeset | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jon <unheiliger> | ||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | ajax, cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, xgl-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-12 10:27:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
This is the wrong component, re-assigned. Please provide information as described in this wiki: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems Thank you for assigning this to xorg-x11-drv-intel. I am attaching the requested information as per the Xorg debug wiki page. One thing to note, whilst generating the snapshot file, the system became unresponsive, and then spontaneously rebooted. This seems to be a problem with detecting the screens. The NUC in question has a mini-displayport connector and an HDMI port. The two connected screens are daisy chained to the mini DP. I have previously noted that the HDMI port is detected as a DP on the Intel NUCs I have used, which may be problematic? Thank you for the attention to this. Created attachment 1222896 [details]
Requested files for debugging
The snapshot file may not be complete. The system rebooted during generation, repeatedly.
This bug may be related: 1338026 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: After the Fedora 24 => 25 update, the desktop does not display Version-Release number of selected component (if applicable): How reproducible: Every time: Make update from fedora 24 to 25 (dnf system-upgrade) with an i915 chipset. Steps to Reproduce: 1. Check you have an i915 chipset (e.g. NUC6i7KYB) 2. Use dnf-system-upgrade from fedora 24 to fedora 25 3. Wait for the reboot. Actual results: Black screen Expected results: Desktop login Additional info: As a work around, setting "i915.modeset=0" brings up the desk top. With Fedora 24 this was not required. This work around is also required on RHEL7 on this HW, so it looks like a backward step. This is from the Xorg logs: Successful start: [root@xyz log]# grep i915 Xorg.0.log [ 5.395] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.8-300.fc25.x86_64 root=/dev/mapper/fedora-root ro i915.modeset=0 rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Unsuccessful start: [root@xyz log]# grep i915 Xorg.1.log 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, From /var/log/messages, I only get this during an unsuccessful start: Nov 22 09:09:48 xyz kernel: [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0 Nov 22 09:09:48 xyz kernel: i915 0000:00:02.0: No connectors reported connected with modes Nov 22 09:09:48 xyz kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device Nov 22 09:09:49 xyz kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) During a successful start (i915.modeset=0) there are no i915 DRM messages (but that's not really surprising). If you need more, I can reboot without the i915 disabled and SSH in to get the logs, however it is my work workstation, so please don't expect rapid responses :-)