Tag Info

Hot answers tagged

6

It seems that support for that particular chip or firmware version is still not very stable. The message is telling you to pass an option to the b43 kernel module to activate support for your chip version. This may improve things or not. To do so, create a file /etc/modprobe.d/local-b43.conf containing the lines # Activate experimental support for some ...


3

You need to put if_bwn_load="yes" in /boot/loader.conf. If you don't have a /boot/loader.conf file on your system, just create it. As with the /etc/defaults/rc.conf file, /boot/defaults/loader.conf contains default values that can be overridden in a per-system fashion. Of course, you'll need to either reboot the system to pick up the new setting, or load ...


3

It is not possible because it's not driver who uses this SRAM, it's adapter itself. This SRAM contains hardware registers of Ethernet chip that are used by driver to communicate with it and is physically arranged this way. And it is not unique for this driver, it's very typical way of interacting between different hardware components in computer system.


3

My educated best guess: No, it's not possible to completely disable the SRAM. A quick look in the Linux tg3 driver code drivers/net/ethernet/broadcom/tg3.* reveals that SRAM operations are like everywhere in there. For example, it even appears to contain the MAC address: #define NIC_SRAM_MAC_ADDR_HIGH_MBOX 0x00000c14 #define NIC_SRAM_MAC_ADDR_LOW_MBOX ...


2

for some reason the ar9721.fw file was empty… downloaded the file again – put it into /lib/firmware and now it works…


2

Check the output of lsmod to see if they are being loaded; if not, try to modprobe $module to load it manually. If this does not help you are probably using the wrong driver for that particular card. If it works, run depmod -a to regenerate module dependencies. It should load it automatically afterwards.


2

According to the ArchWiki, you must blacklist b43 module because it conflicts with brcmsmac.


2

I was originally running kernel 3.7.4-204.fc18.i686 with kmod-wl-3.7.4-204.fc18.i686-5.100.82.112-7.fc18.8.i686 and the wireless had issues. After 2 more updates of the kernel it just works fine. So this is what I have running and working good now: sly@localhost ~$ uname -r 3.7.6-201.fc18.i686 sly@localhost ~$ rpm -qa | grep -e '-wl' | sort ...


2

To unload modules you can use these 2 commands, lsmod and rmmod. lsmod will list what modules are loaded, while rmmod will remove a given module from the Kernel, assuming it was dynamically built so that it can/could be dynamically loaded. $ sudo lsmod | head -5 Module Size Used by bluetooth 89276 0 cpufreq_powersave ...


1

From my friend Google who pointed to https://bbs.archlinux.org/viewtopic.php?id=148170: /usr/lib/systemd/system/rc-local.service [Unit] Description=/etc/rc.local Compatibility After=network.target [Service] Type=oneshot ExecStart=-/etc/rc.local #ExecStart=-/pathtoyour/script1 #ExecStart=-/pathtoyour/script2 TimeoutSec=0 StandardInput=tty ...


1

For the benefit of people landing on this page There is a bug raised on launchpad In the comment #29 there is a solution provided that is to reload the wl module: modprobe -r wl && modprobe wl


1

I found a solution for my problem. I tested different drivers that were mentioned for the Broadcom Chip. The first success was a slow wifi connection. The thing is to have a look that sometimes more than one driver module can be disturbing for the driver. Driver modules can be unloaded with modprobe -r followed by the module name. They can be loaded by the ...


1

Try service NetworkManager stop. It will just interfere with any attempt to manual configure and debug the set-up. Now try iwconfig. Hopefully you see mention of an interface that isn't described with "no wireless extensions". Presuming that is wlan0 (it could be something else), try: ifconfig wlan0 up && iwlist wlan0 scanning You should see ...


1

Like the previous post, it would really help to know more information. There's a couple things I know I can point out: The link is for Arch Linux, which is quite different from Crunchbang (#!). While #! is relatively small in community, many fixes found for Debian and also Ubuntu will work for #!. Waldorf (11) is still in testing, you might have better ...


1

From what you've posted, it looks like there's a problem linking the wl_cfg80211.o file, possibly a library missing. Some of the other errors seem to imply you're missing a header/include file to define things to match the library.


1

There is an extensive howto on getting the driver and making it work at http://www.susegeek.com/networking/fix-bcm4311431243214322-wireless-in-opensuse-111-and-earlier/


1

I'm guessing this has to do with encoding. According to this answer, an SSID may (now) have an explicit UTF-8 or UNSPECIFIED encoding, but the "SSIDEncoding" field is part of a newer standard. Presumably then on networks with equipment older than this, it is effectively "unspecified". I would like to think that anything which sets an SSID from text input ...


1

I should just be able to wget the tarballs from http://linuxwireless.org/en/users/Drivers/b43 put those on the pendrive and then try loading transfering them into arch That is exactly what to do. Unfortunately, Broadcom does not provide distribution licensing for the firmware, so you have to download their full proprietary driver from their website, ...


1

The firmware must be present at the time you load the driver. So be sure to unload the module and reload it: # <install firmware> rmmod bnx2 modprobe bnx2 For some drivers (I don't know about this one), you may need to unload auxiliary modules that it's using. lsmod | grep bnx2 will show what modules bnx2 uses. Call rmmod on all of them in ...



Only top voted, non community-wiki answers of a minimum length are eligible