similar to: [Bug 80769] New: [NVD9] GF119M boot hang with 3.15.2

Displaying 20 results from an estimated 600 matches similar to: "[Bug 80769] New: [NVD9] GF119M boot hang with 3.15.2"

2004 Nov 05
2
Problems with the sort function!?
Hello All. I am running R 2.0.0 with a Win XP operating system. The same problem occured with R 1.9.1 but not with R.1.3.1 on a Win NT computer. My request is about the following problem with the sort function: The vector price is a vector of 789 asset prices of the following form, > mode(price) [1] "numeric" > price[1:10] [1] 1.1315 1.1314 1.1313 1.1314 1.1315 1.1316 1.1315
2012 Sep 13
1
[Bug 43731] New: No support for DP on NVD9
https://bugs.freedesktop.org/show_bug.cgi?id=43731 Bug #: 43731 Summary: No support for DP on NVD9 Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2015 Feb 09
17
[Bug 89047] New: linux-3.19 nvd9 Invalid rom content
https://bugs.freedesktop.org/show_bug.cgi?id=89047 Bug ID: 89047 Summary: linux-3.19 nvd9 Invalid rom content Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at
2012 Sep 07
4
[Bug 54646] New: i2c failure on Quadro NVS 4200M (GF119 (NVD9))
https://bugs.freedesktop.org/show_bug.cgi?id=54646 Bug #: 54646 Summary: i2c failure on Quadro NVS 4200M (GF119 (NVD9)) Classification: Unclassified Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2014 May 06
1
[Bug 78361] New: [NVD9] Screen frozen on resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=78361 Priority: medium Bug ID: 78361 Assignee: nouveau at lists.freedesktop.org Summary: [NVD9] Screen frozen on resume from suspend QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: R.Palmer at
2020 Jul 21
0
[PATCH -next] drm/nouveau/kms/nvd9-: Fix file release memory leak
Reviewed-by: Lyude Paul <lyude at redhat.com> Thanks! On Tue, 2020-07-21 at 15:17 +0000, Wei Yongjun wrote: > When using single_open() for opening, single_release() should be > used instead of seq_release(), otherwise there is a memory leak. > > Fixes: 12885ecbfe62 ("drm/nouveau/kms/nvd9-: Add CRC support") > Reported-by: Hulk Robot <hulkci at huawei.com>
2015 Dec 09
0
[Bug 56615] [NVD9] Unable to start X on ThinkPad T420s laptop
I'm here and alive. I submitted my problem somewhere and have been getting emails related to nouveau ever since. Yes there is a craigcgarner at gmail.com I am glad to be following along with these bugs as they directly affect me and my system :) This where I reported the problem nouveau at lists.freedesktop.org The other buglist just started ? Thank you, Craig On Wed, Dec 9, 2015 at
2014 Jun 08
5
[Bug 79795] New: [NVD9] No devices detected
https://bugs.freedesktop.org/show_bug.cgi?id=79795 Priority: medium Bug ID: 79795 Assignee: nouveau at lists.freedesktop.org Summary: [NVD9] No devices detected QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mail at tcrueger.de
2012 Oct 13
6
[Bug 55948] New: [nvd9 optimus] drm/nouveau/bios: attempt to fetch entire acpi rom image in one shot breaks module load
https://bugs.freedesktop.org/show_bug.cgi?id=55948 Priority: medium Bug ID: 55948 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 optimus] drm/nouveau/bios: attempt to fetch entire acpi rom image in one shot breaks module load QA Contact: xorg-team at lists.x.org Severity: major Classification:
2020 Oct 06
0
[RFC PATCH v2 1/3] drm/nouveau/kms/nvd9-: Introduce some kernel-docs for CRC support
This is not complete documentation, but covers the pieces I read through while reviewing the IGT CRC tests for nouveau. It covers the nouveau-specific debugfs file, an overview of why the code is more complicated than the DRM display CRC support documentation would lead one to expect, and the nv50_crc_func vtable. Many of the details were gleaned from Lyude's commit message, but I think
2013 Nov 15
8
[Bug 71662] New: [nvd9 regression] 3d application hang
https://bugs.freedesktop.org/show_bug.cgi?id=71662 Priority: medium Bug ID: 71662 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 regression] 3d application hang Severity: normal Classification: Unclassified OS: All Reporter: jano.vesely at gmail.com Hardware: Other Status: NEW
2013 Nov 15
37
[Bug 71659] New: [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000
https://bugs.freedesktop.org/show_bug.cgi?id=71659 Priority: medium Bug ID: 71659 Assignee: nouveau at lists.freedesktop.org Summary: [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified
2018 Sep 18
4
[PATCH 3/6] drm/i915: Leave intel_conn->mst_port set, use mst_port_gone instead
Currently we set intel_connector->mst_port to NULL to signify that the MST port has been removed from the system so that we can prevent further action on the port such as connector probes, mode probing, etc. However, we're going to need access to intel_connector->mst_port in order to fixup ->best_encoder() so that it can always return the correct encoder for an MST port to prevent
2020 Jun 29
0
[PATCH] drm/nouveau/kms/nvd9-: Fix disabling CRCs alongside OR reprogramming
While I had thought I'd tested this before, it looks like this one issue slipped by my original CRC patches. Basically, there seem to be a few rules we need to follow when sending CRC commands to the display controller: * CRCs cannot be both disabled and enabled for a single head in the same flush * If a head with CRC reporting enabled switches from one OR to another, there must be a
2018 Sep 19
1
[PATCH v2 3/6] drm/i915: Leave intel_conn->mst_port set, use mst_port_gone instead
Currently we set intel_connector->mst_port to NULL to signify that the MST port has been removed from the system so that we can prevent further action on the port such as connector probes, mode probing, etc. However, we're going to need access to intel_connector->mst_port in order to fixup ->best_encoder() so that it can always return the correct encoder for an MST port to prevent
2020 Feb 02
3
CentOS 8.1 and NVIDIA support
Does CentOS 8.1 support OLDER generate NVIDIA ? Like NVIDIA Corporation GF119M [GeForce GT 520M] I'm looking for hardware acceleration H264 type support. Thanks, Jerry
2018 Sep 21
1
[Intel-gfx] [PATCH 3/6] drm/i915: Leave intel_conn->mst_port set, use mst_port_gone instead
On Fri, 2018-09-21 at 11:27 +0200, Daniel Vetter wrote: > On Tue, Sep 18, 2018 at 07:06:19PM -0400, Lyude Paul wrote: > > Currently we set intel_connector->mst_port to NULL to signify that the > > MST port has been removed from the system so that we can prevent further > > action on the port such as connector probes, mode probing, etc. > > However, we're going to
2019 May 02
4
[PATCH v3 04/10] drm: Convert connector_helper_funcs->atomic_check to accept drm_atomic_state
From: Sean Paul <seanpaul at chromium.org> Everyone who implements connector_helper_funcs->atomic_check reaches into the connector state to get the atomic state. Instead of continuing this pattern, change the callback signature to just give atomic state and let the driver determine what it does and does not need from it. Eventually all atomic functions should do this, but that's
2016 Oct 27
9
[Bug 98457] New: [NVD9] GPU lockup after resume from hibernation with Nouveau driver and firmware-nonfree
https://bugs.freedesktop.org/show_bug.cgi?id=98457 Bug ID: 98457 Summary: [NVD9] GPU lockup after resume from hibernation with Nouveau driver and firmware-nonfree Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium
2014 Jan 18
7
[Bug 73770] New: nouveau doesn't setup 1920x1200 mode on HDMI properly
https://bugs.freedesktop.org/show_bug.cgi?id=73770 Priority: medium Bug ID: 73770 Assignee: nouveau at lists.freedesktop.org Summary: nouveau doesn't setup 1920x1200 mode on HDMI properly QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: All Reporter: martix.cz at