similar to: [Bug 96952] New: Noveau driver doesn't working well when in Kdenlive

When I tried to view Basil's video streams yesterday, it worked with Firefox 3.5.x on both Linux and Windows, but failed with Chrome 3.0 on Windows XP.? I get opposite results with http://www.citizenofplanetearth.org/citizen.ogg The only browser I've tried that plays that video is Chrome 3.0 on Windows XP. The <video> tag I'm using is about as simple as can be. <video

Hi! I am making some tests here, and i wanna miror all the traffic going to a ip from one interface to another ip. example: all packets going to 64.223.167.100 should be transmitted by ppp0 to internet and by eth2 to the adress 192.168.1.100. Someone know how can i do it using iptables or ip route/ip rule? Tks in advance! Fernando Favero _______________________________________________ LARTC

Hi everybody! I know this discussion list isn´t just about wondershaper, but i think someone can help me. I used to have a linux box running red hat 8, as firewall on my lan. I upgraded to debian 3.0 and tried to use the same wondershaper files under debian, but, when i run wondershaper on ppp0 device, it just stops transfering. Remember: its the same files i used with success under red hat 8.

I am trying to run an R script to create a .png file containing a tree map on a headless Linux server using Xvfb. When I try to run tmPlot, I get the following errors and warnings: Error in grid.Call(L_textBounds, as.graphicsAnnot(x$label), x$x, x$y, : X11 font -adobe-helvetica-%s-%s-*-*-%d-*-*-*-*-*-*-*, face 1 at size 9 could not be loaded Calls: tmPlot ... <Anonymous> ->

On 17/02/16 20:14, Fernando Favero wrote: > And, there is any problem if I change the uidNumber manually via ldbmodify > ?? > > On Wed, Feb 17, 2016 at 6:03 PM, Rowland penny <rpenny at samba.org> wrote: > >> On 17/02/16 19:53, Fernando Favero wrote: >> >>> On Wed, Feb 17, 2016 at 4:43 PM, Rowland penny <rpenny at samba.org> wrote: >>>

http://bugs.freedesktop.org/show_bug.cgi?id=20612 Summary: nouveau xv crash with BadMatch (invalid parameter attributes) Product: xorg Version: 7.4 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

On 17/02/16 19:53, Fernando Favero wrote: > On Wed, Feb 17, 2016 at 4:43 PM, Rowland penny <rpenny at samba.org> wrote: > >> have you given all your users a unique uidNumber inside the range you have >> set in smb.conf on the fileservers (2000-50000) ??? > > Hmmm, looking my ldap, I discovered that I have duplicated uidNumbers..... > would that be the problem???

On Thu, 17 Jul 2008 15:49:42 +0200 Micha? Wi?niewski <brylozketrzyn at gmail.com> wrote: > Hi > > I'm writing to you cause I want to help with noveau. I have GF 5200 card and I > can dump any data you need from it's registers, of course, avalaible to dump > with nvclock. Just write what test you want me to perform (if possible, with > explanations; I'll set

Hey Attila, I CC'd the nouveau mailing list. Although if you want help, you should probably provide more details (what version of mesa, etc.). St?phane On Sat, Feb 8, 2014 at 11:23 PM, Attila T?th <tothsoft at gmail.com> wrote: > Hi, > sorry, i have not better email adress of noveau team. Please send email - > mail feedback, that by moving on time in the movie, vdpau

Adding back the nouveau list... On Sun, Feb 9, 2014 at 8:28 AM, Attila T?th <tothsoft at gmail.com> wrote: > Linux mint 16 (64bit) > > Repo: Ubuntu X-SWAT <ubuntu-x at lists.ubuntu.com><ubuntu-x at lists.ubuntu.com> > Mesa: 10.2.0~git20140205.44338cd8-0ubuntu0sarvatt~saucy > libdrm: 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy > libg3dvl-mesa:

Context switching = very slow on NVIDIA. Don't do it if you can avoid it. Each context is like a megabyte of data, if not more. Each time it has to get saved off and restored. On Wed, Feb 8, 2017 at 1:38 PM, Sampsa Riikonen <sampsa.riikonen at iki.fi> wrote: > Dear Devs, > > (I hope this question is not that much OT for this list..) > > My question is about fast OpenGL

On Sat, 2020-06-13 at 20:29 -0500, Aditya Pakki wrote: > nv50_disp_atomic_commit() calls calls pm_runtime_get_sync and in turn > increments the reference count. In case of failure, decrement the > ref count before returning the error. > > Signed-off-by: Aditya Pakki <pakki001 at umn.edu> > --- > drivers/gpu/drm/nouveau/dispnv50/disp.c | 4 +++- > 1 file changed, 3

nv50_disp_atomic_commit() calls calls pm_runtime_get_sync and in turn increments the reference count. In case of failure, decrement the ref count before returning the error. Signed-off-by: Aditya Pakki <pakki001 at umn.edu> --- drivers/gpu/drm/nouveau/dispnv50/disp.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/dispnv50/disp.c

Thanks for the pointer. But I don't like this patch. If you find a bug, make a bug report or just fix it if you know the fix already. Or write something in IRC. Or write on the Mailing list as a general question or something else But I really don't agree on doing it this way. You would have needed like the same amount of time to actual fix the problem. Anyway, for adding a printk:

On Tue, Jul 11, 2017 at 2:08 PM, Mike Galbraith <efault at gmx.de> wrote: > On Tue, 2017-07-11 at 13:51 -0400, Ilia Mirkin wrote: >> Some details that may be useful in analysis of the bug: >> >> 1. lspci -nn -d 10de: > > 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) > 01:00.1 Audio device [0403]: NVIDIA

On Wed, Jul 12, 2017 at 7:25 AM, Mike Galbraith <efault at gmx.de> wrote: > On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote: >> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: >> > >> > Some display stuff did change for 4.13 for GM20x+ boards. If it's not >> > too much trouble, a bisect would be pretty useful. >> >> Bisection

On 7/12/17 7:19 PM, Mike Galbraith wrote: > On Wed, 2017-07-12 at 07:37 -0400, Ilia Mirkin wrote: >> On Wed, Jul 12, 2017 at 7:25 AM, Mike Galbraith <efault at gmx.de> wrote: >>> On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote: >>>> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: >>>>> Some display stuff did change for 4.13 for

On 7/14/17 3:41 PM, Mike Galbraith wrote: > On Fri, 2017-07-14 at 15:36 +0200, Mike Galbraith wrote: >>  All DRM did was to slip a >> WARN_ON_ONCE() that nouveau triggers into a kernel module where such >> things no longer warn, they blow the box out of the water. > BTW, turn that irksome WARN_ON_ONCE() in drivers/gpu/drm/drm_vblank.c > into a WARN_ONCE(), and all is

On Fri, Jul 14, 2017 at 11:15 AM, Mike Galbraith <efault at gmx.de> wrote: > On Fri, 2017-07-14 at 17:10 +0200, Karol Herbst wrote: >> Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE >> usage we could convert to WARN_ONCE? > > Shooting the messenger is generally considered uncool :) That's never stopped it from being a popular practice...

The conversion is a nice catch, but i'd like to have a bit more context, see below! With a better description: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> On 7/14/17 5:10 PM, Karol Herbst wrote: > Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE > usage we could convert to WARN_ONCE? > > Reviewed-By: Karol Herbst <karolherbst at