Bug 124805
Summary: | Kudzu problems with 2 network devices | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Avi Alkalay <avibrazil> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | dario.prester, malex, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-27 21:43:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Avi Alkalay
2004-05-30 14:37:45 UTC
I have the same problem with wireless card Netgear MA311. Every time I boot the box, kudzu detects an hardware change: an old card has removed and then a new card has added. When the system is run, I see by system-config-network that there are 2 cards detected but just one correctly configured and working. Fortunately, the only real card works properly I looks like the problem is not specific to the DWL device, but is happening for me in computers that have 2 network devices: ACM and ethernet, ou wireless and ethernet. Kudzu all the time detects changes in them. For example, my laptop has on board Gig Ethernet and Wireless. It detects removal and resinretion of both. And it sometimes changes the order of them: what was eth0 becomes eth1 and vice-versa, making a big mess with network configutarions of the ifcfg-eth* files. On my system eth0 should be DHCP and eth1 fixed. And on some boots they are being switched on /etc/modprobe.conf without swicth in the ifcfg-eth* files. Big mess. The same for me with Netgear MA311. I fixed removing the extra device using system-config-network and telling kudzu to keep configuration. Anynow I can bring up the adapter only when I set "Activate on boot", if I try to activate it later using the "Activate" button on system-config-network it hangs, so I have to switch on the access point before booting the system. The user activation works well now after installing the update system-config-network-1.3.17-0.FC2.1 Please try the test RPMS at: http://people.redhat.com/notting/kudzu/ Should be fixed in the last kudzu update for FC2. |