Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Aug 2021 07:45:10 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        freebsd-ports@freebsd.org
Subject:   x11/nvidia-driver update to 470.63.01 seems to break GK106GLM [Quadro K2100M]
Message-ID:  <YSuddoAqYrHRvjug@albert.catwhisker.org>

next in thread | raw e-mail | index | archive | help

--ay/MgEHb6wX/Vdui
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

A few days ago, I returned home from a couple of weeks away (during
which I did not do my usual daily updates to FreeBSD & installed ports).

Yesterday, when I updated my main laptop's stable/12 environment, I
found that the machine did not initialize X11 (I use xdm) as expected;
rather, the screen went blank, and I saw a crash dump (information on
which is in
https://www.catwhisker.org/~david/FreeBSD/stable_12/n233672-a436245ccf1/).

A newer laptop (which I have ... slowly ... been trying to get into
suitable working order) did not exhibit the above symptoms upon
performing the same update.

After noticing that the older/failing laptop had:
g1-55(12.2-S)[1] pciconf -lv | grep -B 2 Quadro
vgapci0@pci0:1:0:0:     class=3D0x030000 card=3D0x05cc1028 chip=3D0x11fc10d=
e rev=3D0xa1 hdr=3D0x00
    vendor     =3D 'NVIDIA Corporation'
    device     =3D 'GK106GLM [Quadro K2100M]'


while the newer one had:
g1-48(12.2-S)[8] pciconf -lv | grep -B 2 Quadro
vgapci0@pci0:1:0:0:     class=3D0x030000 card=3D0x17b01028 chip=3D0x13b610d=
e rev=3D0xa2 hdr=3D0x00
    vendor     =3D 'NVIDIA Corporation'
    device     =3D 'GM107GLM [Quadro M1200 Mobile]'

And that x11/nvidia-driver had (during the time I was away) been updated:

commit 1a86bea35222459cae676d18682b85e919f50512
Author: Kevin Bowling <kbowling@FreeBSD.org>
Date:   Sun Aug 15 11:44:34 2021 -0700

    graphics: Make libglvnd a LIB_DEPEND
   =20
    There are still some incoming reports of dep issues when upgrading
    old systems.  This should help with dep solving and getting past the
    file conflicts.
   =20
    Reviewed by:    jbeich, x11 (manu)
    Differential Revision:  https://reviews.freebsd.org/D31465

commit 77a2452a895b80a7136d1453ce4ad5fe00b58773
Author: Kevin Bowling <kbowling@FreeBSD.org>
Date:   Tue Aug 10 19:47:16 2021 -0700

    x11/{linux-nvidia-libs,nvidia-driver}: Update to 470.63.01
   =20
    This is the new stable branch and adds support for Vulkan.
   =20
    See https://www.nvidia.com/Download/driverResults.aspx/177146/en-us
    and https://www.nvidia.com/download/driverResults.aspx/179601/en-us
    for additional changes.
   =20
    PR:             257456
    Approved by:    danfe


I tried removing x11/nvidia-driver and installing x11/nvidia-driver-390
instead ... et voil=E0: working X11 again.

I don't know if this is expected, but figured that some others might
at least be interested, so I'm sharing. :-}

I'm happy to try to help diagnose and/or test, as time & other
resources permit.

Peace,
david
--=20
David H. Wolfskill                              david@catwhisker.org
Life is not intended to be a zero-sum game.

See https://www.catwhisker.org/~david/publickey.gpg for my public key.

--ay/MgEHb6wX/Vdui
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAmErnXZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy
OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2
PclcQQgAmLewxBGcRjfQPybCZhU50eiwrrmRQVdJ72eeXdzqBKjNX5LtGTFiRiqj
kka2IK7VXu6fsNC7JMM5htL6PND42ZQbPlRvYQArakMgkz6XjNXv37HWsU6YvXjU
OCSkxlTW6Fve3yBTpMfymueYO5/qw//FDX6yCaqoo8ld0ANlXju6PhfdjtZSdwg0
8T8epVuG7IJer+WQwxdCpYGTLDAgma+p7NIEDN5ok3kIrO64k0XdAKHbmuNnY6ef
qUYHpNXdDYSG7ec16j4BN9ux6UMa8e4HLR2bmXrFkjE8bHke4gB5UJuyAnHTNS91
bYLzez42ud3i+OoOTgGdZXdnXe1j2Q==
=vc70
-----END PGP SIGNATURE-----

--ay/MgEHb6wX/Vdui--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YSuddoAqYrHRvjug>