similar to: [Bug 51477] New: bad/missing graphics with NV11 / GeForce 2MX/MX400

Displaying 20 results from an estimated 3000 matches similar to: "[Bug 51477] New: bad/missing graphics with NV11 / GeForce 2MX/MX400"

2018 May 31
1
NVIDIA binary on CentOS 7.5 and NOUVEAU
I have NOUVEAU driver disabled however its "showing" in my X log file. [ 140.086] (II) NVIDIA dlloader X Driver 390.59 Wed May 9 21:30:06 PDT 2018 [ 140.086] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 140.086] (II) NOUVEAU driver [ 140.087] (II) NOUVEAU driver for NVIDIA chipset families : [ 140.087] RIVA TNT (NV04) [ 140.087] RIVA TNT2
2013 Dec 12
5
[Bug 72651] New: [NV11] Hang during suspend/resume on Geforce 2 MX200 & MX400
https://bugs.freedesktop.org/show_bug.cgi?id=72651 Priority: medium Bug ID: 72651 Assignee: nouveau at lists.freedesktop.org Summary: [NV11] Hang during suspend/resume on Geforce 2 MX200 & MX400 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)
2009 Dec 30
4
[PATCH 1/3] nv50: remove vtxbuf stateobject after a referenced vtxbuf is mapped
- This avoids problematic "reloc'ed while mapped" messages and some associated corruption as well. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++ src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++ src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++
2010 Apr 22
1
nv20tcl and renouveau questions
First some data errors I get with both nv20 exa and nv20 dri/mesa. 1. RT_FORMAT LINEAR + X8R8G8B8 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x00800080:0x00000105 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x01000100:0x00000105 LINEAR + A8R8G8B8 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x01000100:0x00000108 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x00800080:0x00000108 The only value I found in renouveau dump
2009 Dec 21
2
[PATCH 1/2] Unreference state/buffer objects on context/screen destruction
- unreference state objects so that buffer objects are unreferenced and eventually destroyed - free channel at screen's destruction Index: nv50/nv50_screen.c =================================================================== --- nv50/nv50_screen.c (wersja 32083) +++ nv50/nv50_screen.c (kopia robocza) @@ -162,7 +162,22 @@ nv50_screen_destroy(struct pipe_screen *pscreen) { struct
2019 Jun 19
3
nouveau: DRM: GPU lockup - switching to software fbcon
On Wed, Jun 19, 2019 at 1:48 AM Sergey Senozhatsky <sergey.senozhatsky.work at gmail.com> wrote: > > On (06/19/19 01:20), Ilia Mirkin wrote: > > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky > > <sergey.senozhatsky.work at gmail.com> wrote: > > > > > > On (06/14/19 11:50), Sergey Senozhatsky wrote: > > > > dmesg > > > >
2013 Sep 05
6
[PATCH 1/7] drm/nouveau: remove prototype for non-existent nouveau_connector_bpp
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/nouveau_connector.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.h b/drivers/gpu/drm/nouveau/nouveau_connector.h index 6e399aa..4cefce3 100644 --- a/drivers/gpu/drm/nouveau/nouveau_connector.h +++ b/drivers/gpu/drm/nouveau/nouveau_connector.h @@ -107,7 +107,4
2014 Mar 03
2
TV-Out on a GeForce 2MX supported?
Hello, I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the TV-Out. Is the TV-Out on this card supported by Nouveau? I read on the feature matrix something that the TV-Out is only supported for some Chrontel chips, furthermore xrandr -q shows me only the DVI connection (in fact it's VGA, not DVI), but not the S-Video connection. If not supported, is this planned for future
2008 Feb 06
15
[Bug 14393] New: NV11 card is not detected properly by nouveau on big-endian box
http://bugs.freedesktop.org/show_bug.cgi?id=14393 Summary: NV11 card is not detected properly by nouveau on big- endian box Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:
2008 Nov 11
2
Memory corruption on Gallium window resize, diagnosed?
Hi, I've been playing with nouveau/mesa branch gallium-0.1, trying to get trivial/tri working on nv20 (with nv10 code). When ever I resize the window, it ends up in an assert failure: #0 0xf790744f in _debug_assert_fail (expr=0xf791908f "0", file=0xf7919050 "nv20_state_emit.c", line=139, function=0xf7919034 "nv20_state_emit_framebuffer") at p_debug.c:335
2012 Dec 14
7
[Bug 58316] New: fedora 17 kernel 3.7.0-1.PAE failed plymouth and enable msi error
https://bugs.freedesktop.org/show_bug.cgi?id=58316 Priority: medium Bug ID: 58316 Assignee: nouveau at lists.freedesktop.org Summary: fedora 17 kernel 3.7.0-1.PAE failed plymouth and enable msi error QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux
2014 Feb 12
2
[PATCH v2] drm/nouveau: support for platform devices
On 12/02/14 05:38, Alexandre Courbot wrote: > Upcoming mobile Kepler GPUs (such as GK20A) use the platform bus instead > of PCI to which Nouveau is tightly dependent. This patch allows Nouveau > to handle platform devices by: > > - abstracting PCI-dependent functions that were typically used for > resource querying and page mapping, > - introducing a nv_device_is_pci()
2014 Feb 11
2
[PATCH] drm/nouveau: support for platform devices
On Mon, Feb 10, 2014 at 8:50 PM, Thierry Reding <thierry.reding at gmail.com> wrote: > On Mon, Feb 10, 2014 at 02:53:00PM +0900, Alexandre Courbot wrote: > [...] >> diff --git a/drivers/gpu/drm/nouveau/core/engine/device/base.c b/drivers/gpu/drm/nouveau/core/engine/device/base.c > [...] >> +resource_size_t >> +nv_device_resource_start(struct nouveau_device *device,
2009 Nov 05
6
Some cosmetic NV10TCL method changes.
The attached patch does the cosmetic renouveau.xml changes I proposed. I'm about to reply myself with some other patches to update libdrm and then fix the API break up. -------------- next part -------------- A non-text attachment was scrubbed... Name: rename_some_nv10tcl_methods.patch Type: text/x-diff Size: 2507 bytes Desc: not available Url :
2016 Jul 06
2
Nouveau fails to initialize G94GL / Quadro-FX1800 on aarch64 board
Hi, I am trying to use a G94GL based card (Quadro FX1800) on an arm64/aarch64 based board. As the board is running linux-4.1.8, I had to apply the following patches to get the kernel module / drm working: https://lkml.org/lkml/2015/5/15/83 https://lists.freedesktop.org/archives/dri-devel/2015-July/085449.html So far everything seems to work, the card modesets correctly, and the kernel log also
2014 May 20
2
Ubuntu client ddns failure
Hi I'm trying to get an Ubuntu 14.04 client to update its rr to a working bind dns DC with Samba 4.1.7. The setup is the same as with our openSUSE clients with sssd 1.11.15 sssd.conf id_provider = ad auth_provider = ad access_provider = ad ldap_id_mapping = False /etc/hosts 127.0.0.1 lubuntu-laptop.hh3.site lubuntu-laptop 127.0.1.1 localhost But it is sending a request for the wrong
2009 May 03
1
blank screen with nouveau
I install nouveau from git (from overlay "nouveau"). But when i try start Xorg i have black screen and blinking cursor. I use FX5200 (NV34). Xorg.log X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.29-gentoo-r1 i686 Current Operating System: Linux localhost 2.6.29-gentoo-r2 #1 SMP PREEMPT Sat May 2 14:23:23 MSD 2009
2019 Sep 23
8
[PATCH 0/8] Add workaround for fixing runpm
Changes since last sent: * add a patch to set the device into DRM_SWITCH_POWER_CHANGING state (can be dropped actually, I thought I was needing it, came up with a different approach and forgot to delete it, doesn't hurt though) * expose information about runtime suspending to nvkm so that we can run the pcie workaround only on runtime suspend Karol Herbst (8): pci: disable ASPM
2014 May 20
1
ddns failure on Ubuntu client
Hi I'm trying to get an Ubuntu 14.04 client to update its rr to a working bind dns DC with Samba 4.1.7. The setup is the same as with our openSUSE clients with sssd 1.11.15 sssd.conf id_provider = ad auth_provider = ad access_provider = ad ldap_id_mapping = False /etc/hosts 127.0.0.1 lubuntu-laptop.hh3.site lubuntu-laptop 127.0.1.1 localhost But it is sending a request for the wrong
2014 Feb 15
3
[RFC PATCH] drm/nouveau: split off nvc0 compilation
So... I was wondering what the impact of splitting up the card compilation by e.g. generation would be. Depending on the split things would get fairly intertwined, so I thought I'd start small. This just splits NVC0 from everything else. I figure that for the people this matters the most to, NVC0 is the least relevant card -- people with sub-1GB of RAM, older hardware. With my config options