On Thu, 4 Jan 2024 18:02:05 -0000 (UTC), Jim Henderson wrote:
On Thu, 4 Jan 2024 09:45:03 +0300, Andrei Borzenkov wrote:
[ 6.877] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
It sounds like something changed in the kernel. Try rollback and applying each update one by one to find which package triggers this problem. Educated guess - it should be kernel update.
Thanks - I'll give the kernel update a try and see if that resolves it. I had thought the xorg updates would (hence why I locked them), but that wasn't it.
Will report back today if it was the kernel or not. The full list of updates is quite long (279 as I recall), so one-by-one would take a bit of time (suppose I could narrow it more quickly by going by halves instead of one by one, though).
This was a good guess - I started by locking anything starting with kernel-default, and the system booted successfully. I then updated just the kernel-default package, and the boot failed the same way. It seems that the update that causes this is the update from 5.14.21-150500.55.36 (which is what is working) to the latest 5.14.21-150500.55.39 version. Will get a bugzilla bug entered for it. Thanks for the pointer in the right direction. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits