Re: need perm. fix for monitor/display problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 17/12/2022 22:38, Barry wrote:


On 17 Dec 2022, at 17:47, home user <mattisonw@xxxxxxxxxxx> wrote:

On 12/17/22 10:15 AM, John Pilkington wrote:

I run it in a konsole (KDE terminal) tab and see a screenful of data refreshed every 10 seconds.  Mainly the interest here is on jobs run by user akmods.  For me it's just a guide showing when the system should be able to boot without doing complex things while in an unfamiliar state. If you boot before then it should work, but the action will be more 'under cover'.  Escape should reveal more.

For some time now, I've seen another process/user "mandb" running at the same time as or after the akmod processes at the end of (sometimes after) "dnf update".  That mandb process seems to be slow; it takes a few minutes; yet it uses only one CPU.  I'm guessing it's an I/O intensive process, but I don't really know.  It seems that that, too, apparently has to be watched to make sure it's done before rebooting.

I believe that if you reboot while mandb or akmod is running its fixed up as the system boots.
I do not wait at all after dnf update and i have never seen a problem.
This has been reliable for many years on my experience on multiple systems.
I update approx 8 fedora systems every week like this.

Barry

Agreed. It usually works. But if it doesn't there's more to fix, in a more difficult environment. The rpmfusion guide recommends waiting.

https://rpmfusion.org/Howto/NVIDIA

/!\ Please remember to wait after the RPM transaction ends, until the kmod get built. This can take up to 5 minutes on some systems.

and this is worth a look too:  https://rpmfusion.org/CommonBugs



There were statements here when, 6.0.5 first caused problems, that the 5-to-6 transition was simply linux running out of fingers and toes.  I liked the image, but the problem was, briefly, real.
John

Bill.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux