Bug 215367
Summary: | wireless install fails | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sean Dilda <agrajag> |
Component: | anaconda | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | linville, psj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-28 19:40:44 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
Sean Dilda
2006-11-13 18:03:50 UTC
You can probably workaround this by booting with 'essid=foo' on the kernel command line. The fix is that we should probably initialize things better in isys/wireless.c:get_essid() I see the same issue here. <ctrl>-U clears the ESSID field in the dialogue and allows me to enter my own but then it appears not to connect to the network (still investigating but at least DHCP does not work). Booting installer with "linux essid=foo" did nothing for me - the wireless settings dialogue still showed the ami3333 text reported. Unitialized structures lead to pain and suffering. Committed to devel branch. Thanks. And see, what I meant to say was _uninitialized_. *** Bug 221415 has been marked as a duplicate of this bug. *** |