From Mageia wiki
Jump to: navigation, search
Drakconf multiflag.png
Other languages

Deutsch ; English ; Français



Suitable hardware is obviously needed to create a Wifi connection, that means it must be correctly detected by Mageia. To check that, there are two solutions:

  • Using the Mageia Control Center (MCC) menu -> Tools -> System tools -> Mageia Control Center, tab Hardware and then Browse and configure hardware


Select the Ethernet line (see below) and see what the MCC found :


In this case, there is unfortunately no wireless adapter!

There are below two examples where wireless adapters are present and correctly detected, the first one is a USB stick and the second a PCI card:



It is important to find a device referring to "802.11" or "wireless" terms. You can see also what are the hardware vendor and reference, it may be useful later on.

  • Using the command line is also possible, open a console and enter under root:
[root@computer ~]# iwconfig
[root@computer ~]# _

Here is an answer that says there is no wireless adapter and another one which is nicer, "wlan0" is what we are looking for (it may have other names):




Drivers or firmwares are also needed, most of them are available in the Mageia repositories (Core and Nonfree), if you have an internet connection (a wired one), there is no problem, Mageia will fetch what it needs automatically. See here how to configure the repositories if necessary:


But if you haven't any internet connection, you must install the needed drivers from a CD or a USB stick. See the troubleshooting section below to know the more common drivers.


Your shiny new Mageia operating system is installed on your computer, the hardware is well detected, and you decide you want to use WiFi.
OK, let's go through this together!

  • 1. Access MCC (the Mageia Control Center)
(You will need to give the root password)
  • 2. Once MCC has launched, click on the tab "Network & Internet" and then "Set up a new network interface (LAN, ISDN, ADSL,...)"
  • 3. Select "Wireless (Wi-Fi)", then "Next"
  • 4. Select your network card in the list.


If your card is not in the list or the only option is "Use a Windows Driver (with ndiswrapper)", see the alternative method, below.
Anyway, let us assume your card is there. Select "Next".
It is possible Mageia need to download a driver it doesn't find. Check the repositories are correctly configured. If the driver isn't in the repositories, try to find it and install it, you can ask help in the Mageia forum. In both cases, start again from the point 2


  • 5. Then, you must select your WiFi Access Point by clicking on its SSID (Callsign). If you can't see any, try this I_have_no_access_point_in_the_list
  • 6. If your WiFi network is encrypted, Mageia recognizes the encryption type and selects it automatically. Of course, you will need to enter the correct password. Mageia won't do that for you!


The package wpa_supplicant is automatically installed for encrypted connections


  • 7. You have to select how the computer will be connected to the net. The easiest method is automatically, using DHCP. But, you can also specify an IP address.
  • 8. You should keep the box "Get DNS servers from DHCP" checked. Select "Next".
  • 9. Check the 2 first boxes. Select "Next".
  • 10. Answer "Yes" to the question "Do you want to start the connection now?"
Two messages can appear:

Wireless010.png See the Troubleshooting section below

Wireless013.png Good!

  • 11. Your computer will connect to the Wi-Fi point if all the information was correctly entered.
If it connects, then the networking icon in the taskbar will change from:Non-connected.png to: Connected.png
  • 12. You can test your connection in your favourite browser.



You have followed the above instructions, Mageia recognises your Wifi-card, but the installation failed. You can try another step to solve this. This solution uses Ndiswrapper, which is a method that consists of installing and activating the Windows XP driver. This is useful when your network hardware is not well supported by Linux, which is probably why it's not on the list of supported cards!

Ndiswrappper allows the use of Windows XP drivers, and XP only, for Linux


  • You will need the Windows driver for your card, either on a CD, on your hard disk or other media. You can probably also find it on the Internet, although it is best to download them from the manufacturer's website and not via a general search for drivers.
  • Place the driver in an accessible place, for example on your desktop.
  1. After Step 3 in the original procedure, select "Use a Windows driver (with ndiswrapper)", and then "Next". The system will perhaps install some packages it needs.
  2. Navigate to the directory where you stored the driver and select the_driver_for_my_card.inf.
    You have to choose the file with the ".inf" extension.
  3. You can continue with the above steps 5 to 12 to finalise the installation.

Some more help and many drivers can be found here : Sourceforge

Most common drivers

It may happen that Mageia fails to choose the right driver. If a first try failed, install the following drivers that seems to match your hardware.

Manufacturer driver
Broadcom dkms-broadcom-wl
Intel iwlwifi-3945-ucode
Ralink ralink-firmware
Atheros madwifi-source
Every kernel-firmware

I have no access point in the list

If at step 5, the list is void and you have the message "non listed - edit manually", we give you another solution.

You can install the package "kernel-firmware-nonfree" via MCC and restart your computer.


rfkill is a tool to block/unblock all radio connexions, check that yours are authorized. In a console, enter:

[user@computer ~]$ rfkill list
[user@computer ~]$ _

Wireless011.png Wireless016.png

  • If there is a line with "Soft blocked: yes" then in the console under root, enter:
[root@computer ~]# rfkill unblock all
[root@computer ~]# _

  • If there is a line with "Hard blocked: yes" then find the wireless button/switch on your laptop and enable it. You can see such a switch on the picture below.


Other problems

If the wireless adapter isn't detected, or if you encounter other problems, ask help in the Mageia Forum with the following information:

  • Hardware information
[user@computer ~]$ inxi -n
[user@computer ~]$ _

  • This command output for a PCI card:
[root@computer ~]# lspcidrake | grep -i net
[root@computer ~]# _

  • This command output for a USB card:
[root@computer ~]# lsusb
[root@computer ~]# _

  • The installed driver

To know if a driver is installed, you can use this command in a console:

[root@computer ~]# rpm -qa|grep piece_of_the_driver_name
[root@computer ~]# _



Structured troubleshooting for wireless issues - WORK IN PROGRESS


This section tries to describe how to go from zero to wireless in some more-or-less easy steps and in a structured manner, from the ground up, from bottom to top.

For a high-level overview, the basic steps are always as follows:

  1. get your device properly recognised/initialised (driver & firmware)
  2. make sure your device is unblocked via rfkill (soft block) or hardware switch on laptop (hard blocked)
  3. be able to see wireless networks, and be able to connect to wireless networks (unencrypted for testing)
  4. connect and authenticate to wireless network (WPA/WPA2) and stay connected
  5. get your IP address configuration correct

Steps in detail

1. Driver/firmware installation
  • 1.1 Check which physical device and chipset you have, and what is seen by the kernel
[user@computer ~]$ lspcidrake -v
[user@computer ~]$ _

-v for verbosity is important! Otherwise, information about vendor, product and device ID is omitted. This information is used to know which wireless chipset you have, and gather specific information about that chipset and required firmware.

  • 1.2 Does your chipset require firmware to work? Is the firmware installed on your box? and is it already correctly loaded?

This is actually two-fold; one part you can investigate yourself at and use this table:

List of firmware packages, and what repo they are contained in
Repository Firmware
Core Release kernel-firmware
Core 32 bits release zd1211-firmware
Non-free 32 bits release ipw2100-firmware
kernel-firmware-nonfree (most common firmware including Atheros, Broadcom, Intel IWL)
ralink-firmware (RaLink)
rtlwifi-firmware (Realtek)
  • 1.3 Check which firmware is loaded (might output some more information than just firmware). Enter with root rights (Ctrl C to quit):
[root@computer ~]# journalctl -ab | grep -iE "fw|firmware|iwl|wifi|wire|80211"
[root@computer ~]# _

2. Check if the device is blocked with the commands rfkill list all or rfkill list wlan

See #rfkill for more details

In some cases, you might also see your wireless device listed multiple times, and one is blocked and the other one is not. Those issues are mostly laptop-specific, when the wireless switch is implemented as a softbutton and this softbutton implementation requires a specific kernel module to be loaded. Often the case with some Asus, Acer, HP or Toshiba laptops. See for an example.

3. Check if your device is usable and can see networks
[root@computer ~]# iwconfig
[root@computer ~]# _

This command above shows if your wireless device is initialised, usable and its name (on the left).

Those commands below, search for wireless networks that can be seen by your wireless chipset. Replace wlan0 by your wireless device name.

[root@computer ~]# iwlist wlan0 scan
[root@computer ~]# _


[root@computer ~]# iw dev wlan0 scan
[root@computer ~]# _

4. Check if you can connect to your network

Rule of thumb: Only use one network manager. Mageia by default comes with the inhouse net_applet and the integration in Mageia Control Center via drakconnect and draknetcenter . Also see for an overview. An alternative to net_applet would be NetworkManager, which comes by default e.g. with GNOME. Since Mageia 4 those tools should not be blocking each other, but should run smoothly in parallel.

[user@computer ~]$ ps -ef | grep -v grep | grep -i net
[user@computer ~]$ _

Should only show one out of net_applet or NetworkManager

For ways to switch between both have a look at the related forum thread:

5. Check your IP addressing configuration
[root@computer ~]# ifconfig -a
[root@computer ~]# _

shows your wireless interface IP address.

[root@computer ~]# netstat -rn
[root@computer ~]# _

This command allows you to ping your router/gateway, if this doesn't work, check your wireless connection details

[user@computer ~]$ ping -c10
[user@computer ~]$ _

With this command, you should be able to ping internet hosts (first by IP address to rule out name resolution issues). If this is working, you have internet connection. If next step doesn't work, you only need to fix DNS.

[user@computer ~]$ ping -c10
[user@computer ~]$ _

For these two last commands, make sure your router is configured to answer to the ping command


1. Driver/firmware installation


My chipset is iwl 3945 ...


... and its firmware is loaded. (Ctrl C to quit and space bar to display next page).

2. Check if the device is blocked with the command rfkill list

See #rfkill for more details

3. Check if your device is usable and can see networks


Yes, it is


No, it is not


Several networks are seen

4. Check if you can connect to your network


My file manager is net_applet and it is loaded

5. Check up IP addressing configuration


I can see my IP address ...


... my gateway address (red circled), and the ping is working (0% packet loss).

related links with further information and also

known issues with specific drivers