Red Hat Bugzilla – Bug 121755
Installer hangs at media test screen
Last modified: 2015-01-04 17:05:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312
Description of problem:
Installer seems to hang at the media test screen. The keyboard is
dead; ie caps lock / num lock lights wont toggle. So the system may
not be hung, it's just that the keyboard is dead. I decided to try to
find out when this happens by repeatedly pressing caps lock after
hitting enter at the boot prompt. This turned out to be the fix. Now I
was able to install without any further problems with the keyboard. I
re-tried this several times with the same result: On this system I
have to keep hitting num lock / caps lock until the system comes up to
the media test screen. Didn't try other keys. I did try another
keyboard with the same result. The system consists of:
MSI Kt3 Ultra2 Motherboard
AMD Duron 1600+ CPU
512M DDR 400 Ram (1 DIMM)
Maxtor 91728D8 hard drive
RIVA TNT2 Video card
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Assemble system with above listed componets
2.Attempt installation of fedora core test2 from CD
Actual Results: Can't get past media test screen
Expected Results: Normal installation
fixed in fc3?
I still have the motherboard but its not in use or in a case. I also have FC3.
In a week or so I will assemble this MB into a system and test with FC3. Will
report back then.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to "CURRENTRELEASE", however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thanks in advance.