Page 1:A First Look At Fedora And GNOME Shell
Page 2:Fedora 16 At A Glance
Page 3:Fedora 16 Installation: Phase One
Page 4:Fedora 16 Installation: Phase Two
Page 5:Repos, Flash, Java, And Codecs
Page 6:Graphics, Wi-Fi, And 32-bit Libs
Page 7:GNOME 3 And GNOME Shell Basics
Page 8:GNOME Shell Desktop, Panel, And Notifications
Page 9:GNOME Shell Activities/Overview
Page 10:Input Shortcuts, Tips, And Tricks
Page 11:GNOME 3 Pros And Cons
Page 12:GNOME 3 Tweaks
Page 13:GNOME Shell Extensions A-L
Page 14:GNOME Shell Extensions M-Z
Page 15:Fixing GNOME 3
Page 16:Mimicking GNOME 2
Page 17:Test System Specs And Setup
Page 18:Benchmark Results: Start And Stop Times
Page 19:Benchmark Results: File Copy Time
Page 20:Benchmark Results: Archiving
Page 21:Benchmark Results: Multimedia
Page 22:Benchmark Results: System
Page 23:Benchmark Results: Unigine, AMD And Nvidia
Page 24:Benchmark Results: Games, AMD And Nvidia
Page 25:Benchmark Analysis: Fedora Versus Ubuntu And Windows
Page 26:Fedora 16: Conclusion
Page 27:GNOME 3: Why It Failed
Page 28:GNOME 3: Conclusion
Graphics, Wi-Fi, And 32-bit Libs
As explained earlier, one of the drawbacks to a 100% FOSS distribution like Fedora is the way it handles proprietary drivers. Even the most common drivers, like those for AMD and Nvidia graphics cards, must be installed and configured the old-fashioned way. Unlike the RPM Fusion repos, there are no handy RPM files. And unlike Ubuntu, there isn't a nice graphical wizard to help you out. Fortunately, if you added the RPM Fusion repos, installing AMD or Nvidia drivers doesn't require the command line.
If you opted for the EasyLife route and checked off the appropriate drivers, you can skip ahead to the next step.
For AMD/ATI cards, simply search for "catalyst" in Add/Remove Software and select AMD's proprietary driver for ATI graphic cards.
Proprietary AMD Driver Installation
For Nvidia cards, search for "nvidia" and choose Nvidia's proprietary display driver for Nvidia graphic cards.
Proprietary Nvidia Driver Installation
Both require a restart in order for the new driver to take effect.
The Dell Inspiron Mini 10v that we use for our general mobile experience has a Broadcom B43-series Wi-Fi chipset. While this chip is automatically detected in Ubuntu, Fedora has no mechanism akin to Ubuntu's Additional Drivers utility. If your Wi-Fi doesn't "just work" out-of-the-box, you need to set it up yourself.
Wi-Fi can be a bit of a pain to get working in Fedora because it does require the command line. Launch the CLI from the Applications side of the Activities overview. As with Ubuntu and most GNOME-based distros, Terminal is the name of the command line application in Fedora 16.
While most new Linux users won't feel comfortable using the command line, this is the only way to get your Wi-Fi up and running in Fedora. If you prefer graphical setup wizards, a 100% FOSS distribution just isn't for you.
To get most proprietary Wi-Fi drivers working in Fedora, first obtain the Windows version of the driver. Linuxwireless.org is the place to go for these. Once you have the driver on your machine, open a terminal and enter the appropriate code snippets provided in the device firmware installation section for Fedora.
The procedure for setting up the popular Broadcom Wi-Fi chipset found in our netbook test system is as follows:
yum install wget
yum install b43-fwcutter wget
tar xjf broadcom-wl-5.100.138.tar.bz2
sudo b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o
It's been a while since we had any major issues with the 64-bit version of Ubuntu or any other consumer-oriented Linux desktop. But again, Fedora is somewhat of a throwback to days past. Thirty-two-bit packages don't just work on the 64-bit build of Fedora. And, unlike Ubuntu and other Debian-based distributions, Fedora has no simple method for adding 32-bit libraries to a 64-bit system. On a Debian-based distro, you get around that with a single line of code. In Fedora, each 32-bit library has to be installed manually. The only way to know which library you need is to hit a wall installing applications (or do some preliminary research). If a piece of software won't install, try using the command line. The terminal outputs any errors caused by missing libraries, at which point you can install them from either Terminal or Add/Remove Software.
The Terminal method goes like this:
sudo yum install FULL-LIBRARY-NAME
To install 32-bit libraries on a 64-bit platform via Add/Remove Software, you must first get 32-bit packages to appear in the search results. To do this, open Add/Remove Software, click on Filters in the menu bar, and then uncheck Only Native Packages.
Add/Remove Software - Filters - Only Native Packages
Now you're able to search for and install 32-bit packages on a 64-bit installation.
- A First Look At Fedora And GNOME Shell
- Fedora 16 At A Glance
- Fedora 16 Installation: Phase One
- Fedora 16 Installation: Phase Two
- Repos, Flash, Java, And Codecs
- Graphics, Wi-Fi, And 32-bit Libs
- GNOME 3 And GNOME Shell Basics
- GNOME Shell Desktop, Panel, And Notifications
- GNOME Shell Activities/Overview
- Input Shortcuts, Tips, And Tricks
- GNOME 3 Pros And Cons
- GNOME 3 Tweaks
- GNOME Shell Extensions A-L
- GNOME Shell Extensions M-Z
- Fixing GNOME 3
- Mimicking GNOME 2
- Test System Specs And Setup
- Benchmark Results: Start And Stop Times
- Benchmark Results: File Copy Time
- Benchmark Results: Archiving
- Benchmark Results: Multimedia
- Benchmark Results: System
- Benchmark Results: Unigine, AMD And Nvidia
- Benchmark Results: Games, AMD And Nvidia
- Benchmark Analysis: Fedora Versus Ubuntu And Windows
- Fedora 16: Conclusion
- GNOME 3: Why It Failed
- GNOME 3: Conclusion