similar to: [Bug 93795] New: G98: GL(X) compositing - XRandR DPMS trouble

https://bugs.freedesktop.org/show_bug.cgi?id=94131 Bug ID: 94131 Summary: G98: DRM: GPU lockup Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=96737 Bug ID: 96737 Summary: G98: LightDM 1 : 0 Nouveau Product: xorg Version: git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=92307 Bug ID: 92307 Summary: NV50: WARNING: ... at include/drm/drm_crtc.h:1577 drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper]() Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

On Sun, Nov 9, 2014 at 11:08 PM, Dr. Boris Neubert <omega at online.de> wrote: > Hi, > > I have a NVidia Quadro NVS450 graphics card with on screen (4800 x 1200 > pixels) over three monitors. I use the proprietary NVidia modules to > achieve accelerated 2D graphics and display effects. > > Since about the beginning of 2014, probably related to changes in the > X11 or

Hi, I have a NVidia Quadro NVS450 graphics card with on screen (4800 x 1200 pixels) over three monitors. I use the proprietary NVidia modules to achieve accelerated 2D graphics and display effects. Since about the beginning of 2014, probably related to changes in the X11 or compositing manager, I experience screen lockups lasting from few seconds to several minutes. I therefore would like to

https://bugs.freedesktop.org/show_bug.cgi?id=44942 Bug #: 44942 Summary: Make nouveau work for G98 nVidia chip Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component:

Hey guys, Let me reformulate my question: The nouveau.ko (2015-12-16) calculates and tries to set wrong 'modelines' for my G98 hardware for the most of video modes in console; even 640x480 gets weird vertical refresh 68Hz. Can it be fixed at all? Can the correct modelines be supplied to nouveau.ko somehow? Last but not least, would anybody bother with making driver work with

Hi, Adam. 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > Hi! > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > have your fix. I don't know about earlier versions -- my newer card went > into flames just a few days ago, and I replaced it a brand new 8400GS (G98)

On Wed, Apr 4, 2018 at 6:58 PM, Adam Borowski <kilobyte at angband.pl> wrote: > On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: >> 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: >> > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 >> > >> > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which

https://bugs.freedesktop.org/show_bug.cgi?id=30369 Summary: nvidia 8400GS G98 chip GPU lockup - switching to software fbcon Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Danny, Kristian, All, First let me tell you guys whatever you are doing with compiz, keep it up! It's looking great! I have a new error on ArchLinux when running compiz 0.8.2.1 that I have never seen before. I installed Archlinux on 2 boxes to check it out. One on a x86_64 box with the nvidia driver (no problems there) and one on an i686 box with onboard intel video. When connecting over

On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: > 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > > have your fix. I don't know about earlier versions -- my newer card went > > into

I'm running on Sun Blade 2500 with a GeForce 8400 GS PCI. After (maybe?) fixing a few errrors with bo allocation, I'm getting a lot of IB_EMPTY errors, ultimately resulting in a GPU lockup. I don't have any sort of framebuffer visible. After reading dma-pusher.txt, I see "An attempt to submit IB entry with length zero will raise DMA_PUSHER error of type IB_EMPTY." How would

http://bugs.freedesktop.org/show_bug.cgi?id=27136 Summary: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=93634 Bug ID: 93634 Summary: WARN_ON triggered on DPMS event Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Resending as kwin and plasma mailinglists think that 200k is too large for a mail. The "attachment" can be found in [2] Hi, Pleas note: crossposting to kwin, compiz and plasma development lists. Please keep all lists CCed. Attached you can find a very first draft for a compositing manager specification. It is currently based upon the KWin/Plasma interaction specified in the

Hi! In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0: > drm/nouveau/mmu: ALIGN_DOWN correct variable > > Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round > for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, > but erroneously applied ALIGN_DOWN to a different variable (addr) and left > intended variable (tail) not

On 02.12.2014 14:40, Ilia Mirkin wrote: > On Tue, Dec 2, 2014 at 8:38 AM, poma <pomidorabelisima at 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 to do the mmiotrace, unless you're a nouveau

Good afternoon! After applying the latest bash RPM listed at http://lists.centos.org/pipermail/centos-announce/2014-September/020594.html : The fixed RPM (bash-3.2-33.el5_10.4.x86_64.rpm) DOES work just fine on CentOS 5.10. However, it DOES NOT work on CentOS 5.4. That is, bash runs fine, but IS STILL VULNERABLE TO SHELLSHOCK! Scary screenie at: http://i.imgur.com/yR7sBjV.png It looks like

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