similar to: [Bug 77586] New: [NV98] On recent Linux kernel (3.13 and 3.14), the GPU locks up around the time an X server starts

https://bugs.freedesktop.org/show_bug.cgi?id=104845 Bug ID: 104845 Summary: Nouveau NV98 : 0 A.D. game creates memory mess after short time Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

For NV98+, BSP/VP/PPP are all FUC-based engines. Hook them all up in the same way as NVC0, but with a couple of different values. Also make sure that the PPP engine is handled in the fifo/mc/vm. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- It seems like VP4.0 is basically working here... only mpeg2/vc1 work, but I'm pretty sure that's just a user-side issue. My guess is

https://bugs.freedesktop.org/show_bug.cgi?id=90390 Bug ID: 90390 Summary: [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

https://bugs.freedesktop.org/show_bug.cgi?id=86164 Bug ID: 86164 Summary: Dual screen causes KDE crash on NV50 (NV98) in nouveau (bisected) Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

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=72943 Priority: medium Bug ID: 72943 Assignee: nouveau at lists.freedesktop.org Summary: NV98 [GeForce 9300 gs m] hangs on boot- all linux kernel versions > 3.2 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

>>>>> Tom Callaway >>>>> on Fri, 13 Dec 2019 11:06:25 -0500 writes: > An excellent question. It is important to remember two key > facts: > 1. With gcc on ppc64, long doubles exist, they can > be used, just not safely as constants (and maybe they > still can be used safely under specific conditions?). > 2. I am not an

Do note that 3.6-patched will only be live for a day or two as we branch for 4.0.0 on Friday. Anything committed there is unlikely to make it into an official release (in principle, the 3.6 branch can be revived but it would take a very strong incentive to do so.) If you want an R-3.6.3-for-ppc, I think a vendor patch is the way. AFAIR (it's been more than a decade since I looked at this

Hey, Op 04-06-13 20:38, Ilia Mirkin schreef: > On Mon, Jun 3, 2013 at 5:02 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> These chipsets include the VP2 engine which is composed of a bitstream >> processor (BSP) that decodes H.264 and a video processor (VP) which can >> do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are >> driven by separate

These chipsets include the VP2 engine which is composed of a bitstream processor (BSP) that decodes H.264 and a video processor (VP) which can do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are driven by separate xtensa chips embedded in the hardware. This patch provides the mechanism to load the kernel for the xtensa chips and provide the necessary interactions to do the rest of

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?

$ glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: nouveau GL_RENDERER: Gallium 0.4 on NV98 GL_VERSION: 3.0 Mesa 11.2.0 ======================================================= /etc/X11/xorg.conf.d/nouveau.conf Section "Device" Identifier

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

On Wed, Jun 5, 2013 at 3:05 AM, Maarten Lankhorst <maarten.lankhorst at canonical.com> wrote: > Hey, > > Op 04-06-13 20:38, Ilia Mirkin schreef: >> On Mon, Jun 3, 2013 at 5:02 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> These chipsets include the VP2 engine which is composed of a bitstream >>> processor (BSP) that decodes H.264 and a video

These chipsets include the VP2 engine which is composed of a bitstream processor (BSP) that decodes H.264 and a video processor (VP) which can do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are driven by separate xtensa chips embedded in the hardware. This patch provides the mechanism to load the kernel for the xtensa chips and provide the necessary interactions to do the rest of

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");

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

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

So... I was wondering what the impact of splitting up the card compilation by e.g. generation would be. Depending on the split things would get fairly intertwined, so I thought I'd start small. This just splits NVC0 from everything else. I figure that for the people this matters the most to, NVC0 is the least relevant card -- people with sub-1GB of RAM, older hardware. With my config options

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