similar to: gtx 650 ti boost oc random pixels problem

Displaying 20 results from an estimated 500 matches similar to: "gtx 650 ti boost oc random pixels problem"

2017 Jul 16
0
gtx 650 ti boost oc random pixels problem
Hello i have nvidia gtx 650 ti boots oc 2gb with 2 monitors and gt 240 for xen emulation .My screen displays random pixels and freeze in random times . I don't found errors in /var/log/syslog and /var/log/kern.log its nouveau error on nvidia-driver works fine . Sometimes its freeze. sometimes there are font errors. uname -a Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)
2017 Jul 15
0
gtx 650 ti boost oc random pixels problem
Hello i have nvidia gtx 650 ti boots oc 2gb with 2 monitors and gt 240 for xen emulation .My screen displays random pixels and freeze in random times . I don't found errors in /var/log/syslog and /var/log/kern.log its nouveau error on nvidia-driver works fine . sometimes there are font errors. uname -a Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux
2019 Jul 03
1
[PATCH 20/22] mm: move hmm_vma_fault to nouveau
On 6/30/19 11:20 PM, Christoph Hellwig wrote: > hmm_vma_fault is marked as a legacy API to get rid of, but quite suites > the current nouvea flow. Move it to the only user in preparation for I didn't quite parse the phrase "quite suites the current nouvea flow." s/nouvea/nouveau/ > fixing a locking bug involving caller and callee. > > Signed-off-by: Christoph
2009 Nov 14
2
[Bug 25088] New: Nouveau and KMS doesn't support dual monitors
http://bugs.freedesktop.org/show_bug.cgi?id=25088 Summary: Nouveau and KMS doesn't support dual monitors Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at
2017 May 06
0
NV130 - gtx 1050 ti
First things first -- I've alluded to this before, but let me be clear -- there is no global database that contains monitor-specific information which is used by any linux drivers. Please forget any notions you had of such a thing existing or being used. The information comes from the EDID blob supplied by the monitor. Presumably hwinfo has a primitive EDID parser, which is where that
2017 Aug 15
1
[Bug 102236] New: Pcie link speed is gen2 instead of gen3
https://bugs.freedesktop.org/show_bug.cgi?id=102236 Bug ID: 102236 Summary: Pcie link speed is gen2 instead of gen3 Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee:
2017 May 04
2
NV130 - gtx 1050 ti
This is sort of working -- but I can't get it to do a 4k output. Not sure how the monitor resolution is detected - This monitor is supposed to do 3480x1200 60hz 4:4:4 But the info I get from hwinfo is different. How does nouveau get this information? If it is from an ID - with a list - the list is probably is wrong. # hwinfo --monitor 95: None 00.1: 10002 LCD Monitor [Created at
2010 May 21
2
[Bug 28196] New: Nouveau only loads correct when starting X with nvidia first
https://bugs.freedesktop.org/show_bug.cgi?id=28196 Summary: Nouveau only loads correct when starting X with nvidia first Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2012 Jul 05
3
[REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf
Hi Ben, Dave, Since 3.5-rc0, I have been experiencing occasional screen corruption on my MacBookAir3,1, using a GeForce 320M (nv50, 0xaf). The X driver version is xf86-video-nouvea-1.0.1-1 (arch). I do not know what the root problem is, but I have been able to isolate the symptoms to the usage of nva3_copy.c. The patch below is the least intrusive way I could find which kills the symptoms.
2014 Sep 25
4
[5/5] ARM: tegra: jetson-tk1: enable GK20A GPU
On Thu, Sep 25, 2014 at 09:48:01AM -0600, Stephen Warren wrote: > On 09/25/2014 07:27 AM, Sjoerd Simons wrote: > >Playing a bit with todays linux-next on my jetson, it seems this patch is > >still required for enabling the GPU. Is there anything blocking it (firmware > >not available yet in liux-firmware?) > > I think initially I was waiting for the DRM patch
2014 Sep 25
0
[5/5] ARM: tegra: jetson-tk1: enable GK20A GPU
On 09/25/2014 07:27 AM, Sjoerd Simons wrote: > Playing a bit with todays linux-next on my jetson, it seems this patch is > still required for enabling the GPU. Is there anything blocking it (firmware > not available yet in liux-firmware?) I think initially I was waiting for the DRM patch "drm/nouvea: support for probing platform devices" to be applied, but it looks like
2014 Sep 25
0
[5/5] ARM: tegra: jetson-tk1: enable GK20A GPU
On 09/25/2014 10:41 AM, Thierry Reding wrote: > On Thu, Sep 25, 2014 at 09:48:01AM -0600, Stephen Warren wrote: >> On 09/25/2014 07:27 AM, Sjoerd Simons wrote: >>> Playing a bit with todays linux-next on my jetson, it seems this patch is >>> still required for enabling the GPU. Is there anything blocking it (firmware >>> not available yet in liux-firmware?)
2014 Sep 25
0
[5/5] ARM: tegra: jetson-tk1: enable GK20A GPU
On Thu, 2014-09-25 at 18:41 +0200, Thierry Reding wrote: > On Thu, Sep 25, 2014 at 09:48:01AM -0600, Stephen Warren wrote: > > On 09/25/2014 07:27 AM, Sjoerd Simons wrote: > > >Playing a bit with todays linux-next on my jetson, it seems this patch is > > >still required for enabling the GPU. Is there anything blocking it (firmware > > >not available yet in
2019 Jul 03
2
[PATCH 20/22] mm: move hmm_vma_fault to nouveau
On Mon, Jul 01, 2019 at 08:20:18AM +0200, Christoph Hellwig wrote: > hmm_vma_fault is marked as a legacy API to get rid of, but quite suites > the current nouvea flow. Move it to the only user in preparation for > fixing a locking bug involving caller and callee. > > Signed-off-by: Christoph Hellwig <hch at lst.de> > drivers/gpu/drm/nouveau/nouveau_svm.c | 54
2009 Sep 10
1
[Bug 23830] New: nouvea modules on 2.6.31-rc6 failed
http://bugs.freedesktop.org/show_bug.cgi?id=23830 Summary: nouvea modules on 2.6.31-rc6 failed Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:
2019 Jul 01
0
[PATCH 20/22] mm: move hmm_vma_fault to nouveau
hmm_vma_fault is marked as a legacy API to get rid of, but quite suites the current nouvea flow. Move it to the only user in preparation for fixing a locking bug involving caller and callee. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/nouveau/nouveau_svm.c | 54 ++++++++++++++++++++++++++- include/linux/hmm.h | 54 --------------------------- 2
2013 Nov 26
0
[Bug 70452] [NV43] Graphical corruption after resume from suspend or hibernation
https://bugs.freedesktop.org/show_bug.cgi?id=70452 --- Comment #6 from Moi Jaiunvelo <moijaiunvelo at gmail.com> --- I tried to backport libdrm from debian/sid and it fixed the graphical corruption. More precisely for users who would like to reproduce it, I backported libdrm2, libdrm-intel1, libdrm-radeon1 and libdrm-nouveau2 from debian/sid to have them in 2.4.49-1 version. Start-Date:
2018 Sep 26
3
[Bug 108080] New: GK106 [GeForce GTX 660] System Freeze - warp 3d0009 [ILLEGAL_INSTR_ENCODING]
https://bugs.freedesktop.org/show_bug.cgi?id=108080 Bug ID: 108080 Summary: GK106 [GeForce GTX 660] System Freeze - warp 3d0009 [ILLEGAL_INSTR_ENCODING] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: critical Priority: medium
2016 Nov 29
0
[ANNOUNCE] libdrm 2.4.74
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben Widawsky (1): intel: Add Geminilake PCI IDs Christian Gmeiner (4): etnaviv: add API to get drm fd from etna_device etnaviv: add API to create etna_device from private dup() fd etnaviv: change get_abs_timeout(..) to use ns. etnaviv: add etna_pipe_wait_ns(..) Emil Velikov (2): automake: make the build less
2017 Sep 26
5
dfs links anywhere?
(Let's keep this on the list) Aurélien Aptel via samba <samba at lists.samba.org> writes: > Chad William Seys <cwseys at physics.wisc.edu> writes: >> Somehow the destination having 'msdfsroot yes' prevents the cifs kernel >> module from following the link. I've taken a look at your traces and right off the bat I see things like this: [...]