I am experiencing an weird problem in Linux. Except Fedora, the other Linux distros which I have tried so far, Debian, Mint, Pop OS (I haven’t tried Ubuntu yet, probably never will) didn’t recognise the normal USB ports on my Gigabyte 970A-DS3P motherboard. These three popular distros only recognise the USB 3.0 ports. How could I be sure? When I tried to install these 3 distros from live USB using normal USB ports i.e. USB 2.0 ports, after showing the initial menu, they failed to initiate the live OS showing ‘Device Descriptor Error’. Please note that before doing anything, I thoroughly cleaned my PC and all other hardwarws and ensured that there is no such dust inside the cabinet and on any hardware and their connectors / ports and if dust would be the cause of this problem, then it would happen to Fedora also. Then I installed these 3 OS, Debian, Mint and Pop from live USB using USB 3.0 ports without any error. But after fully installed, they still didn’t recognise the USB 2.0 ports. But when I was installing Fedora, I connected the live USB into a USB 2.0 port and the installation went through without any error and after installation Fedora is showing no problem on accessing all the USB ports i.e USB 2.0 and 3.0 ports. I am even getting a very good bandwidth when accessing internet using my WiFi dongle connected to a USB 2.0 port.
I have no clue about this weird behaviour. Can you friends shed some light on this? It will be really an eye opener.
Let’s compare the output of
lspci -nnk
from Fedora, with the same commands output from a “defect” system.
Edit:
worth to look at:
WOW!!! THANK YOU SO MUCH!!! I will do it tomorrow (the Github solution) and will get back with the result. 
About 2-3 years ago I had an issue with USB (don’t recall specifics) with my Gigabyte AMD mobo - and I did a BIOS/UEFI/Firmware update on the motherboard and that resolved my issues…
I may have even mentioned on here - back then…
The last version of this motherboard is mentioned as ‘BETA BIOS’. I am very scared of doing anything with the BIOS. If anything goes wrong, my motherboard will be gone.
I am describing here the process I followed to solve the USB problem. But before that, I should let you know about another weird problem I have experienced while using a live USB. Today I have downloaded LMDE Mint and made a persistent live USB with 20GB for the Linux partition. Now the process:
- I entered the BIOS setup and enabled the ‘IOMMU Controller’;
- Now, I boot via live USB in UEFI mode and then my mouse and keyboard stopped responding which were connected in USB 3.0 ports. So, I figured that this time USB 3.0 ports are not responding.
- I reconnected the mouse and keyboard in USB 2.0 ports and they started working again. I think, enabling the ‘IOMMU Controller’ caused this problem though I don’t know why.
- Now, my mouse, keyboard, USB drive (live USB) and WI-FI dongle, all were connected in USB 2.0 ports and the boot into the live USB was successful.
- Now when I reached the no. 8 step of the Github tutorial and ran the command
grub2-mkconfig -o /boot/grub2/grub.cfg
and it showed:
Command ‘grub2-mkconfig’ not found, did you mean: command ‘grub-mkconfig’ from deb grub-common
- Then I ran this command:
grub-mkconfig -o /boot/grub2/grub.cfg
and it showed:
/user/sbin/grub-probe: error: failed to get canonical path of ‘overlay’
Now what to do?! I couldn’t find any solution which could solve this problem.
Something is not mounted.
Then I think the culprit was the live USB connected to the USB 2.0 port. I will update after testing it again. Thanks @nevj.
Update: Nope. It is impossible. When I connect the live USB into USB 3 port, it is inaccessible. It’s not even booting from the USB and is giving ‘Device Descriptor Error’ and when I boot from the live USB while connecting it to USB 2 ports, grub cannot be saved. I searched internet and found that grub.cfg cannot be saved while on live USB because it remains read-only. I think, the problem is not in the distro because these 3 are very well-known, very popular distros. So they must tested their products thoroughly before releasing. This problem might be specific to this motherboard as it is very old. So, I think, I should stick to Fedora for the time being and though it consumes almost 2GB RAM when idling, it is not that bad, you know and we all know that GNOME has a bad reputation of being a memory eater. So, Fedora developers cannot do anything about it unless Redhat decides to leave GNOME. But, though the effort did not give the expected result, we tried and that counts. I should thank you @kovacslt, @nevj and @daniel.m.tripp for trying to help me and believe me, I got you, the friends, the brother here, I was looking for through my entire life and for this reason, I will stay here till my end, if I would not be kicked out. Love you all. 
Sorry, I have very busy days…
If you boot from USB, that is a live system. You would need to update GRUB of an installed system