i did all the procedure again. This time, the system did ask me for scanning various sensor.
I did everything and saved the script.
But, again, empty line as output.
I did read , while scanning, "K10" recognized as cpu
I run an AMD Ryzen 5600G. Not the same CPU as you , but this basic info may help.
I noticed that the default config for the cputemp widget was wrong, and when implementing the config in the guide it was also wrong (off by about +18C).
So using some other softwares as a temperature reference (bpytop and inxi), I was able to determine that instead of the k10temp value from sensors, I needed to use the CPUTIN value. I ended up modifying the /usr/sbin/cpu-temp file to use this line, instead of the line in the guide:
sensors nct6779-isa-0290 | awk '$1 == "CPUTIN:" { print $2 }' | grep -o '[0-9.]\+' | sed 's/\.//'
I don't know if the Phenom uses the same CPUTIN value, but if you want to try to find the correct one using the method I used, you can install bpytop and/or inxi with apt-get install bpytop and/or apt-get install inxi. Bpytop is a nice top alternative that combines the most important info of most top programs in one application, and inxi is kind of a general system info utility similar to dmidecode, but a fair bit better for finding info.
Run bpytop and look for the cpu temperature in the top right of the screen or run inxi -Cs and it will give you the cpu temp. Then run sensors and look through the list of values to see which temperature variable name looks to be the right one. If you are not sure it may help to run 2 terminal windows with with bpytop or watch inxi -Cs (watch will make inxi live monitor the temps instead of exiting after running it) in one and sensors in the other, so you can find the variable/sensor name that matches the CPU temp in inxi or bpytop, you may want to re-run sensors a few time to make sure the teps change in a similar fashion. Then if you think you have the right one picked out, look at the top of that section of the sensors output and you will see the chipname that the sensor belongs to. You can run watch sensors <chip_name> and do something that will cause the CPU temp to change and confirm that the same change happens in both the bpytop/inxi window and the sensors window. (For me the chip my sensor was on was nct6779-isa-0290 and the sensor name was CPUTIN)
You will note that since I found that the correct sensor for me was CPUTIN and it was in the nct6779-isa-0290 chip group, my config modification is invoking sensors with the chip name, then piping to awk, grep and sed like the guide to extract the temperature and remove all the non numeric characters. The difference is that I found the correct chip name and sensor for my CPU and used those to re-write the first part of the config from the guide.