I've had similar problems on an iBook G4 (July 2005 run I think, bought in about October). I'm not entirely sure what the cause is. It worked fine for about a week, then I went overseas to a conference and it would associate rarely (1 or 2 times per day, out of many tries). I then updated my (Debian) 2.6.15 kernel (it was a 2.6.15 to 2.6.15 update) and ever since then whenever the module is loaded core 1 is always disabled. Running iwconfig shows that there is a wireless interface, but running iwlist eth2 scan produces "Interface doesn't support scanning : No such device".
Thinking it might have been a problem with the firmware I extracted myself a couple of months ago, I installed the Debian bcm43xx-fwcutter package and used its script to automatically download a driver from the internet and cut out the firmware. This didn't seem to change anything. Unfortunately I don't have the solution yet, but I'll probide some module output in case it's at all helpful. The command I used successfully in the past was iwconfig eth2 rate 11M essid rattlewasp It would then do open authentication and I'd get some messages in dmesg before running dhclient and getting a lease. Now when I run that there are no kernel messages at the iwconfig stage. I presume the problem has to do with core 1 being disabled. I read one user report on this list a while ago where the driver worked if the user unloaded and reloaded the driver a few times until all the cores were enabled. I've tried that many times to no avail. bcm43xx driver 0.0.1 bcm43xx: Chip ID 0x4318, rev 0x2 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) bcm43xx: Radio turned off bcm43xx: Radio turned off I've occasionally booted to Mac OS X and verified that the hardware still works - it hasn't been baked :) Thanks for all your hard work everyone, I hope this information is useful. -Ted Tim Cooijmans wrote: > On Monday 13 February 2006 21:16, Tim Cooijmans wrote: > >>According to `dmesg', everything went fine: > > I'm sorry, this hardly says everything went fine. It did say so on earlier > tries, so I didn't even look at what it said when pasting it in the e-mail. > On earlier tries `dmesg' would say associating succeeded, though I'd still > get the ``network is down'' error. > > I also forgot to mention I've tried to connect to another access point as > well, with the same error. I tried using the ``auto'' value for settings > like rate and channel, also to no avail. I have no firewall rules loaded. > > Tim > _______________________________________________ > Bcm43xx-dev mailing list > [email protected] > http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
signature.asc
Description: OpenPGP digital signature
