I'm on wireless-2.6, branch everything, git commit
7446b6c0e3b18fd2c5f9c406bb20841e6193d058
When I insert a b43 based card, I don't get associated
automatically. This happens:
$ # Insert the card
pccard: CardBus card inserted into slot 0
PCI: Enabling device :03:00.0 ( - 0002)
ACPI: PCI
Hello list,
I'm using Gentoo Linux (2.6.23) on a Apple iBook and was very happy that
my wireless chip is supported.
After installation everything seems to be OK and working fine.
But when the distance to my AP ascends to more than 4 meters, the
connection seems to be down or unstable. Sometimes
On Thu, 22 Nov 2007, Alexander Koeppe wrote:
I'm using Gentoo Linux (2.6.23) on a Apple iBook and was very happy that
my wireless chip is supported.
After installation everything seems to be OK and working fine.
But when the distance to my AP ascends to more than 4 meters, the
connection
First off, let me state that I don't think this is a regression.
$ iwconfig eth1 essid BLAHMUMPF
HW CONFIG: channel=1 freq=2412 phymode=2
[...]
As you can see, it doesn't find anything that matches the current
configuration.
$ iwconfig eth1 key s:1
b43-phy0 debug: Using hardware based
On Thu, Nov 22, 2007 at 02:05:52PM +0100, Johannes Berg wrote:
Note that the same happens if I let Debian manage the card. An excerpt
from my /etc/network/interfaces shows:
That sucks, I guess debian's scripts need to be fixed.
As it stands, setting the SSID is the closest thing we have
Alexander Koeppe wrote:
Hello list,
I'm using Gentoo Linux (2.6.23) on a Apple iBook and was very happy that
my wireless chip is supported.
After installation everything seems to be OK and working fine.
But when the distance to my AP ascends to more than 4 meters, the
connection seems to
On Wednesday 21 November 2007 22:38:12 Larry Finger wrote:
The BCM94311MCG rev 02 chip has an 802.11 core with revision 13 and
has not been supported until now. The changes include the following:
(1) Add the 802.11 rev 13 device to the ssb_device_id table to load b43.
(2) Add PHY revision 9
On Thu, 2007-11-22 at 08:26 -0500, John W. Linville wrote:
As it stands, setting the SSID is the closest thing we have to an
associate now trigger. I would have to advise distros and users to
always set it last in the wireless init, just before running dhclient
or whatever.
Maybe mac80211
On Thu, 2007-11-22 at 18:18 -0700, Ehud Gavron wrote:
2. dmesg repeats: wlan0: authentication with AP 00:50:bf:b1:da:64 timed out
I think it's an unrelated hardware specific issue. mac80211 tried to
associate but failed.
--
Regards,
Pavel Roskin
John H. wrote:
wrt54gs with latest firmware.
it seems exclusive to linux:O
On Nov 21, 2007 4:18 PM, Larry Finger [EMAIL PROTECTED] wrote:
John H. wrote:
uname -a
Linux laptop 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 21:41:26 EST 2007 i686
i686 i386 GNU/Linux
fedora 8
on certain APs, the
Michael Buesch wrote:
partially acked.
Though, I'm not quite sure yet why you remove that
address extension bits. The specs clearly say that they _are_ there.
And it makes sense to use them, as two bytes of the address are used
for the routing stuff. So the highest 2 bits of the address
11 matches
Mail list logo
