Hello, Brian!
On Thu, 2005-08-04 at 21:39 +0200, Brian Schau wrote:
[snip]
> I don't know what kind of debug messages to send. I have attached:
>
> - dmesg in 2.6.11 and 2.6.13-rc4
> - lsmod of modules in 2.6.11 and 2.6.13-rc4
>
> I'm ready to supply more - just ask! :-)
Here are the differences I see:
In 2.6.13-rc4, the port window shifted from 0x0100-0x013f to
0x3100-0x313f. I believe it may be fixed in 2.6.13.1. But it doesn't
seem to affect the card in any significant way.
In both cases, the link status goes through "association failed" and
"connected".
$ grep "New link status" dmesg-2.6.11
eth1: New link status: Association Failed (0006)
eth1: New link status: Connected (0001)
eth1: New link status: Disconnected (0002)
eth1: New link status: Association Failed (0006)
eth1: New link status: Connected (0001)
$ grep "New link status" dmesg-2.6.13-rc4
eth1: New link status: Association Failed (0006)
eth1: New link status: Connected (0001)
eth1: New link status: Disconnected (0002)
There are several warnings "This firmware requires an ESSID in
IBSS-Ad-Hoc mode". I guess you should supply ESSID or change the mode.
Are you actually using Ad-Hoc mode?
I suggest that you upgrade to 2.6.13.1. Try running iwconfig manually
to set the card parameters. The "iwconfig" output could be helpful to
find the problem.
--
Regards,
Pavel Roskin
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
|
