https://wiki.archlinux.org/api.php?action=feedcontributions&user=Crazor&feedformat=atomArchWiki - User contributions [en]2024-03-28T09:44:06ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Broadcom_wireless&diff=362470Broadcom wireless2015-02-23T16:19:30Z<p>Crazor: /* Suppressing console messages */ Updated suppression method with a simpler version.</p>
<hr />
<div>[[Category:Wireless Networking]]<br />
[[ja:Broadcom wireless]]<br />
[[zh-CN:Broadcom wireless]]<br />
== Introduction ==<br />
<br />
Broadcom has been notorious in its support for its Wi-Fi cards on GNU/Linux. Until recently, most Broadcom chips were either entirely unsupported or required the user to tinker with firmware. A limited set of wireless chips were supported by various reverse-engineered drivers ({{ic|brcm4xxx}}, {{ic|b43}}, etc.). The reverse-engineered [http://wireless.kernel.org/en/users/Drivers/b43 b43] drivers have been in the kernel since 2.6.24.<br />
<br />
In August 2008, Broadcom released the [http://www.broadcom.com/support/802.11/linux_sta.php 802.11 Linux STA driver] officially supporting Broadcom wireless hardware on GNU/Linux. These are restrictively licensed drivers, but Broadcom promised to work towards a more open approach in the future. Further, they do not work with hidden ESSIDs.<br />
<br />
In September 2010, Broadcom [http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418 finally released] fully open source drivers for its hardware. This driver, [http://wireless.kernel.org/en/users/Drivers/brcm80211 brcm80211], has been included into the kernel since 2.6.37. With the release of 2.6.39, these drivers have been renamed to {{ic|brcmsmac}} and {{ic|brcmfmac}}.<br />
<br />
At the time of writing, there are three choices for users with Broadcom Wi-Fi chipsets:<br />
<br />
{| class="wikitable"<br />
! Driver !! Description<br />
|-<br />
|brcmsmac/brcmfmac || Open-source kernel driver<br />
|-<br />
|b43 || Reverse-engineered kernel driver<br />
|-<br />
|broadcom-wl || Proprietary Broadcom STA driver<br />
|}<br />
<br />
== Determine which driver you need/can use ==<br />
<br />
First, determine your card's [[Wikipedia:PCI_configuration_space|PCI-ID]]. Type the following (case-sensitive) command into a console:<br />
$ lspci -vnn | grep 14e4:<br />
<br />
Then check your card against this [http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices list of supported b43 devices] and this [http://wireless.kernel.org/en/users/Drivers/brcm80211#Supported_Chips list of supported brcm80211 devices].<br />
<br />
== Getting the driver ==<br />
<br />
=== brcmsmac/brcmfmac ===<br />
The {{ic|brcm80211}} drivers are included in the kernel. They are named {{ic|brcmsmac}} for PCI cards and {{ic|brcmfmac}} for SDIO devices.<br />
<br />
These drivers should be automatically loaded during start-up and no further action should be required of the user. If the driver does not load automatically, simply [[Kernel modules#Loading|load]] it manually.<br />
<br />
{{Note|1=Since {{pkg|linux}}>=3.3.1, the {{ic|brcmsmac}} driver depends on the {{ic|bcma}} module; therefore, make sure the {{ic|bcma}} module is not [[Kernel_modules#Blacklisting|blacklisted]].}}<br />
<br />
{{Note|[http://wireless.kernel.org/en/users/Drivers/brcm80211 wireless.kernel.org] states that brcm80211 does not support older PCI/PCI-E chips with SSB backplane.}}<br />
<br />
=== b43/b43legacy ===<br />
The drivers are included in the kernel since 2.6.24.<br />
<br />
==== Loading the b43/b43legacy kernel module ====<br />
Verify which module you need by looking up your device [http://wireless.kernel.org/en/users/Drivers/b43#Known_PCI_devices here]. You can also check by computer model [http://wireless.kernel.org/en/users/Drivers/b43/devices here]. Blacklist the other module (either {{ic|b43}} or {{ic|b43legacy}}) to prevent possible problems/confusion. For instructions, see [[Kernel_modules#Blacklisting]].<br />
<br />
{{Expansion|<br />
* The official repository package contains {{Pkg|b43-fwcutter}} which is supported but not mentioned below yet.<br />
** How does it relate to the external scripts and/or the AUR packages listed?<br />
** Can it be used to replace the manual download explained below?<br />
* Discussion: [https://wiki.archlinux.org/index.php/Talk:Broadcom_wireless#b43_firmware_.26_fwcutter b43 firmware & fwcutter]}}<br />
<br />
Install the appropriate {{AUR|b43-firmware}} or {{AUR|b43-firmware-legacy}} package from the [[AUR]].<br />
<br />
If you have a low-power version of a b43-supported device, you will need to install special firmware. A quick way to check whether you have a low-power chip is by running {{ic|<nowiki>lspci | grep Broadcom | grep LP-PHY</nowiki>}}. You can install it by downloading [http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2 the appropriate package] and using {{ic|b43-fwcutter}} as outlined below, or by using [https://github.com/dbb/scripts/blob/master/b43-lp-installer this installation script].<br />
<br />
To install the LP-PHY firmware, perform the following:<br />
{{bc|<nowiki>curl -LO http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2<br />
tar xjf broadcom-wl-4.178.10.4.tar.bz2<br />
cd broadcom-wl-4.178.10.4/linux<br />
b43-fwcutter -w /lib/firmware wl_apsta.o</nowiki>}}<br />
<br />
After installing the firwmare, you can now configure your device.<br />
<br />
{{Note|1=If the b43 module appears to be loaded and functional but the device is inaccessible, you may need to [[Kernel_modules#Blacklisting|blacklist]] the {{ic|bcma}} module. See [[Broadcom_wireless#Wi-Fi_card_does_not_work_or_show_up_after_kernel_upgrade_.28brcmsmac.29|Section 4.1]].}}<br />
<br />
=== broadcom-wl ===<br />
{{Warning|Even though this driver has matured a lot throughout the years and works quite well now, its usage is recommended only when neither of the two open-source drivers support your device. Please refer to project [http://linuxwireless.org/en/users/Drivers/b43/#Supported_devices b43's] page for list of supported devices.}}<br />
For users of the {{ic|broadcom-wl}} driver, there are packages available in the [[Arch User Repository|AUR]] named {{AUR|broadcom-wl}}, or, for those who prefer to use [[DKMS]], {{AUR|broadcom-wl-dkms}}.<br />
<br />
==== Loading the wl kernel module ====<br />
The {{ic|wl}} module may need to be manually loaded if there are other usable modules present. Before loading the {{ic|wl}} module, remove the {{ic|b43}} or other module that may have been automatically loaded instead:<br />
# rmmod b43<br />
<br />
Also unload {{ic|ssb}}, if loaded:<br />
# rmmod ssb<br />
<br />
{{Note|Failure to unload {{ic|ssb}} may result in the wireless interface not being created.}}<br />
<br />
Load the {{ic|wl}} module<br />
# modprobe wl<br />
<br />
The {{ic|wl}} module should automatically load {{ic|lib80211}} or {{ic|lib80211_crypt_tkip}}. Check with {{ic|lsmod}} to see if this is the case. If not, you may need to add one of those two modules as well.<br />
# modprobe lib80211<br />
<br />
or<br />
# modprobe lib80211_crypt_tkip<br />
<br />
If you installed the driver directly from Broadcom, you may also need to update the dependencies:<br />
# depmod -a<br />
<br />
To make the module load at boot, refer to [[Kernel modules]].<br />
<br />
You can also blacklist other modules (to prevent them from interfering) in {{ic|/etc/modprobe.d/modprobe.conf}}. To blacklist a module, refer to [[Kernel modules#Blacklisting]].<br />
<br />
{{Note|Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] does not work with blacklisting {{ic|b43}} and {{ic|ssb}}.}}<br />
<br />
== Troubleshooting ==<br />
=== Wi-Fi card does not seem to even exist ===<br />
<br />
{{Expansion|no solution provided}}<br />
<br />
Some users with newer cards like the Broadcom BCM43241 will experience an issue where lspci or lsusb will not show any trace of the card. A solution to this will be posted when found.<br />
<br />
=== Wi-Fi card does not work or show up after kernel upgrade (brcmsmac) ===<br />
<br />
This is caused by the kernel using the {{ic|bcma}} module instead of the {{ic|brcmsmac}} module. The solution is to blacklist the {{ic|bcma}} module. For instructions, see [[Kernel_modules#Blacklisting]].<br />
{{Note|This affects only Linux kernels 3.0, 3.1, and 3.2. Since kernel 3.3, the {{ic|brcmsmac}} module actually uses {{ic|bcma}}, so {{ic|bcma}} needs to be unblacklisted or the Wi-Fi interface will not appear.}}<br />
<br />
=== Wi-Fi card does not work/show up (broadcom-wl) ===<br />
Check if you are loading the correct modules. You may need to blacklist the {{ic|brcm80211}}, {{ic|b43}}, and {{ic|ssb}} kernel modules to prevent them from loading automatically. For instructions, see [[Kernel_modules#Blacklisting]].<br />
<br />
{{Note|You may not have to blacklist the {{ic|brcm80211}} driver; although as of 2011-06-20, it will still default to loading the {{ic|brcm80211}} module before the {{ic|wl}} driver, which prevents {{ic|wl}} from being used.}}<br />
<br />
Check if you updated your module dependencies:<br />
# depmod -a<br />
<br />
* Verify that your wireless interface(s) appear using {{ic|ip addr}}.<br />
* You may need to restart your machine to see the device appear in {{ic|iwconfig}} or {{ic|ip addr}}.<br />
* If you have recently upgraded your kernel, you need to rebuild the {{ic|broadcom-wl}} package with the new kernel installed to update the module.<br />
<br />
=== Interfaces swapped (broadcom-wl) ===<br />
Users of the {{ic|broadcom-wl}} driver may find their Ethernet and Wi-Fi interfaces have been swapped. See [[Network configuration#Device_names]] for solution.<br />
<br />
=== Suppressing console messages ===<br />
<br />
You may continuously get some verbose and annoying messages during the boot, similar to<br />
<br />
phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement)<br />
phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)<br />
phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)<br />
enabled, active<br />
<br />
To disable those messages, increase the loglevel of printk messages that get through to the console.<br />
<br />
Create a file in {{ic|/etc/sysctl.d/}} called {{ic|printk.conf}} or something similar:<br />
{{hc|printk.conf|<br />
<nowiki><br />
kernel.printk = 3 3 3 3<br />
</nowiki><br />
}}<br />
<br />
Refere to [http://unix.stackexchange.com/questions/44999/how-can-i-hide-messages-of-udev/45525#45525|this StackExchange thread] for an explanation of this variable.<br />
<br />
=== Interface is showing but does not allow connections ===<br />
<br />
Append the following to your [[Kernel parameters|kernel command line]]:<br />
b43.allhwsupport=1<br />
<br />
=== Miscellaneous user notes ===<br />
<br />
See [[Talk:Broadcom wireless]].</div>Crazorhttps://wiki.archlinux.org/index.php?title=MATE&diff=219568MATE2012-08-24T13:42:23Z<p>Crazor: /* Installation */ Removed the warning about mate-session-manager, since as of today, it gets pulled in automatically again</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[it:MATE]]<br />
[[ru:MATE]]<br />
[[zh-CN:MATE]]<br />
{{Article summary start}}<br />
{{Article summary text|What is MATE and how to get it.}}<br />
{{Article summary heading|Required software}}<br />
{{Article summary link|MATE|http://mate-desktop.org}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|GNOME}}<br />
{{Article summary end}}<br />
<br />
The '''MATE Desktop Environment''' is a fork of GNOME 2 that aims to provide an attractive and intuitive desktop to Linux users using traditional metaphors. For more information, see [https://bbs.archlinux.org/viewtopic.php?id=121162 this forum thread.]<br />
<br />
== Obtaining ==<br />
<br />
MATE is currently developed on [https://github.com/Perberos/Mate-Desktop-Environment GitHub].<br />
Stable packages with release-based version numbering are hosted on http://packages.mate-desktop.org/repo/archlinux/.<br />
Development packages with date-based version numbering are also available through the AUR ({{AUR|mate-desktop-environment}}).<br />
<br />
== Installation ==<br />
<br />
To install the stable version of MATE via [[pacman]] add the following lines to your {{ic|/etc/pacman.conf}}:<br />
<br />
{{bc|<nowiki><br />
[mate]<br />
Server = http://repo.mate-desktop.org/archlinux/$arch<br />
</nowiki>}}<br />
<br />
Run<br />
<br />
# pacman -Syy<br />
<br />
and then<br />
<br />
# pacman -S mate<br />
<br />
It might also be of interest to people to install certain packages from the '''mate-extras''' group (most being counterparts to packages in the {{Grp|gnome-extra}} group):<br />
<br />
# pacman -S mate-extras<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
<br />
{{note|Currently, many MATE packages do not provide, conflict or replace any GNOME packages.}}<br />
<br />
== Starting ==<br />
<br />
Always make sure dbus is in your DAEMONS array in [[rc.conf]] before starting MATE.<br />
<br />
=== Manually ===<br />
<br />
In order to start MATE manually, you must add<br />
<br />
exec ck-launch-session mate-session<br />
<br />
to your {{ic|[[xinitrc|~/.xinitrc]]}} file and then run<br />
<br />
$ startx<br />
<br />
{{note|If you have authorization problems (e.g. when mounting disks), try adding {{ic|dbus-launch}} after {{ic|ck-launch-session}}.}}<br />
<br />
=== Automatically at boot time ===<br />
<br />
See [[Display Manager]] and [[Start X at Boot]] for details.<br />
<br />
==== GDM (Old) ====<br />
<br />
If you are using {{AUR|gdm-old}} from the AUR, simply select the MATE session from the Sessions list. For your first time launching MATE, make sure to click "Just this session" when prompted.<br />
<br />
==== LXDM ====<br />
<br />
Just select MATE from the Sessions list. Works well.<br />
<br />
==== MATE Display Manager ====<br />
<br />
The MATE Display Manager (MDM) is the MATE desktop's counterpart to the GNOME Display Manager (GDM). It's package 'mate-display-manager' has been found in the '''mate-extra''' group or in the AUR package {{AUR|mate-display-manager}}. It has worked relatively the same as GDM does/did; unfortunately, the subproject is currently in flux, and MDM is not now (2012/07/01) available.<br />
<br />
==== [[KDM]] ====<br />
<br />
In order to be able to launch MATE from [[KDM]], the [[KDE]] Display Manager, you have to edit the KDM configuration.<br />
As root, edit the <code>/usr/share/config/kdm/kdmrc</code> configuration file. Find the '''SessionsDir''' parameter and add <code>/usr/share/xsessions</code> to the list.<br />
It should then look like this:<br />
<br />
SessionsDirs=/usr/share/config/kdm/sessions,/usr/share/apps/kdm/sessions,/usr/share/xsessions<br />
<br />
Restart KDM and select the "MATE session" from the list.<br />
<br />
==== [[SLIM]] ====<br />
<br />
Just fоllow the [[SLIM]] tutorial to know how to install and how to copy and use the .xinitrc file. And just add this line to the .xinitrc file :<br />
exec mate-session<br />
<br />
== Applications ==<br />
<br />
=== Core applications ===<br />
<br />
It is important to note that many GNOME core applications are rebranded for MATE, as per the licensing terms. Here is a simple Rosetta Stone of GNOME -> MATE applications. <br />
<br />
* Nautilus is renamed '''caja'''<br />
* Metacity is renamed '''marco'''<br />
* Gconf is renamed '''mate-conf'''<br />
<br />
Other applications and core components prefixed with GNOME (such as GNOME Panel, GNOME Menus etc) have simply had the prefix renamed "MATE" and become MATE Panel and MATE Menus.<br />
<br />
=== Extra applications ===<br />
<br />
Not all of the GNOME extra applications (built for GTK2) have been forked yet. The following extra applications '''are''' available in MATE:<br />
<br />
* Totem (mate-video-player)<br />
* Eye of GNOME (mate-image-viewer)<br />
* Gedit (mate-text-editor)<br />
* File Roller (mate-file-archiver)<br />
* GNOME Panel applets (mate-applets)<br />
* GNOME Terminal (mate-terminal)<br />
<br />
If you are using NetworkManager to connect to the internet, you can install {{AUR|network-manager-applet-gtk2}} from the AUR for a GTK2 nm-applet. You will need to modify the PKGBUILD to depend on mate-bluetooth rather than gnome-bluetooth to prevent a recursive dependency on gnome-desktop.<br />
<br />
== Known issues ==<br />
<br />
=== Endless spawning of file manager instances ===<br />
<br />
You may find that after you log in, the Caja file manager keeps spawning new instances and never stops. A temporary fix is performed with the following command:<br />
<br />
# ln -s /usr/lib/libgnutls.so /usr/lib/libgnutls.so.26<br />
<br />
Log out and log back in again once you perform this command.<br />
<br />
This may also fix an issue where the clock panel applet does not appear.<br />
<br />
=== Qt Applications are not styled ===<br />
<br />
You may find that Qt4 applications are not inheriting the GTK2 theme like they should. This can be fixed easily by installing {{pkg|libgnomeui}} with the {{ic|--force}} flag. If the problem persists, run qtconfig and make sure that the selected GUI Style is GTK+. This is likely to be fixed as MATE development continues.<br />
<br />
=== Evolution Email Not Working ===<br />
<br />
Please see [[Evolution#Using_Evolution_Outside_Of_Gnome]].<br />
<br />
=== Sticky Notes lost between Reboots ===<br />
<br />
As of Version 1.1.0, the Sticky Notes Panel Applet fails to save the notes created. This can be easily solved with the following two commands:<br />
<br />
$ mkdir /home/username/.config/mate/<br />
$ touch /home/username/.config/mate/stickynotes_applet<br />
<br />
For more information, see [http://forums.mate-desktop.org/viewtopic.php?f=7&t=15 this post] in the MATE Forums.</div>Crazor