Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1036883 > unrolled thread

Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02 Konstantinos Margaritis <markos@freevec.org> - 2020-12-10 17:10 +0100
    Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02 Konstantinos Margaritis <markos@freevec.org> - 2020-12-21 15:00 +0100

#1036883 — Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02

On 10/12/20 5:37 μ.μ., Andreas Beckmann wrote:
> If it works with Linux 5.8, can you stick to an older kernel (which will
> not receive security updates) until there is a newer driver release
> available from Nvidia?

I just installed 5.8 from buster-backports along with tesla-440 driver 
and it seems to give slightly better results,the modules build and load, 
but similar errors in kernel:


[   15.167039] NVRM: GPU 0000:01:00.0: DMA address not in addressable 
range of device (0x800200541060000-0x80020054106ffff, 
0x800000000000000-0x80000ffffffffff)
[   15.167070] NVRM: GPU 0000:01:00.0: DMA address not in addressable 
range of device (0x800200541060000-0x80020054106ffff, 
0x800000000000000-0x80000ffffffffff)
[   15.168422] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0x40:937)
[   15.168517] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device 
minor number 0

...
[   18.058799] NVRM: GPU 0000:01:00.0: DMA address not in addressable 
range of device (0x800200532660000-0x80020053266ffff, 
0x800000000000000-0x80000ffffffffff)
[   18.058816] NVRM: GPU 0000:01:00.0: DMA address not in addressable 
range of device (0x800200532660000-0x80020053266ffff, 
0x800000000000000-0x80000ffffffffff)
[   18.059885] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x31:0x40:937)
[   18.059943] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device 
minor number 0


As for Xorg.0.log:

...

[    18.046] (II) NVIDIA GLX Module 440.118.02  Thu Sep  3 09:45:23 UTC 2020
[    18.049] (II) NVIDIA: The X server supports PRIME Render Offload.
[    18.158] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at 
PCI:1:0:0.  Please
[    18.158] (EE) NVIDIA(GPU-0):     check your system's kernel log for 
additional error
[    18.158] (EE) NVIDIA(GPU-0):     messages and refer to Chapter 8: 
Common Problems in the
[    18.158] (EE) NVIDIA(GPU-0):     README for additional information.
[    18.158] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA 
graphics device!
[    18.158] (EE) NVIDIA(0): Failing initialization of X screen
[    18.158] (II) UnloadModule: "nvidia"
[    18.158] (II) UnloadSubModule: "glxserver_nvidia"
[    18.158] (II) Unloading glxserver_nvidia
[    18.158] (II) UnloadSubModule: "wfb"
[    18.158] (II) UnloadSubModule: "fb"
[    18.158] (==) NVIDIA(G0): Depth 24, (==) framebuffer bpp 32
[    18.158] (==) NVIDIA(G0): RGB weight 888
[    18.158] (==) NVIDIA(G0): Default visual is TrueColor
[    18.158] (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0)
[    18.158] (**) NVIDIA(G0): Enabling 2D acceleration
[    18.158] (EE) NVIDIA(G0): GPU screens are not yet supported by the 
NVIDIA driver
[    18.158] (EE) NVIDIA(G0): Failing initialization of X screen
[    18.158] (II) UnloadModule: "nvidia"
[    18.158] (II) UnloadSubModule: "wfb"
[    18.158] (II) UnloadSubModule: "fb"
[    18.158] (EE) Screen(s) found, but none have a usable configuration.
[    18.158] (EE)
Fatal server error:
[    18.158] (EE) no screens found(EE)

I don't mind waiting for a newer release, or using an older kernel, 
however any suggestions to solve the problem would be appreciated, even 
outside this particular bug report.

Regards

Konstantinos

[toc] | [next] | [standalone]

#1038581

On 19/12/20 3:24 μ.μ., Andreas Beckmann wrote:
> Control: severity -1 important
>
> This bug should not cause nvidia-cuda-toolkit to be removed from testing...

Indeed, and seeing that Nvidia only supports the "compute" mode of the 
driver on ppc64le, I'm having second thoughts about using them on my 
Talos II. I think I will revert back to AMD in this case and use plain 
the Titan cards on plain x86.

> Did you ever have a working kernel/driver/toolkit combination?
Partly yes, I could get CUDA working, on latest testing even, but it was 
very shakey and as soon as I tried to use both cards, it would crash the 
driver and I would have to reboot the system.
>
> IIRC you had two GPUs in that machine, could you try with only one
> installed?
That made things a bit better, but still it's not entirely stable. It's 
not a tested/supported configuration and it shows.
>
> I seem to remember reading that Ubuntu on ppc64el is in cuda 11.x no
> longer a combination supported by nvidia. That makes it a bit more
> difficult to find a setup that is supposed to work. But if it actually
> works in some RHEL/CentOS environment, why shouldn't we get it runnning
> on Debian as well?

Indeed, that is the case. Unless one owns a very high end data center 
card on ppc64le, it's probably not going to be supported by nvidia.

I'm not sure if I should ask you to close the bug as wontfix, I don't 
expect the situation will change soon, and it's not something that 
Debian can fix tbh. As I said I already considering using the cards on x86.

Nevertheless, I appreciate your help, thank you.

Regards

Konstantinos

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web