| Summary: | [nv15] screen corruption (color) with latest git | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Johannes Obermayr <johannesobermayr> | ||||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | ||||||||||
| Version: | git | ||||||||||
| Hardware: | x86 (IA32) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Johannes Obermayr
2009-10-17 15:09:18 UTC
Pictures are useful, logs are even better! :) Can you attach /var/log/Xorg.0.log and the output of the dmesg command when the corruption is present. Created attachment 30515 [details]
Xorg.0.log
Created attachment 30516 [details]
dmesg.txt
Created attachment 30526 [details] [review] ums_lut.patch The attached patch should do the trick. However you should already be using KMS, userspace modesetting is more or less abandoned. I applied the patch and I see the right colors again... But I do not understand what you mean with "you should already be using KMS". What must I do? Set another configure/compiler flag? Btw. is it possible that I disable 3D acceleration (Gallium) and use 2D acceleration if it is already compiled into Mesa via "--enable-gallium-nouveau"? Maybe you directly answer to my email address. Thanks for your work... I am closing the bug now... (In reply to comment #5) > But I do not understand what you mean with "you should already be using KMS". > What must I do? Set another configure/compiler flag? http://nouveau.freedesktop.org/wiki/KernelModeSetting > Btw. is it possible that I disable 3D acceleration (Gallium) and use 2D > acceleration if it is already compiled into Mesa via > "--enable-gallium-nouveau"? Just do not install gallium-enabled Mesa system-wide. |
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.