Slack 12.1 Atheros Wireless on gbook
I am posting this via an Everex gbook via the eth0 interface. I have installed the Madwifi SlackBuild for 12.1 and but have spent the better part of the day trying to get wireless working
Followed Aliens Directions at Madwifi and tried both editing rc.wireless.conf and rc.inet1.conf. Code:
# Multiband Atheros based 802.11a/b/g universal NIC cards I can scan my access point Code:
Cell 05 - Address: 00:1A:70:D1:4B:E9 My lspci Code:
bash-3.1# lspci (the video settings required the openchrome driver and modeline in xorg.conf) Any advice appreciated. |
Why do you say your wireless doesn't work?
Please post the output of: Code:
iwconfig ath0 |
You need the madwifi drivers for Atheros to get it working (at least on my machine it is that way). Checkout www.madwifi.org
|
Bruce
I am unable to ping google and when I attemp to start a browser it is unable to connect My lsmod Code:
bash-3.1$ lsmod | grep -i ath Code:
bash-3.1$ cat /etc/resolv.conf Code:
bash-3.1# iwconfig ath0 |
shepper,
Use code tags instead of quotes for command output, and you'll get rid of those smileys and format the output nicer. Can you post the output of "ping -c2 www.google.com" and "ifconfig -a" ? What do you get for "host www.google.com 4.2.2.1" ? |
ifconfig -a
Code:
bash-3.1# ifconfig -a Code:
bash-3.1# ping -c2 www.google.com No smiley's this time:D |
You will have to stop eth0 and start ath0 for us to help you,
because you're not posting output of your ath0. You can start ath0 at the same time eth0 is running ... Also you should post the output of /etc/rc.d/rc.inet1.conf and /etc/rc.d/rc.wireless.conf |
The edited portion of my rc.wireless.conf is in the first post but if you need the whole thing. As mentioned earlier I tried the configuration settings in both rc.wireless.conf and rc.inet1.conf. I will post the results of iwconfig ath0 and ifconfig -a shortly
Code:
# Wireless LAN adapter configuration # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support 00:60:1D:*|00:02:2D:*) INFO="Wavelan IEEE example (Lucent default settings)" ESSID="Wavelan Network" MODE="Managed" #RATE="auto" KEY="s:secu1" # To set all four keys, use : #KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]" # For the RG 1000 Residential Gateway: The ESSID is the identifier on # the unit, and the default key is the last 5 digits of the same. #ESSID="084d70" #KEY="s:84d70" ;; My rc.inet1.conf Code:
# /etc/rc.d/rc.inet1.conf |
He is what I get with the nic (eth0) unplugged and trying to connect via ath0. I have another FreeBSD box running fine on wireless as I write this.
Code:
bash-3.1# ping www.google.com |
Looking at your "ifconfig -a" output you dont have an IP configured for your wireless card, there inlies the major problem.
I noticed in your "rc.inet1.conf" you dont have anything edited...? You should uncomment and edit the lines you need for your connection. For example: Code:
# Default gateway IP address: |
Also in your "rc.wireless.conf" file you could try the <catch all> setting to test for simplicity sake, althought by the output of your "iwconfig" your card is associating with the ESSID correctly from your input in the "rc.wireless.conf" file.
Code:
## --------- START SECTION TO REMOVE ----------- |
Alstare
Thanks for the reply. My configs were to use dhcp but they did not automatically obtain the address. Later on in the log I posted I ran dhcpcd manually and did get an IP (192.168.1.7) but it would not ping google or my wireless router (192.168.1.1) I just finished trying Windows and it does run so I have ruled out a hardware issue. Of course putting windows on blew away my Slackware install so I will have to reinstall after some more research. Of the many things I tried an updated kernel as my dmesg would always show a memory leak and a disable IRQ. Kernel 2.6.25.2 now has an atheros driver (ath5k) that is supposed to be 100% FOSS. |
If you wanted to use DHCP to automatically configure your IP for your wireless, you will have to uncomment the DHCP related lines to make them work.
The "rc.inet1.conf" you posted still had them commented <# in front of the line> so that would definitly cause an issue with it trying to get an IP automatically. When you ran DHCPD manually it gave you an IP which is good news, but I suspect your connection problems still were partially attributed to having no gateway listed in the "rc.inet1.conf" file, as I am not sure if that gets updated via dhcp. So I'd suggest when you get your machine back up and running, un-comment the dhcp lines and add a gateway IP to the "rc.inet1.conf" file. And configure the "rc.wireless.conf" file as you had it as it seemed ok and was getting an essid. You also may want to temporarily disable the encryption on your router well trying to get everything working, might help rule out some connection and IP problems. Good luck and have fun. |
Ooops, double post...
|
Thanks Alstare
The second time around I left everything stock with the generic-smp kernel and got the wireless connection up before doing anything else. The Via C7 processor is relatively new and my unfamiliarity with it may have been part of the problem. I have some older C3 systems that ran great with a C3 stripped and optimized kernel. I remember reading somewhere in the Documentation that an SMP kernel is recommended even for non-smp processors as some devices may require it. Previously madwifi ran fine on my non-SMP C3 systems. |
All times are GMT -5. The time now is 07:41 AM. |