Bug 177069
Summary: | bcm43xx fails to start (SIOCSIFFLAGS File not found) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Quiring <pquiring> |
Component: | kernel | Assignee: | David Woodhouse <dwmw2> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bjohnson, davej, linville, wtogami |
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: | 2006-01-27 20:09:57 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
Peter Quiring
2006-01-05 23:05:45 UTC
Should this bug be assigned to 'iproute' since that is the package that contains the 'ip' app? I've noticed that iproute version is 2.6.14 but the kernel is 2.6.15, does this mean we are waiting for the update to iproute? You need the firmware -- the kernel messages should have made that clear. Get the fwcutter tool from http://bcm43xx.berlios.de/ and extract the firmware from your existing MacOS or Windows driver (or indeed any driver you can download) with it. In that case I'll stick with ndiswrapper. I tried the fwcutter with mixed success. DHCP doesn't work, and it only goes upto 11M but seems to be stuck in 1M mode (very slow). Thanks for the info, I'll keep trying with future releases of the kernel. Yeah, the driver is fairly new and still under active development. DHCP is likely to work if you do it in something like the following order... 1. ip link set eth1 up 2. Set rate to something that works (it doesn't automatically back down) 2. set the WEP key (if any) 3. set essid 4. dhclient NetworkManager does manage to get it right, apart from the rate -- I just use NetworkManager and then set the rate to 11M manually to make sure it doesn't lose packets (which it does at 54M). This should be improved in the 2.6.16-1.2070_FC5 kernel. |