Bug 708257 - F15 Gnome3 gnome-shell not working - GeForce 8300
Summary: F15 Gnome3 gnome-shell not working - GeForce 8300
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-27 03:29 UTC by Julian Tosh
Modified: 2011-06-02 01:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 01:14:37 UTC
Type: ---


Attachments (Terms of Use)
standard log files (49.65 KB, application/zip)
2011-05-27 03:29 UTC, Julian Tosh
no flags Details
additional logs (70.01 KB, application/zip)
2011-06-01 22:56 UTC, Julian Tosh
no flags Details
new batch of log files. (79.14 KB, application/zip)
2011-06-02 00:45 UTC, Julian Tosh
no flags Details

Description Julian Tosh 2011-05-27 03:29:03 UTC
Created attachment 501235 [details]
standard log files

Description of problem:
F15 Gnome3 gnome-shell does not load causing fallback mode.

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


How reproducible:
Every time.

Steps to Reproduce:
1. Ensure gnome-shell will try gnome-shell at next login.
2. reboot and login.
  
Actual results:
gnome-shell fails to load and window manager loads in fallback mode.


Expected results:
gnome-shell loads to gnome3 desktop

Additional info:
The system was recently upgraded from F14 to F15. During its life as F14, nvidia drivers were used. After the upgrade, I realized I was not getting the full gnome3 experience and getting stuck in fallback mode, I removed the nvidia drivers and unblacklisted nouveau. Following some debugging and troubleshooting steps found on the internet I tried:
creating a custom xorg.conf and trying some device options like 'Option "AccelMethod" "XAA"' and 'Option "AccelMethod" "EXA"', nomodeset, etc.

Comment 1 Adam Jackson 2011-06-01 18:39:06 UTC
[    61.089] Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us nomodeset #nouveau.modeset=
0 #rdblacklist=nouveau

"nomodeset" disables KMS.  This means you fall back to the nv driver, which does not have accelerated 3d support.  Remove this word from your kcmdline, rebuild your initramfs with /usr/libexec/plymouth/plymouth-update-initrd, and reboot.

Not entirely sure why you filed this against the intel driver.  I've reassigned it to the nouveau driver instead.  Please reopen if you still have issues.

Comment 2 Julian Tosh 2011-06-01 22:56:10 UTC
(In reply to comment #1)
> "nomodeset" disables KMS.  This means you fall back to the nv driver, which
> does not have accelerated 3d support.  Remove this word from your kcmdline,
> rebuild your initramfs with /usr/libexec/plymouth/plymouth-update-initrd, and
> reboot.

performed this with some errors. recorded in plymouth.log. No luck - And I did try to reset gnome to attempt native mode at next login.

> 
> Not entirely sure why you filed this against the intel driver.  I've reassigned
> it to the nouveau driver instead.  Please reopen if you still have issues.

PBKAC

Attaching new logs in 2011-06-01.zip. Thanks!

Comment 3 Julian Tosh 2011-06-01 22:56:53 UTC
Created attachment 502396 [details]
additional logs

Comment 4 Julian Tosh 2011-06-01 23:04:38 UTC
Another self-attempt/grasping at straws:
1) mv xorg.conf to xorg.conf.2011-06-01
2) reset "attempt gnome-shell at next login"
3) reboot
4) Do NOT profit. 8/

Comment 5 Ben Skeggs 2011-06-02 00:22:48 UTC
(In reply to comment #4)
> Another self-attempt/grasping at straws:
> 1) mv xorg.conf to xorg.conf.2011-06-01
> 2) reset "attempt gnome-shell at next login"
> 3) reboot
> 4) Do NOT profit. 8/

I have no idea what you've done, but there's no mention of nouveau whatsoever in your kernel log.  Something, somewhere is blacklisting the nouveau driver from being loaded (/etc/modprobe.d/blacklist.conf? maybe?)..

Comment 6 Julian Tosh 2011-06-02 00:45:17 UTC
Hum. Thought I removed that, but it must have been from another machine I was working on. It was indeed being blacklisted in the pathname you specified. I remarked the line and now I'm clearly able to hear marbles bouncing around in my computer as it boots now (dry humor), but still no love from gnome-shell native mode.

Attached new logs in 2011-06-01-1737.zip.

Comment 7 Julian Tosh 2011-06-02 00:45:48 UTC
Created attachment 502411 [details]
new batch of log files.

Comment 8 Ben Skeggs 2011-06-02 00:54:48 UTC
According to your X logs you don't even have the nouveau X driver installed..  Which is odd, because, it's installed by default..

yum install xorg-x11-drv-nouveau

Comment 9 Julian Tosh 2011-06-02 01:14:37 UTC
Package was not present. Installed. Gnome-shell now loads as expected.

YOU ARE A BOSS!

nouveau was probably unloaded several upgrades ago when I was trying to use the nvidia proprietary drivers (the initial OS install was probably done around F10 and upgraded ever since).

Thank you so much for sticking with me on this. I def got a little troubleshooting skills out of this.


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