Le (on) Thursday 04 September 2008 02:40, Celejar a écrit (wrote) :
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> This line generally appears when the card comes on-line; if all goes well,
> it should soon be followed by something like 'ADDRCONF(NETDEV_CHANGE):
> eth0: link becomes ready'
>
Well, the whole point is, it isn't followed by any "link becomes ready"
message (unless I modprobe -r ath9k && modprobe ath9k, which is a pain).
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> eth0: direct probe to AP 00:17:5a:4f:31:c0 try 1
> eth0 direct probe responded
> eth0: authenticate with AP 00:17:5a:4f:31:c0
> eth0: authenticated
> eth0: associate with AP 00:17:5a:4f:31:c0
> eth0: RX AssocResp from 00:17:5a:4f:31:c0 (capab=0x401 status=0 aid=53)
> eth0: associated
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
It's exactly what happens on my box /after/ I removed and reprobed the
driver, and what I would like to happen automatically.
> I'm not much of an expert, but here are a couple of suggestions:
>
> Try disabling WEP, and see if the problem persists.
It does.
> Try configuring the interface manually, without DHCP:
> ifconfig wlan0 up
> iwconfig wlan0 essid xxxxxxxx
> ifconfig wlan0 x.x.x.x
>
I tried. I doesn't change anything. The chip remains "non associated" to any
AP, and the only things I can see in syslog is the above mentionned "links
is not ready" message when I try tu use dhclient. Static IP configuration
doesn't work either.
Unless somebody comes with an idea about what I'm doing, I'll assume this is
a problem with the driver and report on ath9k-devel.
Thanks for your suggestions,
Manuel.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-08-2008, 04:33 PM
"Kevin Mitchell"
problems with madwifi and Atheros AR5418
The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60
AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Here
are instructions for compiling the kernel in Debian:
http://www.thinkwiki.org/wiki/How_to_install_the_development_version_of_atk9k.
There is also someone on Ubuntu forums who has created a script to
compile the module for pre 2.6.27 kernels and stick it in a .deb
package for you. I have found this be compatible with Debian, though I
haven't tried out his latest version
http://ubuntuforums.org/showpost.php?p=5535562&postcount=3.
I used to use madwifi and didn't experience the kind of problems you
speak of. I did however notice that somewhere along the way, there was
a regression that slowed down the connection by a non negligible
amount http://madwifi.org/ticket/2043. You might try downloading 3401
snapshot (I think you use the "-r 3401" as an argument to svn). I had
meant to pinpoint exactly when and where this regression occured, but
then ath9k came out and there was an exponential decay in my caring
coefficient.
Kevin
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-08-2008, 04:49 PM
Manuel Pégourié-Gonnard
problems with madwifi and Atheros AR5418
Kevin Mitchell a écrit :
> The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60
> AR5418. I'm even creeping past 11g speeds (25MB/s on a good day).
Wow. Here I can't do tests since my only other local machine has slow
wifi, but yes, ath9k form 2.6.27-rc5 works fine too (except that that
card won't reconnect to the AP if it goes down then up unless I reload
the driver... fortunately, my AP doens't go down that often).
> I used to use madwifi and didn't experience the kind of problems you
> speak of. I did however notice that somewhere along the way, there was
> a regression that slowed down the connection by a non negligible
> amount http://madwifi.org/ticket/2043. You might try downloading 3401
> snapshot (I think you use the "-r 3401" as an argument to svn). I had
> meant to pinpoint exactly when and where this regression occured, but
> then ath9k came out and there was an exponential decay in my caring
> coefficient.
>
Well, since ath9k is working well, I don't think I'll try to go back to
madwifi. Now the only drawback is, module-assistant doesn't succed any
more in building modules: I'm under the impression it tries to use the
2.6.26 headers...
Manuel.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-08-2008, 05:02 PM
"Kevin Mitchell"
problems with madwifi and Atheros AR5418
Sorry if I used the wrong notation, that was 25 Mbits/s ~ 3.2 Mbytes/s
which is only slightly faster that 11g so it's not that "wow", but an
improvement nonetheless.
What modules is module assistant trying to build? The headers
shouldn't be a problem. If you've compiled your own kernel, just make
sure to keep the source tree from the compile (that means don't "make
clean" it too). I did however notice a few things weren't yet bleeding
edge enough for the new kernel. A common problem is that the
asm/semaphore.h header is now at linux/semaphore.h. If you take a look
in your source files and switch that around, things might work. For
example, see this bug on tp_ctrl:
http://sourceforge.net/tracker/index.php?func=detail&aid=2041469&group_id=1212&at id=101212
Kevin
On Mon, Sep 8, 2008 at 9:49 AM, Manuel Pégourié-Gonnard <mpg@elzevir.fr> wrote:
> Kevin Mitchell a écrit :
>> The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60
>> AR5418. I'm even creeping past 11g speeds (25MB/s on a good day).
>
> Wow. Here I can't do tests since my only other local machine has slow
> wifi, but yes, ath9k form 2.6.27-rc5 works fine too (except that that
> card won't reconnect to the AP if it goes down then up unless I reload
> the driver... fortunately, my AP doens't go down that often).
>
>> I used to use madwifi and didn't experience the kind of problems you
>> speak of. I did however notice that somewhere along the way, there was
>> a regression that slowed down the connection by a non negligible
>> amount http://madwifi.org/ticket/2043. You might try downloading 3401
>> snapshot (I think you use the "-r 3401" as an argument to svn). I had
>> meant to pinpoint exactly when and where this regression occured, but
>> then ath9k came out and there was an exponential decay in my caring
>> coefficient.
>>
> Well, since ath9k is working well, I don't think I'll try to go back to
> madwifi. Now the only drawback is, module-assistant doesn't succed any
> more in building modules: I'm under the impression it tries to use the
> 2.6.26 headers...
>
> Manuel.
>
>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-08-2008, 05:21 PM
Manuel Pégourié-Gonnard
problems with madwifi and Atheros AR5418
Kevin Mitchell a écrit :
> Sorry if I used the wrong notation, that was 25 Mbits/s ~ 3.2 Mbytes/s
> which is only slightly faster that 11g so it's not that "wow", but an
> improvement nonetheless.
>
Well, even if the improvement is not great, it's an improvement. So it's
cool given that my basic problem was just to get the thing working at all.
> What modules is module assistant trying to build?
Alsa and virtualbox-ose. I tried with alsa-source from sid as well as
from testing, and virtualbox-ose-source only from testing (I'm basically
running testing except when I *need* bleeding edge versions).
> The headers
> shouldn't be a problem. If you've compiled your own kernel, just make
> sure to keep the source tree from the compile (that means don't "make
> clean" it too).
Yes, actually it's ok. I forgot to rename the 2.6.26 directory to
2.6.27-rc5 after patching it, so that's why I thought it was using the
wrong headers.
> I did however notice a few things weren't yet bleeding
> edge enough for the new kernel. A common problem is that the
> asm/semaphore.h header is now at linux/semaphore.h. If you take a look
> in your source files and switch that around, things might work. For
> example, see this bug on tp_ctrl:
> http://sourceforge.net/tracker/index.php?func=detail&aid=2041469&group_id=1212&at id=101212
>
Oh yes, exactly. I had this problem while trying to compile the modules
for virtualbox. Would a symlink be fine to make sure everyone can find
semaphore.h where it expects it?
Thanks,
Manuel.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-10-2008, 05:16 PM
"Kevin Mitchell"
problems with madwifi and Atheros AR5418
I would suggest reporting this to the ath9k-devel list:
https://lists.ath9k.org/mailman/listinfo/ath9k-devel especially if it
is reproducible.
Kevin
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-18-2008, 07:06 PM
"Kevin Mitchell"
problems with madwifi and Atheros AR5418
When you run dhclient without arguments, it tries to get an ip address
on any of the interfaces listed with /sbin/ifconfig minus the lo
interface. If you take a look at that output with the ath9k module
loaded, you'll see a "wmaster0" interface. My understanding is that
this is a kind of abstraction layer from which the wlan0 interface is
created. Thus, trying to get an ip address directly on it doesn't
work. Of course wlan0 should get an ip just fine provided your
associated to an AP with dhcp. If that message disturbs you, you could
try runnning "dhclient wlan0" so that it only tries to get an address
on wlan0 which is all you really want anyway.
Kevin
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> When you run dhclient without arguments, it tries to get an ip address
> on any of the interfaces listed with /sbin/ifconfig minus the lo
> interface. If you take a look at that output with the ath9k module
> loaded, you'll see a "wmaster0" interface. My understanding is that
> this is a kind of abstraction layer from which the wlan0 interface is
> created. Thus, trying to get an ip address directly on it doesn't
> work. Of course wlan0 should get an ip just fine provided your
> associated to an AP with dhcp. If that message disturbs you, you could
> try runnning "dhclient wlan0" so that it only tries to get an address
> on wlan0 which is all you really want anyway.
> Kevin
Thanks. I understood what you have explained; my perplexity concerns
the fact that even when dhclient is called on the actual interface
(wlan0, or eth0 as renamed by udev), not on wmaster0, I still get those
warnings.
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-18-2008, 09:51 PM
"Kevin Mitchell"
problems with madwifi and Atheros AR5418
Oh, you're right, I guess I didn't notice that before. In any case, it
doesn't appear to cause any problems for me either. It's just an
annoying error message.
Kevin
On Thu, Sep 18, 2008 at 12:42 PM, Celejar <celejar@gmail.com> wrote:
> On Thu, 18 Sep 2008 12:06:10 -0700
> "Kevin Mitchell" <kevmitch@gmail.com> wrote:
>
>> When you run dhclient without arguments, it tries to get an ip address
>> on any of the interfaces listed with /sbin/ifconfig minus the lo
>> interface. If you take a look at that output with the ath9k module
>> loaded, you'll see a "wmaster0" interface. My understanding is that
>> this is a kind of abstraction layer from which the wlan0 interface is
>> created. Thus, trying to get an ip address directly on it doesn't
>> work. Of course wlan0 should get an ip just fine provided your
>> associated to an AP with dhcp. If that message disturbs you, you could
>> try runnning "dhclient wlan0" so that it only tries to get an address
>> on wlan0 which is all you really want anyway.
>> Kevin
>
> Thanks. I understood what you have explained; my perplexity concerns
> the fact that even when dhclient is called on the actual interface
> (wlan0, or eth0 as renamed by udev), not on wmaster0, I still get those
> warnings.
>
> Celejar
> --
> mailmin.sourceforge.net - remote access via secure (OpenPGP) email
> ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
>
>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
09-22-2008, 12:44 AM
Michelle Konzack
problems with madwifi and Atheros AR5418
Am 2008-09-08 09:33:46, schrieb Kevin Mitchell:
> The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60
> AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Here
25 MByte or 25 MBit?
If you mean the first one, you are a liar...
If you mean the second one, you have a crapy AP.
I get on with the Chipset arround 43 MBit/Sec.
But I prefer the 11a stuff, since my AP "Proxim Tsunami MP.11a" with my
i.MX31 (using the new Maxim MAX2829; much cheaper as the Atheros Chip)
give me over 47 MBit. And of course, I get it in a distance of more
then 1500m on a good day or 900m if a hurican blows over Strasbourg.
problems with madwifi and Atheros AR5418
