Bug 110764 - no console on normal install
no console on normal install
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2003-11-24 10:07 EST by Pádraig Brady
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-05 12:09:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pádraig Brady 2003-11-24 10:07:39 EST
Description of problem:

Can't Ctrl-Alt-F2 to virtual console on install
I used to be able to do this in fedora core test 3
I just can a blank screen with a blinking cursor
in the top left.

Machine is a Dell poweredge 1750
Comment 1 Jeremy Katz 2003-11-24 17:20:50 EST
This works fine here.  Did you have 'noshell' on your boot command line?
Comment 2 Pádraig Brady 2003-11-25 11:27:09 EST
nope. Works fine on my P4 laptop actually.
However I've now got an error message from the 2xP4 1750

relocation error: -/bin/sh: symbol , version GLIBC_2.0 not defined in
file libc.so.6 with link time reference
Comment 3 Pádraig Brady 2003-11-25 11:47:48 EST
the sh on rescue mode executes fine
Comment 4 Jeremy Katz 2003-11-25 11:58:12 EST
Have you checked your media with the built-in mediacheck?
Comment 5 Pádraig Brady 2003-11-25 14:35:30 EST
Comment 6 Peter van Egdom 2003-11-29 10:36:55 EST
I experienced this probleem too. Try booting with the option "linux
allowcddma". See Bugzilla Bug 109462 for details.
Comment 7 Jeremy Katz 2004-10-05 11:44:46 EDT
Does this occur on newer releases?
Comment 8 Pádraig Brady 2004-10-05 11:50:02 EDT
Actually I've just installed FC1 on that machine last week.
So that must have been fixed between FC1_test3 and release?
Maybe it's intermittent?

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