similar to: Nouveau fails to initialize G94GL / Quadro-FX1800 on aarch64 board

Very odd. Perhaps you're trying to run X as non-root and don't have proper permissions on /dev/dri/card0? It seems like something in https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nv_driver.c#n400 is failing. Not sure what it would be though. HasKMS is returning successfully (since no error is printing and you see the interface version). Will require you to do some

Hi Ilia, > Very odd. Perhaps you're trying to run X as non-root and don't have > proper permissions on /dev/dri/card0? It seems like something in > https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nv_driver.c#n400 Thanks for the pointer, I'll try to dig a bit deeper there. I forgot to mention that I am trying to run X inside an debian unstable chroot (the

Hi, >> Very odd. Perhaps you're trying to run X as non-root and don't have >> proper permissions on /dev/dri/card0? It seems like something in >> https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nv_driver.c#n400 The call to HasKMS came from NVPlatformProbe - NVPlatformProbe succeeds and returns true. However, it seems Xorg aborts before NVPciProbe is

Hi again, Some further digging revealed that NVPlatformProbe is called with the flag PLATFORM_PROBE_GPU_SCREEN, so the flag XF86_ALLOCATE_GPU_SCREEN is passed to xf86AllocateScreen. After xf86AllocateScreen I end up with xf86GPUScreens == 1 and xf86NumScreens == 0. The xf86GPUScreens seems to be ignored by all the following code, only xf86NumScreens is evaluated afterwards in xf86BusConfig:

It's surprising that it's coming up as a platform device and not a pci device. Perhaps xorg was built without pci support? (Not sure if that's even possible.) It should definitely not be coming up as a GPU screen, but as a regular screen. -ilia On Thu, Jul 7, 2016 at 1:15 PM, Clemens Eisserer <linuxhippy at gmail.com> wrote: > Hi again, > > Some further digging

https://bugs.freedesktop.org/show_bug.cgi?id=99071 Bug ID: 99071 Summary: [G94][Quadro FX1800]Trigger rally Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=35171 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Ilia Mirkin <imirkin at

Dear R-help users, I am trying to analyze some visual transect data of organisms to generate a habitat distribution model. Once organisms are sighted, they are followed as point data is collected at a given time interval. Because of the autocorrelation among these "follows," I wish to utilize a GAM-GEE approach similar to that of Pirotta et al. 2011, using packages 'yags' and

https://bugs.freedesktop.org/show_bug.cgi?id=51645 Bug #: 51645 Summary: Unreadable and flickering text in iceweasel Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=107817 Bug ID: 107817 Summary: NV50 : Nvidia NVS295 - Printing out EDID errors about not connected monitor ports Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority:

On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. > I just upgraded to 11.2. I'm getting errors like this in the log: [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f9ed000 unknown] [

Hi Team I need to run vfio driver using qemu and I'm using below xml file for this.. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>instance</name> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu

https://bugs.freedesktop.org/show_bug.cgi?id=97505 Bug ID: 97505 Summary: X11 does not detect nouveau when using the linux kernel EFI Loader (GRUB loader works fine) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=27905 Summary: DVI monitor is blank - DVI detected as Display Port ? Product: xorg Version: 7.5 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

I have the signed firmware (I think) and I'm running a fresh 4.6 kernel. I got an image to show up briefly, rendering the Fedora sign-in screen at something like one frame per ten seconds. But then I got all kinds of garbage, and I see: [ 719.300820] nouveau 0000:09:00.0: disp: outp 04:0006:0f44: link training failed dmesg |grep nouveau says: [ 10.053162] fb: switching to nouveaufb

Hi, The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. I've posted an updated DCB spec here: ftp://download.nvidia.com/open-gpu-doc/DCB/2/DCB-4.x-Specification.html You can diff it against the previous version: ftp://download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html to see what changed (sorry for having to diff html files). The biggest differences are

What seems to be the problem? I think you forgot to include a description of the issues you're seeing. On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [

The nv31m in bug 23212 claims its TV-out and LVDS are in the same connector. Ignore it completely as it's otherwise useless. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_bios.c | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c

Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. Cheers, -ilia On Sat, May 28, 2016 at 4:51 PM, Andy Lutomirski <luto at kernel.org> wrote: > I have the signed firmware (I think) and I'm running a fresh 4.6 > kernel. I got an image to show up briefly, rendering the Fedora > sign-in screen at something like one frame per ten seconds. But then >

Generically, yes, the hardware is supported. On Mon, Sep 18, 2017 at 11:42 PM, <ygrishin-lists at mail2.ca> wrote: > I will update the thread as soon as I get the hardware back. It was > something serious like artifacts or no video in X so that I had to resort to > proprietary drivers. > So the question is whether this hardware is supported or not. > > > On 2017-09-18