No graphics output Quadro RTX 4000 Ubuntu 18.04

Here is my problem. I have a Nvidia Quadro RTX 4000 installed on my ubuntu 18.04 workstation. I do not manage to get a graphics output from the nvidia card, instead I am using the output from the onboard aspeed graphics card.

I have installed Cuda 10.1 according to the nvidia website and my card is found by nvidia-smi

| NVIDIA-SMI 418.87.01    Driver Version: 418.87.01    CUDA Version: 10.1     |
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|   0  Quadro RTX 4000     On   | 00000000:AF:00.0 Off |                  N/A |
| 30%   38C    P8     1W / 125W |      0MiB /  7952MiB |      0%      Default |
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|  No running processes found                                                 |

If I start nvidia-settings I get an error message

ERROR: Unable to load info from any available system

If I want to start for instance the particles cuda test program a window opens and closes again immediately with the output

CUDA Particles Simulation Starting...

NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.

grid: 64 x 64 x 64 = 262144 cells
particles: 16384
GPU Device 0: "Quadro RTX 4000" with compute capability 7.5

CUDA error at code=999(cudaErrorUnknown) "cudaGraphicsGLRegisterBuffer(cuda_vbo_resource, vbo, cudaGraphicsMapFlagsNone)"

Interestingly BOINC finds the graphics card and can run CUDA and OpenCL code.

I am really confused about this problem. I will also attach the nvidia bug report.

nvidia-bug-report.log.gz (1.18 MB)

The graphics is running on the integrated Aspeed server graphics.
Please disable the Aspeed in bios and connect the monitor to the outputs of the nvidia gpu.

That worked. Although I cannot enter my BIOS settings anymore, which is nevertheless not an NVIDIA problem, I guess.