I've upgraded from F37 with no issue, I am using RPi4 as a PC. My RPi4
overclocked to 2000. 

On Tue, 2023-04-25 at 22:44 +0100, Peter Robinson wrote:
> On Tue, Apr 25, 2023 at 10:40 PM Randy DuCharme
> <radio.ad...@gmail.com> wrote:
> > 
> > Am I the only one having difficulties with this?  It's worse than
> > half
> > as fast as f37 was, NTP/Chrony refuses to work..... I could go on.
> > Afraid I'm going to have to ditch this.  Kernel's been building for
> > 7
> > hours now.  Clocking, over-clocking, governors, schedulers make no
> > difference.  Btrace, strace points to nothing. CPU load through the
> > roof
> > though yet I don't see anything especially noteworthy.
> > 
> > Thoughts?
> 
> I've not seen regressions like that, but I've also not had the time
> to
> look at performance, but then time sync seems to work fine.
> 
> Maybe check kernel major versions, what did you have prior to the
> upgrade from F-37, you don't give any real details, like when you
> upgraded, whether you're running wired or wireless network.
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-le...@lists.fedoraproject.org
> 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/arm@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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/arm@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to