Summary: | [NV34] Display all whited out | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Alex Buell <alex.buell> | ||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | critical | ||||||||||
Priority: | medium | CC: | orion, overcaff3inated | ||||||||
Version: | unspecified | ||||||||||
Hardware: | x86 (IA32) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Alex Buell
2012-12-13 20:35:58 UTC
Can you post your dmesg output with the messed up display? +dmesg from 3.6, please. (btw, it might be a duplicate of bug 56461) I think I'm experiencing the same in Fedora, see: https://bugzilla.redhat.com/show_bug.cgi?id=905631 I've attached dmesg outputs there. This looks a little suspicious: nouveau W[ PTIMER][0000:01:00.0] unknown input clock freq This bug here may be the same : https://bugs.freedesktop.org/show_bug.cgi?id=60516 Created attachment 75002 [details]
Dmesg for 3.6.0 (working)
Created attachment 75003 [details]
Dmesg for 3.7.0 (bad)
Have attached the dmesgs for both 3.6.0 (working) and 3.7.) (bad). Hope this helps to resolve the problem. Let me know if you need further information. Created attachment 75172 [details]
dmesg from linux-v3.8-91-g2fee6f5
I'm running nouveau on this hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation NV34M [GeForce FX Go5200 64M] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device 0001
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
Memory at c1000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (32-bit, prefetchable) [size=256M]
Expansion ROM at <unassigned> [disabled]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
Kernel driver in use: nouveau
Kernel modules: nouveau
This is broken since commit cb75d97e9c77743ecfcc43375be135a55a4d9b25, tested by bisecting.
The following commit should address your issue. Can you confirm 6d175e8f6: drm/nouveau: Fix typo in init_idx_addr_latched() The bisect result + commit that fixed all make sense. No followup from a 5-month old request to retest, I'm assuming this is indeed fixed. Feel free to reopen if it's not. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.