I am running Fedora 16 64-bit, with GNOME3 Desktop, and as of a few hours ago my system starts in fallback mode. What happens is as follows:

In an attempt to getter better FPS in a JAVA game, Minecraft, I installed the catalyst drivers from the rpmfusion repositories, both the kmod and akmod. This caused my system to start in fallback mode, as it had the last time I had checked it (about a week ago. The driver was working just fine just over a month ago, but then it stopped working with an update.) I have been routinely attempting to re-install it, but without success, booting into fallback mode, so I simply remove it via "yum remove akmod-catalyst kmod-catalyst" at which point it also remove the xorg-x11-drv-catalyst package, which is installed as a a/kmod dependancy. Then the system returns to normal on reboot.

**important note- with the Catalyst drivers installed, the booting screen is a bar that fills up along the bottom of the screen. Without, it has the Fedora logo slowy get filled with color**

My reboot started normal, with the Fedora logo booting, all seemed well. But when I arrived at the login screen, it wass clearly in fallback mode, which was very odd. I double-checked, and sure enough, the catalyst packages were not there. I enable/disable the forced fallback mode, rebooted, and was met with the same problem. Oh yes, I have a Radeon HD6850. I then attempted to install ATI's own Linux drivers, which did the same thing as the rpmfusion ones, and caused the bar-filling boot screen to occur. I then removed the driver, and the system returned to booting with the fedora logo, but still entered fallback mode. My current graphics settings are "Gallium 0.4 on AMD BARTS " according to sytem settings >> system information >> Graphics. I cannot figure out how to get back to where I was before, with regards to the GNOME3 full experience. What's more, Minecraft (a 3D-Acceleration game) still runs with the same FPS it did before today, something it shouldn't be able to do without any 3D-Acceleration drivers, and which will not work with the catalyst drivers installed. This I feel proves that GNOME3 should work just fine right now, and it may be a simple configuration fix somewhere down the line that i know not about. Any suggestions are welcome.

Thanks,
bplis*