| Summary: | (regression/bisected) (2.6.37 nouveau/KMS) internal laptop display remains blank | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Dragos Delcea <dragos.delcea> | ||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | mpagano | ||||
| Version: | unspecified | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Dragos Delcea
2011-02-16 10:01:23 UTC
I wouldn't be certain this commit is the culprit yet. That commit has a typo which would also mess things up, and was fixed by 85341f27b49833325f97580edcd687b4d90bb30b. (In reply to comment #1) > I wouldn't be certain this commit is the culprit yet. That commit has a typo > which would also mess things up, and was fixed by > 85341f27b49833325f97580edcd687b4d90bb30b. ok, but neither 2.6.37 nor 2.6.38-rc4-git8 work for me, even if they have the above commit. You probably only mean that the bisection might be misleading due to the above, but where does this leave me? what are the next steps I can take to get around that (if any)? some git-fu pointers would be highly appreciated, as I'm just learning the ropes... In the meantime, I'll try building a kernel based on 85341f27b49833325f97580edcd687b4d90bb30b and see what I get. (In reply to comment #1) > I wouldn't be certain this commit is the culprit yet. That commit has a typo > which would also mess things up, and was fixed by > 85341f27b49833325f97580edcd687b4d90bb30b. ok, so you were right, 85341f27b49833325f97580edcd687b4d90bb30b works here. I'll start a new bisect with 85341f27b49833325f97580edcd687b4d90bb30b as the good and v2.6.37 as the bad and report back..another 13 steps..doh. (In reply to comment #3) .. > I'll start a new bisect with 85341f27b49833325f97580edcd687b4d90bb30b as the > good and v2.6.37 as the bad and report back..another 13 steps..doh. due some hardware related problems I had the internal display swapped with a new one (the internal display was occasionally flickering badly), and now the situation is completely upside down: 2.6.37 works, while 2.6.36 doesn't anymore. The flickering display problem was going on for some time, even back in the 2.6.35 and 2.6.36 times, and it was manifesting even during BIOS POST, hence the thinking that it was a hw problem. However, now I'm thoroughly confused about the current situation. Is the newer display different and triggers different (inverse) behavior? I can't see any meaningful difference in dmesg output of 2.6.37 between working and non working... It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report. In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one. Thanks, The Nouveau Team |
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.