SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have tried Ndiswrapper AND Madwifi, switching back and forth between the two but settled with Madwifi considering my card is Atheros. When i set up Ndiswrapper, I would get a wlan0 interface and could set the access point information but would get no connection. Madwifi, not even the ath0 OR wlan0 interface will start. I've researched and found a lot of methods and information but nothing will work...
Also bear in mind that, particularly with Atheros chipsets, lspci lies.
I have a laptop with an AR2425 AKA AR5007EG AKA AR5BXB63, which lspci
reports back as an AR5006EG--incorrect. This chipset is only supported in
Sam Leffler's new HAL, which is now included as a separate branch in the
MadWIFI snapshot/SVN directories (the new HAL is 0.10.5.6).
Note that, as of this writing, snapshot containing the new HAL won't
compile with kernel 2.6.26 because of a parameter passing change. I've
written a ticket that they forgot to include the patch for 2.6.26 in that
branch and I'm hoping it'll show up today.
P.S. The "ath_info" utility should tell you the truth about what you have.
Again, this isn't part of Slackware AFAIK.
UPDATE: The the patch has been included as of 7-16-08 and is working for me on SlamD64 and kernel 2.6.26.
i am a linux n00b and had the same problem. I beat my head on the wall untill one day i read something on some forum (wish i could site the source, because it's not entirely all my own brainchild). i believe the /etc/rc.d/rc.inet1.conf file contains the wireless settings for start up. On my laptop the default was setup for the the rj-45 plug not my wireless card. eth0 i believe was setup by default. i don't have my laptop with me so this may be a little rough. i disabled the dhcp option(and maybe some other options) under eth0. then enable it for wlan0 (and maybe some other options). I played with the options for a bit before I finally was able to connect. Hope this helps, or at least points you in the right direction.
Last edited by p|ush; 07-16-2008 at 11:33 PM.
Reason: wrong file listed for wireless settings
Ah yes, the rc.inet1 mess. I mostly love Slackware, but when it comes to wireless rc.inet1 and rc.wireless is a huge mess--they really need to clean it up! One of these days, I'll probably do it myself and submit the changes to Pat and Fred.
My own technique is to disable rc.wireless and change the first wireless settings in rc.inet1.conf while making sure the 2nd is all commented out. If you're running original MadWiFi like I am, make sure to change the interface name from "wlan0" to "ath0" as well. After this, it seems to work just fine. I still haven't figured out if kmod is loading "ath_pci" or a script is doing it (haven't looked, bigger fish to fry like getting all of ACPI working right), but once installed it gets loaded automagically during boot and you only have to "modprobe ath_pci" right after you install it fresh.
You guys should read the previous posts. And fwiw, with Slackware the
/etc/rc.d/rc.inet1.conf file is all you need to touch. And it's NOT a mess,
unless someone who can't read the massively commented file messes
it up. I've setup quite a number of boxen with wireless, and it's never
been a problem.
And storkus, Fred (assuming you mean Fred Emmott) has nothing to do with
those scripts. Not even in his own distro ... he copies them from Slackware.
The one writing the scripts is Alien Bob, and Pat V. finalizes them.
tar -zxvf madwifi-nr-r3366+ar5007.tar.gz
checkinstall --fstrans=no -S -y
rm -rf madwifi-nr-r3366+ar5007*
I believe that some some cards or systems require this..."special" madwifi version. Regardless anyone with problems try this; may have to set up checkinstall in order to make the packages. BUT IT WORKED!
I have had _some_ success with madwifi and wpa_supplicant, and I'm using a Linksys WPC 100 (Atheros 5416 chipset). It is correct that you'll need the madwifi-trunk-current tarball. There are links on the wiki to Alien Bob's build scripts, and he's tweaked the one for the 'current' branch of madwifi. Build the madwifi, then removepkg wpa_supplicant and reinstall it. Should work, and I've been able to use WPA2 and connect. There _are_ issues with rc.inet1, but mine have involved an on-board ethernet port and whether it was connected or not. But more on that in a later post.
I did that in Slackware 12.0 and got my wireless card running just fine; however, since I installed 12.1 (first by upgrade and then when I couldn't get wireless up and running by fresh install) I managed to break something and I'm just not sure what I broke!
Relevant bits of config:
# lspci -v
04:02.0 Ethernet controller: Belkin Unknown device 700f (rev 20)
Subsystem: Belkin Unknown device 700f
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at cc00 [size=256]
Memory at dfaffe00 (32-bit, non-prefetchable) [size=512]
Capabilities:  Power Management version 2
Kernel driver in use: ndiswrapper
Ok, so that is my wireless card, for which I had the windows driver working under 12.0 with ndiswrapper, as you can see above, lspci is reporting ndiswrapper is in use.
And there is ndiswrapper reporting that everything is tickety-boo.
# cat /etc/rc.d/rc.inet1.conf
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
# Config information for eth0:
# Config information for eth1:
# Config information for eth2:
# Default gateway IP address:
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
The above is my 12.0 config file and from what I can work out should carry straight over to 12.1 - to make sure there was no craziness going on between rc.inet1 and rc.wireless I have done "# chmod -x rc.wireless"
# cat /etc/wpa_supplicant.conf
# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample
# for many more options that you can use in this file.
# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
# By default, only root (group 0) may use wpa_cli
# WPA protected network, supply your own ESSID and WPAPSK here:
group=CCMP TKIP WEP104 WEP40
# Plaintext connection (no WPA, no IEEE 802.1X),
# nice for hotel/airport types of WiFi network.
As with rc.inet1.conf this is the same as I used for 12.0, I can see nothing that means it should fail on 12.1, so why is it I get this:
# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:46 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
If anyone can please tell me what I've forgotten/missed out it'd be much appreciated!