Bug 634285

Summary:	Graphical USB Installation Presents Text Screens
Product:	[Fedora] Fedora	Reporter:	Daniel Qarras <dqarras>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	14	CC:	anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-27 14:40:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Qarras 2010-09-15 17:57:30 UTC

Description of problem:
Now that USB installations are working starting from F14ß (see bug 528809), I see this minor issue:

When installing from CD, Anaconda starts X, and asks for language, keyboard, and so.

When installing from USB, Anaconda asks for language and keyboard in text mode, then starts X, and continues asking other questions.

Why there is two text mode questions when installing from USB? It would be nice if USB installation would be also fully graphical.

Thanks.

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

Comment 1 Chris Lumens 2010-09-22 18:38:37 UTC

Were language and keyboard the only two questions you got early on in the USB install, or was there something else after that?

Comment 2 Daniel Qarras 2010-09-22 19:33:02 UTC

> Were language and keyboard the only two questions you got early on in the
> USB install, or was there something else after that?

Only language and keyboard, after that graphical mode was started and installation proceeded just like when booting from CD.

Thanks.

Comment 3 Chris Lumens 2010-09-24 15:47:31 UTC

Okay, what I think is happening here is that in the loader, we expect that you'll have the stage2 image on a CD.  When that's true, we skip the kbd and lang screens.  However that's not the case here, so we fall back and check what's in the stage2= parameter.  On these USB installs, that parameter exists and points at the hard drive.  We don't set the skip flag, though.

And the reason we don't set the skip flag is because if the stage2= parameter turns out to have been invalid later on, we need to be able to prompt the user to fix it using their native language and keyboard.

We could probably fix this, but this section of the loader is notoriously difficult to get right without breaking something else.  I'm also actively working on deleting this entire section for F15 since is really is just this bad.  So, I suggest we just live with the bug for now.