From Fedora Project Wiki

(add entry for eee top no video issue (491627))
(add note on how to check whether your onboard nvidia chip is AGP)
Line 75: Line 75:


Problems have been reported with several NVIDIA AGP graphics cards, with the new ''nouveau'' graphics driver used in Fedora 11. AGP is a tricky case that the driver does not yet handle well for several cards. If you experience failure to start the graphical desktop (X server), or hanging or crashing of the graphical desktop, and you have an NVIDIA-based AGP graphics card, you may want to try the following workaround. Add the kernel parameter <tt>nouveau.noagp=1</tt>. For many reporters, this resolves the problem.
Problems have been reported with several NVIDIA AGP graphics cards, with the new ''nouveau'' graphics driver used in Fedora 11. AGP is a tricky case that the driver does not yet handle well for several cards. If you experience failure to start the graphical desktop (X server), or hanging or crashing of the graphical desktop, and you have an NVIDIA-based AGP graphics card, you may want to try the following workaround. Add the kernel parameter <tt>nouveau.noagp=1</tt>. For many reporters, this resolves the problem.
Some NVIDIA onboard graphics chipsets use AGP, as well as expansion cards that fit in an AGP slot. To check whether your onboard chipset is an AGP one, run this command:
<pre>
grep -i agp /var/log/Xorg.0.log
</pre>
if it returns anything, your chip is an AGP one. If not, it isn't.


If you experience a problem of this kind, and your graphics card is not the same model as in any of the existing reports listed above, please file a new bug report on the ''xorg-x11-drv-nouveau'' component, explaining your symptoms, and providing [[BugsAndFeatureRequests#Xorg|all the usual information required for X.org bug reports]].
If you experience a problem of this kind, and your graphics card is not the same model as in any of the existing reports listed above, please file a new bug report on the ''xorg-x11-drv-nouveau'' component, explaining your symptoms, and providing [[BugsAndFeatureRequests#Xorg|all the usual information required for X.org bug reports]].


{{Anchor|eee-top-no-video}}
{{Anchor|eee-top-no-video}}
=== Graphical desktop fails to start on Asus Eee Top ===
=== Graphical desktop fails to start on Asus Eee Top ===
<small>[[Common F11 bugs#eee-top-no-video|link to this item]] - [[rhbug:491627|Bugzilla: #491627]]</small>
<small>[[Common F11 bugs#eee-top-no-video|link to this item]] - [[rhbug:491627|Bugzilla: #491627]]</small>

Revision as of 23:31, 20 May 2009

This page documents common bugs in Fedora 11 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Release Summary, Announcement and Notes

Read the Fedora 11 Preview release notes for specific information about changes in Fedora 11 Preview, known issues, and other general information.

My Bug Is Not Listed

Not every bug is listed in this page. You can use bugzilla queries in the bottom of this page for that. We have collected this based on commonly discussed issues in our mailing lists and forums. If you believe any particular bug report is missed out here and if you have wiki access, add it this page or contact Rahul Sundaram with the bugzilla report number explaining why you believe that particular report qualifies as a common issue.

Common Issues

Update notification doesn't disappear

link to this item - Bugzilla: #492005

After updating using PackageKit, the updates notice may reappear even when there are no package updates left to receive. The maintainer is aware of the issue and we expect to resolve it soon. In the meantime, changing the following option in the configuration file may work for some people, although results vary:

UseUpdateCache=false

git-* commands moved from $PATH

link to this item - Bugzilla: #479216

Most of the git-* commannds have been moved from the standard $PATH. Use of the git-* form has been deprecated since around 2006 and upstream moved these commands by default with git-1.6.0. Any script that references the commands will need to be updated. Below is a possible workaround:

PATH=$(git --exec-path):$PATH

updating from F10 in X fails and X falls over

link to this item - Bugzilla #494046

Systems updating from F10 using yum and in some cases PackageKit can fall over (Bugzilla #494046). The best way to work around this problem is to first update fontconfig to the version in F11. Then restart your X server and finish the rest of the update.

Invisible mouse cursor on systems with Intel 845 graphics chipset

link to this item - Bugzilla: #488980

On systems with Intel 845 graphics chipsets, by default the mouse cursor will be invisible. You can work around this problem by disabling kernel modesetting, using the nomodeset kernel parameter. A potential fix for this issue is available in kernel-2.6.29.3-155, which will be available in Fedora 11 pre-release repositories on 2009-05-21, or can be found in Koji here. If you are affected by this issue, please test and provide feedback in the bug report.

Enabling desktop effects causes system hang with Intel 845 graphics chipset

link to this item - Bugzilla: #490005

On systems with Intel 845 graphics chipsets, attempting to enable accelerated desktop effects (Compiz) via the System / Preferences / Desktop Effects menu entry causes the system to hang (in fact, X is stuck, but if you have the appropriate network setup, you should be able to ssh into the affected machine to shut it down in an orderly fashion). There is no know workaround for this issue, therefore we advise not trying to enable desktop effects on this graphics chipset for now.

Screen stays black when returning from idle mode on Thinkpad X41T

link to this item - Bugzilla: #489907

On the Lenovo / IBM Thinkpad X41T model laptop, with default settings, the screen will fail to turn back on once it has gone into power-saving idle mode (either on a timeout, or on closing and re-opening the lid). Disabling kernel modesetting via the nomodeset kernel parameter works around this problem, but may cause other problems to occur instead. Another workaround is to create a file with the following contents:

#!/bin/bash
xrandr --output LVDS1 --off
xrandr --output LVDS1 --auto

Make it executable, and set a shortcut key combination to launch it. Running the script via the shortcut should restore the display. Fedora developers are currently working on a fix for this problem.

Graphical desktop failing to start or crashing with AGP NVIDIA graphics cards

link to this item - Bugzilla: #490358, Bugzilla: #487456, Bugzilla: #498579, Bugzilla: #499730

Problems have been reported with several NVIDIA AGP graphics cards, with the new nouveau graphics driver used in Fedora 11. AGP is a tricky case that the driver does not yet handle well for several cards. If you experience failure to start the graphical desktop (X server), or hanging or crashing of the graphical desktop, and you have an NVIDIA-based AGP graphics card, you may want to try the following workaround. Add the kernel parameter nouveau.noagp=1. For many reporters, this resolves the problem.

Some NVIDIA onboard graphics chipsets use AGP, as well as expansion cards that fit in an AGP slot. To check whether your onboard chipset is an AGP one, run this command:

grep -i agp /var/log/Xorg.0.log

if it returns anything, your chip is an AGP one. If not, it isn't.

If you experience a problem of this kind, and your graphics card is not the same model as in any of the existing reports listed above, please file a new bug report on the xorg-x11-drv-nouveau component, explaining your symptoms, and providing all the usual information required for X.org bug reports.

Graphical desktop fails to start on Asus Eee Top

link to this item - Bugzilla: #491627

It has been reported that with a default configuration, Fedora 11 fails to initialize the graphical desktop (X server) properly on the Asus Eee Top system. You can work around this issue by downloading this file and installing it as /etc/X11/xorg.conf. With this file in place, the X server should start correctly at the native resolution of the system.

References