Bug 670736

Summary:	Console font is only set properly in 20% of boot attempts (randomly)
Product:	[Fedora] Fedora	Reporter:	Artem S. Tashkinov <aros>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	iarlyy, jonathan, notting, plautrba, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-25 21:08:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Artem S. Tashkinov 2011-01-19 07:13:44 UTC

Description of problem: when my Linux boots, only in 20% of cases I get console font set properly. My Linux boots into VESA mode (using vga=0x31a parameter) then switches to KMS mode, and it seems like this switch which happens when udev is being started coincides with font setting routing. So, in rare cases i915 module loads before font is being set, then everything is alright, in majority of other cases, font is being set when we are still in VESA mode, then upon switching to KMS mode, font is being reset to default one.

Version-Release number of selected component (if applicable): initscripts-9.20.1-1.fc14.i686

How reproducible: 80% of the time


Steps to Reproduce:
1. Boot into Fedora 14 VESA mode without initrd
2.
3.
  
Actual results: in 80% of cases font will be applied to VESA mode (i.e. too early)

Expected results: font being applied to KMS mode

Additional info:

Comment 1 Bill Nottingham 2011-02-25 21:08:56 UTC

Console changes need done before plymouth switches to graphics mode, so this is intentional.

Comment 2 Artem S. Tashkinov 2011-02-25 21:49:34 UTC

plymouth is a part of initrd, right?

I don't have it at all.

However I now don't own that PC so this bug (even though it is "intentional" WTF?!) doesn't affect me any longer.