From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312
Description of problem:
If I move the mouse at all during the "Fedora" splash screen during a
graphical Anaconda install, then the system freezes. The installation
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert FC-Test 2 CD #1
2. Boot CD
3. When Fedora Core ISOLinux Boot Screen Comes Up, press Enter for
4. The screen then states "Loading OHCI 1394"
5. Press "Skip" on the "CD Found" Screen
6. Anaconda Starts X, Start Moving Mouse after X cursor is displayed
Actual Results: System locks up after Fedora splash screen is
displayed with regular pointer cursor. The floppy disk light comes on
for a sec and then goes off. The CD spins down.
Expected Results: I should have been able to continue the install.
The CDs have been tested to ensure the MD5SUMs are correct.
I can install Fedora core using the Text Based Install without incident.
My motherboard is an ASUS A7V8X-X. I am running an Athlon XP 2600+.
A dump of lspci will be attached.
Created attachment 99655 [details]
A dump from lspci for hardware data.
I hope something in here is helpful in resolving the anaconda bug that I've
Welp, unpluggin my USB Microsoft Intellimouse Explorer 3.0 and my USB
Hewlett Packard Internet Keyboard allows anaconda to run without incident.
I also have a Radeon 9800 Pro.
So, in effect, this might be a dupe of bug 109256 or bug 109751, but
I'm uncertain as everything went find after I unplugged the USB
keyboard and mouse.
I've even installed successfully with the USB keyboard and mouse
plugged in now. RHGB freezes sometimes if I move the mouse. I've
found that if I don't move the mouse during the anaconda install, the
RHGB, or the initial loading of the Fedora login screen, everything
seems to be fine.
I had assumed that this was an issue with the VIA chipset on my
motherboard, seeing as other Linux distros have successfully locked up
my system when they scan the USB bus.
I would switch motherboards, but there are so many Asus A7V8X-Xs out
there (or at least there were at CompUSA a few months ago), that this
problem is probably pretty widespread.
*** This bug has been marked as a duplicate of 109256 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.