| View previous topic :: View next topic |
| Author |
Message |
tknd n00b

Joined: 30 Jul 2005 Posts: 7
|
Posted: Sat Jun 24, 2006 11:40 pm Post subject: madwifi-ng kernel panic |
|
|
I'm getting the following when attempting to do a modprobe ath_pci on the new madwifi-ng driver:
| Code: | kernel panic not syncing ifmedia_set
|
Some info on my system:
| Code: | # uname -a
Linux serv 2.6.16-gentoo-r9 #1 SMP Sat Jun 24 13:27:33 PDT 2006 x86_64 AMD Athlon(tm) 64 Processor 3000+ GNU/Linux
# lspci | grep Atheros
00:0c.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
# grep CONFIG_CRYPTO /usr/src/linux/.config
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_MICHAEL_MIC=y
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set
# grep CONFIG_SYSCTL /usr/src/linux/.config
CONFIG_SYSCTL=y
# grep CONFIG_NET_RADIO /usr/src/linux/.config
CONFIG_NET_RADIO=y
|
The last three grep are for kernel features required by the madwifi driver. I have attempted unmerging and remerging the driver.
On a side note, module-rebuild is still reporting the old madwifi driver somehow:
| Code: | # module-rebuild list
** Packages which I will emerge are:
=net-wireless/madwifi-driver-0.1_pre20050420
=media-sound/alsa-driver-1.0.11
|
I don't know if I can fix that in module-rebuild. The reason why I needed to upgrade the madwifi was I did a compiler upgrade (followed the compiler upgrade guide) followed by a kernel upgrade (followed the kernel upgrade guide). I've remerged both madwifi and alsa and only alsa has successfully worked while madwifi still kernel panics.
I've tried both the marked stable version of the madwifi-ng as well as the latest ~amd64 masked version with the same kernel panic.
I'm guessing there's just one thing that's screwing things up but I don't have any good ideas on where it is. Everything was working on the very old driver (which no longer is supported by gentoo) minus a few annoying bugs in the driver itself. |
|
| Back to top |
|
 |
dkostic Apprentice


Joined: 24 May 2006 Posts: 220 Location: Madison, NJ
|
Posted: Sun Jun 25, 2006 2:31 am Post subject: |
|
|
This...
http://madwifi.org/ticket/615
...looks like the bug you might be encountering. There's a patch to fix it here...
http://madwifi.org/changeset/1604
I hope this helps! _________________ Toshiba Satellite A105 laptop, 1.7 mHz Celeron M, 100 Gb hard disk, 512 Mb RAM, 2006.0, 2.6.16-r7 kernel
Homemade desktop, 3.2+ mHz AMD Athlon 64 processor, 120 Gb hard disk, 1 Gb RAM, 2005.0, 2.6.14-r2 kernel |
|
| Back to top |
|
 |
tknd n00b

Joined: 30 Jul 2005 Posts: 7
|
Posted: Sun Jun 25, 2006 4:23 am Post subject: |
|
|
Instead of using the ebuilds in portage I went ahead and downloaded the current revision (trunk 1650) from the madwifi SVN by following the download instructions here:
http://madwifi.org/wiki/UserDocs/GettingMadwifi
You can then follow the first time how to located here:
http://madwifi.org/wiki/UserDocs/FirstTimeHowTo
Of course you will want to make sure your kernel and hardware meets the requirements prior to compiling and installing by checking the for the following page:
http://madwifi.org/wiki/Requirements
It should be noted that if you want to use the card in master mode (as your own access point), that you append to your modprobe the autocreate setting by doing something like:
| Code: | | modprobe ath_pci autocreate=ap |
If you want to use wep encryption, make sure the wlan_wep module is loaded as well:
| Code: | | lsmod | grep wlan_wep |
If not, load it:
From there, you should be able to use the normal gentoo net or wireless scripts to configure the ath0 wireless interface or through using iwconfig at the command line.
Once everything is working as you expect, you can add the modules you loaded with modprobe to /etc/modules.autoload.d/kernel-2.6 by doing something like:
| Code: | echo "ath_pci autocreate=ap" >> /etc/modules.autoload.d/kernel-2.6
echo "wlan_wep" >> /etc/modules.autoload.d/kernel-2.6
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|