Bug 12008 - Long wait with empty blue screen: what's happening?
Summary: Long wait with empty blue screen: what's happening?
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
Keywords: FutureFeature
: 12073 12077 12158 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-06-09 03:21 UTC by Brent Nordquist
Modified: 2007-04-18 16:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-13 20:49:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brent Nordquist 2000-06-09 03:21:35 UTC
In both graphical and text mode installs, there's a blue text-mode screen 
at the beginning that says "Welcome to RedHat Linux".  Then there is a long 
pause while the CD and disk are active.  (Presumably we're searching for 
drivers at this point, because I see a dialog briefly "Loading aic7xxx 

On systems with slower CD drives, this could be quite a wait with a blank 
screen, which is a little unsettling.  How about a dialog "Searching for 
drivers" or something during this time?

Comment 1 Gene Czarcinski 2000-06-09 08:37:26 UTC
On a Compaq DeskPro PII 450MHz with 96MB memory and installing in text mode, I
got even longer waits.  Changing to the F3 screen showed a number of "error"
messages when loading drivers which indicated "null path" accessing the modules.

Although the system did finally install, these was an extremely long delay as
compared to previous versions of the installer.


Comment 2 Brock Organ 2000-06-09 15:49:06 UTC
after the waits, does the install continue without harm, and finish

Comment 3 Brent Nordquist 2000-06-10 04:29:36 UTC
Yes, it got past that point for me.  That's why I submitted this as
"enhancement"; just an idea to let users know what's going on during the long

Comment 4 Hans de Goede 2000-06-12 18:03:40 UTC
I have a K7-650 with 128 megs of memory and an 16x scsi cdrom on an adaptec 2920
and the above described blue screen seems to take forever, at least a message
and preferrable a fix would be mucb appreciated.

Comment 5 Dale Lovelace 2000-06-12 21:18:13 UTC
*** Bug 12158 has been marked as a duplicate of this bug. ***

Comment 6 Dale Lovelace 2000-06-12 21:18:54 UTC
*** Bug 12073 has been marked as a duplicate of this bug. ***

Comment 7 Dale Lovelace 2000-06-12 21:19:46 UTC
*** Bug 12077 has been marked as a duplicate of this bug. ***

Comment 8 Gene Czarcinski 2000-06-26 07:51:45 UTC
Please update for beta2 ... still true.

Comment 9 Brent Nordquist 2000-07-11 04:16:32 UTC
Erik Troan posted a new boot.img for Beta-3 tonight, and I'm happy to report
that the blue screen delay went from 2 minutes to 20 seconds on my system.  He's
also added an "anaconda loading, may take a while" kind of message; anaconda and
X load much more quickly now.

I'll let someone else close this, if it's felt that the new faster process
precludes the need for a dialog or progress bar... I'd still like to see one,
though, rather than a blank blue screen, no matter how short.

Note You need to log in before you can comment on or make changes to this bug.