Re: Panic after update: stable/12-n233561-42cb78bdd49 - n233682-a436245ccf1
- In reply to: David Wolfskill : "Panic after update: stable/12-n233561-42cb78bdd49 - n233682-a436245ccf1"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 29 Aug 2021 14:27:40 UTC
On Sat, Aug 28, 2021 at 08:54:16PM -0700, David Wolfskill wrote: > But only after starting X11. > > The former (stable/12-n233561-42cb78bdd49) is from 10 August; the latter > (stable/12-n233682-a436245ccf1) is from today (28 August). I normally > update this machine (my laptop) daily, but was out of town for a couple > of weeks with fairly spotty connectivity (with a lot of cycling), and > did not attempt updates during that period. > .... After a bit of relection on the issues (catalyzed, in part, by the realization that merely reverting the OS back to stable/12-n233561-42cb78bdd49 did not produce a "working system"), I noticed that the other laptop has a slightly different video controller: Failing: g1-55(12.2-S)[1] pciconf -lv | grep -B 2 Quadro vgapci0@pci0:1:0:0: class=0x030000 card=0x05cc1028 chip=0x11fc10de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GK106GLM [Quadro K2100M]' Working: g1-48(12.2-S)[8] pciconf -lv | grep -B 2 Quadro vgapci0@pci0:1:0:0: class=0x030000 card=0x17b01028 chip=0x13b610de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GM107GLM [Quadro M1200 Mobile]' So, on a hunch, I tried replacing x11/nvidia-driver (which had recently been updated) with x11/nvidia-driver-390. And that allowed X11 to work. I plan to follow up in -ports@, Cc:ing folks involved in that update. Peace, david -- 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.