Basic steps for enabling wireless

  1. It is easiest to start without encryption first, then add it afterwards. This will only work if the access point to which you are trying to connect is itself unencrypted —and you may legally use an access point only if you own it or have permission from the owner.
  2. If you installed MEPIS-64, make sure any drivers you are trying to use are 64-bit drivers.
  3. Configure your card with MEPIS Network Assistant (command line: mnetwork), by clicking KMenu --> System --> MEPIS --> MEPIS Network Assistant and supplying the root password.
    • General tab:
      1. The automatic mode using networkmanager may work on some systems, and it (or another wireless frontend) may be preferable for laptops that often switch access points. Click the Automatic radio button, then click Apply. Remember to start the Knetworkmanager application after choosing this option.
      2. The manual mode (default) works better for many wireless users, especially when using the same access point all the time, and is the standard mode for wired access. If necessary, click that radio button to activate it and then Apply. If the Knetworkmanager icon is in the system tray of the Panel at the bottom right of the screen, right-click it to quit so that it does not interfere with the manual mode.
    • Wireless tab: note the interface (e.g., wlan0) where wireless is located. Enter the name of your network (SSID); you can also try any or default. Select your encryption mode and enter the key, if any. Select any other options that are required by your access point. Click Apply.
    • Interfaces tab: use the pull-down menu to get to your wireless interface, then click Start at boot. Uncheck Start at boot for any other interfaces you will not be using (e.g., eth0 if you have wireless on wlan0 and will be using it exclusively). Click Apply then OK. You may have to reboot for the changes to take effect.
  4. If you are using the LiveCD and suspect a conflict between the native driver and Ndiswrapper, see these workarounds.
  5. Some cards may require particular methods because of the chipset they use. To find out what chipset your card uses, open a terminal and type:
    lspci -v
    Look for the chipset name in the entry Network controller or Ethernet, for instance (in bold):
    0000:02:01.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
    Here are the three most common problematic chipsets: If you have a different chipset that is giving you problems, use the search function on one of the MEPIS forums (see Section 11) to find relevant and recent help.
  6. If MEPIS Network Assistant doesn't work, try to configure your card in a root terminal with the command line utilities (see Section 5.7.1).
  7. If you have hardware recognized but are not able to connect with the methods listed above, try downloading and installing a wireless front end application such as Wlassistant, Wifi-Radar, or Wicd (see link to Wiki page on wireless). Please note that MEPIS can not guarantee the performance of these applications.
  8. If your card starts but does not connect, check the Use static DNS button on the General tab of MEPIS Network Assistant, and click Apply if necessary. If that works, then reboot, go into Network Assistant again, and try to switch back to Use DHCP for DNS.
  9. If WEP or WPA does not work, follow the Wiki page on wireless link below. The frontend Wicd is particularly strong on WPA.
  10. If still no luck, post the following information on the MEPIS forum of your choice:
    • your MEPIS version and architecture (32 or 64)
    • the output of entering the following into a terminal as root:
      lspci | grep -i net (lsusb | grep -i net, for a usb adapter)
      ndiswrapper -l

MEPIS Wiki: Wireless: