Bug 191637
| Summary: | bcm43xx module fails on kernel 2.6.16-1.2111_FC5smp | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jon Jahren <jon.jahren> | ||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5 | CC: | davej, dwmw2, wtogami | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 2.6.17-1.2157 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-03-01 19:00:05 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
Jon Jahren
2006-05-14 10:55:27 UTC
Have you tried the fedora-netdev kernels? http://people.redhat.com/linville/kernels/fedora-netdev/ Is the problem still evident w/ those kernels? Please try them and post the results...thanks! I haven't tried the netdev kernels, but the problem went away when Fedora updated to 2.6.17-1.2157, sorry for not responding earlier. Those kernels get fixes for networking faster? The fedora-netdev kernels are Fedora kernels w/ as many networking patches from upstream applied on top as practically possible. The idea is to provide the ability for some early testing of upstream stuff. Anyway, if the problem is gone for you now, I'm going to close this as CURRENTRELEASE...thanks! I've got customers still having problems, unfortunately (see below):
I can't get it to work. Here is what I did:
First, I tried again with the 2.6.17-1.2157 kernel: no luck.
Then, I installed the 2.6.17-1.2145.2.4_FC5.netdev.6 kernel: no luck.
With the netdev kernel, I downloaded and tried several different firmware versions:
3.20.23.0, 3.30.15.0, 3.40.73.0, 3.100.46.0, 3.120.27.0, 4.10.40.0
Still the same. In /var/log/messages I still see this line:
ADDRCONF(NETDEV_UP): eth1: link is not ready
The interface comes up enough for iwconfig eth1 to work:
root@dhcp-24-180 259> iwconfig eth1
Warning: Driver for device eth1 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"dhcp-24-180.slac.stanford.edu"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=1 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But that is all that works. "iwlist eth1 scan" just says
"eth1 Interface doesn't support scanning." and "dhclient eth1" does not get
me an
IP address.
So, it still does not work and unless I have picked 6 not working firmware
versions, I am out of ideas what to try :-(
And the really annoying thing is that it used to work for a short time.
Many thanks,
Alf.
Kent, 2.6.17-1.2157.2.1_FC5.netdev.7 is now available. Does that work any better for you and your customers? Created attachment 136896 [details]
sysreport
Here's the sysreport from Alf's laptop. Let me know if you need anything else.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. Is this still a problem with current kernels? |