Bug 15095 - Could not get anaconda to start on laptop
Summary: Could not get anaconda to start on laptop
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-02 05:45 UTC by Mark Allen
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-09 20:15:45 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 Mark Allen 2000-08-02 05:45:23 UTC
Downloaded the CD1 ISO last night from SourceForge, burned it today onto a
CD-R and CD-RW disc. Our test system is a Compal 30W laptop (Dell Inspiron
5000) with DVD-ROM, 256MB RAM, 6GB IDE disc, ATI Mobility/P video card, ESS
Maestro 2E sound and the install process terminated every time with signal
11.  I saw the message for "Greetings. Welcome to Red Hat install init 6.2"
Running /sbin/loader... which is supposed to kickstart anaconda, but
anaconda never came up.

I know the CDs are good because they booted and loaded on some other

Comment 1 Michael Fulbright 2000-08-04 20:15:06 UTC
If you try a text mode installation does it do better?

Just type 'text' at the install boot prompt.

Comment 2 Mark Allen 2000-08-04 21:09:51 UTC
I already tried text and graphical installation methods. Neither worked. init
6.2 started, but I never saw a message that said "running /sbin/loader" like

Comment 3 Michael Fulbright 2000-08-17 16:27:30 UTC
What are the last couple of lines of output on VC3?

Comment 4 Michael Fulbright 2000-08-21 17:00:35 UTC
Sounds like perhaps the CD you burned is not working in the CDROM drive of the
problem system.

If you could try another drive in that system and see how that works it would be
very helpful.

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