GPU fan speed uncontrolable

Just re-installed Manjaro on mine new config and have troubles with the GPU fan speed (currently on max speed i suppose).

Here is the output of inxi -F

System:    Host: nemanja-m Kernel: 5.9.11-3-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.20.3 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <superuser/root required> 
           UEFI: American Megatrends v: 5603 date: 10/14/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP L2 cache: 4096 KiB 
           Speed: 1885 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 1887 2: 1887 3: 2159 4: 2191 5: 2193 6: 2195 7: 2066 
           8: 2067 9: 2191 10: 1886 11: 1956 12: 2093 13: 1884 14: 1887 15: 1931 16: 2189 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu 
           v: kernel 
           Display: x11 server: X.O rg 1.20.9 driver: amdgpu,ati unloaded: modesetting resolution: 1: 1920x1080~60Hz 
           2: 1920x1080~60Hz 
           OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.39.0 5.9.11-3-MANJARO LLVM 11.0.0) v: 4.6 Mesa 20.2.3 
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.9.11-3-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: 24:4b:fe:5c:62:a5 
Drives:    Local Storage: total: 2.05 TiB used: 15.18 GiB (0.7%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
           ID-2: /dev/sda vendor: Samsung model: HD103UJ size: 931.51 GiB 
           ID-3: /dev/sdb vendor: Biostar model: S100-256GB size: 238.47 GiB 
Partition: ID-1: / size: 915.60 GiB used: 15.18 GiB (1.7%) fs: ext4 dev: /dev/nvme0n1p2 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 46.4 C mobo: N/A gpu: amdgpu temp: 39.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 343 Uptime: 3m Memory: 15.63 GiB used: 1.36 GiB (8.7%) Shell: Bash inxi: 3.1.08 

I executed sensors-detect

sensors-detect version 3.6.0
 Board: ASUSTeK COMPUTER INC. PRIME A320M-K
 Kernel: 5.9.11-3-MANJARO x86_64
Processor: AMD Ryzen 7 2700X Eight-Core Processor (23/8/2)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8655E Super IO Sensors'                        Success!
    (address 0x290, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       Success!
    (confidence 6, driver `lm78')
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.
Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: AMDGPU DM i2c hw bus 0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: AMDGPU DM i2c hw bus 1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: AMDGPU DM i2c hw bus 2 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Next adapter: AMDGPU DM i2c hw bus 3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Next adapter: AMDGPU DM i2c hw bus 4 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: AMDGPU DM aux hw bus 0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: AMDGPU DM aux hw bus 1 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes
Now follows a summary of the probes I have just done.
Just press ENTER to continue:  
Driver `to-be-written':
  ISA bus, address 0x290
    Chip `ITE IT8655E Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
  Chip `AMD Family 17h thermal sensors' (confidence: 9)
Note: there is no driver for ITE IT8655E Super IO Sensors yet.
Check hwmon.wiki.kernel. org/ device_support_status for updates.
No modules to load, skipping modules configuration.
Unloading i2c-dev... OK
Unloading cpuid... OK

and then sensors:

k10temp-pci-00c3
Adapter: PCI adapter
Vcore:         1.46 V  
Vsoc:        825.00 mV 
Tctl:         +59.0°C  
Tdie:         +49.0°C  
Icore:        40.00 A  
Isoc:          4.50 A  
 > nvme-pci-0100
Adapter: PCI adapter
Composite:    +39.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +39.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)
>amdgpu-pci-0800
Adapter: PCI adapter
vddgfx:      950.00 mV 
fan1:        1147666 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +38.0°C  (crit = +94.0°C, hyst = -273.1°C)
power1:       35.17 W  (cap = 155.00 W)

For a fact i know that this card can work great on Manjaro (followed random tutorials several months ago and got it working).

Now i tweaked some random files and got the 1147666 RPM , and got some random freezes every couple of second, but the default value was N/A , i will probably reinstall Manjaro again as i done already too much stuff for couple of days in trying to setup the fan speed.

I also tried installing radeon-profile and fan-control, but nothing changes the speed too.
If anyone haves any idea that could help me let me test them…

This is about one of the most useless snippets of information I’ve ever seen. Was it .[bash,zsh]rc? Or, something in $HOME/.local/share? A line in your firefox/thunderbird profile? See what I mean?

Or, is this a mild way of saying that you started editing files on the fly, because some $INTERNET_PERSON says so, and you don’t remember what you changed?

I could’ve added some stuff to look at, but if you’re just going to reinstall…I won’t bother.

The sensors output by default (after manjaro installation)

Adapter: PCI adapter
vddgfx: 950.00 mV
fan1: 1147666 RPM (min = 0 RPM, max = 3200 RPM)
edge: +38.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 35.17 W (cap = 155.00 W)

The edits i made did not affect anything regarding of the fan speed (i can provide urls when i get home from work of the forum post , and further information).