| Summary: | Wireless BCM4322 not working after upgrading to Fedora 18 with kernel 3.8.4 | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Eduardo <edward.lara.lara> |
| Component: | wl-kmod | Assignee: | NVieville <nicolas.vieville> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jarod |
| Priority: | P5 | ||
| Version: | 18 | ||
| Hardware: | i386 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
| Attachments: |
logs and info
akmod compilation failure with kernel 3.9 |
||
Hello, Thank you for this detailed report. I'll try to look at it as soon as possible, as for the next few days I will not be able to work on it (heavy load at work, and family and kids). As you already found the WEXT workaround, I hope this delay will not be so harmful for you. As you mentioned it kernel 3.9 needs a patch to get this driver working, and this one is already applied in the rpmfusion devel branch of the akmod-wl package, but not in the F-18 or F-19 branch yet. Reading your logs seems to show that your problem is probably located in the part involved by this patch, but I'm not sure for the moment. If you want you could give a try to this devel package to see if this bug appears again (not sure). Feel free to provide any feedback you think useful about this issue. Thanks again. Cordially, -- NVieville Thank you for the quick response. My system is working so it is not a problem if it takes some time. I will try the new akmod and new kernel this weekend and let to know how it goes. Regards, Eduardo Created attachment 1067 [details]
akmod compilation failure with kernel 3.9
Hi,
I tried akmod-wl-5.100.82.112-10.fc19.i686.rpm with kernel 3.9.0-0.rc3.git1.4.fc19.i686.PAE (there was a newer one but failed installation on matching the hash of a file). Compilation failed. It seems to complain about the usage of a GNU-only symbol from a non GNU module. Let me know if there is some other information I should gather. I hope this helps,
Hello, Is this issue still there with the last Broadcom wireless device driver (e.g. 6.30.223.141)? In case you get it working, I'll close this bug report in the next few weeks. Cordially, -- NVieville Sorry for the slow response. I will try it this weekend It is working without the WEXT flag now. I am using the following versions: kernel-3.11.6-200.fc19.i686 akmod-wl-6.30.223.141-1.fc19.2.i686 broadcom-wl-6.30.223.141-1.fc19.noarch kmod-wl-3.11.6-200.fc19.i686-6.30.223.141-1.fc19.2.i686 Thank you! Eduardo (In reply to comment #6) > It is working without the WEXT flag now. I am using the following versions: > kernel-3.11.6-200.fc19.i686 > akmod-wl-6.30.223.141-1.fc19.2.i686 > broadcom-wl-6.30.223.141-1.fc19.noarch > kmod-wl-3.11.6-200.fc19.i686-6.30.223.141-1.fc19.2.i686 Great news! Concerning your previous message: delay is not a problem. Resolving issues sometimes needs delay. I'll close this bug. Thank you for your feedback. Cordially, -- NVieville |
Created attachment 1064 [details] logs and info I upgraded a dell mini from Fedora 17 to 18 using fedup and wireless is not working with the latest 3.8.4 kernel, but it works after recompiling akmod with WEXT. Since WEXT is been deprecated I am filing this bug. I had the following packages: [CODE] akmod-wl-5.100.82.112-9.fc18.i686 broadcom-wl-5.100.82.112-4.fc18.noarch kernel-doc-3.8.3-203.fc18.noarch kernel-headers-3.8.3-203.fc18.i686 kernel-PAE-3.7.9-104.fc17.i686 kernel-PAE-3.7.9-205.fc18.i686 kernel-PAE-3.8.4-202.fc18.i686 kernel-PAE-devel-3.7.9-104.fc17.i686 kernel-PAE-devel-3.7.9-205.fc18.i686 kernel-PAE-devel-3.8.4-202.fc18.i686 kernel-tools-3.8.3-203.fc18.i686 kernel-tools-libs-3.8.3-203.fc18.i686 kmod-wl-3.7.9-104.fc17.i686.PAE-5.100.82.112-10.fc18.i686 kmod-wl-3.7.9-205.fc18.i686.PAE-5.100.82.112-9.fc18.i686 kmod-wl-3.8.4-202.fc18.i686.PAE-5.100.82.112-9.fc18.i686 [/CODE] From lspci: [CODE] # lspci | grep Network 03:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) # lspci -vn | grep 14e4 03:00.0 0280: 14e4:432b (rev 01) [/CODE] I noticed that I started to get an error even in Fedora 17 when I upgraded from kernel 3.6.11-5.fc17.i686.PAE with driver kmod-wl 5.100.82.112-7.fc17.i686 to kernel 3.7.3-101.fc17.i686.PAE with driver kmod-wl 5.100.82.112-7.fc17.13.i686. I did not notice the error because it only appear in logs after my second reboot to the new kernel and I was able to connect to my wireless network without any problem. I did not see anything significant between the first reboot of the 3.7.x kernel and the second one where the error happened, but the first reboot was a short test so it might not had enough time for the error to occur. When I upgraded to Fedora 18 with fedup and I got a new kernel 3.8.x. Wireless stopped working so I noticed the error happening and followed the trail to the previous 3.7.x kernel. When I run on kernel 3.8.x executing a network command like ifconfig or iwconfig the command gets stuck. Trying to kill it (-15 and -9) does not have any effect, the command never returns and I do not see anything else in the logs. Wireless starts working again when I go back to my last fedora 17 kernel, so I got the last 3.7.x kernel for Fedora 18 and it works fine (except for the scan.c error in the log). I tried also a newer kernel 3.9 from koji but akmod-wl did not compile. Finally I tried configuring the akmod with WEXT on kernel 3.8 and it works fine. Please see attachments for error logs and loaded modules from kernels 3.7.3 and 3.8.3 and a full cycle with kernel 3.8.3. Let me know if there is additional information that could be helpful to diagnose and fix the problem Thank you, Eduardo