On Sunday 16 September 2007, you wrote:
> On Sunday 16 September 2007 12:17:50 Marcin Kosiba wrote:
> > On Sunday 16 September 2007, Michael Buesch wrote:
> > > On Sunday 16 September 2007 11:26:21 Marcin Kosiba wrote:
> > > > On Sunday 16 September 2007, Larry Finger wrote:
> > > > > The only switch associated with any of the BCM cards that I know
> > > > > about is the radio-enable switch. If that is what you need, it can
> > > > > only be controlled externally. The software can read its state, but
> > > > > not control it.
> > > >
> > > > not fun - oh well... gotta warm that soldering iron up then...
> > > >
> > > > > What OS are you using? If Linux and the appropriate driver is
> > > > > installed, the output of the dmesg command will show some details.
> > > >
> > > > slackware linux 12.0
> > > > (uname -a:
> > > > Linux ebox 2.6.21.5 #2 Tue Jun 19 15:22:48 CDT 2007 i586 05/00 SiS
> > > > SiS SiS GNU/Linux)
> > > >
> > > > dmesg | grep bcm
> > > >
> > > > bcm43xx: Chip ID 0x4306, rev 0x3
> > > > bcm43xx: Number of cores: 5
> > > > bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
> > > > bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
> > > > bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
> > > > bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
> > > > bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
> > > > bcm43xx: PHY connected
> > > > bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
> > > > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> > > > bcm43xx: Radio turned off
> > > > bcm43xx: Radio turned off
> > > >
> > > > as I've said - off :/
> > >
> > > What about bringing the device up?
> >
> > ok, my bad - had the wrong firmware version up there (seems as though the
> > error messages are shown in dmesg only if I load the module manually - if
> > it is loaded on startup they probably go somewhere else..)
> >
> > bcm43xx: Radio turned off
> > bcm43xx: Radio turned off
> > bcm43xx: PHY connected
> > bcm43xx: Microcode rev 0xf5, pl 0x5a (2003-12-22  20:11:25)
> > bcm43xx: Radio turned on
> > bcm43xx: Radio enabled by hardware
> > bcm43xx: Chip initialized
> > bcm43xx: 30-bit DMA initialized
> > bcm43xx: Keys cleared
> > bcm43xx: Selected 802.11 core (phytype 2)
>
> So everything's fine?

Hard to say really, iwlist scan doesn't get any results and I can't associate 
with the AP which is physically right next to the device. I'll try the newest 
bcm43xx from git and see what happens.

Same thing (no scan results and can't associate with the AP) happens with 
ndiswrapper, though I don't know if the radio is on or off.

Cheers,
        Marcin
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to