[SOLVED] Fedora 16 Gnome 3 to fallback on Asus EEE PC 1001PX
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Fedora 16 Gnome 3 to fallback on Asus EEE PC 1001PX
I recently upgrade from Fedora 14 to Fedora 16 and I'm having a problem with Gnome 3 (Gnomeshell). I think it is capable of using the normal Gnome shell mode as it has the required hardware acceleration. But it keeps going to fallback mode.
I've check the system settings and it's not on "forced" fallback. I've had a look on the forum and did a general internet search. All without much luck. Most problems seem to be with the ATI graphics card, while my netbook has an intel graphics card (I think ...). For most people the problem seems to disappear after a software update. I've tried that, but again without success.
hardware: Asus 1001PX (Atom N450 processor, 1 GB RAM)
distro: fedora 16
diplay driver: xorg-x11-drv-intel-2.17.0-4.fc16.i686
I've attached the glxinfo output and the Xorg.0.log.
I'm running fedora directly, not in a virtual machine.
I've checked and the chipset for this netbook is in fact i915 (Pineview). In windows (this is a dual boot system) it uses the GMA 3150 driver. I've check the XOrg log attached in my first post and it seems to load the 915 module correctly. The log does have some warning though.
Another thing that I noticed is the output from lspci:
00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Atheros Communications AR8132 Fast Ethernet (rev c0)
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Last night I got tired of trying to find a solution and move on to the upgrade of my other laptop (a 6 year old Toshiba Satellite M50-196) ... Ended up with the same problem!! Gnome 3 in fallback mode. It had a similar set-up (i.e. similar packages) and was also upgraded from F14 to F16. I thought it was a bit coincidental that a laptop with completely different hardware would suffer the same problem. On the other hand it did have an old video card (ATI), so I tried to focus on one problem at a time.
After reading through several forums and search for various keywords, including the chipset model (thanks to Aut/Geek), I finally discovered what was the problem. In both cases the actual gnome-shell package (and mutter) was not installed!
In both cases I used Fedora's pre-upgrade. Although this process is not the recommended upgrade method, I would expect major changes like Gnome to upgrade correctly. Perhaps it happened because I had compiz-fusion installed (I read something about this) or because I also have Xfce installed.
In any case, for those who face the same problem the simple solution is:
1. check if the gnome-shell is installed (e.g. rpm -qa gnome-shell)
2. if not, use yum to install it: yum install gnome-shell (this also installs mutter as a dependency if it's not available).
Distribution: Fedora FC23, Raspbian, Ubuntu Precise via Chrome/Crouton
I ran into the same problem, but I have Sony PGM-K13 that is stuck in fallback and the gnomeshell is installed.
I wish there was some kind of documentation and log that one could analyze to see the logic gnome uses to decide on fallback mode or not. As far as I can tell it makes a totally opaque decision force many people to guess and test what is going on.
Yeah, I agree. It was quite difficult to find the actual cause and in the end I found it by accident. I haven't tried it but it may be useful for people with a similar problem to try to (re)start the gnome-shell from the command line and log/redirect any messages to a file. Maybe it'll give some additional info ...
Having said that I feel that the main problem in my case was either pre-upgrade or anaconda, which failed to get the gnome-shell package. I'll need to submit a bug report for that when I have some time.
Not that I'm sticking with Gnome. I'm still not very happy with it for day to day use. It just doesn't work smoothly/naturally. I know that a lot of people say that I need to "get used to it", but my question is "why?". I've tried the MGSE from the colleagues over at Mint Linux, which helped a bit. But I'm switching to Xfce.
Anyway, sorry for the rant, I'm glad you were able to solve your problem as well ... :-)