Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Nouveau + gallium + Compiz Fusion = :(
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Sat Apr 10, 2010 9:35 pm    Post subject: Nouveau + gallium + Compiz Fusion = :( Reply with quote

I have just spent most of yesterday getting Nouveau and Gallium3d up and running on my 2.6.32 kernel with a NV34 (FX 5200) card on my laptop. Everything works very nicely, glxgears and oolite both work very well indeed on my Gnome 2.26 desktop. Kudos that it all works despite it being unstable.

However, I've been trying to get Compiz Fusion up and running. Whenever I try to start compiz, it buggers up the display somewhat, so I see a corrupted white band across the top of both my laptop's display and the CRT display which incidentally, has a virtual 3200 x 1600 display, and on the rest of the display appears to be blank with some icons on the far most left side that I can't click on, and the mouse seems a bit sluggish when moving around. I cannot click on anything at all.

Killing compiz and restarting metacity gets everything working normally. Any ideas on how I might be able to get Compiz Fusion working?

If you need further information, I'll be quite happy to supply. Just ask. :)

Many thanks
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
Need4Speed
Guru
Guru


Joined: 06 Jun 2004
Posts: 497

PostPosted: Sat Apr 10, 2010 10:46 pm    Post subject: Reply with quote

I haven't had a nvidia card in a while, so I can't help you with any specific details, but you would probably have better luck with the very latest versions of the relevant parts. I would try running a 2.6.34rc kernel and use live ebuilds for libdrm, xorg-server, and the nouveau drivers. I think you should find them in the x11-overlay. Look in /var/log/Xorg.log and dmesg for any errors, and if things still don't work, ask in #nouveau on freenode.
_________________
2.6.34-rc3 on x86_64 w/ paludis
WM: ratpoison
Term: urxvt, zsh
Browser: uzbl
Email: mutt, offlineimap
IRC: weechat
News: newsbeuter
PDF: apvlv
Back to top
View user's profile Send private message
viralex
Apprentice
Apprentice


Joined: 24 Apr 2008
Posts: 237
Location: Viareggio (Lu,Italy)

PostPosted: Sun Apr 11, 2010 9:14 am    Post subject: Reply with quote

I'm running 2.6.34-rc3 with KMS nouveau and mesa with gallium useflag.
Compiz gives me a black screen :P
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Sun Apr 11, 2010 9:45 am    Post subject: Reply with quote

viralex wrote:
I'm running 2.6.34-rc3 with KMS nouveau and mesa with gallium useflag.
Compiz gives me a black screen :P


I just tried Metacity's compositing. It works, but very very slowly, the background looks like there's LOTS of windows open, and when moving a window, it leaves bits of itself all over the display. I'm just impressed it didn't crash. :)
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
viralex
Apprentice
Apprentice


Joined: 24 Apr 2008
Posts: 237
Location: Viareggio (Lu,Italy)

PostPosted: Sun Apr 11, 2010 10:33 am    Post subject: Reply with quote

my metacity compositing works perfectly!
I also tried mutter and gnome-shell :P!!
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Sun Apr 11, 2010 10:49 am    Post subject: Reply with quote

viralex wrote:
my metacity compositing works perfectly!
I also tried mutter and gnome-shell :P!!


I'm using the following packages:

x11-base/nouveau-drm-20100316
x11-libs/libdrm-2.4.20
x11-drivers/xf86-video-nouveau-0.0.15_pre20100329
media-libs/mesa-7.8.1 +gallium

Which versions of those packages are you using?
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
viralex
Apprentice
Apprentice


Joined: 24 Apr 2008
Posts: 237
Location: Viareggio (Lu,Italy)

PostPosted: Sun Apr 11, 2010 11:42 am    Post subject: Reply with quote

I'm using:

kernel's staging driver of nouveau drivers (2.6.34-rc3-git10)
x11-libs/libdrm-2.4.20
x11-drivers/xf86-video-nouveau-0.0.15_pre20100329
media-libs/mesa-7.8.1 +gallium
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Sun Apr 11, 2010 2:11 pm    Post subject: Reply with quote

viralex wrote:
kernel's staging driver of nouveau drivers (2.6.34-rc3-git10)


Looks like that's the only difference between yours and mine. What version is that driver? Many thanks
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
viralex
Apprentice
Apprentice


Joined: 24 Apr 2008
Posts: 237
Location: Viareggio (Lu,Italy)

PostPosted: Sun Apr 11, 2010 2:24 pm    Post subject: Reply with quote

Code:

viralex@dron3 ~ $ dmesg | grep nouveau
[    6.843408] nouveau 0000:01:00.0: power state changed by ACPI to D0
[    6.843422] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    6.843430] nouveau 0000:01:00.0: setting latency timer to 64
[    6.847403] [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x086700a2)
[    6.853986] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
[    6.932689] [drm] nouveau 0000:01:00.0: ... appears to be valid
[    6.932693] [drm] nouveau 0000:01:00.0: BIT BIOS found
[    6.932696] [drm] nouveau 0000:01:00.0: Bios version 60.86.64.00
[    6.932699] [drm] nouveau 0000:01:00.0: TMDS table revision 2.0 not currently supported
[    6.932702] [drm] nouveau 0000:01:00.0: Found Display Configuration Block version 4.0
[    6.932704] [drm] nouveau 0000:01:00.0: Raw DCB entry 0: 01000323 00010034
[    6.932707] [drm] nouveau 0000:01:00.0: Raw DCB entry 1: 02011300 00000028
[    6.932709] [drm] nouveau 0000:01:00.0: Raw DCB entry 2: 0000000e 00000000
[    6.932711] [drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 14 2
[    6.932713] [drm] nouveau 0000:01:00.0:   0: 0x00000040: type 0x40 idx 0 tag 0xff
[    6.932716] [drm] nouveau 0000:01:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
[    6.932724] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC11C
[    6.972681] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xC486
[    7.010040] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xCEDB
[    7.010053] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xCFCD
[    7.016780] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xD1C7
[    7.016783] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0xD22C
[    7.040053] [drm] nouveau 0000:01:00.0: 0xD22C: Condition still not met after 20ms, skipping following opcodes
[    7.040064] [drm] nouveau 0000:01:00.0: 0xB1D6: parsing output script 0
[    7.040079] [drm] nouveau 0000:01:00.0: Detected 128MiB VRAM
[    7.193296] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[    7.193652] [drm] nouveau 0000:01:00.0: Allocating FIFO number 1
[    7.200543] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
[    7.201568] [drm] nouveau 0000:01:00.0: Detected a LVDS output
[    7.201573] [drm] nouveau 0000:01:00.0: Detected a DAC output
[    7.201576] [drm] nouveau 0000:01:00.0: Detected a LVDS connector
[    7.300520] [drm] nouveau 0000:01:00.0: Detected a VGA connector
[    8.352826] [drm] nouveau 0000:01:00.0: allocated 1280x800 fb: 0x40250000, bo ffff88013b6b6a00
[    8.354703] [drm] nouveau 0000:01:00.0: 0xB1DA: parsing output script 1
[    8.354729] [drm] nouveau 0000:01:00.0: 0xB03B: parsing clock script 0
[    8.358133] fb0: nouveaufb frame buffer device
[    8.358206] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[    8.376983] [drm] nouveau 0000:01:00.0: 0xB199: parsing clock script 1
[   17.789854] [drm] nouveau 0000:01:00.0: Allocating FIFO number 2
[   17.796628] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
[   17.912918] [drm] nouveau 0000:01:00.0: Allocating FIFO number 3
[   17.919704] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 3
[ 4686.446617] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
[ 4686.453496] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
[ 4686.456357] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
[ 8575.285435] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
[ 8575.292383] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
[ 8575.295330] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
viralex@dron3 ~ $ cat /var/log/Xorg.0.log | grep nouveau
[    17.420] (II) LoadModule: "nouveau"
[    17.436] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[    17.474] (II) Module nouveau: vendor="X.Org Foundation"
[    17.528] (II) [drm] nouveau interface version: 0.0.16
[    17.796] (II) NOUVEAU(0): [DRI2]   DRI driver: nouveau
[    17.934] (II) AIGLX: Loaded and initialized /usr/lib64/dri/nouveau_dri.so
viralex@dron3 ~ $ cat /var/log/Xorg.0.log | grep NOUVEAU
[    17.526] (II) NOUVEAU driver
[    17.526] (II) NOUVEAU driver for NVIDIA chipset families :
[    17.529] (II) NOUVEAU(0): Loaded DRI module
[    17.529] (--) NOUVEAU(0): Chipset: "NVIDIA NV86"
[    17.529] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[    17.529] (==) NOUVEAU(0): RGB weight 888
[    17.529] (==) NOUVEAU(0): Default visual is TrueColor
[    17.529] (==) NOUVEAU(0): Using HW cursor
[    17.529] (II) NOUVEAU(0): Output LVDS-1 using monitor section Monitor0
[    17.627] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[    17.627] (II) NOUVEAU(0): EDID for output LVDS-1
[    17.627] (II) NOUVEAU(0): Manufacturer: SEC  Model: 5441  Serial#: 0
[    17.627] (II) NOUVEAU(0): Year: 2007  Week: 0
[    17.627] (II) NOUVEAU(0): EDID Version: 1.3
[    17.627] (II) NOUVEAU(0): Digital Display Input
[    17.627] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 29  vert.: 18
[    17.627] (II) NOUVEAU(0): Gamma: 2.20
[    17.627] (II) NOUVEAU(0): No DPMS capabilities specified
[    17.627] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[    17.627] (II) NOUVEAU(0): First detailed timing is preferred mode
[    17.627] (II) NOUVEAU(0): redX: 0.580 redY: 0.340   greenX: 0.310 greenY: 0.550
[    17.627] (II) NOUVEAU(0): blueX: 0.155 blueY: 0.155   whiteX: 0.313 whiteY: 0.329
[    17.627] (II) NOUVEAU(0): Manufacturer's mask: 0
[    17.627] (II) NOUVEAU(0): Supported detailed timing:
[    17.627] (II) NOUVEAU(0): clock: 72.1 MHz   Image Size:  261 x 163 mm
[    17.627] (II) NOUVEAU(0): h_active: 1280  h_sync: 1328  h_sync_end 1360 h_blank_end 1448 h_border: 0
[    17.627] (II) NOUVEAU(0): v_active: 800  v_sync: 803  v_sync_end 809 v_blanking: 830 v_border: 0
[    17.627] (II) NOUVEAU(0): Unknown vendor-specific block f
[    17.627] (II) NOUVEAU(0):  DW919�133AT
[    17.627] (II) NOUVEAU(0): Unknown vendor-specific block 0
[    17.627] (II) NOUVEAU(0): EDID (in hex):
[    17.627] (II) NOUVEAU(0):    00ffffffffffff004ca3415400000000
[    17.627] (II) NOUVEAU(0):    00110103801d12780a87f594574f8c27
[    17.627] (II) NOUVEAU(0):    27505400000001010101010101010101
[    17.627] (II) NOUVEAU(0):    0101010101012b1c00a850201e303020
[    17.627] (II) NOUVEAU(0):    360005a3100000190000000f00000000
[    17.627] (II) NOUVEAU(0):    000000000032d2023200000000fe0044
[    17.627] (II) NOUVEAU(0):    573931398031333341540a2000000000
[    17.627] (II) NOUVEAU(0):    00ffffffffffffffff01010a20200057
[    17.627] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[    17.627] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    17.627] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    17.627] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
[    17.627] (II) NOUVEAU(0): Modeline "1280x800"x60.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "1024x768"x59.9   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync (47.8 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "800x600"x59.9   38.25  800 832 912 1024  600 603 607 624 -hsync +vsync (37.4 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "640x480"x59.4   23.75  640 664 720 800  480 483 487 500 -hsync +vsync (29.7 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "720x400"x59.6   22.25  720 744 808 896  400 403 413 417 -hsync +vsync (24.8 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "640x400"x60.0   20.00  640 664 720 800  400 403 409 417 -hsync +vsync (25.0 kHz)
[    17.627] (II) NOUVEAU(0): Modeline "640x350"x59.8   17.50  640 664 720 800  350 353 363 366 -hsync +vsync (21.9 kHz)
[    17.725] (II) NOUVEAU(0): EDID for output VGA-1
[    17.725] (II) NOUVEAU(0): Output LVDS-1 connected
[    17.725] (II) NOUVEAU(0): Output VGA-1 disconnected
[    17.725] (II) NOUVEAU(0): Using exact sizes for initial modes
[    17.725] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1280x800
[    17.725] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    17.725] (--) NOUVEAU(0): Virtual size is 1280x800 (pitch 1280)
[    17.725] (**) NOUVEAU(0):  Driver mode "1280x800": 72.1 MHz (scaled from 0.0 MHz), 49.8 kHz, 60.0 Hz
[    17.725] (II) NOUVEAU(0): Modeline "1280x800"x60.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[    17.725] (II) NOUVEAU(0): Modeline "1024x768"x59.9   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync (47.8 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
[    17.725] (II) NOUVEAU(0): Modeline "800x600"x59.9   38.25  800 832 912 1024  600 603 607 624 -hsync +vsync (37.4 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
[    17.725] (II) NOUVEAU(0): Modeline "640x480"x59.4   23.75  640 664 720 800  480 483 487 500 -hsync +vsync (29.7 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
[    17.725] (II) NOUVEAU(0): Modeline "720x400"x59.6   22.25  720 744 808 896  400 403 413 417 -hsync +vsync (24.8 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
[    17.725] (II) NOUVEAU(0): Modeline "640x400"x60.0   20.00  640 664 720 800  400 403 409 417 -hsync +vsync (25.0 kHz)
[    17.725] (**) NOUVEAU(0):  Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
[    17.725] (II) NOUVEAU(0): Modeline "640x350"x59.8   17.50  640 664 720 800  350 353 363 366 -hsync +vsync (21.9 kHz)
[    17.725] (**) NOUVEAU(0): Display dimensions: (290, 180) mm
[    17.725] (**) NOUVEAU(0): DPI set to (112, 112)
[    17.796] (II) NOUVEAU(0): Opened GPU channel 2
[    17.796] (II) NOUVEAU(0): [DRI2] Setup complete
[    17.796] (II) NOUVEAU(0): [DRI2]   DRI driver: nouveau
[    17.797] (II) NOUVEAU(0): GART: 512MiB available
[    17.798] (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer
[    17.842] (==) NOUVEAU(0): Backing store disabled
[    17.842] (==) NOUVEAU(0): Silken mouse enabled
[    17.842] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[    17.842] (II) NOUVEAU(0): [XvMC] Extension initialized.
[    17.853] (II) NOUVEAU(0): NVEnterVT is called.
[    17.853] (==) NOUVEAU(0): DPMS enabled
[    17.853] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    17.934] (II) NOUVEAU(0): Setting screen physical size to 338 x 211
[    24.998] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[    24.998] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    24.998] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    25.097] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[    25.097] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    25.097] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    25.205] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[    25.206] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    25.206] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[    33.666] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[    33.666] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    33.666] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[  4676.257] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[  4676.257] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[  4676.257] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)
[  8565.132] (II) NOUVEAU(0): EDID vendor "SEC", prod id 21569
[  8565.132] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[  8565.132] (II) NOUVEAU(0): Modeline "1280x800"x0.0   72.11  1280 1328 1360 1448  800 803 809 830 -hsync -vsync (49.8 kHz)



I found this linux/drivers/gpu/drm/nouveau/nouveau_drv.h:

Code:

#define DRIVER_DATE             "20090420"

#define DRIVER_MAJOR            0
#define DRIVER_MINOR            0
#define DRIVER_PATCHLEVEL       16


I have installed also: x11-drivers/nouveau-firmware.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Sun Apr 11, 2010 2:37 pm    Post subject: Reply with quote

viralex wrote:
[code]
viralex@dron3 ~ $ dmesg | grep nouveau
[ 8.358206] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0


That is the same as the one in nouveau-drm. Looks like we've got the same software running. You've got a NV50 device whilst I've got a NV34 device. I suppose we'll have to wait for the next upgrades to come along to resolve these problems with compiz fusion and metacity's compositing.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 2152
Location: Berlin, Germany

PostPosted: Tue Apr 13, 2010 9:23 am    Post subject: Reply with quote

The nouveau gallium driver in mesa-7.8 is not so great. Especially for nv30/nv40 generation chipsets, many features are still missing (nexuiz should work though). Try the live ebuild from the x11 overlay instead. But be warned, this is unstable development stuff which can crash your X server or worse.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Tue Apr 13, 2010 9:44 am    Post subject: Reply with quote

chithanh wrote:
The nouveau gallium driver in mesa-7.8 is not so great. Especially for nv30/nv40 generation chipsets, many features are still missing (nexuiz should work though). Try the live ebuild from the x11 overlay instead. But be warned, this is unstable development stuff which can crash your X server or worse.


Thanks, I'll be testing the 9999 builds some time later today.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
s0be
Apprentice
Apprentice


Joined: 23 Nov 2002
Posts: 239

PostPosted: Wed Apr 14, 2010 2:41 pm    Post subject: Reply with quote

For those wanting to try more recent drm modules with KMS, I've been using nouveau-git injected into my gentoo-sources-2.6.33-r1 kernel.

here's the directions:

http://pat.erley.org/Other/nouveau

I generally keep it kinda up-to-date, but no guarantees. One or two of the patches are whitespace damaged, so they must be applied with patch -l (that's a lowercase L). This provides you with the latest nouveau kernel code, on an older stable kernel.

I run 2.6.33+gentoo+nouveau git+bfs+compat-wireless(wireless-testing instead of wireless-next) with good stability. compiz-fusion with mesa+gallium 'works' but not long term stable. day to day 3d is fine.

YMMV
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Wed Apr 14, 2010 2:58 pm    Post subject: Results Reply with quote

Best results can be obtained by using the nvfx-next branch from the official mesa.git tree. This works perfectly with celestia 1.6.0 on NV30 hardware. However, there are still issues to resolve with compioz and metacity's compositing.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Wed Apr 14, 2010 3:02 pm    Post subject: Reply with quote

s0be wrote:
For those wanting to try more recent drm modules with KMS, I've been using nouveau-git injected into my gentoo-sources-2.6.33-r1 kernel.

YMMV


By using the 9999* ebuilds, you can always get the latest and compile as modules. This approach works exceptionally well and means you don't need to recompile and reboot each time you get updates for the nouveau set of drivers.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
s0be
Apprentice
Apprentice


Joined: 23 Nov 2002
Posts: 239

PostPosted: Wed Apr 14, 2010 6:48 pm    Post subject: Reply with quote

alexbuell wrote:
s0be wrote:
For those wanting to try more recent drm modules with KMS, I've been using nouveau-git injected into my gentoo-sources-2.6.33-r1 kernel.

YMMV


By using the 9999* ebuilds, you can always get the latest and compile as modules. This approach works exceptionally well and means you don't need to recompile and reboot each time you get updates for the nouveau set of drivers.


I understand that, but that requires going to a latestart approach to nouveaufb, and/or dicking around with an initrd. This approach 'just works' without either. I use the 9999 ebuilds for libdrm et. al, but my own hand rolled kernel balls.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Wed Apr 14, 2010 7:23 pm    Post subject: Reply with quote

s0be wrote:
alexbuell wrote:
s0be wrote:
For those wanting to try more recent drm modules with KMS, I've been using nouveau-git injected into my gentoo-sources-2.6.33-r1 kernel.

YMMV


By using the 9999* ebuilds, you can always get the latest and compile as modules. This approach works exceptionally well and means you don't need to recompile and reboot each time you get updates for the nouveau set of drivers.


I understand that, but that requires going to a latestart approach to nouveaufb, and/or dicking around with an initrd. This approach 'just works' without either. I use the 9999 ebuilds for libdrm et. al, but my own hand rolled kernel balls.


Yeah, that's the beauty of Linux :)
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
PraetorZero
Apprentice
Apprentice


Joined: 11 Dec 2004
Posts: 239
Location: /home

PostPosted: Wed Apr 14, 2010 11:16 pm    Post subject: Reply with quote

chithanh wrote:
The nouveau gallium driver in mesa-7.8 is not so great. Especially for nv30/nv40 generation chipsets, many features are still missing (nexuiz should work though). Try the live ebuild from the x11 overlay instead. But be warned, this is unstable development stuff which can crash your X server or worse.


What's worse than crashing the server?
_________________
What's the worst that can happen?
Back to top
View user's profile Send private message
SMOKEING
n00b
n00b


Joined: 07 Jan 2009
Posts: 5

PostPosted: Mon Apr 19, 2010 10:00 pm    Post subject: Reply with quote

Here's my report.

ThinkPad R61 with Quadro NVS 140M.

Running gentoo-sources-2.6.33-r1 with nouveau-drm-20100316 from ~amd64 and xorg-server, libdrm and xf86-video-nouveau from x11 overlay.

Compiz works (yay!) except for:

* any window resize operation immediately crashes compiz: temporary workaround by changing resize mode to "stretch".

* windows with transparency (as a vte-based terminal w/ transparet background, but also when I expressly make a window transparent) likely to freeze everything.

* transparent areas get darker, also manifest in the "fade" effect (the window goes dark before getting unmapped).

* occasional artifacts (not quite like those seen with the binary nvidia driver and unchecked "force sync between X and XGL").

* when sliding between viewports, if there are windows on (both the viewport I am leaving and) the viewport I am switching to, they down get mapped until the sliding is complete.

* sluggish overall.

Verdict: emerge -C nvidia-drivers.
Back to top
View user's profile Send private message
Gordex
n00b
n00b


Joined: 10 Jul 2008
Posts: 26

PostPosted: Thu Apr 22, 2010 2:34 pm    Post subject: Reply with quote

Status here:
compiz-fusion with fusion-icon and emerald,
all unstable arch
everything (including kms) works perfectly with gnome-2.28, nouveau, nouveau-kernel-2.6.34-rc4, gallium-enabled mesa
8) nice experience (got an nv50 chip)
Gentoo rocks!
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 2152
Location: Berlin, Germany

PostPosted: Mon Apr 26, 2010 4:40 pm    Post subject: Reply with quote

If you want 3D, it is best to use nouveau from kernel 2.6.34_rc4 or later.

In my experience, the drm in x11-base/nouveau-drm in portage does not work properly with 3D on NV30/NV40 generation cards.
Back to top
View user's profile Send private message
agent_jdh
Veteran
Veteran


Joined: 08 Aug 2002
Posts: 1779
Location: Scotland

PostPosted: Mon Apr 26, 2010 8:37 pm    Post subject: Reply with quote

chithanh wrote:
If you want 3D, it is best to use nouveau from kernel 2.6.34_rc4 or later.

In my experience, the drm in x11-base/nouveau-drm in portage does not work properly with 3D on NV30/NV40 generation cards.


I'll need to look into this - I've got an NV4B card (7600GT), and while 3d GL 'works', it really isn't up to much in terms of speed.

EDIT - OK tried 2.6.34-rc5 (vanilla-sources), no real difference. Had to back out to Xrender for KDE effects as opengl is still too slow. This is with mesa/gallium from git.
_________________
Jingle Jangle Jewellery
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Fri May 14, 2010 12:53 pm    Post subject: Reply with quote

PraetorZero wrote:
chithanh wrote:
The nouveau gallium driver in mesa-7.8 is not so great. Especially for nv30/nv40 generation chipsets, many features are still missing (nexuiz should work though). Try the live ebuild from the x11 overlay instead. But be warned, this is unstable development stuff which can crash your X server or worse.


What's worse than crashing the server?


From experience:

Sometimes critical system libraries or programs gets overwritten. Yes it can happen, I've had it happen on two difference occasions with the nvfx branch from the mesa.git repository.

I think that happens because the X11 Nouveau driver gets muddled up and overwrites parts in system memory which gets written out to disk hence the corruption.

I eventually went back to mesa-9999. Not as good for working OpenGL applications but system's a lot more stable!
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
chithanh
Developer
Developer


Joined: 05 Aug 2006
Posts: 2152
Location: Berlin, Germany

PostPosted: Wed May 19, 2010 10:32 am    Post subject: Reply with quote

There were two bugs related to x86 PAT which could indeed cause filesystem corruption in conjunction with DRI2/TTM. But this was not restricted to nouveau, and only a few specific kernel releases were affected. But this was not caused by mesa.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 481
Location: "Hemp"shire, UK

PostPosted: Wed May 19, 2010 10:49 am    Post subject: Reply with quote

chithanh wrote:
There were two bugs related to x86 PAT which could indeed cause filesystem corruption in conjunction with DRI2/TTM. But this was not restricted to nouveau, and only a few specific kernel releases were affected. But this was not caused by mesa.


These two fixes are already in the kernel (2.6.32-r8). I'm still sure it was the nvfx branch that caused what I experienced. Going back to mesa-9999, the problems disappeared.
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum