On Thu, Feb 01, 2007 at 02:59:03PM +0100, Erik Mouw wrote:
Well I assumed it messed up the eeprom settings, since we had to go into
the advanced driver settings and change it from 802.11b only back to
auto mode and I would think those settings are stored in the eeprom if
booting a 2.6.18 kernel and loading the bcm43xx driver can cause it to
stop working, then it has to be an eeprom setting.
Actually I suppose the other posibility is that you simply have to power
cycle before booting windows after linux to avoid any left over settings
in the chip from being a problem. That may be what I did. Given I
couldn't get the card to connect using the bcm43xx driver anyhow, I
didn't spend too much time trying (I am fairly sure I set the AP to
802.11g only though which may have been a problem).
I just don't like things sticking out that are breakable.
Excellent. Is the bcm43xx planning to get 802.11g mode working at some
point? Is broadcom ever going to help out with any specs for their
hardware or do they still mistakenly believe that end users are not
their customers? Given the behaviour of broadcom over the years I know
I don't intend to buy anything with a broadcom chip in it again, which
means broadcom's behaviour directly means they will get less sales to the
laptop makers, since some people will actively avoid anything with
broadcom's hardware in it. :)
--
Len Sorensen
-
