| View previous topic :: View next topic |
| Author |
Message |
depontius
Veteran
Joined: 05 May 2004
Posts: 1925
|
 Posted: Mon Apr 09, 2007 4:02 pm Post subject: |
 |
|
Did you double-check to see if your modules loaded? Mine didn't.
ath_pci: Unknown symbol ieee80211_rate_attach
ath_pci: Unknown symbol ieee80211_rate_detach
So in the manner of idiots, I've set ~x86 for gentoo-sources-2.6.20-r5 and will try a new kernel.
Then maybe I'll mask madwifi-ng-0.9.3 if that doesn't work.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
 |
silverwolf
n00b
Joined: 30 Jul 2003
Posts: 48
Location: UK::Cambridgeshire
|
| Posted: Sat Apr 28, 2007 5:31 pm Post subject: |
|
|
| sheriff-jms wrote: | Madwifi 0.9.3-r2 doesn't appear to play nicely with my kernel (2.6.19-r5).
I saw the same problems as other in this thread had reported, i.e. the system wouldn't create an "ath" or "wifi" interface, so net.ath0 wouldn't do anything. Looking in dmesg, I also saw an error about my kernel not supporting automatic module loading, which is not correct. This was making the 'ath_rate_sample' module unhappy.
I rolled back to madwifi 0.9.2.1 and my wireless interface fired right back up.
I guess I'll hold off on upgrading to madwifi 0.9.3 (or newer) until I upgrade to a 2.6.20 (or newer) kernel. |
I have a similar problem running 0.9.3 and linux-2.6.19-gentoo-r5.
How do I roll back to 0.9.2.1 (for example)? I've never been through this process before.
Would appreciate someone's help on how to do this -- thanks. |
|
| Back to top |
|
|
Paczesiowa
Guru
Joined: 06 Mar 2006
Posts: 593
Location: Oborniki Śląskie, Poland
|
| Posted: Sun Apr 29, 2007 10:52 am Post subject: |
|
|
I found solution to this problem I think. 0.9.3 now creates interface. All I did was enabling autoloading of modules in kernel config (before I had static module loading through /etc/modules.autoload.d/kernel-2.6) and now it works. I was loading all needed modules but perhaps I was doing it in wrong order or smth.
If you want revert back to 0.9.2 try this:
add | Code: | >=net-wireless/madwifi-ng-0.9.3
>=net-wireless/madwifi-ng-tools-0.9.3 |
to /etc/portage/package.mask
and | Code: | | emerge madwifi-ng madwifi-ng-tools -vat |
|
|
| Back to top |
|
|
depontius
Veteran
Joined: 05 May 2004
Posts: 1925
|
| Posted: Sun Apr 29, 2007 10:54 am Post subject: |
|
|
| silverwolf wrote: | | sheriff-jms wrote: | Madwifi 0.9.3-r2 doesn't appear to play nicely with my kernel (2.6.19-r5).
I saw the same problems as other in this thread had reported, i.e. the system wouldn't create an "ath" or "wifi" interface, so net.ath0 wouldn't do anything. Looking in dmesg, I also saw an error about my kernel not supporting automatic module loading, which is not correct. This was making the 'ath_rate_sample' module unhappy.
I rolled back to madwifi 0.9.2.1 and my wireless interface fired right back up.
I guess I'll hold off on upgrading to madwifi 0.9.3 (or newer) until I upgrade to a 2.6.20 (or newer) kernel. |
I have a similar problem running 0.9.3 and linux-2.6.19-gentoo-r5.
How do I roll back to 0.9.2.1 (for example)? I've never been through this process before.
Would appreciate someone's help on how to do this -- thanks. |
Either put
| Code: | >=net-wireless/madwifi-ng-0.9.3
>=net-wireless/madwifi-ng-tools-0.9.3 |
into /etc/portage/package.mask or just upgrade to a 2.6.20+ kernel. They've been stable for a bit, already.
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
silverwolf
n00b
Joined: 30 Jul 2003
Posts: 48
Location: UK::Cambridgeshire
|
| Posted: Sun Apr 29, 2007 4:56 pm Post subject: |
|
|
| Quote: | Eiither put
| Code: | >=net-wireless/madwifi-ng-0.9.3
>=net-wireless/madwifi-ng-tools-0.9.3 |
into /etc/portage/package.mask or just upgrade to a 2.6.20+ kernel. They've been stable for a bit, already. |
Thanks for that. I took the first route -- just need to test things now. I daren't upgrade the kernel as I have a pcmcia wireless card that's about to have support withdrawn, and I can't afford to replace it yet. |
|
| Back to top |
|
|
depontius
Veteran
Joined: 05 May 2004
Posts: 1925
|
| Posted: Sun Apr 29, 2007 6:51 pm Post subject: |
|
|
| silverwolf wrote: |
Thanks for that. I took the first route -- just need to test things now. I daren't upgrade the kernel as I have a pcmcia wireless card that's about to have support withdrawn, and I can't afford to replace it yet. |
Linux support being withdrawn, or Windows support? The latter is easy to believe, the former is a bit surprising. What card?
_________________
.sigs waste space and bandwidth |
|
| Back to top |
|
|
silverwolf
n00b
Joined: 30 Jul 2003
Posts: 48
Location: UK::Cambridgeshire
|
| Posted: Sun Apr 29, 2007 7:56 pm Post subject: |
|
|
| Quote: | | Linux support being withdrawn, or Windows support? The latter is easy to believe, the former is a bit surprising. What card? |
I'm being a little sloppy -- apologies. After booting, dmesg tells me the following:
| Code: | pcmcia: Detected deprecated PCMCIA ioctl usage from process: cardmgr.
pcmcia: This interface will soon be removed from the kernel; please expect break
age unless you upgrade to new tools. |
Maybe I took the word "interface" the wrong way. Reading it through, I need to do something else. But the hardware is not the problem. Unintentional flame -- my bad. |
|
| Back to top |
|
|
|
Networking & Security
