On Wed, 2013-07-10 at 14:54 +0200, Guillaume Thouvenin wrote: > Alex Williamson <alex.williamson@xxxxxxxxxx> a écrit : > > > Are you sure that nvidia-smi is relevant to the K1/K2 devices? Does it > > work on the host? > > Yes it works on the host and I have some information like power > consumption, temperature of the GPU, etc... > > > Are > > there other tests you can do to check whether the device is otherwise > > available? > > I also tried to start an X server but I got the same error reported in > the syslog: [ 435.745673] NVRM: RmInitAdapter failed! (0x26:0x38:1170) > [ 435.745695] NVRM: rm_init_adapter(0) failed > > And in the xorg.log I have: > > > [ 423.624] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32 > [ 423.624] (==) NVIDIA(0): RGB weight 888 > [ 423.624] (==) NVIDIA(0): Default visual is TrueColor > [ 423.624] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) > [ 423.624] (**) NVIDIA(0): Option "NoLogo" "true" > [ 423.624] (**) NVIDIA(0): Option "UseDisplayDevice" "none" > [ 423.624] (**) NVIDIA(0): Enabling 2D acceleration > [ 423.624] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; > enabling NoScanout > [ 423.624] (**) NVIDIA(0): mode > [ 435.746] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at > PCI:0:3:0. Please > [ 435.746] (EE) NVIDIA(0): check your system's kernel log for > additional error > [ 435.746] (EE) NVIDIA(0): messages and refer to Chapter 8: > Common Problems in the > [ 435.746] (EE) NVIDIA(0): README for additional information. > [ 435.746] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! > [ 435.746] (EE) NVIDIA(0): Failing initialization of X screen 0 AFAICT, rm_init_adapter is in the binary blob part of the nvidia driver, so we can't simply check the code to see what's wrong. Google finds this: http://forums.gentoo.org/viewtopic-t-961110.html?sid=0a60d40ba001f7bbe799bb16b2921cac That was of course on bare metal, but note that the IOMMU prevented some accesses and the solution was to disable the IOMMU. Of course we can't disable the IOMMU in this case. Do you see any IOMMU faults in dmesg on the host around this error? Does nouveau work? Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
