Bug 1215458

Summary:	Switching to tty2 causes display to flicker on MacBook Air
Product:	[Fedora] Fedora	Reporter:	Alexander Todorov <atodorov>
Component:	xorg-x11-drivers	Assignee:	X/OpenGL Maintenance List <xgl-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	22	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora, xgl-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 20:30:28 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:
Embargoed:

Description Alexander Todorov 2015-04-26 18:48:15 UTC

Description of problem:

While trying Fedora 22 Beta on a MacBook Air (from 2015) I did switch to tty2 inside stage2 and the display started to flicker. Both the text mode terminal on tty2 and the graphical screen were flickering in the same patterns. See this video here:
https://www.youtube.com/watch?v=EzSMc0NcmWE


The computer has:
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)


Please advise if this is something related to anaconda or Xorg (are we using Wayland instead) ? and what log files would you need.

Comment 1 Fedora End Of Life 2016-07-19 20:30:28 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.