similar to: [Bug 44942] New: Make nouveau work for G98 nVidia chip

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

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

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=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=51798 Bug #: 51798 Summary: Cannot enable second video card on nvidia quadro NVS420 Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority:

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?

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

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

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

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

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

Is this expected result for Chipset: G98 (NV98)? $ modinfo nvidia -F version 304.123 $ stat -c %s mmiotrace.log 134659197 $ file mmiotrace.log mmiotrace.log: ASCII text $ grep -i lost mmiotrace.log ; echo $? 1 $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d"); open($fh41ac, ">fuc41ac");

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

On 15.09.2014 15:36, Ilia Mirkin wrote: > On Mon, Sep 15, 2014 at 4:23 AM, poma <pomidorabelisima at 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 >> >>

On 02.12.2014 14:52, Ilia Mirkin wrote: > On Tue, Dec 2, 2014 at 8:50 AM, poma <pomidorabelisima at gmail.com> wrote: >> 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

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

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

I want to try to get VGA passthrough working in a Windows 7 x64 domU. I''m running debian squeeze/testing/unstable with Jeremy''s 2.6.32.x kernel. The best I got to work is the device showing up under Windows 7, with all resources and whatnot. I''ve applied the vga-loadbios patch and vBAR-pBAR patch to xen, and the vBAR-pBAR patch to qemu-dm. This behaviour