similar to: drm/nouveau contiguous bo check produces lots of output

op 11-11-13 17:05, Jerry Cooperstein schreef: > On 11/11/2013 09:57 AM, Maarten Lankhorst wrote: >> op 11-11-13 16:31, Jerry Cooperstein schreef: >>> Hi: >>> >>> commit bd9c5a2016307164c419c5e24a46921c10e620a0 >>> >>> (drm/nouveau: require contiguous bo for framebuffer) >>> produces about 2000 lines of >>> >>> nouveau

On 11/11/2013 09:57 AM, Maarten Lankhorst wrote: > op 11-11-13 16:31, Jerry Cooperstein schreef: >> Hi: >> >> commit bd9c5a2016307164c419c5e24a46921c10e620a0 >> >> (drm/nouveau: require contiguous bo for framebuffer) >> produces about 2000 lines of >> >> nouveau E[ DRM] framebuffer requires contiguous bo >> >> on system boot and

https://bugs.freedesktop.org/show_bug.cgi?id=69349 Priority: medium Bug ID: 69349 Assignee: nouveau at lists.freedesktop.org Summary: Random image corruptions (in Debian Wheezy with Linux 3.2) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

This was already required before, but no check in the kernel was done to enforce it. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c b/drivers/gpu/drm/nouveau/nouveau_display.c index 73cf240..ddb065c 100644 --- a/drivers/gpu/drm/nouveau/nouveau_display.c +++ b/drivers/gpu/drm/nouveau/nouveau_display.c @@ -107,6

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 after "fb: switching to nouveaufb from VESA VGA" display is powered off. The magic SysRq key

Hi! On v4.18-rc1, the mouse cursor is missing on my right monitor. Card is G98 [GeForce 8400 GS Rev. 2]. I have two monitors: one small landscape 1280x1024 on DVI-I-1 left, and one big 1600x1200 (1200x1600 portrait) on HDMI-1 right. Curiously, the cursor is missing not only with proper xrandr setup after logging in but even in mirrored mode at the lightdm greeter[1]. How is this even possible

Dear All, After recently taking a little dive into the NVAC clock tree, I was wondering what that net would look like on cards I expect to be similar. In this case I'm looking for MMIOtraces of NVAA and NVAF, which is marketed as the 8x00 mGPU, 9x00 mGPU, 320M, ION and/or some nForce IGP. If there is anyone who could provide me with an MMIO trace for any of these cards that would be

Hi all, I am installing a zone onto two different V445s running S10U4 and the zones are taking hours to install (about 1000 packages), that is, the problem is identical on both systems. A bit of trussing and dtracing has shown that the pkginstalls being run by the zoneadm install are making door_call calls to nscd that are taking very long, so far observed to be 5 to 40 seconds, but always in

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.x86_64 >> -

Add a flag allowing Nouveau to specify that an object should be coherent at allocation time. This is required for some class of objects like fences which are randomly-accessed by both the CPU and GPU. This flag instructs the kernel driver to make sure the object remains coherent even on architectures for which coherency is not guaranteed by the bus. Signed-off-by: Alexandre Courbot <acourbot

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 or 8400 GS'. Proprietary NVIDIA drivers: * 340.96 installs okay, console works, but X doesn't start, with unspecified error occuring

Add a flag allowing Nouveau to specify that an object should be coherent at allocation time. This is required for some class of objects like fences which are randomly-accessed by both the CPU and GPU. This flag instructs the kernel driver to make sure the object remains coherent even on architectures for which coherency is not guaranteed by the bus. Signed-off-by: Alexandre Courbot <acourbot

Hi everyone. I read on a 2011 article - http://www.phoronix.com/scan.php?page=article&item=nouveau_comp_2011&num=19 - that my particular card, GeForce 8400 GS, overheats with nouveau. (So, I never tried using if for long, before, as soon as possible, installing the proprietary drivers...) But, because it's a 2-year-old article, I was wondering if that problem could have been, in the

RedHat 9.0, kernel 2.4.20-8bigmem I can't get Samba 3.0.0 to talk to anything except lo. ./configure --prefix=/usr/share --exec-prefix=/usr --silent --with-logfilebase=/var/log/samba --with-privatedir=/etc/samba/private --with-configdir=/etc/samba --with-lockdir=/var/lock/subsys/samba --enable-cups --with-acl-support --with-winbind --with-pam_smbpass --with-ldapsam

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?

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 VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL ((VdpVideoMixerFeature)0) /** * \hideinitializer * \brief A

On 09.05.2016 19:37, Ilia Mirkin wrote: > Mesa only supports the non-spatial temporal deinterlace (deint=3). I'm > guessing that due to some unfortunate issues, you're no longer getting > hw accelerated video decoding. Check in vdpauinfo to make sure that > it's indeed showing the relevant codec as supported. If not, you can > turn that back on by updating to mesa

dmesg -t | grep -i nvidia nouveau 0000:02:00.0: NVIDIA G98 (098200a2) input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input6 input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input7 input: HDA NVidia Line as /devices/pci0000:00/0000:00:07.0/sound/card0/input8 input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:07.0/sound/card0/input9

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only

https://bugs.freedesktop.org/show_bug.cgi?id=71662 Priority: medium Bug ID: 71662 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 regression] 3d application hang Severity: normal Classification: Unclassified OS: All Reporter: jano.vesely at gmail.com Hardware: Other Status: NEW