Bug 109365
Summary: | Wireless Prism2 card detected as "Ethernet" not "Wireless" | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Josiah Royse <jroyse> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 1 | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-04-28 18:18:46 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: | |||||||||
Attachments: |
|
Description
Josiah Royse
2003-11-07 03:04:18 UTC
Created attachment 95786 [details]
kudzu -p output
Created attachment 95787 [details]
lspci output
How did you initially configure the card? In the "Description of problem" when I said "previously" I really meant "in past releases". The card (Dell True Mobile Prism2) was in the laptop at boot, and during the install of a fresh Fedora 1.0 install the two cards were configured with static ip addresses. Sorry for the confusion. I didn't attach the /etc/sysconfig/network-scripts/ifcfg-eth1 - but it had TYPE="Ethernet" instead of the "Wireless" and was strangely missing the: # Card Comments section at the top like the 3com built-in NIC got on it's ifcfg-eth0 file. Is Kudzu the right component? So, /etc/sysconfig/network-scripts/ifcfg-eth1 was existing directly after install? Exactly. The ifcfg-eth1 file for the Prism2 was filled with the right information directly after boot, however it had the TYPE variable wrong. Since the TYPE was set to Ethernet, the GUI tools don't allow the user to set WEP settings. Does this persist with later releases? |