Description of problem:
On x86_64 with a hardware as described by attachments to a bug #122393
I tried to install FC2T3 over a network. Anaconda correctly
discovered two network interfaces - one 3c940 and one Intel Pro 100 -
but presented both as eth0 to be chosen from. Even if 3c940 with
sk98lin driver was picked up in a dialog it appears that e100 was
used by anaconda anyway as at this moment I lost any further
network responses. Only when 'noprobe' was added to boot parameters
I was able to load one, correct, network driver and an installation
continued without further suprises.
Paired with a bug #122397 I had to boot 'linux nousb noprobe'
to get things installed.
Version-Release number of selected component (if applicable):
anaconda from FC2T3 installation media
Always on two or three attempts.
*** This bug has been marked as a duplicate of 120988 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.