The call of Theo de Raadt, leader of the OpenBSD project, for access to hardware documentation again ring true then. It's not Linux's fault that it can't work well with the hardware by the likes of Intel or nvidia, it's the process of interacting with those devices through what he call's BLOBS that are closed source binaries that cause these. I experienced this wi-fi hassle with my laptop's built-in Atheros wlan card.
On Wed, Apr 1, 2009 at 4:43 PM, Orlando Andico <[email protected]>wrote: > Personally I've soured on the Linux desktop (after many years of using > a Linux desktop... starting with Slackware 3.0) because support for > Intel Wireless is so cranky / unreliable! > > I was using FC8 some months back and although I followed all the > instructions for setting up wireless, 7 times out of 10 I could not > connect to the AP. I would have to try and try and try before the > wireless connection would "take." I was using the GNOME wireless > manager though, some other offerings might be more robust. > > And I could never get Intel dual-display working (so you can drive a > projector). Every time I would enable it from the GNOME display > manager, the display would freeze. Needless to say, inability to drive > a projector was a deal-breaker for me. > > It's really quite annoying because all my enterprise software needs > run best on Linux. But dual-boot is so cumbersome and running Linux > inside a VM is no joy at all (slow). > > > -- > Orlando Andico > +63.2.976.8659 | +63.920.903.0335 > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph > -- Tito Mari Francis H. Escaño Computer Engineer and Free Software Proponent
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
