Paolo Arnaldo Dallari wrote:
> Hi all.
> I'm writing because I have some problems with my Airport Extreme card on
> my ibook g4.
> I've recompiled a 2.6.17 kernel with bcm43xx support.
> No problem in compilation, no one when i bring up the module:
> 
> ieee80211_crypt: registered algorithm 'NULL'
> ieee80211: 802.11 data/management/control stack, git-1.1.7
> ieee80211: Copyright (C) 2004-2005 Intel Corporation
> <[EMAIL PROTECTED]>
> bcm43xx driver
> bcm43xx: Chip ID 0x4306, rev 0x2

There is something different about BCM4306, rev 2 chips. I have the same chip 
in my Linksys WPC54G 
card. On my interface, the mac_suspend routine works correctly most of the 
time, but it will 
sometimes fail with a "MAC suspend failure" message. The system will go for 
several hours without 
getting any of these, then get several in a row. On my system, these are 
usually not fatal.

> bcm43xx: Number of cores: 6
> bcm43xx: Core 0: ID 0x800, rev 0x2, vendor 0x4243, enabled
> bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, disabled
> bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor 0x4243, enabled
> bcm43xx: Core 3: ID 0x807, rev 0x1, vendor 0x4243, disabled
> bcm43xx: Core 4: ID 0x804, rev 0x7, vendor 0x4243, enabled
> bcm43xx: Core 5: ID 0x812, rev 0x4, vendor 0x4243, disabled
> bcm43xx: Ignoring additional 802.11 core.
> bcm43xx: PHY connected
> bcm43xx: Detected PHY: Version: 1, Type 2, Revision 1
> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> bcm43xx: Radio turned off
> bcm43xx: Radio turned off
> 
> But when i bring up the interface with ifconfig eth1 up, kernel says
> many times:
> 
> bcm43xx: TODO: Incomplete code in keymac_write() at
> drivers/net/wireless/bcm43xx/bcm43xx_main.c:1135

These are normal. Ignore them.

> then:
> 
> bcm43xx: Keys cleared
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> 
> At this point if I try to associate with an access point
> iwconfig says: Access Point: Invalid
> and dmesg: ADDRCONF(NETDEV_UP): eth1: link is not ready
> 
> Then this is a strange thing... If i turn off my ap and
> i try to set Monitor mode, it seems that everything works fine..
> I can start kismet... and it's ok... it find nothing..
> But when I turn on my ap, Boom, the CPU works at 99% and kernel repeat
> many times:
> 
> Jul 24 11:03:50 localhost kernel: printk: 4 messages suppressed.
> Jul 24 11:03:50 localhost kernel: bcm43xx: MAC suspend failed
> 
> then System hangs and my ibook halts... no other messages.
> 
> Well, in MacOSX the Airport card works fine..
> I try to change my card with the one of my friend, a bcm4306 rev3 and
> everything works fine! I tried to change the card in another ibook with
> same kernel and it do the same of mine, doesn't work..

I would stay away from monitor mode at the start. I would bring the interface 
up with an 'ifup eth1' 
command, then check if it will scan by issuing an 'iwlist s' command. Your AP 
should be on at this 
point. The reason that the cpu is at 99% is due to the loop in 
bcm43xx_mac_suspend.

Before you run another test, please apply the following patch:

index 3889f79..c40609c 100644
--- a/drivers/net/wireless/bcm43xx/bcm43xx_main.c
+++ b/drivers/net/wireless/bcm43xx/bcm43xx_main.c
@@ -2324,7 +2324,7 @@ void bcm43xx_mac_suspend(struct bcm43xx_
                        return;
                udelay(10);
        }
-       printkl(KERN_ERR PFX "MAC suspend failed\n");
+       printkl(KERN_ERR PFX "MAC suspend failed with IRQ_REASON = 
0x%08x\n",tmp);
  }

  void bcm43xx_set_iwmode(struct bcm43xx_private *bcm,

I generated this patch from v2.6.18-rc2 so there may be some offsets, but the 
resulting output 
should show why your interface will not suspend the MAC.

After you rebuild bcm43xx.ko, please run the iwlist test and send the results 
back to me.

Larry




_______________________________________________
Bcm43xx-dev mailing list
[email protected]
http://bat.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to