similar to: Nouveau Digest, Vol 104, Issue 60, GV-N430OC-1GL is needed to work under kernel 2.4

Hi Ben, Karol and Tom are seeing this on init with a nvif-enabled kernel + libdrm. What are we doing wrong? I think that route == NVIF_IOCTL_V0_ROUTE_NVIF (== 0), while owner is apparently 1, whatever that is. [362619.242238] nouveau: glxgears[6096]:00000000:00000000: ioctl: size 32 [362619.242240] nouveau: glxgears[6096]:00000000:00000000: ioctl: vers 0 type 00 object 0000000000000000 owner 00

Hi, I'm planning to use a K2200 board with an Eizo monitor at 10 bits color depth together with a standard monitor on a debian sid system. Is it possible to have one monitor with 8, the other with 10 bit colors? Is it possible to configure such a setup choosing for each monitor a different resolution (dpi) such that a window would not change size when moved from one monitor to the other?

https://bugs.freedesktop.org/show_bug.cgi?id=95193 Bug ID: 95193 Summary: Nouveau not working with Quadro K2200 (NV117) and Debian Wheezy Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=107735 Bug ID: 107735 Summary: Xorg stops responding when running DRI_PRIME=1 glxgears Product: Mesa Version: 18.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi All, So I've been working~w banging my head against the nv46 vblank bug again and I've been finding out some interesting things. This is all using the latest kernel + ddx + mesa code. All of this was tested with *cold* (power removed from wall outlet for 20 seconds) boots in between the scenarios because this is really weird, all boots where into text mode. Scenario 1: a) startx

Listmates, No response from the suse list, so I am trying here. I bought a new HIS Radeon x1650 card for my daughter's computer, and I cannot get the card to work with compiz. I thought I knew the fglrx driver pretty well, but I am stumped here. The card has 512M of Ram and sits in the AGP slot of an MSI KM2M board running openSuSE 11.0/KDE 3.59 and compiz-0.7.6-16.1. All bios setting are

Hi I found a way to reliably reproduce PFIFO CACHE_ERRORS, but I don't see why. How to reproduce them: 1) Run a couple of glxinfo loops - 3 is usually enough. while [ true ]; do nvgl glxinfo >/dev/null 2>/dev/null; done 2) Run glxgears. 3) If you can't see it now, resize glxgears window or add more glxinfos. Note: you need at least 2 CPUs. Usually the error looks like this

Hi there, last week I installed Ubuntu Gnome 14.04 on my Thinkpad W530. It has the following specifications: Intel Core i7-3820QM Intel HD 4000 and nVidia Quadro K2000M 15,6" FHD RGB 1920x1080 With "Optimus" enabled in the BIOS, I am able to use the external monitor via VGA-1-2. But there are refresh problems only on the external monitor: Mouse traces, parts of a window remain on

On 04.11.2015 12:27, poma wrote: > On 04.11.2015 11:57, Martin Peres wrote: >> On 02/11/15 08:28, poma wrote: >>> An interesting results. >>> >>> DRI2: >>> >>> $ vblank_mode=0 glxgears >>> ATTENTION: default value of option vblank_mode overridden by environment. >>> 6321 frames in 5.0 seconds = 1264.103 FPS >>> 6380

Hi, While trying to reproduce: https://bugzilla.redhat.com/show_bug.cgi?id=1325667 I also gave glxgears a quick test with mesa master, this resulted in the following errors being printed to the terminal from which glxgears was started : unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader param 17 unknown fragment shader

https://bugs.freedesktop.org/show_bug.cgi?id=53219 Bug #: 53219 Summary: glxgears crashes kernel Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=69952 Priority: medium Bug ID: 69952 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA] Xorg crash+restart after glxgears on 3.12-rc2 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

On 2020-05-20 4:43 p.m., Christian K?nig wrote: > Am 13.05.20 um 13:03 schrieb Christian K?nig: >> Unfortunately AGP is still to widely used as we could just drop >> support for using its GART. >> >> Not using the AGP GART also doesn't mean a loss in functionality since >> drivers will just fallback to the driver specific PCI GART. >> >> For now

Wine's FAQ has the following question under 7.3: > I want my Windows application to be able to launch a Linux > application to open documents Answer: > You can start Linux applications directly from Wine only if you > specify full path or use shell: > /usr/bin/glxgears > # or > /bin/sh -c glxgears This advice is wrong or at best incomplete. I have tried it out

Am 13.05.20 um 13:03 schrieb Christian K?nig: > Unfortunately AGP is still to widely used as we could just drop support for using its GART. > > Not using the AGP GART also doesn't mean a loss in functionality since drivers will just fallback to the driver specific PCI GART. > > For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support

Am 20.05.20 um 18:25 schrieb Michel D?nzer: > On 2020-05-20 4:43 p.m., Christian K?nig wrote: >> Am 13.05.20 um 13:03 schrieb Christian K?nig: >>> Unfortunately AGP is still to widely used as we could just drop >>> support for using its GART. >>> >>> Not using the AGP GART also doesn't mean a loss in functionality since >>> drivers will

On 05/31/2016 08:15 AM, Johnny Hughes wrote: > On 05/31/2016 06:09 AM, isdtor wrote: >> >> Ever since I upgraded to CentOS 6.8, some software has stopped working alogether. This is related to OpenGL/mesa and can be demonstrated with glxgears: >> >> $ glxgears >> libGL error: No matching fbConfigs or visuals found >> libGL error: failed to load driver: swrast

Am 20.05.20 um 18:18 schrieb Alex Deucher: > On Wed, May 20, 2020 at 10:43 AM Christian K?nig > <ckoenig.leichtzumerken at gmail.com> wrote: >> Am 13.05.20 um 13:03 schrieb Christian K?nig: >>> Unfortunately AGP is still to widely used as we could just drop support for using its GART. >>> >>> Not using the AGP GART also doesn't mean a loss in

https://bugs.freedesktop.org/show_bug.cgi?id=73445 Priority: medium Bug ID: 73445 Assignee: nouveau at lists.freedesktop.org Summary: [NV4E] regression with 3.13 -rcX: glxgears etc. hard lockup/freezes machine, on 3.12 everything works Severity: critical Classification: Unclassified OS: Linux (All)

On Wed, May 20, 2020 at 10:43 AM Christian K?nig <ckoenig.leichtzumerken at gmail.com> wrote: > > Am 13.05.20 um 13:03 schrieb Christian K?nig: > > Unfortunately AGP is still to widely used as we could just drop support for using its GART. > > > > Not using the AGP GART also doesn't mean a loss in functionality since drivers will just fallback to the driver