Bug 704984

Summary:	display early failure messages like "cpu is 32bit only" when booting with rhgb
Product:	[Fedora] Fedora	Reporter:	Jens Petersen <petersen>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	akozumpl, dwmw2, gansalmon, itamar, johannbg, jonathan, kernel-maint, lpoetter, madhu.chinakonda, metherid, mschmidt, notting, plautrba, vanmeeuwen+fedora
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:	2012-02-02 17:14:55 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 Jens Petersen 2011-05-16 09:19:48 UTC

Description of problem:
When booting fails early on (before "stage2") no error message
is displayed with "quiet".  So boot just appears to hang.
It would be nice to display some message to users, as seen without "quite rhgb",
rather than just to hang silently.

Comment 1 Ales Kozumplik 2011-05-16 10:32:24 UTC

What installation method are you using to get the 'quiet rhgb' parameters? Are those present by default or do you add them manually (in which case I don't think we can help you).

Comment 2 Chris Lumens 2011-05-16 13:26:47 UTC

This is either due to the kernel or systemd, since anaconda is not yet involved.  Let's start at the higher layers and work our way down.

Comment 3 Lennart Poettering 2011-05-16 18:42:02 UTC

Hmm? can you say which error message precisely you expect to be visible that currently isn't visible? Only if we know which component logs it we can ensure that it makes it to the screen?

Comment 4 Jens Petersen 2011-06-24 04:58:56 UTC

(In reply to comment #1)
> What installation method are you using to get the 'quiet rhgb' parameters?

I think Live images use 'quiet rhgb' by default.
Definitely nothing to do with systemd...
I guess I filed under anaconda in the hope
that something could be done on the installer side
for this maybe LiveCD would have been more appropriate.

I suppose the error in my example would be from the kernel.
I guess it would be nice if there was a timeout for quiet:
say after 10s show some error output but maybe difficult to do.

Moving this needle into the kernel bug haystack. :)

Comment 5 Dave Jones 2011-12-06 17:57:26 UTC

what message isn't getting displayed ?