On 15/12/2022 21:17, home user wrote:
On 12/15/22 2:56 AM, John Pilkington wrote:
> On 15/12/2022 03:45, home user wrote:
[... snip ...]
>
> I just did 'dnf upgrade' on a system with an old Dell monitor and an
> Android tv. Graphics card is GT 710 running X11 in KDE. The active
> screen switches during boot, so it's best to have both screens powered
> up at that time.
I almost always have both monitors on when starting to boot. The only
exceptions I can think of is when dealing with possible monitor or
graphics card issues.
> There have been lots of KDE-related updates since Nov 3, so the
> upgrade may take some time. And allow several minutes to build the
> kmods before doing 'sudo systemctl reboot'
It's seems to have been true for a long time now that, after "dnf
upgrade", the kmods build takes a long time. There seems to also be a
process involving mandb that takes a long time. What I always do is
watch ksysguard. Only once that shows negligible CPU activity and the
cooling fans get slower and quieter, I reboot. I've also noticed that
the shutdown part of reboot sometimes (recently: always!) takes quite
long (minutes).
> HTH
>
> John P
No one has yet answered my question:
Is what is currently in RPM Fusion non-free 36 updates everything I need
to really fix the problem for f36?
That should need only a yes or no answer.
I have no way of knowing what idiosyncrasies your system may have.
I said what works for me. I use 'atop' to judge when the builds have
completed, and yes, recent shutdowns (but not today's) have also been
affected by a delay timer.
I notice that my list of installed rpms includes a recent firmware
update. I suppose that must be from rpmfusion, but I haven't checked.
John