Bug 917260
| Summary: | [GeForce 9100] [10de:0847:103c:2a7a] Garbled text screen; no X after modeset with kernel 3.9.0-0.rc0.git14.1.fc19.x86_64 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steven Usdansky <usdanskys> |
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | airlied, ajax, awilliam, bskeggs, esm, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-28 11:07:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 704476 [details]
xorg.conf
monitor does not emit a proper EDID; xorg.conf needed to get native 1680x1050 resolution
Created attachment 704477 [details]
Xorg.0.log for failed modeset
Created attachment 704478 [details]
Xorg.0.log with nomodeset kernel parameter
Created attachment 704479 [details]
dmesg output failed modeset
No problems with kernel-3.7.9-205.fc18.x86_64. Best to file these bugs against the X driver component even though it's not technically correct, because it gets them to the right maintainer. New kernel builds are coming through at a rate of knots - can you try the latest ones every day or two and report back? Thanks! I've been trying new kernels as they appear. kernel-3.9.0-0.rc1.git0.4.fc19.x86_64 exhibits same misbehavior kernel-3.9.0-0.rc2.git0.3.fc19.x86_64 exhibits same misbehavior Created attachment 712563 [details]
/var/log/messages good (3.7) and bad (3.9) kernels
Shows both successful boots (kernel-3.7.9-205.fc18.x86_64) and unsuccessful boot (kernel-3.9.0-0.rc3.git0.3.fc19.x86_64) on March 19
Created attachment 712565 [details] Xorg.0.log for failed modeset with kernel-3.9.0-0.rc3.git0.3.fc19.x86_64 Should probably obsolete attachment #704477 [details], but xorg.conf was changed to explicitly load various modules as shown below (it didn't make a difference): Section "Module" Load "dri2" Load "dbe" Load "glx" Load "extmod" Load "record" Load "dri" Load "fb" Load "exa" Load "shadowfb" Load "evdev" EndSection Problem persists with: kernel-3.9.0-0.rc3.git1.3.fc19.x86_64 xorg-x11-drv-nouveau-1.0.6-7.fc19.x86_64 Problem persists with kernel 3.9.0-0.rc7.git3.1.fc19.x86_64 and with the testday iso. I gave up and switched to the nvidia driver (akmod-nvidia-313.30-2.fc19.x86_64) |
Created attachment 704475 [details] smolt profile Description of problem: Screen consists of scrambled dots instead of text after kernel modeset; X won't start Version-Release number of selected component (if applicable): kernel-3.9.0-0.rc0.git14.1.fc19.x86_64 xorg-x11-drv-nouveau-1.0.6-5.fc19.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install a new kernel (3.9.0- git11 or higher) 2. Boot with that kernel 3. Actual results: Text screen consists of semi-randomly scattered dots instead of text characters. X will not start when command startx is executed Expected results: Text on screen is readable throughout the session X starts in response to startx Additional info: