Summary: | [NVC1] [Quadro 600] Display update issues, stale rendered content | ||
---|---|---|---|
Product: | xorg | Reporter: | Sudarshan <spartha80> |
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Sudarshan
2014-02-15 09:50:29 UTC
I see that you're using displayport. Is it an actual DP monitor, or are you using a DP->xyz adapter? I recently posted a patch that should fix computing number of lanes/lane speeds for DP on pre-nvd0 cards: http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html Can you see if that helps you? Should apply to any 3.9+ kernel. Some highlights from the logs * Dual gpu system - intel + nouveau combo * Default GPU: intel(Haswell Desktop?), ddx version 2.99.904 * nouveau ddx version 1.0.9 * Mesa 9.2.1 * The following Xorg.log spam could be related (coming from xserver/randr) reporting 6 10 18 137 reporting 6 10 18 137 [nouveau] parsing EDID reporting 6 10 18 137 [intel](II) intel(0): resizing framebuffer to 1680x1050 have a master to look out for adjust shatters 0 1680 resize called 1680 1050 need to create shared pixmap 1reporting 6 10 18 137 reporting 6 10 18 137 reporting 6 10 18 137 ... reporting 6 10 18 137 [nouveau] parsing EDID reporting 6 10 18 137 ... (In reply to comment #1) > I see that you're using displayport. Is it an actual DP monitor, or are you > using a DP->xyz adapter? > > I recently posted a patch that should fix computing number of lanes/lane > speeds for DP on pre-nvd0 cards: > http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html > > Can you see if that helps you? Should apply to any 3.9+ kernel. I am not using the Dislay Port. My monitor works only on the VGA(The DVI port is not functional). So I have plugged it to DVI port via DVI->VGA adapter. (In reply to comment #1) > I see that you're using displayport. Is it an actual DP monitor, or are you > using a DP->xyz adapter? > > I recently posted a patch that should fix computing number of lanes/lane > speeds for DP on pre-nvd0 cards: > http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html > > Can you see if that helps you? Should apply to any 3.9+ kernel. I tried the patch but no luck :( (In reply to comment #4) > (In reply to comment #1) > > I see that you're using displayport. Is it an actual DP monitor, or are you > > using a DP->xyz adapter? > > > > I recently posted a patch that should fix computing number of lanes/lane > > speeds for DP on pre-nvd0 cards: > > http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html > > > > Can you see if that helps you? Should apply to any 3.9+ kernel. > > I tried the patch but no luck :( Yeah, if you're not using the DP port, I wouldn't expect it to. In hindsight, I realized that I misread your log -- you're using the DVI-I-1 connector, not DP-1. Unfortunately I don't have any great ideas atm... could you try to upgrade to the latest kernel and see if things have magically resolved themselves? Assuming that they haven't, can you attach a boot log with nouveau.config=PDISP=debug,VBIOS=trace drm.debug=0xe from the latest kernel? Perhaps it'll yield some interesting info. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #1) > > > I see that you're using displayport. Is it an actual DP monitor, or are you > > > using a DP->xyz adapter? > > > > > > I recently posted a patch that should fix computing number of lanes/lane > > > speeds for DP on pre-nvd0 cards: > > > http://lists.freedesktop.org/archives/nouveau/2014-February/016205.html > > > > > > Can you see if that helps you? Should apply to any 3.9+ kernel. > > > > I tried the patch but no luck :( > > Yeah, if you're not using the DP port, I wouldn't expect it to. In > hindsight, I realized that I misread your log -- you're using the DVI-I-1 > connector, not DP-1. > > Unfortunately I don't have any great ideas atm... could you try to upgrade > to the latest kernel and see if things have magically resolved themselves? > > Assuming that they haven't, can you attach a boot log with > > nouveau.config=PDISP=debug,VBIOS=trace drm.debug=0xe > > from the latest kernel? Perhaps it'll yield some interesting info. I will try that. One observatino is that the issue is not seen with Live CD. Is there a difference between the installed OS and the live CD? This surprised me, as I was expecting a smooth sail... (In reply to comment #6) > One observatino is that the issue is not seen with Live CD. > Is there a difference between the installed OS and the live CD? This > surprised me, as I was expecting a smooth sail... Depends on the Live CD, doesn't it :) In the Ubuntu case, I haven't the slightest clue. I'm guessing it has different versions of something -- would be good to figure out what versions it's running and what versions you're running on the installed system of: (a) kernel (b) xf86-video-nouveau (potentially called xorg-server-video-nouveau or something else along those lines) (c) libdrm (d) mesa (specifically the dri drivers) Those 4 pieces of software basically make up nouveau. I doubt the last 2 really matter for your case, but... no harm done grabbing versions. (In reply to comment #7) > (In reply to comment #6) > > One observatino is that the issue is not seen with Live CD. > > Is there a difference between the installed OS and the live CD? This > > surprised me, as I was expecting a smooth sail... > > Depends on the Live CD, doesn't it :) In the Ubuntu case, I haven't the > slightest clue. I'm guessing it has different versions of something -- would > be good to figure out what versions it's running and what versions you're > running on the installed system of: > > (a) kernel > (b) xf86-video-nouveau (potentially called xorg-server-video-nouveau or > something else along those lines) > (c) libdrm > (d) mesa (specifically the dri drivers) > > Those 4 pieces of software basically make up nouveau. I doubt the last 2 > really matter for your case, but... no harm done grabbing versions. I am for the time being giving up. I was unable to build a TOT kernel that would boot. For now, falling back to the onboard graphics card. Will try to post the findings when I get some time. Hope there is resolution for this issue, otherwise I will be left with a 100$ card that I cannot use :) No update in quite a while, marking invalid. If the issue persists with fresh software, feel free to reopen. |
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.