Red Hat Bugzilla – Bug 80347
3Com 3c590/3c595/3c90x/3cx980 driver problems
Last modified: 2007-04-18 12:49:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021207
Description of problem:
I tried to install the redhat phoebe beta.
Using the installation images to boot from floppy
I wanted to use FTP install method.
To be able to use the driver
for my eth1 device, I was forced to use the additional
driver disk. In previous versions this network card was
Manually selecting the card, an FTP installation was
After installation, the network card gave an initialisation
problem (the boot sequence suggested to check the UTP cable).
Also manual configuration and activation of the card did not
Due to the fact that I also use the machine as router and
firewall I had to roll back to the official 8.0 redhat version,
and I cannot further test teh pheobe beta.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Use pheobe FTP installation
2.Additional driver disk is required for 3Com 3c590/3c595/3c90x/3cx980
3.Manullay selecting the driver works. Automatic detection fails
4.After installation the boot sequence cannot initialse and start
Actual Results: No activation of network card
Expected Results: Activation of network card
> for my eth1 device, I was forced to use the additional
> driver disk. In previous versions this network card was
> detected automatically.
I think this part is intentional if you read the release notes. IIRC the
bootdisk.img no longer has any drivers on it, you need the secondary disk with
> After installation, the network card gave an initialisation
> problem (the boot sequence suggested to check the UTP cable).
> Also manual configuration and activation of the card did not
Does it work if you manually load the appropriate kernel module before or after
enabling the network devices?
Okay, I understand that all network drivers are shifted to the
additional drivers image. Still in previous releases the detection
of the network card was automatically.
Furthermore: The problem does not seem to be related to a kernel
module that needs to be loaded. If have the exact same network card
on my eth0 device (internal network) and that card does work correctly
What are the exact errors you get?
During boot sequence as above.
Using the Network Icon from the "Start Here" dialog, and
trying to initialse the network card post installation from
- The networkcard is shown in the "Hardware" tab
- Trying to (add and) configure in the "Devices" tab and
Activating the card results in an error dialog being
popped up after some time wait out. When the error dialog
is closed using the "X" right above the "Network Configuration"
Not an anaconda issue.
-> the boot sequence suggested to check the UTP cable
hmm, crash dump of redhat-config-netwotk would be interesting also..
more info or close this bug, please...