search for: nv42

...>> that it's not native PCIe, but some sort of bridge thing IIRC), >>> Cases like the nv34 here (i think there's some nv4x that aren't native >>> pcie too) are what I'm wondering about primarily. >> >> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >> it (with no clients connecting to said X), causes a "failed to idle >> channel" mes...

...e PCIe, but some sort of bridge thing IIRC), >>>>> Cases like the nv34 here (i think there's some nv4x that aren't native >>>>> pcie too) are what I'm wondering about primarily. >>>> >>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>>> it (with no clients connecting to said X), causes a "failed to idle &g...

...thing IIRC), >>>>>>> Cases like the nv34 here (i think there's some nv4x that aren't native >>>>>>> pcie too) are what I'm wondering about primarily. >>>>>> >>>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>>>>> it (with no clients connecting to said X), causes a...

...I have nv18 PCI, nv34 PCIe (note >> that it's not native PCIe, but some sort of bridge thing IIRC), > Cases like the nv34 here (i think there's some nv4x that aren't native > pcie too) are what I'm wondering about primarily. And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing it (with no clients connecting to said X), causes a "failed to idle channel" message in dmesg, which apparently neve...

...system for those old cards set up. > > But I remember Ilia having some legacy things plugged in, so maybe he > could test this patch and see how it goes? Sure, let me know what you need -- I have nv18 PCI, nv34 PCIe (note that it's not native PCIe, but some sort of bridge thing IIRC), nv42 PCIe, nv44 PCIe, nv96 PCIe. Can I just apply this patch, or do I need to do the whole series? What constitutes a success? -ilia

...t;>>> Cases like the nv34 here (i think there's some nv4x that aren't native > >>>>>>>> pcie too) are what I'm wondering about primarily. > >>>>>>> > >>>>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, > >>>>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely > >>>>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing > >>>>>>> it (with no clients conn...

...'s not native PCIe, but some sort of bridge thing IIRC), >>>> Cases like the nv34 here (i think there's some nv4x that aren't native >>>> pcie too) are what I'm wondering about primarily. >>> >>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>> it (with no clients connecting to said X), causes a "failed to idle >>> c...

...sort of bridge thing IIRC), >>>>>> Cases like the nv34 here (i think there's some nv4x that aren't native >>>>>> pcie too) are what I'm wondering about primarily. >>>>> >>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>>>> it (with no clients connecting to said X), causes a "faile...

...;>>>>>>> Cases like the nv34 here (i think there's some nv4x that aren't native >>>>>>>> pcie too) are what I'm wondering about primarily. >>>>>>> >>>>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>>>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>>>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>>>>>> it (with no clients connecting to said...

...t; Cases like the nv34 here (i think there's some nv4x that aren't native >> >>>>>>>> pcie too) are what I'm wondering about primarily. >> >>>>>>> >> >>>>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >> >>>>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >> >>>>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >> >>>>>>> it (with no...

...PCIe (note >>> that it's not native PCIe, but some sort of bridge thing IIRC), >> Cases like the nv34 here (i think there's some nv4x that aren't native >> pcie too) are what I'm wondering about primarily. > > And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, > with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely > starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing > it (with no clients connecting to said X), causes a "failed to idle > channel" message in dmesg, w...

https://bugs.freedesktop.org/show_bug.cgi?id=102352 Bug ID: 102352 Summary: nv4x fan run whole time at 100%, stable patch existing since about 1 year, please merge Product: xorg Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: trivial Priority: medium

...like the nv34 here (i think there's some nv4x that aren't native >>>>>>>>>>> pcie too) are what I'm wondering about primarily. >>>>>>>>>> >>>>>>>>>> And rightly so. With the NV18 PCI, NV34 PCIe, NV42 PCIe plugged in, >>>>>>>>>> with "AutoAddGPU" disabled the NV18 and NV42 seem fine. However merely >>>>>>>>>> starting X (not xinit, not startx, not [gkx]dm) on the NV34 and ^C'ing >>>>>>>>>> it...

...meson: replace deprecated program.path -> program.full_path Ezequiel Garcia (1): modetest: avoid erroring if there's no gamma legacy support Geert Uytterhoeven (8): amdgpu: Fix pointer/integer mismatch warning amdgpu: Use PRI?64 to format uint64_t util: add NV24 and NV42 frame buffer formats util: add pattern support for DRM_FORMAT_NV{24,42} modetest: add support for DRM_FORMAT_NV{24,42} util: fix grey in YUV SMPTE patterns modetest: fix mode_vrefresh() for interlace/dblscan/vscan util: remove unused definitions of RED, GREEN, and BLUE...

...---------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> --- Going to that page doesn't hang firefox for me on NV42 on mesa 9.1.2 or 9.2. (Rendering does appear to be messed up with all webgl things though.) I think there might be some confusion about what you were doing -- were you using osmesa or nouveau as the opengl backend? In any case, check the newest version of mesa and see if it's still happening....

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Tested on NV42 and NV44. drivers/gpu/drm/nouveau/core/engine/mpeg/nv31.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/gpu/drm/nouveau/core/engine/mpeg/nv31.c b/drivers/gpu/drm/nouveau/core/engine/mpeg/nv31.c index b966728..1ab1c7f 100644 --- a/drivers/gpu/drm/nouveau/core/eng...

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Hmmm... FWIW I couldn't reproduce any oddness with a NV42 card, kernel 3.11, and xf86-video-nouveau 1.0.9 both with and without xcompmgr running. Without a compositor, it _is_ a bit on the slow side, but like a half-second, nothing like the 3s delay mentioned in the original description. Anything else odd about your setup? -- You are receiving this mai...

...it goes? > > Sure, let me know what you need -- I have nv18 PCI, nv34 PCIe (note > that it's not native PCIe, but some sort of bridge thing IIRC), Cases like the nv34 here (i think there's some nv4x that aren't native pcie too) are what I'm wondering about primarily. > nv42 > PCIe, nv44 PCIe, nv96 PCIe. > > Can I just apply this patch, or do I need to do the whole series? What > constitutes a success? > > -ilia

The inst variable (and thus engctx) will not be properly populated for pre-NV44 cards. The dma setter method didn't need it anyways, so call it directly instead of the nv_call indirection. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Tested on NV42. Ben, I'm going to guess that you hate this patch, since it gets rid of the beautiful nv_call stuff. However I wasn't sure how to make it work without doing that. Also worth noting that playing back two files via xvmc at the same time corrupts the playback. Not sure what's going on ther...

https://bugs.freedesktop.org/show_bug.cgi?id=56757 Priority: medium Bug ID: 56757 Assignee: nouveau at lists.freedesktop.org Summary: [regression][bisected][screenshots] nvfx -> nv30 driver rework causes regression in UrbanTerror4.2 (beta5) Severity: normal Classification: Unclassified