Updated kmod-madwifi, no wireless now

[defcon3]

Hello:

Minutes ago I updated my system with yum -y update, shutdown and went to my office, where I no longer have my Atheros wireless card listed, nor I can get it. What I noticed is that the update replaced my original /etc/modprobe.conf file and eliminated the
alias ath0 ath_pci
line. However, adding it back did not help at all... I still cannot enable my wireless, which was working perfectly until just an hour ago?! Anyone had this problem who found a solution already?

Regards,

EDIT: This only applies to kernel 2.6.23.1-10, when I revert to my "old" kernel 2.6.22.9-91 all is fine... So, I presume problem lies within the kernel, rather than the module...

[Iron_Mike]

They probalably haven't gotten around to building the new madwifi kernel module for 2.6.23 yet. Give'em a few days.

[leigh123linux]

They probalably haven't gotten around to building the new madwifi kernel module for 2.6.23 yet. Give'em a few days.

They have already done it

http://livna-dl.reloumirrors.net/fed...0.fc7.i686.rpm

[Iron_Mike]

Hello:

Minutes ago I updated my system with yum -y update, shutdown and went to my office, where I no longer have my Atheros wireless card listed, nor I can get it. What I noticed is that the update replaced my original /etc/modprobe.conf file and eliminated the
alias ath0 ath_pci
line. However, adding it back did not help at all... I still cannot enable my wireless, which was working perfectly until just an hour ago?! Anyone had this problem who found a solution already?

Regards,

EDIT: This only applies to kernel 2.6.23.1-10, when I revert to my "old" kernel 2.6.22.9-91 all is fine... So, I presume problem lies within the kernel, rather than the module...

So there you have have it. Check the Livna repo....

[defcon3]

Thank you guys but I have the livna repo added by default, so as soon as I got the new kernel I also received the updated module. Having it does not solve the issue, sorry. Do you need any logs? I am confused as to what to look into...

[Antifreeze]

I updated my kernel to 2.6.23.1-10 as well, and compiled my own kernel modules.

Compile succeeded just fine, and installed properly..

However when I do a modprobe.. I get this.

[root@biohazard ~]# modprobe ath_pci
FATAL: Error inserting ath_pci (/lib/modules/2.6.23.1-10.fc7/extra/madwifi/ath_pci.ko): No such device

When I do a LSPCI I get the following.

[root@biohazard ~]# lspci | grep Atheros
01:05.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
[root@biohazard ~]#

dmesg reports

ath_pci: 0.9.4.5 (0.9.3.3)
kobject_add failed for ath_pci with -EEXIST, don't try to register things with the same name in the same directory.
 [<c04f1393>] kobject_shadow_add+0x159/0x18b
 [<c04f1481>] kobject_register+0x19/0x2d
 [<c0564caa>] bus_add_driver+0x50/0x16d
 [<c04feb5a>] __pci_register_driver+0x48/0x74
 [<f89d0035>] init_ath_pci+0x35/0x57 [ath_pci]
 [<c044a7ef>] sys_init_module+0x1361/0x14a5
 [<c043352b>] proc_dointvec_minmax+0x0/0x45
 [<c040518a>] syscall_call+0x7/0xb
 [<c0610000>] attach_one_algo+0x46/0x64
 =======================
ath_pci: No devices found, driver not installed.

[dereknjeny04]

This is due to ath5k support in the latest version of the kernel. Edit your blacklist file to prevent it from loading.

as root:

vi /etc/modprobe.d/blacklist

add this entry to the blacklist file

blacklist ath5k

save and restart your system.

[defcon3]

Thank you, this worked fine for me.

[Antifreeze]

Worked here as well, thank you very much!

[ww7ba]

What a morning. First, adding ath5k to the blacklist worked. A short time later, a new update arrived for madwifi from livna. After installing the update, I removed ath5k from the blacklist, rebooted the system, and the card still works. Now, I just need to get madwifi to work in Debian 4.0.

[ml115]

Adding blacklist ath5k to /etc/modprobe.d/blacklist did not help. The boot hung up when starting network. I had to power down and restart with 2.6.22.9-91.fc7 kernel.

[philbac]

Hi,

I had the same problem, and also did configure the blacklist described here above.

I'm on a laptop HP Compaq NC4000

[root@fc6 ~]# lspci | grep Atheros
00:09.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

[root@fc6 ~]# uname -r
2.6.23.1-10.fc7

[root@fc6 /]# yum list madwifi
Installed Packages
madwifi.i386 0.9.4-0.1.r2594.fc7 installed

[root@fc6 ~]# modprobe -l | grep ath
/lib/modules/2.6.23.1-10.fc7/kernel/drivers/net/wireless/ath5k/ath5k.ko
/lib/modules/2.6.23.1-10.fc7/kernel/drivers/md/multipath.ko
/lib/modules/2.6.23.1-10.fc7/kernel/drivers/md/dm-multipath.ko
/lib/modules/2.6.23.1-10.fc7/extra/ath_rate_sample.ko
/lib/modules/2.6.23.1-10.fc7/extra/ath_hal.ko
/lib/modules/2.6.23.1-10.fc7/extra/ath_rate_amrr.ko
/lib/modules/2.6.23.1-10.fc7/extra/ath_rate_onoe.ko
/lib/modules/2.6.23.1-10.fc7/extra/ath_pci.ko

[root@fc6 ~]# dmesg | grep ath
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133)
ath_pci: 0.9.4.5 (0.9.4)
ath_pci: switching rfkill capability off
ath_rate_sample: 1.2 (0.9.4)
ath_pci: switching per-packet transmit power control off
device-mapper: multipath: version 1.0.5 loaded
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
ath0: no IPv6 routers present

After a restart it does work !

Philippe

[ml115]

Usually when a new kernel is installed by yum I download a most recent madwifi-ng driver
from http://snapshots.madwifi.org/madwifi-ng and install it.
In case of 2.6.23.1-10.fc7 this did not work using madwifi-ng-r2799-20071030 driver.
Instead I installed madwifi-0.9.4-39_r2756.fc7.i386.rpm, madwifi-devel-0.9.4-39_r2756.fc7.i386.rpm, madwifi-hal-kmdl-2.6.23.1-10.fc7-0.9.4-39_r2756.fc7.i686.rpm, and
madwifi-kmdl-2.6.23.1-10.fc7-0.9.4-39_r2756.fc7.i686.rpm from atrpms repo and this works.

[malcidragon]

If you are having problems I would recommend, the rather drastic measure of
deleting ath5k.ko completely.

find /lib/modules/ -name ath5k.ko -exec rm {} \;

Then the madwifi driver (or the ndiswrapper if you must) should work ok

This maybe causing a lot of pain, but at least there is a greater chance of having a working
atheros driver in the kernel sooner - which is good news for everyone!

Cheers,

Malc