Madwifi + 2.6.16-1.2133_FC5 update = HELP!

[figgles]

All,

I recently upgraded my kernel via yum to 2.6.16-1.2133_FC5. I also updated my madwifi drivers. My usual procedure is:

1. Uninstall madwifi
2. Update kernel (only using fedora core repositories!)
3. Install madwifi from atrpms

and this process has been working for me... until now. I don't see the ath0 device in the system-config-network dialog. The Hardware tabs shows a "Atheros COmmuncications" device at wifi0 that is "ok"

Help!

[Kobnar]

Ive got the same problem... sorry I can't help

[figgles]

Hmmm... for what it's worth... iwconfig reports on a device at ath0 but it doesn't show in the network config utility. Normally, running the add device wizard would show an atheros device, but not after the 2133 update.

[nuttygraphics]

I would say my situation is the same.
I have not yet managed to make it run, but I think I know how to deal with the new wifi0 naming.
The first problem for me was, that using the wifi0 hardware, I could only make an ethernet device. But By altering the file /etc/sysconfig/network-scripts/ifcfg-wifi0 that is created for this device and switching the type from ethernet to Wireless, I at least had the option to set the wireless related stuff in the system-config-network gui.
I also changed the name ifcfg-wifi0 to ifcfg-ath0 to get the old name back.

But be careful, I am not really sure what I am doing here...

Ingo

[pjfg]

Any reason why you can't use the madwifi driver from livna instead of atrpms? Livna works with kernel 2.6.16-1.2133_FC5.

[nuttygraphics]

I can see no difference so far, I just followed your advice and removed madwifi and reinstalled it from livna. yum also updated the kernel and removed the nvidia driver.
No I have no gl and no wireless.
Is there any reasy why I should use livna?

[figgles]

...But By altering the file /etc/sysconfig/network-scripts/ifcfg-wifi0 that is created for this device and switching the type from ethernet to Wireless, I at least had the option to set the wireless related stuff in the system-config-network gui...
I appreciate reading from others on this issue. I've posted at the madwifi gmane newsgroup, but there is little response.
If you follow the madwifi RedHat/FedoraCore instructions for aliasing your reference to ath_pci, you'll be able to setup a wireless card in the system-config-network control panel. It's just that I can't connect, as I used to be able to.

FWIW; I did try the livna respository, but without success.

[pjfg]

You will need this in /etc/modprobe.conf:

alias wifi0 ath_pci
alias ath0 ath_pci
options ath_pci autocreate=sta

Without the third line you will have no wireless interface - the OS instead will see only a standard wired ethernet interface.

Madwifi causes a lot of problems for many users, not least because madwifi changed the whole driver model from madwifi to madwifi_ng (next generation) some time ago which results in confusion about which procedures to use. I mentioned trying the livna driver as I know that they use madwifi_ng (which I know to work) whilst I used to have problems with atrpms; I haven't looked at the driver from atrpms in some time so I'm unsure if it is 'ng' or not.

[figgles]

You will need this in /etc/modprobe.conf:

alias wifi0 ath_pci
alias ath0 ath_pci
options ath_pci autocreate=staYep -- it's there, but thanks.

Madwifi causes a lot of problems for many users, not least because madwifi changed the whole driver model from madwifi to madwifi_ng (next generation) some time ago which results in confusion about which procedures to use. I mentioned trying the livna driver as I know that they use madwifi_ng (which I know to work) whilst I used to have problems with atrpms; I haven't looked at the driver from atrpms in some time so I'm unsure if it is 'ng' or not.I uninstalled the atrpms drivers, configured my yum to use livna as per their instructions, and installed madwifi from there. I still can not connect. dmesg only shows "ath0: no IPv6 routers present" (I have toggled "Enable IPv6 for this interface" neither with a positive result) Is there another log file where I can see what's going on?

[pjfg]

Do you have a directory called /proc/sys/net/ipv6 ?

Also, could you post the contents of /etc/sysconfig/networking/devices/ifcfg-ath0

[figgles]

Do you have a directory called /proc/sys/net/ipv6 ?Yes
Also, could you post the contents of /etc/sysconfig/networking/devices/ifcfg-ath0# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=no
USERCTL=yes
IPV6INIT=no
PEERDNS=yes
TYPE=Wireless
DEVICE=ath0
HWADDR=00:0d:88:82:08:32
BOOTPROTO=none
NETMASK=255.255.255.0
DHCP_HOSTNAME=
IPADDR=10.0.1.20
DOMAIN=
ESSID=Fithies
CHANNEL=1
MODE=Auto
RATE=Auto
GATEWAY=10.0.1.1

[pjfg]

Your ifcfg-ath0 looks ok. I'd suggest turning off ipv6 unless you specifically need it. I think you need "alias net-pf-10 off" in /etc/modprobe.conf and reboot. The /proc/sys/net/ipv6 should then dissapear. Now see if you wireless interface works.

[figgles]

Your ifcfg-ath0 looks ok. I'd suggest turning off ipv6 unless you specifically need it.I don't need it; IPv6 is off.I think you need "alias net-pf-10 off" in /etc/modprobe.conf and reboot. The /proc/sys/net/ipv6 should then dissapear. Now see if you wireless interface works.I added the alias and rebooted. The IPv6 dirtectory is gone with an IPv4 directory now there.
I'm still not able to connect.

[pjfg]

Can you be more specific about not able to connect? Are you using the gui to start the interfaces? If so try running "service network restart" or "ifconfig ath0 up" from the shell. Any information in /var/log/messages? Lastly, what does "iwconfig ath0" tell you?

[kusanagi533d]

i experianced the same problems,
the wireless card shows up as a regular wired ethernet card with wifi0 as its device name
another thing i noticed is that when you add a new device or a new hardware
it dosent show the correct card connected for me...ie my netgear WG311t
the funny thing is that when you probe the mac it shous it as being there
...i dunno if this is a fedora problem or a madwifi problem but it sure is annoying

[figgles]

Can you be more specific about not able to connect? Are you using the gui to start the interfaces? If so try running "service network restart" or "ifconfig ath0 up" from the shell. I am using the GUI (system-config-network) to start the interface.

Running /sbin/service network restart:Shutting down interface ath0: [ OK ]
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... done.
[ OK ]entering ifconfig ath0 up causes the wireless cards to light in the same way that using the GUI does -- but without a connection.Any information in /var/log/messages?Here is a partial result from /var/log/messages:Jul 8 18:45:33 localhost dhclient: wifi0: unknown hardware address type 801
Jul 8 18:45:33 localhost dhclient: wifi0: unknown hardware address type 801
Jul 8 18:45:33 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 8 18:45:33 localhost dhclient: DHCPACK from 10.0.1.1
Jul 8 18:45:33 localhost avahi-daemon[2037]: New relevant interface eth0.IPv4 for mDNS.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.6.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Registering new address record for 10.0.1.6 on eth0.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Withdrawing address record for 10.0.1.6 on eth0.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.6.
Jul 8 18:45:33 localhost avahi-daemon[2037]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Interface eth0.IPv4 no longer relevant for mDNS.
Jul 8 18:45:33 localhost avahi-daemon[2037]: New relevant interface eth0.IPv4 for mDNS.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.6.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Registering new address record for 10.0.1.6 on eth0.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Withdrawing address record for 10.0.1.6 on eth0.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.6.
Jul 8 18:45:33 localhost avahi-daemon[2037]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Interface eth0.IPv4 no longer relevant for mDNS.
Jul 8 18:45:33 localhost avahi-daemon[2037]: New relevant interface eth0.IPv4 for mDNS.
Jul 8 18:45:33 localhost NET[5729]: /sbin/dhclient-script : updated /etc/resolv.conf
Jul 8 18:45:33 localhost avahi-daemon[2037]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.6.
Jul 8 18:45:33 localhost dhclient: bound to 10.0.1.6 -- renewal in 1601 seconds.
Jul 8 18:45:33 localhost avahi-daemon[2037]: Registering new address record for 10.0.1.6 on eth0.
Jul 8 18:45:33 localhost NET[5770]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
Lastly, what does "iwconfig ath0" tell you?[toot@localhost fithies]# /sbin/iwconfig ath0
Warning: Driver for device ath0 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...

ath0 IEEE 802.11g ESSID:"fithies" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:17 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:6A33-7375-73 Security mode:restricted
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Thanks for all your help so far!

[pjfg]

Your wireless card is not associated with your access point. Try "iwconfig ath0 ap mac-address-of-ap". Get the mac from "iwlist scan". Then try "dhclient ath0" to see if you can get a dhcp lease.

[Kobnar]

Ok so I don't really know if this will work but I had a similar problem... I posted my solution on another thread so here it should be: Then I ran "system-config-network" and set up my "wifi0" device up (recognized it as an ethernet connection for some reason but the device was still called "wifi0").

Then I edited "/etc/modprobe.conf" and added "alias wifi0 ath_pci" to the end of the file (remembering to keep an empty line at the end). This last part was because my Atheros cards was actually operating as the device "ath0" but it couldn't be used unless they were linked to wifi0 (atleast that's my understanding).

Err I hope that might help...

[figgles]

Your wireless card is not associated with your access point. Try "iwconfig ath0 ap mac-address-of-ap". Get the mac from "iwlist scan". Then try "dhclient ath0" to see if you can get a dhcp lease.That's the rub. It won't connect. I ran the commands you suggested. Here what I got:
[toot@localhost fithies]# /sbin/iwconfig ath0 ap 0 <ap-address-from-iwlist-scan>
[toot@localhost fithies]# /sbin/dhclient ath0
Internet Systems Consortium DHCP Client V3.0.3-RedHat
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:0d:88:82:08:32
Sending on LPF/ath0/00:0d:88:82:08:32
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

My message log says:
Jul 11 21:23:16 localhost avahi-daemon[2058]: Registering new address record for 10.0.1.6 on eth0.
Jul 11 21:23:16 localhost NET[4158]: /sbin/dhclient-script : updated /etc/resolv.conf
Jul 11 21:23:16 localhost dhclient: bound to 10.0.1.6 -- renewal in 5271 seconds.
Jul 11 21:26:58 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
Jul 11 21:26:58 localhost dhclient: send_packet: Network is down
Jul 11 21:27:01 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
Jul 11 21:27:01 localhost dhclient: send_packet: Network is down
Jul 11 21:27:08 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
Jul 11 21:27:08 localhost dhclient: send_packet: Network is down
Jul 11 21:27:22 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 21
Jul 11 21:27:22 localhost dhclient: send_packet: Network is down
Jul 11 21:27:43 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
Jul 11 21:27:43 localhost dhclient: send_packet: Network is down
Jul 11 21:27:50 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
Jul 11 21:27:50 localhost dhclient: send_packet: Network is down
Jul 11 21:27:59 localhost dhclient: No DHCPOFFERS received.

[pjfg]

After you run "iwconfig ath0 ap mac-address-of-ap" what does "iwconfig ath0" tell you? Is it now associated? Has "Access Point: Not-Associated" changed to something else? Or perhaps you encryption key is wrong. Without the correct key or association with an access point your will never receive an address lease.

There could be problems on three levels here:

1. You wireless card is somehow misconfigured at the hardware/driver level
2. You wireless card is not joining the correct wireless network
3. You have a network misconfiguration

Obviously, each stage depends on the preceding step working. I'm assuming all is well with step 1 as you seem to be able to run commands such as "iwlist scan" or "iwconfig ath0" and get sensible results. So that leaves a problem at stage 2.

[Kobnar]

Yeah I had this problem too.

Have you tried my suggestion? Try setting it up as "wifi0" with "system-config-network" then link it in "/etc/modprobe.conf" with "alias wifi0 ath_pci" at the end. All of your wireless commands will still show that it is connected to "ath0" but it should work correctly.

[figgles]

After you run "iwconfig ath0 ap mac-address-of-ap" what does "iwconfig ath0" tell you? Is it now associated? Has "Access Point: Not-Associated" changed to something else? Or perhaps you encryption key is wrong. Without the correct key or association with an access point your will never receive an address lease.I greatly appreciate your sticking with me on this annoying problem. The system never reports that the card associates with the AP. I do have a "junkyard" network of old hetergenious computers that reliably connect to the said Apple Snow Airport Basestation, as this once great laptop *used* too... (sniff...)There could be problems on three levels here:

1. You wireless card is somehow misconfigured at the hardware/driver levelI can't rule that out2. You wireless card is not joining the correct wireless networkWe have plenty of evidence of that problem.3. You have a network misconfigurationLikewiseObviously, each stage depends on the preceding step working. I'm assuming all is well with step 1 as you seem to be able to run commands such as "iwlist scan" or "iwconfig ath0" and get sensible results. So that leaves a problem at stage 2.Well, I didn't get to finish this post, as I loaded the DWL-G650 on my Windows laptop, loaded the drivers, and rebooted the system. I did so to confirm the card works fine -- and it does.

[pjfg]

I'm running out of ideas :)

I posted on another madwifi thread recently. Not the same issue but perhaps you could take a look anyway - I include a full working config: http://forums.fedoraforum.org/showthread.php?t=112716

You could also try adding ath_debug to your ath_pci options in /etc/modprobe.conf. Perhaps this would debug the association issue. This is the output from modinfo madwifi:

parm: ath_debug:Load-time debug output enable (int)
parm: autocreate:Create ath device in [sta|ap|wds|adhoc|ahdemo|monitor] mode. defaults to sta, use 'none' to disable (charp)
parm: rfkill:Enable/disable RFKILL capability (int)
parm: xchanmode:Enable/disable extended channel mode (int)
parm: outdoor:Enable/disable outdoor use (int)
parm: countrycode:Override default country code (int)

Also, have you tried using NetworkManager? I've never had much luck with NM and madwifi but YMMV.

[figgles]

Yeah I had this problem too.

Have you tried my suggestion? Try setting it up as "wifi0" with "system-config-network" then link it in "/etc/modprobe.conf" with "alias wifi0 ath_pci" at the end. All of your wireless commands will still show that it is connected to "ath0" but it should work correctly.I *thought* I had, but tonight I'm going to follow the above instruction literally. I have the alias to wifi0 instruction in my modprobe.conf file, but not as the last instruction, if order counts? I look forward to giving it shot -- thanks!

[figgles]

I *thought* I had, but tonight I'm going to follow the above instruction literally. I have the alias to wifi0 instruction in my modprobe.conf file, but not as the last instruction, if order counts? I look forward to giving it shot -- thanks!Follow-up: didn't help any but I profoundly appreciate your suggestion. I'm trying the debug option next.

[figgles]

I'm running out of ideas :)But I remain deeply appreciative of your help.You could also try adding ath_debug to your ath_pci options in /etc/modprobe.conf. Perhaps this would debug the association issue.Sorry to be so dense, but I couldn't find reference on how to exactly construct that line in my modprobe.conf file. Would you kindly show me how to form that instruction?Also, have you tried using NetworkManager? I've never had much luck with NM and madwifi but YMMV.I'm giving that a try now -- thanks.

[pjfg]

Sorry to be so dense, but I couldn't find reference on how to exactly construct that line in my modprobe.conf file. Would you kindly show me how to form that instruction?I'm giving that a try now -- thanks.

I'm guessing something like:

options ath_pci autocreate=sta,ath_debug=1

I've never used the option for debug before so that may not be right, but the manpage suggests it uses an integer as the switch. Debug ooutput should go to the console device and/or /var/log/messages.

[figgles]

options ath_pci autocreate=sta,ath_debug=1/var/log/messages nor modinfo madwifi show any debug (or additional info, based on the options string. In fact, /sbin/modinfo madwifi returns:"Cannot find module madwifi" If I were a rich man, I'd simply buy a compatible card right about now -- but I'm not.

[pjfg]

/var/log/messages nor modinfo madwifi show any debug (or additional info, based on the options string. In fact, /sbin/modinfo madwifi returns:"Cannot find module madwifi" If I were a rich man, I'd simply buy a compatible card right about now -- but I'm not.

That's because the correct command is "modinfo ath_pci" ;) Sorry, that was my mistake.

As for the debug, try entering it without the comma, eg: options ath_pci autocreate=sta ath_debug=1

Like I said, I've never passed multiple options to a module through modprobe.conf before so I'm unsure what the delimeter is.

If all else fails, perhaps you should review this: http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

[figgles]

That's because the correct command is "modinfo ath_pci" ;) Sorry, that was my mistake.No apologizes necessary.As for the debug, try entering it without the comma, eg: options ath_pci autocreate=sta ath_debug=1Actually, the inclusion of the ath_debug string appears to work, now that I'm using the correct module call to modinfo. Here's the code:parm: ath_debug:Load-time debug output enable (int)
parm: autocreate:Create ath device in [sta|ap|wds|adhoc|ahdemo|monitor] mode. defaults to sta, use 'none' to disable (charp)
parm: rfkill:Enable/disable RFKILL capability (int)
parm: xchanmode:Enable/disable extended channel mode (int)
parm: outdoor:Enable/disable outdoor use (int)
parm: countrycode:Override default country code (int)
If all else fails, perhaps you should review this: http://madwifi.org/wiki/UserDocs/FirstTimeHowToThat is actually where started my reading and troubleshooting before I posted to FedoraForum. Again, I greatly appreciate your help on this.

[figgles]

Using unorthodox procedures, I got my card working... I installed SuSE 10.1. I can now connect to a linksys router but not my Apple Snow Airport basestation. Jeeze-Louise...