Linked by Thom Holwerda on Wed 5th Oct 2011 20:36 UTC, submitted by zizban
Permalink for comment 492317
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-27
Totally unrelated - completely different hardware.
Interesting. I can't remember if my broadcom chip showed up or not prior to installation of the firmware. It may have, and simply failed to work.
Not necessarily a driver, I misspoke. The firmwares. The firmware is what the driver loads onto the wifi chip before it can be used - basically it's the operating system that the wifi chip runs, and it doesn't come pre-installed. This is pretty much how every wifi chip works, and if you don't have the firmware, you're SOL.
Since the firmware is technically "software", and thus requires a license to distribute it, this produces a tricky situation for OS developers who want to provide drivers for the hardware. "
Ok, I installed the firmwares (using a Ethernet connection)and then it saw our wireless network, but couldn't connect to it, because the net_server crashed or something. Disconnected Ethernet, rebooted, and now it refuses to see our network (or any wifi network, period). Says "No network detected", in the prefs, again. Weird.
Any idea why?