Posts: 3
paxform
Joined: 24 Apr 2012
#1
I am very pleased to be part of this forum, and I am excited about using antix. For me, so far, antix is a nice balance between automation and control--it's a good learning linux, and I am still a beginner. I've done some searching on this forum and have read several posts about wireless issues, but I think I might have a unique problem, or at least one that has not really been addressed here.

I just did a fresh install of antiX-M11 Jayaben Desai, and following the advice on
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post23952.html#p23952"
linktext was:"this posting"
====================================
, got wireless up and running no problem. I specifically used this chain of commands

Code: Select all

modprobe -r b43
modprobe -r ssb
modprobe -i b43
and then assigned wlan0 to"Wireless interface" in wicd preferences. Refreshed and done. Even after rebooting, I still have the wireless connection I set up automatically, though the wicd status icon is gone.

I did the same thing earlier today, so this recent reinstall is a sort of confirmation that my wireless card is working properly and that antix has everything needed to get my card receiving signals.

The reason I just did this reinstall was also to revert back to whatever settings allowed my wireless to work. Earlier today, after doing

Code: Select all

apt-get upgrade
my wireless no longer worked, and I could not get it to work by repeating the steps I followed after the fresh reinstall.

This is where I am stumped. My wlan0 still exists and shows up with ifconfig, etc. but in wicd and ceni, a scan for available networks yields nothing:"No wireless networks found." I figure that the upgrade must have created a change in configuration or introduced a driver/firmware incompatibility, but I am not sure how. I thought apt-get upgrade did not introduce new packages, just updates to existing ones. And if there are things I need to remove to eliminate the incompatibility, I am not sure what to remove or even how to remove it.

Would anyone be willing to help me troubleshoot this one? I am willing to post whatever I need to and will continue to experiment until I get to the bottom of it. I am hoping also that this process might reveal some possible fixes that can be applied to antix12, in light of the recent exchange about wireless drivers in
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post23952.html#p23952"
linktext was:"this posting"
====================================
.
Posts: 279
afab4
Joined: 17 Oct 2009
#2
Sometimes an upgrade wipes out the B43 directory. Make sure it is there at /lib/firmware/b43

If not, copy it over from your live cd. i used to keep b43 directory on a thumb drive just for this purpose.
Posts: 3
paxform
Joined: 24 Apr 2012
#3
Sometimes an upgrade wipes out the B43 directory. Make sure it is there at /lib/firmware/b43.
This suggestion pointed me in the right direction. Thanks! The b43 directory was still there after the upgrade but it contained many additional files.

/lib/firmware/b43 before apt-get upgrade:

Code: Select all

a0g0bsinitvals5.fw
a0g0bsinitvals9.fw
a0g0initvals5.fw
a0g0initvals9.fw
a0g1bsinitvals13.fw
a0g1bsinitvals5.fw
a0g1bsinitvals9.fw
a0g1initvals13.fw
a0g1initvals5.fw
a0g1initvals9.fw
b0g0bsinitvals13.fw
b0g0bsinitvals5.fw
b0g0bsinitvals9.fw
b0g0initvals13.fw
b0g0initvals5.fw
b0g0initvals9.fw
lp0bsinitvals13.fw
lp0bsinitvals14.fw
lp0bsinitvals15.fw
lp0initvals13.fw
lp0initvals14.fw
lp0initvals15.fw
n0absinitvals11.fw
n0bsinitvals11.fw
n0initvals11.fw
pcm5.fw
ucode11.fw
ucode13.fw
ucode14.fw
ucode15.fw
ucode5.fw
ucode9.fw
/lib/firmware/b43 after apt-get upgrade:

Code: Select all

a0g0bsinitvals5.fw
a0g0bsinitvals9.fw
a0g0initvals5.fw
a0g0initvals9.fw
a0g1bsinitvals13.fw
a0g1bsinitvals5.fw
a0g1bsinitvals9.fw
a0g1initvals13.fw
a0g1initvals5.fw
a0g1initvals9.fw
b0g0bsinitvals13.fw
b0g0bsinitvals5.fw
b0g0bsinitvals9.fw
b0g0initvals13.fw
b0g0initvals5.fw
b0g0initvals9.fw
ht0bsinitvals26.fw
ht0bsinitvals29.fw
ht0initvals26.fw
ht0initvals29.fw
lcn0bsinitvals24.fw
lcn0bsinitvals25.fw
lcn0bsinitvals26.fw
lcn0initvals24.fw
lcn0initvals25.fw
lcn0initvals26.fw
lcn1bsinitvals24.fw
lcn1bsinitvals25.fw
lcn1bsinitvals26.fw
lcn1initvals24.fw
lcn1initvals25.fw
lcn1initvals26.fw
lcn2bsinitvals24.fw
lcn2bsinitvals25.fw
lcn2bsinitvals26.fw
lcn2initvals24.fw
lcn2initvals25.fw
lcn2initvals26.fw
lcn400bsinitvals33.fw
lcn400initvals33.fw
lp0bsinitvals13.fw
lp0bsinitvals14.fw
lp0bsinitvals15.fw
lp0bsinitvals16.fw
lp0initvals13.fw
lp0initvals14.fw
lp0initvals15.fw
lp0initvals16.fw
lp1bsinitvals20.fw
lp1bsinitvals22.fw
lp1initvals20.fw
lp1initvals22.fw
lp2bsinitvals19.fw
lp2initvals19.fw
n0absinitvals11.fw
n0bsinitvals11.fw
n0bsinitvals16.fw
n0bsinitvals17.fw
n0bsinitvals22.fw
n0bsinitvals24.fw
n0bsinitvals25.fw
n0initvals11.fw
n0initvals16.fw
n0initvals17.fw
n0initvals22.fw
n0initvals24.fw
n0initvals25.fw
n16bsinitvals30.fw
n16initvals30.fw
n18bsinitvals32.fw
n18initvals32.fw
n1bsinitvals20.fw
n1initvals20.fw
n2bsinitvals19.fw
n2initvals19.fw
pcm5.fw
sslpn0bsinitvals16.fw
sslpn0initvals16.fw
sslpn1bsinitvals20.fw
sslpn1bsinitvals27.fw
sslpn1initvals20.fw
sslpn1initvals27.fw
sslpn2bsinitvals19.fw
sslpn2initvals19.fw
sslpn3bsinitvals21.fw
sslpn3initvals21.fw
sslpn4bsinitvals22.fw
sslpn4initvals22.fw
ucode11.fw
ucode13.fw
ucode14.fw
ucode15.fw
ucode16_lp.fw
ucode16_mimo.fw
ucode16_sslpn.fw
ucode16_sslpn_nobt.fw
ucode17_mimo.fw
ucode19_sslpn.fw
ucode19_sslpn_nobt.fw
ucode20_sslpn.fw
ucode20_sslpn_nobt.fw
ucode21_sslpn.fw
ucode21_sslpn_nobt.fw
ucode22_mimo.fw
ucode22_sslpn.fw
ucode24_lcn.fw
ucode24_mimo.fw
ucode25_lcn.fw
ucode25_mimo.fw
ucode26_mimo.fw
ucode27_sslpn.fw
ucode29_mimo.fw
ucode30_mimo.fw
ucode32_mimo.fw
ucode33_lcn40.fw
ucode5.fw
ucode9.fw
The additional files seem to have come from the updated firmware-b43-installer, which pulls from a newer firmware. Here is some output from the apt-get upgrade that might shed some light:

Code: Select all

Setting up firmware-b43-installer (1:015-14) ...
No chroot environment found. Starting normal installation
This card work with newer 5.100.138 firmware. Trying to install it.
--2012-04-24 23:36:53--  http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
Resolving www.lwfinger.com... 69.175.20.18
Connecting to www.lwfinger.com|69.175.20.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13514651 (13M) [application/x-tar]
Saving to: “broadcom-wl-5.100.138.tar.bz2”

100%[===================================================================================================================>] 13,514,651  1.54M/s   in 10s     

2012-04-24 23:37:03 (1.27 MB/s) - “broadcom-wl-5.100.138.tar.bz2” saved [13514651/13514651]

Creating new firmware directory...
broadcom-wl-5.100.138/
broadcom-wl-5.100.138/linux/
broadcom-wl-5.100.138/linux/wl_apsta.o
broadcom-wl-5.100.138/linux/wl_ap.o
broadcom-wl-5.100.138/linux/wl_sta.o
broadcom-wl-5.100.138/README
broadcom-wl-5.100.138/config/
broadcom-wl-5.100.138/config/wlconfig_lx_shared
broadcom-wl-5.100.138/config/wl.mk
broadcom-wl-5.100.138/config/wl_default
broadcom-wl-5.100.138/config/wl_hnd
broadcom-wl-5.100.138/config/wlconfig_nomimo
This file is recognised as:
  filename   :  wl_apsta.o
  version    :  666.2
  MD5        :  e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
  ucode time:     01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
  ucode date:     2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
  ucode time:     01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/n0initvals11.fw
Extracting b43/lcn0initvals25.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/sslpn1initvals20.fw
Extracting b43/lcn1bsinitvals26.fw
Extracting b43/n0initvals22.fw
Extracting b43/ht0bsinitvals29.fw
Setting up firmware-b43legacy-installer (1:015-14) ...
No chroot environment found. Starting normal installation
No supported card found.
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
When I replaced the new b43 directory with the old one and restarted the module, everything worked fine. When I restored the new directory and restarted the module, I could not detect any wireless networks. So it appears that some of the additional files in the updated firmware are causing the problem, though I don't know which ones or why.

Hope this discovery helps someone out. Also, I hope an expert might be able to shed some light on why the newer firmware caused wireless to fail (at least for BCM4318).

Thanks to all.
Posts: 279
afab4
Joined: 17 Oct 2009
#4
]"Setting up firmware-b43legacy-installer (1:015-14)"

Your 4318 card does not use b43legacy drivers. Uninstall firmware-b43legacy-installer (1:015-14). I believe there is a thread somewhere on this board.
It appears that your upgrade is forcing use of the legacy driver creating a conflict.

viewtopic.php?f=15&t=3110&hilit=firmware%20b43legacy%20installer
Posts: 3
paxform
Joined: 24 Apr 2012
#5
Your 4318 card does not use b43legacy drivers. Uninstall firmware-b43legacy-installer (1:015-14). I believe there is a thread somewhere on this board. It appears that your upgrade is forcing use of the legacy driver creating a conflict.
I purged firmware-b43legacy-installer, rebooted, and tried the updated firmware again. Same result:"no wireless networks found" in wicd. Once I restored the older set of b43 files, I could connect again. So it seems, in my case, that the problem is the newer version of the firmware, or how the newer firmware works with antix, not sure.

At this point, I have working wireless, but I am willing to keep working on this until the real nature of the problem is revealed. In the end, updating b43 firmware should not render any b43 wireless card inoperable, but this seems to be happening with antix-M11.
Posts: 279
afab4
Joined: 17 Oct 2009
#6
paxform wrote: Once I restored the older set of b43 files, I could connect again. So it seems, in my case, that the problem is the newer version of the firmware, or how the newer firmware works with antix, not sure.

At this point, I have working wireless, but I am willing to keep working on this until the real nature of the problem is revealed. In the end, updating b43 firmware should not render any b43 wireless card inoperable, but this seems to be happening with antix-M11.
Well, keep fighting it if you want and I hope you come up with a final solution. (and if you do please share!) but I went round and round with this with my Dell D800 with the Broadcom wireless. Every time I did an upgrade it would roach my wireless.
I rolled back the b43 firmware, removed firmware-b43legacy-installer and pinned firmware-b43-installer.
Never had any more problems.
I don't think it has anything to do with antiX. It is a debian issue. i did notice that your upgrade installed the wl driver and this may be causing the problem too. Maybe blacklisting wl will do the trick.
check this out
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://linuxwireless.org/en/users/Drivers/b43"
linktext was:"http://linuxwireless.org/en/users/Drivers/b43"
====================================

The notebook I use now has an Intel card and it is nice not to have to fight with the Broadcom wireless cards my previous 2 lappies had.