similar to: nVidia hardware donations available

I finally got my halflife running (don't ask how...it just decided to work for some reason). Anyway there's a couple problems: first off once cstrike loads and I'm in the game, there's a lot of missing textures. Also any status area around the screen with text is just a yellow-shaded kinda transparent box. I'm using NVidia drivers on a geforce 256 (elsa erazor x if it

--- man/nouveau.man | 29 +++++++++++++++++++++++------ 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 7c72907..a8dfacd 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -13,7 +13,7 @@ nouveau \- NVIDIA video driver .fi .SH DESCRIPTION .B nouveau -is an __xservername__ driver for NVIDIA video cards. The driver supports 2D +is an

I am newbie in this topic and I have problems trying to bring x.org up on the hardware I have: IBM QS22 BladeServer (PowerPC64 architecture) with PCI-Express connected nVidia 6200 video card. OS: Fedora 10-ppc: Linux localhost.localdomain 2.6.27.5aik #1 SMP Tue Feb 10 14:55:56 EST 2009 ppc64 ppc64 ppc64 GNU/Linux I downloaded and compiled DRM driver (git clone

This will allow the nouveau module to only include support for nv04-nv50, nv50-nvc0, nvc0+ cards individually (or in any combination). Only compiling one of the card types at a time reduces the size of the nouveau module, from 1.3M to 700-800K, depending on the type (including symbols/etc). It should also yield a reduction in compile time as a lot fewer files are compiled. Here are the sizes

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

> I've build gcc many times over the years for different target processors > and was never able to get my head around it internally. It is incredibly > complex. I also didn't like the fact that I had to have N copies of gcc > to support N processors. Scott McPeak is rather familiar with the internals of gcc and edg and says elsa is far simpler. > I became interested in

Chris Lattner wrote: > On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote: > >> I'm a little further along now. I've started to put together a simple >> driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think >> it works). >> >> The file being compiled is a "printf" function. Here are timing >> results

Daniel Wilkerson wrote: >> I've build gcc many times over the years for different target processors >> and was never able to get my head around it internally. It is incredibly >> complex. I also didn't like the fact that I had to have N copies of gcc >> to support N processors. > > Scott McPeak is rather familiar with the internals of gcc and edg and >

Hi, I've restarted my Elsa/LLVM project after three months of having real life intrude. I upgraded my LLVM source to the current trunk. I had to make a few changes to my source, e.g. LLVMFoldingBuilder became IRBuilder and several instances of "new" became "Create". Now, a test case that previously succeeded fails. I run the following script: #!/bin/sh if [ 1 -ne 0 ]

On 12/21/07, Richard Pennington <rich at pennware.com> wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). Er. Hm. Can you explain the name? The problem with names like "ellsif" is that it sounds like "else if". I like the

The handling of permissions in rsync (2.5.2) is nasty or broken. (tested platforms: Linux 2.4.x and Solaris 7) We have a directory which should only accessible to a group of users (test) : [sn@noname test]$ ls -lda /home/test drwxrws--- 2 root test 4096 Feb 13 15:44 /home/test Every user has an umask of 007 and his/her own default group: [sn@noname sn]$ id uid=500(sn)

On Dec 22, 2007, at 2:40 AM, Richard Pennington wrote: > Does Elsa provide an advantage over g++? For me, understanding it is a > big plus. ;-) In addition, Elsa has a Berkeley-like license which I > prefer. Ok. If you're not planning on extending the front-end, understandability doesn't really matter ;-). I get where you're coming from though! > Since I only

Chris Lattner wrote: > On Dec 22, 2007, at 2:40 AM, Richard Pennington wrote: > >> Does Elsa provide an advantage over g++? For me, understanding it is a >> big plus. ;-) In addition, Elsa has a Berkeley-like license which I >> prefer. > > Ok. If you're not planning on extending the front-end, > understandability doesn't really matter ;-). I get

https://bugs.freedesktop.org/show_bug.cgi?id=36174 Summary: Xorg crashing in nv44 card in 3D apps Product: Mesa Version: 7.10 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Wow! Cool! Hey, if you sign my contributor agreement, we can consider making your Elsa/LLVM compiler an Oink tool. Scott's intention is for Elsa to be basically "done": that is, aside from bug fixes, it shouldn't have more features. Oink is basically a bucket into which to throw tools like this one that use Elsa as a front-end. Daniel On Dec 7, 2007 6:37 AM, Richard

I'm a little further along now. I've started to put together a simple driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think it works). The file being compiled is a "printf" function. Here are timing results for optimized and unoptimized runs: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions Adding test/ofmt.i as a preprocessed C file

On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). > > The file being compiled is a "printf" function. Here are timing > results > for optimized and unoptimized runs: Cool, this is

http://bugs.freedesktop.org/show_bug.cgi?id=21124 Summary: nouveau: fonts "chipped" on NV44 Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Fixes: 590801c1a3 ("drm/nouveau/mpeg: remove dependence on namedb/engctx lookup") Cc: stable at vger.kernel.org # v4.3+ --- This is just a nice-to-have, as it only affects an error print afterwards. drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.c | 2 +- drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv44.c | 2 +- 2 files changed,

Ok thanks, i make new tests. 2017-04-17 15:21 GMT-03:00 Rowland Penny <rpenny at samba.org>: > On Mon, 17 Apr 2017 14:57:45 -0300 > Luiz Guilherme Nunes Fernandes <narutospinal at gmail.com> wrote: > > > Well, i dont have sssd installed. > > OK, now we know that ;-) > > > > > With winbind i install this packages: > > yum install realmd oddjob