similar to: (no subject)

Displaying 20 results from an estimated 300 matches similar to: "(no subject)"

2008 Aug 19
1
Interested in helping Nouveau
Hi everyone, I know there's a TODO page on the wiki, but it's kind of old (may), and it doesn't really indicate priorities. So I thought I'd list my skillset and interests here, and let those who are experienced with nouveau development point me to a good place to start. I'm currently running a P4 (presler) with a GeForce 6600. The family gaming macine is being upgraded soon
2009 Dec 26
2
[MESA PATCH] Fix nv40_miptree_layout pitch
This patch fixes two issues in nv40_miptree_layout. First, pt->width0 is used, which is the size of the whole texture, while width, which is the size of the mipmap level, should be used. Second, the current code does not 64-byte align the pitch of swizzled textures. However, on my NV40 this causes a pgraph error regarding the pitch register (and sometimes a system lockup too), which is fixed
2007 Jun 26
3
[PATCH] Always use mipmaps in cube plugin
Currently, the cube plugin uses mipmapping only when cube is unfolded. When the cube is rotated, mipmaps are not used, which leads to ugly look of textures. The attached patch fixes this. This leads to another kind of artifacts, which are fixable with anisotropic filtering. http://team.pld-linux.org/~wolf/aniso.png The leftmost image is the current state of cube plugin. The center image is with
2009 Apr 17
1
NV40 Cubic Texture HW Mip Map Generation
Hello, I have been looking at cubic texture mapping for a bit, and I have found that hw mipmap generation doesn't work at all or the textures are all messed up (normal 2d work fine). This is with linear textures. Also of note is that software mipmap generation works fine. I have done sanity checks for the miptree pitches, offsets, etc and everything seems to match up fine for both the
2008 Feb 23
4
compiz 0.7 error "No GLXFBConfig for default depth"
Since upgrading to compiz 0.7, it does not start anymore on my x86_64 system, with the error message compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work. compiz (core) - Error: Failed to manage screen: 0 compiz (core) - Fatal: No manageable screens found on display :0.0 I am using an nvidia graphics card with nvidia 169.09 driver. xorg.conf and Xorg.0.log can
2007 Jun 01
1
run compiz error: No GLXFBConfig for default depth
Compile compiz and run it on MID, met the following error, who can give me some suggestion? compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display 0:0 -------------- next part -------------- An HTML attachment was scrubbed... URL:
2018 Mar 05
2
nouveau 30bpp / deep color status
On Mon, Mar 5, 2018 at 2:25 AM, Mario Kleiner <mario.kleiner.de at gmail.com> wrote: > On 02/05/2018 12:50 AM, Ilia Mirkin wrote: >> >> In case anyone's curious about 30bpp framebuffer support, here's the >> current status: >> >> Kernel: >> >> Ben and I have switched the code to using a 256-based LUT for Kepler+, >> and I've also
2007 Jun 05
2
Direct and Indirect: Difference in rendering quality
Hi Why is the quality of scaled textures/objects using --indirect-rendering much worse than direct rendering? Also, vsync does not work with indirect-rendering. I am using an Nvidia Geforce go 7300, with 97.55 drivers. Thanks, Matt
2007 Oct 27
1
Possible Bug in multiple Compiz 1-Click Install
Listmates, There was no rhyme or reason why another /usr/lib/libIndirectGL.so.1 got installed on my system, but it did: [root Rankin-P35a/home/david] # l /usr/lib/libIn*? -rwxr-xr-x 1 root root 440676 2007-09-21 20:34 /usr/lib/libIndirectGL.so.1.2*? lrwxrwxrwx 1 root root 20 2007-10-12 03:00 /usr/lib/libIndirectGL.so.1.old -> libIndirectGL.so.1.2*? lrwxrwxrwx 1 root root 20
2018 Mar 08
0
nouveau 30bpp / deep color status
Cc'ing mesa-dev, which was left out. On 03/05/2018 01:40 PM, Ilia Mirkin wrote: > On Mon, Mar 5, 2018 at 2:25 AM, Mario Kleiner > <mario.kleiner.de at gmail.com> wrote: >> On 02/05/2018 12:50 AM, Ilia Mirkin wrote: >>> >>> In case anyone's curious about 30bpp framebuffer support, here's the >>> current status: >>> >>>
2006 Oct 21
1
compiz: No GLXFBConfig for default depth, this isn't going to work.
Hi Since a few days compiz fails to start on my system. It bails out with the message: compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 I'm using Ubuntu Edgy with the beta nvidia drivers and a recent git checkout of compiz. I read somewhere, that this error could be related to mesa
2010 Jan 28
1
Direct3D registry entries don't work
Sometime since Wine 1.0.1, the entries I used to make games run smoother, or not as smooth such as "Multisampling" and "UseGLSL" do nothing. I can't go back to 1.0.1 because it doesn't work with most of the games I want to run, but somewhere beyond 1.0.1 the Direct3D registry entries stopped working. Any ideas how to fix?
2011 Aug 22
1
OpenGL + DIB
Hello, I am testing some OpenGL software that uses a DIB backed device context followed by a BitBlt operation to draw graphics on to an on-screen canvas. Unfortunately this does not seem to work.? I have tried to patch the latest wine with DIB engine patches (bug 421), but, was unable to get it working still. My question(s) are: 1) Is this a known issue? 2) Is it in the scope of the DIB engine
2018 Mar 05
0
nouveau 30bpp / deep color status
On 02/05/2018 12:50 AM, Ilia Mirkin wrote: > In case anyone's curious about 30bpp framebuffer support, here's the > current status: > > Kernel: > > Ben and I have switched the code to using a 256-based LUT for Kepler+, > and I've also written a patch to cause the addfb ioctl to use the > proper format. You can pick this up at: > >
2009 Oct 30
2
wxRuby on Ubuntu 9.10
Installing the gem from rubygems, along with the available wxwidgets packages from synaptic, I'd recieve this error: /usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so: /usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so: symbol _ZN13wxAuiNotebook14ShowWindowMenuEv, version WXU_2.8.5 not defined in file libwx_gtk2u_aui-2.8.so.0 with link time reference -
2010 Jun 15
1
Lots of bugs in xubuntu lucid
Hello guys, i've decided to test nouveau driver and installed it recently from official repos. My videocard is GeForce 4 with additional S-video and Composite outputs, 64 MB of memory. I installed xubuntu, and tried to use nouveau driver instead of official nvidia's. After switching driver, the boot splash xubuntu logo turned into poor coloured low-resolutioned one, but X loaded normally.
2012 Jun 11
0
running diablo 3 in virtual desktop
I've gotten Diablo 3 working with wine, but it is only playable inside a virtual desktop. If I run it outside a virtual desktop, I can't even get past the login screen and the music stutters. Inside the virtual desktop, I only get around 10-12 fps. I've found as infernix on the "Diablo 3" app page has, that if I run wine with the backbuffer as the render target instead of
2018 Feb 04
4
nouveau 30bpp / deep color status
In case anyone's curious about 30bpp framebuffer support, here's the current status: Kernel: Ben and I have switched the code to using a 256-based LUT for Kepler+, and I've also written a patch to cause the addfb ioctl to use the proper format. You can pick this up at: https://github.com/skeggsb/linux/commits/linux-4.16 (note the branch!)
2010 Apr 12
16
[Bug 27603] New: Celestia 1.6.0 crashes with nv04_surface_copy_swizzle assertion
https://bugs.freedesktop.org/show_bug.cgi?id=27603 Summary: [nouveau] Celestia 1.6.0 crashes with nv04_surface_copy_swizzle assertion Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2007 Jun 12
1
Compiz porting plan, for help
David & All, As you might have heard, Intel recently introduced a new low-power device called a Mobile Internet Device (MID). We're working in Intel's Open source Technology Center on the Linux Desktop UI. Given the small screen we're planning on using a stack-based window manager where each application runs full-screen (think Matchbox). We think it would be very cool to get a