Red Hat Bugzilla – Bug 179534
RHGB shows only frozen "busy" cursor (but works)
Last modified: 2007-11-30 17:11:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5
Description of problem:
RHGB has started showing nothing on the screen while it's booting. All that I see is a non-moving version of the standard X "busy" cursor. It is working, though; the hard drive and network are active, and if I leave it Fedora eventually starts up properly.
I chose "fc5t2" although I haven't ever explicitly installed T2 on this machine; it was installed as fc5t1 and kept updated against Rawhide.
This is a Dell Inspiron 5160 laptop with a 1024x768 display and the following graphics card:
01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200] (rev a1)
I'm running the stock "nv" driver in X (as opposed to the binary "nvidia" driver which I haven't tried yet in the new X).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot with "rhgb" on the grub command line
These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
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 CANTFIX, 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.
Thank you in advance.
(this message is mass message)