Re: [Nouveau] GeForce 8400 GS

-- VideoBios information -- Version: 62.98.2c.00.00 Signon message: ASUS EN8400GS VGA BIOS Ver 62.98.2C.00.AS07 Performance level 0: gpu 567MHz/shader 1400MHz/memory 400MHz/100% poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 13.09.2014 07:02, poma wrote: On 13.09.2014 06:57, poma wrote: Actually I have nothing to show cause logs are all OK. Haha, it seems to me that the bugs become intelligent. 3.15.10-201.fc20.x86_64 3.16.2-200.fc20.x86_64 3.17.0-0.rc4.git3.2.fc22.1.x86_64 nouveau [ DRM] suspending

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 13.09.2014 22:58, Ilia Mirkin wrote: On Sat, Sep 13, 2014 at 4:52 PM, poma pomidorabelis...@gmail.com wrote: On 13.09.2014 07:02, poma wrote: On 13.09.2014 06:57, poma wrote: Actually I have nothing to show cause logs are all OK. Haha, it seems to me that the bugs become intelligent

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 13.09.2014 23:46, Ilia Mirkin wrote: On Sat, Sep 13, 2014 at 5:25 PM, poma pomidorabelis...@gmail.com wrote: On 13.09.2014 22:58, Ilia Mirkin wrote: On Sat, Sep 13, 2014 at 4:52 PM, poma pomidorabelis...@gmail.com wrote: On 13.09.2014 07:02, poma wrote: On 13.09.2014 06:57, poma wrote

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 13.09.2014 23:45, Roy Spliet wrote: Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why we (nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 14.09.2014 11:53, Roy Spliet wrote: Op 14-09-14 om 10:31 schreef poma: On 13.09.2014 23:45, Roy Spliet wrote: Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why we (nouveau developers) generally ask for a git bisection is because we don't know or track

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 15.09.2014 15:36, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3) 3.15.0-rc8.1.git.7a014a8 3.15.0-rc8.2.git.456b057 3.15.0-rc8.3.git.b8407c9 3.15.0-rc8.4.git.bb7ef1e

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively

On 16.09.2014 01:21, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 1:28 PM, poma pomidorabelis...@gmail.com wrote: On 15.09.2014 15:36, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) - resolved

3.17.0-0.rc7.git0.2.fc21.x86_64 PASSED i.e. 3.17.0-0.rc7.git0.1.fc22.x86_64 patched with disp/nv50: fix dpms regression on certain boards http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=a68e953 poma ___ Nouveau mailing list Nouveau

[Nouveau] INFO: task echo:622 blocked for more than 120 seconds. - 3.18.0-0.rc0.git

02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64

[Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded

On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded Fedora kernels 3.18 boot from soft-off(S5) broken

On 20.10.2014 21:30, poma wrote: On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22

Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - reloaded Fedora kernels 3.18 boot from soft-off(S5) broken

On 21.10.2014 02:23, poma wrote: On 20.10.2014 21:30, poma wrote: On 20.10.2014 08:13, poma wrote: 02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22

Re: [Nouveau] VGA resume thaw boot (wake up from S3 S4 boot from S5) broken 3.18

- http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-fixes git clone -b drm-fixes git://people.freedesktop.org/~airlied/linux - http://cgit.freedesktop.org/~darktama/nouveau/ git://people.freedesktop.org/~darktama/nouveau ./autogen.sh cd drm make su mkdir

Re: [Nouveau] display force off - kernel 3.18

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4d60422 also broken with this commit ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau

Re: [Nouveau] display force off - kernel 3.18

dependency filters for SI drm/radeon/dpm: drop clk/voltage dependency filters for NI drm/radeon: disable audio when we disable hdmi (v2) drm/radeon: split audio enable between eg and r600 (v2) ... Up to and with prior commit da92da3 nouveau(S3/4/5) works OK. poma

Re: [Nouveau] [PATCH] nv50/disp: Fix modeset on G94

...@riesch.at Tested-by: poma pomidorabelis...@gmail.com Tested-by: Adam Williamson ad...@happyassassin.net --- drivers/gpu/drm/nouveau/nv50_display.c | 26 -- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_display.c b

Re: [Nouveau] Logo Nouveau

. Never ask engineers for design, it will always bring out the cube. :) We all know Claudia would rather drive a german, but Valeria do you have something more fluid designed, something like a una macchina italiana. poma

[Nouveau] kworker/u16:57: page allocation failure: order:0, mode:0x284000

No problemos with x86_64, however on i686 kworker/u16:57: page allocation failure: order:0, mode:0x284000 CPU: 0 PID: 1425 Comm: kworker/u16:57 Not tainted 3.18.0-0.rc5.git0.1.fc22.i686+debug #1 Workqueue: events_unbound async_run_entry_fn Call Trace: [c0b2b55a] dump_stack+0x48/0x60

Re: [Nouveau] demmio

On 02.12.2014 14:40, Ilia Mirkin wrote: On Tue, Dec 2, 2014 at 8:38 AM, poma pomidorabelis...@gmail.com wrote: Is this expected result for Chipset: G98 (NV98)? Yep, 100% expected. [Perhaps you might glance at the wiki page you got that from for clues as to why.] You basically never need

Re: [Nouveau] demmio

On 02.12.2014 14:52, Ilia Mirkin wrote: On Tue, Dec 2, 2014 at 8:50 AM, poma pomidorabelis...@gmail.com wrote: On 02.12.2014 14:40, Ilia Mirkin wrote: On Tue, Dec 2, 2014 at 8:38 AM, poma pomidorabelis...@gmail.com wrote: Is this expected result for Chipset: G98 (NV98)? Yep, 100% expected

Re: [Nouveau] demmio

On 02.12.2014 14:59, poma wrote: On 02.12.2014 14:52, Ilia Mirkin wrote: On Tue, Dec 2, 2014 at 8:50 AM, poma pomidorabelis...@gmail.com wrote: On 02.12.2014 14:40, Ilia Mirkin wrote: On Tue, Dec 2, 2014 at 8:38 AM, poma pomidorabelis...@gmail.com wrote: Is this expected result for Chipset

Re: [Nouveau] Testers needed for NVAA/NVAC kernel patch

On 02.12.2014 23:29, Pierre Moreau wrote: Hello everyone, I would need testers to check that this patch doesn't break working NVAA/NVAC configurations. It fixes an issue where some NVAC would hang on boot; if similar issues exist on NVAA, it may fix them too. You will find the patch below

[Nouveau] Nouveau Images - 3D

https://nouveau.pmoreau.org How to test Mesa i.e. hardware-accelerated OpenGL? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau

Re: [Nouveau] Handling GeForce GTX 850M GPU on Arch Linux

On 18.05.2015 01:46, Ilia Mirkin wrote: Your errors are most likely due to: [2.421428] nouveau [ PFB][:01:00.0] RAM size: 1975398418 MiB I'm guessing you don't *actually* have 1.9PB of VRAM. At least one other person with a GM108 was seeing a similar issue. You're getting a

Re: [Nouveau] enable dri3 support without glamor causes gnome-shell regression on nv4x

On 03.08.2015 15:02, Hans de Goede wrote: Hi, On 30-07-15 16:09, Ilia Mirkin wrote: FWIW this is a fail on nv50+ as well. See for example https://bugs.freedesktop.org/show_bug.cgi?id=91445 My suspicion is that this is due to the lack of PUSH_KICK in the *Done exa handlers -- works fine

Re: [Nouveau] Odd text behavior on Websites and others

On 12.08.2015 00:11, Ilia Mirkin wrote: Add a file to /etc/X11/xorg.conf.d, named anything-you-want.conf, which contains Section Device Driver modesetting EndSection Hopefully that should do it. /var/log/Xorg.0.log ... [ 4223.892] (==) Using config directory:

Re: [Nouveau] [PATCH mesa] nv30: Fix creation of scanout buffers

On 12.08.2015 14:24, Hans de Goede wrote: Scanout buffers on nv30 must always be non-swizzled and have special width alignment constraints. These constrains have been taken from the xf86-video-nouveau src/nv_accel_common.c: nouveau_allocate_surface() function. nouveau_allocate_surface()

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v3) -> v4

On 10.11.2015 17:25, Mario Kleiner wrote: > On 11/10/2015 05:00 PM, Thierry Reding wrote: >> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wrote: >>> From: Daniel Vetter >>> >>> Apparently pre-nv50 pageflip events happen before the actual vblank >>> period.

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v3) -> v4

On 12.11.2015 14:48, Thierry Reding wrote: > On Wed, Nov 11, 2015 at 09:12:33PM +0100, poma wrote: >> On 10.11.2015 17:25, Mario Kleiner wrote: >>> On 11/10/2015 05:00 PM, Thierry Reding wrote: >>>> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wr

[Nouveau] NOUVEAU(0): DRI3 on EXA enabled

An interesting results. DRI2: $ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 6321 frames in 5.0 seconds = 1264.103 FPS 6380 frames in 5.0 seconds = 1275.943 FPS 6369 frames in 5.0 seconds = 1273.629 FPS 6377 frames in 5.0 seconds = 1275.322

Re: [Nouveau] NOUVEAU(0): DRI3 on EXA enabled

On 04.11.2015 12:27, poma wrote: > On 04.11.2015 11:57, Martin Peres wrote: >> On 02/11/15 08:28, poma wrote: >>> An interesting results. >>> >>> DRI2: >>> >>> $ vblank_mode=0 glxgears >>> ATTENTION: default value of option vblank

Re: [Nouveau] NOUVEAU(0): DRI3 on EXA enabled

On 04.11.2015 11:57, Martin Peres wrote: > On 02/11/15 08:28, poma wrote: >> An interesting results. >> >> DRI2: >> >> $ vblank_mode=0 glxgears >> ATTENTION: default value of option vblank_mode overridden by environment. >> 6321 frames in 5.0 seconds

Re: [Nouveau] NOUVEAU(0): DRI3 on EXA enabled

On 04.11.2015 12:27, poma wrote: > On 04.11.2015 11:57, Martin Peres wrote: >> On 02/11/15 08:28, poma wrote: >>> An interesting results. >>> >>> DRI2: >>> >>> $ vblank_mode=0 glxgears >>> ATTENTION: default value of option vblank

Re: [Nouveau] NOUVEAU(0): DRI3 on EXA enabled

On 05.11.2015 23:47, poma wrote: > On 04.11.2015 12:27, poma wrote: >> On 04.11.2015 11:57, Martin Peres wrote: >>> On 02/11/15 08:28, poma wrote: >>>> An interesting results. >>>> >>>> DRI2: >>>> >>>> $ vblank_

Re: [Nouveau] Chipset & Family

NVidia Line Out Side as /devices/pci:00/:00:07.0/sound/card0/input12 input: HDA NVidia Front Headphone as /devices/pci:00/:00:07.0/sound/card0/input13 - patched: $ dmesg -t | grep -i chipset nouveau :02:00.0: GPU NVIDIA Chipset: G98 (098200a2) Signed-off-by: poma

Re: [Nouveau] Chipset & Family

On 07.10.2015 03:55, Ben Skeggs wrote: > NACK. > > All the relevant information is shown, "nouveau" (video driver) > detected an "NVIDIA G98" (complete with full chip identification > register value for specifics). I'm not bikeshedding this topic any > further than that. > > Thanks, > Ben. >

Re: [Nouveau] Chipset & Family

On 06.10.2015 21:07, Pierre Moreau wrote: > Hello poma, > > The chipset didn't disappear and is still displayed: it is the G98 you get on > the "[2.483843] nouveau :02:00.0: NVIDIA G98 (098200a2)" line. The > "NV98" was the "Nouveau" chi

Re: [Nouveau] RFC: drop glamor from nouveau ddx

On 07.07.2015 23:05, Ben Skeggs wrote: On 8 July 2015 at 06:06, Ilia Mirkin imir...@alum.mit.edu wrote: Ben, Looks like the reality is that glamor is just not hooked up properly in the nouveau DDX. Mainly it's missing DRI2, which in turn means no core GL contexts, and probably lots of other

Re: [Nouveau] nvs280 / nv34 card only does 1680x1050, not 1920x1080 ?

On 04.09.2015 16:56, Ilia Mirkin wrote: > Tmds is limited to 135mhz on nv3x. If you use analog, you can get full > resolution. > On Sep 4, 2015 9:00 AM, "Hans de Goede" wrote: > >> Hi All, >> >> I've recently acquired a nvs280 card, which is a nv34 >> gpu based card with a

[Nouveau] Chipset & Family

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [2.483843] nouveau

Re: [Nouveau] nvs280 / nv34 card only does 1680x1050, not 1920x1080 ?

On 04.09.2015 19:40, poma wrote: > On 04.09.2015 16:56, Ilia Mirkin wrote: >> Tmds is limited to 135mhz on nv3x. If you use analog, you can get full >> resolution. >> On Sep 4, 2015 9:00 AM, "Hans de Goede" <hdego...@redhat.com> wrote: >> >>>

Re: [Nouveau] Chipset & Family

On 06.10.2015 02:21, poma wrote: > 4.1.8-200.fc22.x86_64 dmesg: > [ 11.809467] nouveau [ DEVICE][:02:00.0] BOOT0 : 0x098200a2 > [ 11.809493] nouveau [ DEVICE][:02:00.0] Chipset: G98 (NV98) > [ 11.809508] nouveau [ DEVICE][:02:00.0] Family : NV50 > > &g

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events

On 02.12.2015 09:55, Daniel Vetter wrote: > On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote: >> On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner >> <mario.kleiner...@gmail.com> wrote: >>> When we are at it, the one with the title "[PATCH] drm/nouveau: Use >&

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events

On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner wrote: > When we are at it, the one with the title "[PATCH] drm/nouveau: Use > drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested > by me also never made it into nouveau. > > Maybe pick that up as

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v4)

On 10.11.2015 17:41, Thierry Reding wrote: > On Tue, Nov 10, 2015 at 05:37:31PM +0100, Thierry Reding wrote: >> From: Daniel Vetter >> >> Apparently pre-nv50 pageflip events happen before the actual vblank >> period. Therefore that functionality got semi-disabled in >> >>

Re: [Nouveau] nouveau sync DMA memory not allocated

On 12.11.2015 14:48, Thierry Reding wrote: > On Wed, Nov 11, 2015 at 09:12:33PM +0100, poma wrote: >> On 10.11.2015 17:25, Mario Kleiner wrote: >>> On 11/10/2015 05:00 PM, Thierry Reding wrote: >>>> On Tue, Nov 10, 2015 at 03:54:52PM +0100, Mario Kleiner wr

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v4)

On 15.12.2015 12:21, Emil Velikov wrote: > On 15 December 2015 at 11:11, poma <pomidorabelis...@gmail.com> wrote: > >> >> Apparently not reached @stable (stable: 4.3.3 2015-12-15), >> so here's one more time. >> > It has reached 4.4-rcX and will get

Re: [Nouveau] Activate DVI-I behind KVM on FX 5200

On 05.01.2016 04:08, Thomas Richter wrote: > Hi folks, > > I don't seem to be able to enable the DVI-I output of an old FX 5200 > behind a KVM switch. Autodetection works fine if the FX 5200 DVI output > is switched to the monitor, but when it is not, I have not found a way > to force-enable it.

Re: [Nouveau] Activate DVI-I behind KVM on FX 5200

On 05.01.2016 14:47, Thomas Richter wrote: > Am 05.01.2016 um 11:41 schrieb poma: > >> >> append to kernel cmdline: >> drm_kms_helper.edid_firmware=DVI-I-1:edid/edid.bin >> >> $ cat /proc/cmdline >> ... drm_kms_helper.edid_firmware=DVI-I-1:edid

Re: [Nouveau] Activate DVI-I behind KVM on FX 5200

On 05.01.2016 20:31, Thomas Richter wrote: > Hi, > >> >> Try your luck here >> http://lists.freedesktop.org/mailman/listinfo/dri-devel > > The major problem is that there is no way to tell the nouveau kernel > module to enforce a specific output. There is a video=XXX kernel > parameter, but

[Nouveau] League of Legends Refueled

http://cgit.freedesktop.org/~darktama/nouveau https://github.com/skeggsb/nouveau Is the one at freedesktop.org - ride on diesel, became a part of museum's collection? ___ Nouveau mailing list Nouveau@lists.freedesktop.org

Re: [Nouveau] Activate DVI-I behind KVM on FX 5200

On 05.01.2016 04:08, Thomas Richter wrote: > Hi folks, > > I don't seem to be able to enable the DVI-I output of an old FX 5200 > behind a KVM switch. Autodetection works fine if the FX 5200 DVI output > is switched to the monitor, but when it is not, I have not found a way > to force-enable it.

Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events

On Mon, Nov 16, 2015 at 4:11 PM, Daniel Vetter wrote: > On Mon, Nov 02, 2015 at 04:45:00PM +0900, Michel Dänzer wrote: >> On 31.10.2015 06:55, Daniel Vetter wrote: >> > Apparently pre-nv50 pageflip events happen before the actual vblank >> > period. Therefore that functionality

Re: [Nouveau] GV98 adapter, experience with nouveau

On 01.06.2016 20:44, poma wrote: > On 01.06.2016 20:20, Yury Tarasievich wrote: >> Thank you! >> >> Now, I'd appreciate some hints on how to make >> console work, at least. >> How are the video modes controlled, e.g., can I >> have some analogue of

Re: [Nouveau] GV98 adapter, experience with nouveau

On 01.06.2016 13:48, Yury Tarasievich wrote: > I'm trying to put to work the nouveau driver on > slackware 64 bits current, kernel 4.4.*. > > I've thought the hardware to be some obscure OEM > variant of GT610. However, kind soul on IRC > pointed out that it's a G98 really, 'GeForce > 9300 GS

Re: [Nouveau] GV98 adapter, experience with nouveau

On 01.06.2016 20:20, Yury Tarasievich wrote: > Thank you! > > Now, I'd appreciate some hints on how to make > console work, at least. > How are the video modes controlled, e.g., can I > have some analogue of /etc/fb.modes for nouveau? > > -Yury > After hand-over: "fb: switching to nouveaufb

[Nouveau] freshclam: page allocation failure: order:0, mode:0x2204010

Hi Fi, as you can see it looks very peculiar mix, nouveau and usbnet. Are they hidden viruses!? ... freshclam: page allocation failure: order:0, mode:0x2204010 CPU: 0 PID: 12885 Comm: freshclam Not tainted 4.4.0-1.fc22.x86_64 #1 ... Call Trace: [] dump_stack+0x4b/0x72 []

[Nouveau] nouveau_drv_video.so ?

nouveau_drv_video.so - what should it be? https://koji.fedoraproject.org/koji/buildinfo?buildID=722316 ... 0.7.4-13 - Revert symlinks - should be handled by mesa rhbz#1271842 https://bugzilla.redhat.com/show_bug.cgi?id=1271842 ... 0.7.4-12 - Add symlinks for

[Nouveau] stable? kms: take mode_config mutex in connector hotplug path

https://github.com/skeggsb/nouveau/commit/9862b21 https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau/nouveau_connector.c?id=0a882cad this was sent to @stable, but test result is: nouveau: Unknown symbol mutex_lock (err 0) nouveau: Unknown symbol

[Nouveau] glmark2: high CPU usage - DRI3 & modeset

$ glmark2 === glmark2 2014.03 === OpenGL Information GL_VENDOR: nouveau GL_RENDERER: Gallium 0.4 on NV98 GL_VERSION:3.0 Mesa 11.2.0

Re: [Nouveau] glmark2: high CPU usage - DRI3 & modeset

is busy waiting) > >> poma <pomidorabelis...@gmail.com> hat am 7. April 2016 um 13:56 geschrieben: >> >> >> >> $ glmark2 >> === >> glmark2 2014.03 >> ==

[Nouveau] [PATCH] nouveau: Switch perms from macros to octal notations, module params readable to everyone

From: poma <pomidorabelis...@gmail.com> Switch from "silly" S_* macros to "definitely more readable" octal "way" permissions, moreover to not "so restrictive" module parameters permissions. Suggested-by: Ilia Mirkin <imir...@alum.mit.edu> Fixe

[Nouveau] [PATCH] module parameters: permissions as defines, readable to everyone

cel = "0" nofbaccel = "0" runpm = "-1" tv_disable = "0" tv_norm = "(null)" vram_pushbuf= "0" Signed-off-by: poma <pomidorabelis...@gmail.com> --- drive

Re: [Nouveau] [PATCH v5 00/13] PRIME Synchronization

On 29.04.2016 07:41, Dave Airlie wrote: > On 13 April 2016 at 14:17, Alex Goins wrote: >> Hello all, >> >> These patches change the xserver to support setting up PRIME with double >> buffering, and implement double buffered PRIME sink and source support in >> the modesetting

[Nouveau] VDPAU DEINTERLACE

NVIDIA G98 mesa-dri-drivers-11.2.1-2.20160501.fc22.x86_64 (incl. mesa commit 38fcf7c) vdpauinfo | grep -i deint DEINTERLACE_TEMPORAL y DEINTERLACE_TEMPORAL_SPATIAL - https://cgit.freedesktop.org/vdpau/libvdpau/tree/include/vdpau/vdpau.h#n3420 #define

Re: [Nouveau] VDPAU DEINTERLACE

TERLACER: ability without capability, i.e. underpowered GPU? > > On Thu, May 5, 2016 at 1:12 AM, poma <pomidorabelis...@gmail.com> wrote: >> >> NVIDIA G98 >> mesa-dri-drivers-11.2.1-2.20160501.fc22.x86_64 >> (incl. mesa commit 38fcf7c)

Re: [Nouveau] VDPAU DEINTERLACE

On 09.05.2016 20:45, Ilia Mirkin wrote: > You can try playing with pstate in /sys/kernel/debug/dri/0/pstate > # cat /sys/kernel/debug/dri/0/pstate 0f: core 567 MHz shader 1400 MHz memory 400 MHz AC: core 566 MHz shader 1400 MHz memory 399 MHz ±1 MHz :) > On Mon, May 9, 2016 at 2:42

Re: [Nouveau] [Mesa-dev] nouveau_drv_video.so ?

On 30.06.2016 13:11, Emil Velikov wrote: > Hi poma, > > Seems like you're missed your question. "nouveau_drv_video.so ?" does > not mean much I'm afraid :-( > > On 30 June 2016 at 11:03, poma <pomidorabelis...@gmail.com> wrote: >> On 30.06.2016 08:27,

Re: [Nouveau] NVAC: WARN_ON(nvbo->pin_refcnt > 0);

[...] > WARNING: CPU: 1 PID: 701 at drivers/gpu/drm/nouveau/nouveau_bo.c:137 > nouveau_bo_del_ttm+0x7f/0x90 [nouveau] [...] Which does not appear within mainline 4.10, tested with 4.10.0-1.fc26.x86_64+debug. OK ___ Nouveau mailing list

Re: [Nouveau] nouveau preventing shutdown after suspend-resume

On 17.02.2017 18:06, Ilia Mirkin wrote: > On Fri, Feb 17, 2017 at 11:22 AM, João Paulo Rechi Vita > wrote: >> Hello Ilia, >> >> On 17 February 2017 at 11:14, Ilia Mirkin wrote: >>> On Fri, Feb 17, 2017 at 10:54 AM, João Paulo Rechi Vita >>>

[Nouveau] NVAC: WARN_ON(nvbo->pin_refcnt > 0);

Hello fellows! Signal finally goes through ION's HDMI, however # chvt from 5 "graphical" to 3 "textual", and then at the very end of reboot, WARN emerges: ... nouveau :01:00.0: DRM: EVO timeout [ cut here ] WARNING: CPU: 1 PID: 701 at

Re: [Nouveau] NVAC "No Signal"

sted-by: Roy Spliet <nouv...@spliet.org> > > Given "no display on HDMI since 4.8" is quite a serious regression > (albeit for a small userbase), please consider submitting this to 4.10 > as well as a "back-port" to the upstream 4.8 and 4.9 trees. > Tha

Re: [Nouveau] NVAC "No Signal"

http://goo.gl/Gm4ffO mmiotrace-nouveau/ ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau

Re: [Nouveau] Atomic modesetting + DisplayPort MST

On 04.11.2016 10:41, Ben Skeggs wrote: > Hey all, > > I've just pushed out the initial Nouveau support for $subject \o/ > > As the atomic modesetting transition is basically a rewrite of the KMS > portion of the driver, I would be very grateful for any additional > testing that people could

Re: [Nouveau] NVAC "No Signal"

On 21.10.2016 10:56, Pierre Moreau wrote: > On 01:15 am - Oct 21 2016, Lukas Wunner wrote: >> On Thu, Oct 20, 2016 at 10:08:28AM +0200, Lukas Wunner wrote: >>> On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: For example, my laptop (which also has an NVAC) has been triggering

Re: [Nouveau] NVAC "No Signal"

On 06.11.2016 18:02, poma wrote: > > http://goo.gl/Gm4ffO > mmiotrace-nouveau/ > $ uname -r 4.9.0-0.rc4.git0.1.fc26.x86_64+debug $ dmesg -t | grep -P '(?=.*nouveau)(?=.*MMIO)' nouveau :01:00.0: bus: MMIO write of 8015 FAULT at 61a804 nouveau :01:00.0: bus: MMIO read

Re: [Nouveau] NVAC "No Signal"

On 18.10.2016 09:35, Karol Herbst wrote: > how sure are you, that this is needed for _every_ nvac? > Thank you for asking. If you consider, as relevant, referring to the original commit: "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380"

[Nouveau] NVAC "No Signal"

git3.1.fc25 Patched and tested with: $ modinfo -n nouveau /lib/modules/4.8.2-300.fc25.x86_64/updates/nouveau.ko Tested-by: poma <p...@gmail.com> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/eng

Re: [Nouveau] NVAC "No Signal"

On 18.10.2016 16:02, Karol Herbst wrote: > well, I just don't want that this fix breaks the same thing for other > users, that's why I am asking. > Affected device ID: https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nvkm/engine/device/pci.c#L1229 can it be excluded from

Re: [Nouveau] NVAC "No Signal"

On 19.10.2016 17:03, Karol Herbst wrote: > You don't get why I try to say. We have to actually find out when to > apply this workaround, not to create some silly whitelist/blacklist. > It's the last option, we never want to actually use. > Well if you do not say, who can understand!? :)

Re: [Nouveau] NVAC "No Signal"

On 20.10.2016 00:46, Ben Skeggs wrote: [...] > I'd like to see a mmiotrace of the NVIDIA binary driver on a system > where this WAR breaks things. I applied it to all the GPUs that NVIDIA > told me required it. > > Ben. > Still broken, more than four months, tested with mainline 4.9-rc6.

Re: [Nouveau] MediaWriter & Nouveau

[...] = "basic" render $ QSG_INFO=1 mediawriter Debug: QSG: basic render loop ((null):0, (null)) Debug: texture atlas dimensions: 1024x512 ((null):0, (null)) Debug: R/G/B/A Buffers:8 8 8 0 ((null):0, (null)) Debug: Depth Buffer: 24 ((null):0, (null)) Debug: Stencil Buffer: 8

[Nouveau] MediaWriter & Nouveau

Pan Bříza, to se stane, když Custom image - Pick a file from your drives(s) ... nouveau :02:00.0: fifo: DMA_PUSHER - ch 5 [mediawriter[20975]] get 0020171c34 put 00201746ec ib_get 0017 ib_put 0018 state 8000a32c (err: INVALID_CMD) push 00406040 nouveau :02:00.0: gr: DATA_ERROR

[Nouveau] NVAC - BUG: unable to handle kernel NULL pointer dereference

With lightweight desktoping, the atomic modesetting seems far from robust. BUG: unable to handle kernel NULL pointer dereference at 0021 IP: dma_fence_wait_timeout+0x36/0xf0 ... Oops: [#1] SMP Modules linked in: ... nouveau ... CPU: 0 PID: 6895 Comm: Xorg Not tainted

[Nouveau] NVAC - WARN_ON(nvbo->pin_refcnt > 0);

[ cut here ] WARNING: CPU: 3 PID: 692 at drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau] Modules linked in: ... nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper drm wmi ... CPU: 3 PID: 692 Comm: Xorg Not tainted

[Nouveau] xfree86: use modesetting driver by default on GeForce 8 and newer - Fedora

Hello Default to xf86-video-modesetting on GeForce 8 and newer. https://src.fedoraproject.org/cgit/rpms/xorg-x11-server.git/commit/?id=de1c849ff18b41f53d003bb70bf8b1744b749af8 This is thrown onto users downstream, without any further explanation, why modesetting is preferred for GeForce 8. Is