Bug 702866 - gnome-session fallback for Intel gen2
Summary: gnome-session fallback for Intel gen2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-07 20:14 UTC by Larry Bolan
Modified: 2011-06-14 15:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-09 15:14:45 UTC
Type: ---


Attachments (Terms of Use)

Description Larry Bolan 2011-05-07 20:14:34 UTC
Description of problem:

after updating all of my xorg packages in the most recent update, gnome 3 goes to fallback mode as if the graphics are not enough.

My laptop uses an intel i855-GM for graphics... I was running gnome shell without issues before the update.

glxgears shows no 3d issues... 250-300 fps during a quick test.

Version-Release number of selected component (if applicable):


How reproducible:

100%
Steps to Reproduce:
1.find laptop with intel 855-gm graphics
2.install most recent updates
3.reboot and log in
  
Actual results:
boot to gnome 3 fallback mode

Expected results:
boot to gnome shell

Additional info:

Comment 1 Adam Jackson 2011-05-09 15:14:45 UTC
gnome-session blacklists Intel 8xx series chips now:

* Wed Apr 27 2011 Owen Taylor <otaylor> - 3.0.1-2
- Add a quick-and-dirty blacklist for Radeon R100, R200, Intel 8xx

This is intentional.  8xx chips have many silicon bugs that tend to manifest as system lockups.

Comment 2 Larry Bolan 2011-05-09 18:56:59 UTC
Is there a way to undo that? i was not having any issues beofre this... no lock ups or whatever.

heck the reason i went to fedora was it did not have bugs with that chip like ubuntu did...

Comment 3 udo 2011-06-14 15:41:13 UTC
I get fallback as well over here on a box where `gnome-shell --replace` works OK.
So how to circumvent this?


Note You need to log in before you can comment on or make changes to this bug.