similar to: Suggestion for the list manager(s)

Hiya, I sent the enclosed email to linux-kernel before realizing that it would, perhaps, be more proper to send it here, which I hereby do. I shall be happy to try out any and all patches. Best regards, Sune M?lgaard -------- Original Message -------- Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing Date: Tue, 12 Mar 2013 19:57:55 +0100 From: Sune M?lgaard <sune at

https://bugs.freedesktop.org/show_bug.cgi?id=62351 Priority: medium Bug ID: 62351 Assignee: nouveau at lists.freedesktop.org Summary: Segfault in nouveau_dri.so Severity: major Classification: Unclassified OS: Linux (All) Reporter: sune at molgaard.org Hardware: x86-64 (AMD64) Status: NEW

Hi all. New to the list, so my apologies, if I am out of line. I was told, that window shading (rolling them up into the title bar) is on the TODO-list. As I normally rely heavily on this feature, I just wondered which priority it has, i.e. when I can expect it. I rely solely on your kindness for this, as I am neither versed in C nor graphical effects, and thus cannot provide code of my own.

My thanks still stands, however, when one reloads compiz, any shaded windows are closed. Just wanted to let you know Best regards, Sune M?lgaard -- The best way to accelerate a Macintosh is at 9.8m sec sec. - Marcus Dolengo

Actually GM108 is not one of the recognized chips. Someone needs to go through and check that its goldens didn't change. Nobody's done that. See https://bugs.freedesktop.org/show_bug.cgi?id=89558 On Thu, Mar 31, 2016 at 4:57 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Hello, > > Acceleration support for GM107 was merged in kernel 4.1, and modesetting > support

Hiya, Is there any change for Quadro K620M support at some point in time, and what can I do to help, apart from the info below? Best regards, Sune Mølgaard dmesg |grep -i nouveau [ 1.164919] nouveau 0000:08:00.0: unknown chipset (1183a0a2) [ 1.164943] nouveau: probe of 0000:08:00.0 failed with error -12 lspci|grep -i nvidi 08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

Hello, A patch was merged yesterday to recognise GM108 (see https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). I guess it will make it into 4.7. Pierre On 12:14 PM - Apr 18 2016, Sune Mølgaard wrote: > Is there anything I can do in this regard? > > /smo > > On 2016-03-31 23:12, Pierre Moreau wrote: > > Oh, hum, GM108 is NV118 and not

Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere

Hello, Acceleration support for GM107 was merged in kernel 4.1, and modesetting support was added to 3.15. Which kernel version did you try? The GM108 chipset seems to be recognised since at least 2015/08/20. Regards, Pierre Moreau On 02:55 PM - Mar 29 2016, Sune Mølgaard wrote: > Hiya, > > Is there any change for Quadro K620M support at some point in time, and > what can I do to

Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! SMF from the bug report seemed to have some working setup, and since he didn't pinged back, I guess it's working nicely. But some more checking might still be needed? On 04:59 PM - Mar 31 2016, Ilia Mirkin wrote: > Actually GM108 is not one of the recognized chips. Someone needs to go > through and check that its goldens

Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with

you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in

Greetings, On the official documentation page, http://www.xiph.org/ogg/vorbis/docs.html, there are links to the documents describing the released libraries, ie. libvorbis, vorbisfile and vorbisenc. However, the first one is not a link at all, although I seem to remember that it was so earlier. I also downloaded the SDK for Mac OSX, which sorta contains a documentation for libvorbis, but

Many people prefer to use LMTP for delivery from postfix for better efficiency but X-Original-to header support still missing after many years. One affect of this is need to set sieve_vacation_dont_check_recipient = yes which violate Sieve standard and cause auto-replyies sent to messages that should not happen. Or abandon LMTP. or abandon postfix?? So while feature request is stalled are

Hi, I''m new to shorewall and iptables. I installed shorewalls ver. 2.2 two days ago and it''s working now, but I have some questions concerning pppoe. I have my ISP''s connection to internet trough PPPoE over an ethernet card. On the ethernet card I have a static IP and I have access to all other ISP''s clients wich are in the same subnet (it''s a small

also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.

Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to

On 2019-05-22 08:18, Tuomo Soini via dovecot wrote: > On Tue, 21 May 2019 18:24:46 +0000 > MRob via dovecot <dovecot at dovecot.org> wrote: > >> Many people prefer to use LMTP for delivery from postfix for better >> efficiency but X-Original-to header support still missing after many >> years. One affect of this is need to set >>

I upgraded from Samba 2.2.8a to Samba 3.0.1, since doing I'm having problems with my SQL Server and applications running on Windows 2000. When a users (running a windows 98 client) attempts to query the SQL Server, either using ODBC (even the Test Sources) or an application that uses the db. I get a login failed from the sql app, and from the ODBC I get: "Login failed for user