Xorg Nvidia blank screen Thinkpad T460p

rayit · May 27, 2017

I am trying/searching for some weeks now to get the nvidia card working also.
I am now working with scfb, but would like to get nvidia working.
Startx gives me blank screen with cursor and non moving mouse:
Anybody some idea's?

If you need more information, please let me know.

pciconf -lvbce

 

...

vgapci1@pci0:6:0:0:     class=0x030200 card=0x223217aa chip=0x137a10de rev=0xa2 hdr=0x00

    vendor     = 'NVIDIA Corporation'

    device     = 'GM108GLM [Quadro K620M / Quadro M500M]'

    class      = display

    subclass   = 3D

    bar   [10] = type Memory, range 32, base 0xf3000000, size 16777216, enabled

    bar   [14] = type Prefetchable Memory, range 64, base 0xe0000000, size 268435456, enabled

    bar   [1c] = type Prefetchable Memory, range 64, base 0xf0000000, size 33554432, enabled

    bar   [24] = type I/O Port, range 32, base 0xd000, size 128, enabled

    cap 01[60] = powerspec 3  supports D0 D3  current D0

    cap 05[68] = MSI supports 1 message, 64 bit enabled with 1 message

    cap 10[78] = PCI-Express 2 endpoint max data 256(256) RO NS

                 link x4(x4) speed 2.5(8.0) ASPM L1(L0s/L1)

    ecap 0002[100] = VC 1 max VC0

    ecap 0018[250] = LTR 1

    ecap 001e[258] = unknown 1

    ecap 0004[128] = Power Budgeting 1

    ecap 000b[600] = Vendor 1 ID 1

    ecap 0019[900] = PCIe Sec 1 lane errors 0

This is my 10-nvidia.conf file in:
/usr/local/etc/X11/xorg.conf.d/

 

Section "Device"

   Identifier "NVIDIA Card"

   VendorName "NVIDIA Corporation"

   Driver "nvidia"

   BusID    "PCI:6:0:0"

 EndSection

xorg output:

 

nvidia1: <Quadro M500M> on vgapci1

vgapci1: child nvidia1 requested pci_enable_io

vgapci1: child nvidia1 requested pci_enable_io

nvidia-modeset: Allocated GPU:0 (GPU-eca7559f-4977-efe0-7f8a-6c257259d39c) @ PCI:0000:06:00.0

nvidia-modeset: Freed GPU:0 (GPU-eca7559f-4977-efe0-7f8a-6c257259d39c) @ PCI:0000:06:00.0

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

ACPI Warning: \134_SB.PCI0.RP09.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160527/nsarguments-97)

 

nvidia-debugdump -l

Found 1 NVIDIA devices

        Device ID:              0

        Device name:            Quadro M500M

        GPU internal ID:        GPU-eca7559f-4977-efe0-7f8a-6c257259d3

I tried bith nvidia and nvidia-modeset

free-and-bsd · May 29, 2017

Do you have proper input drivers installed?
You need at least x11-drivers/xf86-input-keyboard and x11-drivers/xf86-input-mouse. And in case of a notebook you might want a touchpad solution.

...well, if you're working with scfb, then I suppose you have them. But it won't hurt to ask.

free-and-bsd · May 29, 2017

Here's another idea (since you welcomed ideas): are you booting via UEFI? If so, you may try booting in BIOS (legacy) mode instead and see if nvidia will work properly that way.
As for me, I'm using legacy because I'm using GRUB instead of the FreeBSD direct boot methods, and the last time I tried it (about 2 years ago, I guess) graphics didn't work well after booting UEFI mode. It may have changed, but I've never checked...

Here is another idea related to UEFI + nvidia.

rayit · May 30, 2017

free-and-bsd said:
Here's another idea (since you welcomed ideas): are you booting via UEFI? If so, you may try booting in BIOS (legacy) mode instead and see if nvidia will work properly that way.
As for me, I'm using legacy because I'm using GRUB instead of the FreeBSD direct boot methods, and the last time I tried it (about 2 years ago, I guess) graphics didn't work well after booting UEFI mode. It may have changed, but I've never checked...

Here is another idea related to UEFI + nvidia.

I tried booting in legacy mode but my laptop stopped.
So I first need to find a way to switch to legacy mode.
As soon as I find some time I will give it a try!

The
kld_list="nvidia" method did not work for me.
Thanks
Raymond

free-and-bsd · Jun 16, 2017

rayit said:
I tried booting in legacy mode but my laptop stopped.
So I first need to find a way to switch to legacy mode.

I wonder if it stopped because the installation itself doesn't contain the legacy booting code... You know, these automated installations decide things on their own. Because, as I understand it, ALL the BIOSes are supposed to support this «fallback» feature.