After Upgrading My Hardware, Fedora No Longer Works Properly

Ask Fedora
1

After upgrading my desktop’s hardware, weird stuff started happening on Fedora 42. I could no longer launch Steam. Anytime I tried performing a search on the internet, it was slow, and I had to perform the search multiple times for it to go through. Trying to update packages through the terminal resulted in could not reach server outputs. Originally, I thought there was something wrong with a recent update to Fedora. However, after testing my laptop, which is also running Fedora 42, everything was working fine. I thought that I could maybe try a clean install of Fedora 42, but the ISO faces the same problems.

The hardware in the desktop:

  • Gigabyte X870 Aorus Wifi 7
  • Ryzen 9700x
  • Corsair DDR5 ram- adding up to 64 gigs
  • XFX 7800 XT GPU
2

Given you have changed the hardware I would suspect an issue with that.
Top of my list would be to check cabling and that connections are solid.
Are you overclocking?
Regardless try reseting the BIOS to it defaults and see if that helps.
Then check ram for issues with memtest.

Also have a look at system journal for errors as well as check dmesg for errors.

3

Welcome to Fedora @gilledsail

First I would do is to check if there are updates for your bios. This you could do with:

fwupdmgr get-devices
4

Try running a traceroute to whatever search engine you’re using eg., use traceroute www.google.com if you’re using Google. See if there are any slow hops, or any that don’t respond, showing only a set of three asterisks.

5

Thanks for the responses guys. I checked the wiring and everything appeared to be fine. The motherboard was using an older software version. Updating that to the latest version did not seem to fix anything.

I ran fwupdmgr and its update, but it said that there were no updates to pull.

I tried traceroute on duckduckgo, and there were quite a bit of triple asterisks in the output.

6

OK, Those non-responding hops are where your trouble is. Do they all look like they’re in the same network or geographic region? If so, it’s a known issue and whoever’s in charge there knows about it and is working to fix it.

7

Triple * is common for routers that are deliberately not setup to respond to ping. It is not a sign of problems.

8

One set of triple stars may be that, but “quite a bit” of them suggests otherwise especially when there are routing issues being diagnosed.

9

Not my experience. If there are lots of hops then its common to see lots of triple *. As an example for this site…

$ traceroute discussion.fedoraproject.org
traceroute to discussion.fedoraproject.org (2602:fd3f:3:ff01::2b), 30 hops max, 80 byte packets
 1  6.b.b.0.9.b.e.f.f.f.e.a.3.4.a.d.0.0.0.0.f.2.8.1.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:182f:0:da43:aeff:feb9:bb6)  0.619 ms  0.631 ms  0.571 ms
 2  b.gormless.tch.aa.net.uk (2001:8b0:0:53::52)  4.124 ms  4.060 ms  3.998 ms
 3  ixp-lonap-ld.as20712.net (2001:7f8:17::50e8:1)  3.937 ms  3.882 ms  3.830 ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  civilized-discourse-construction-kit-inc.e0-45.switch1.sea1.he.net (2001:470:1:513::2)  127.987 ms  127.923 ms civilized-discourse-construction-kit-inc.port-channel11.switch1.sea1.he.net (2001:470:1:34c::2)  127.665 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *