KGPE-D16/KCMA-D8 Tip: Force sensor module load order to avoid the improper changing of hwmon paths which breaks fancontrol
Applicable to: SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16.
Situation: If you don't have OpenBMC installed you need to run pwmconfig/fancontrol to manage fan speeds.
Problem: Normally the hwmon paths will change almost every boot resulting in the need to run pwmconfig repeatedly or fix them manually in /etc/fancontrol - this was driving me nuts so I searched for and found a solution.
Solution: Create a .conf file in /etc/modprobe.d/ to set sensor module load order with these contents then reboot and fix the hwmon paths in your /etc/fancontrol, reboot again and all should be well :D
softdep fam15h_power pre: k10temp softdep k10temp pre: jc42 softdep jc42 pre: w83795g softdep w83795g pre: radeon
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/10/2018 07:48 PM, Taiidan@gmx.com wrote:
Applicable to: SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16.
Situation: If you don't have OpenBMC installed you need to run pwmconfig/fancontrol to manage fan speeds.
Problem: Normally the hwmon paths will change almost every boot resulting in the need to run pwmconfig repeatedly or fix them manually in /etc/fancontrol
- this was driving me nuts so I searched for and found a solution.
Solution: Create a .conf file in /etc/modprobe.d/ to set sensor module load order with these contents then reboot and fix the hwmon paths in your /etc/fancontrol, reboot again and all should be well :D
softdep fam15h_power pre: k10temp softdep k10temp pre: jc42 softdep jc42 pre: w83795g softdep w83795g pre: radeon
We should probably create a board documentation tips/tricks section in GIT since the Wiki is no longer available.
Side note: I still wish there was an easier way to do this; I never bothered transferring documentation to GIT because of the added time / complexity vs. the Wiki WYSIWYG editor.
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
On 12/11/2018 05:34 PM, Timothy Pearson wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/10/2018 07:48 PM, Taiidan@gmx.com wrote:
Applicable to: SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16.
Situation: If you don't have OpenBMC installed you need to run pwmconfig/fancontrol to manage fan speeds.
Problem: Normally the hwmon paths will change almost every boot resulting in the need to run pwmconfig repeatedly or fix them manually in /etc/fancontrol
- this was driving me nuts so I searched for and found a solution.
Solution: Create a .conf file in /etc/modprobe.d/ to set sensor module load order with these contents then reboot and fix the hwmon paths in your /etc/fancontrol, reboot again and all should be well :D
softdep fam15h_power pre: k10temp softdep k10temp pre: jc42 softdep jc42 pre: w83795g softdep w83795g pre: radeon
We should probably create a board documentation tips/tricks section in GIT since the Wiki is no longer available.
Or create a website with a copy of the wiki.
Side note: I still wish there was an easier way to do this; I never bothered transferring documentation to GIT because of the added time / complexity vs. the Wiki WYSIWYG editor.
Ditto
I edited and made a variety of very helpful wiki pages but even after the community voted to keep the wiki the powers that be got rid of it just the same.
When I have some extra cash I am going to create my own coreboot wiki website with a copy of the previous one since whomever is in charge no longer wishes to host it and I am not willing to transfer everything especially without an easy editor and ability to add images/charts etc...the latest mediawiki version has a top notch WYSIWYG editor!
I feel as though not many people really care about nurturing the non-developer power-user part of the coreboot community, it is choices like getting rid of the easy to edit wiki that discourage potential users by making things seem more difficult and out of principal I simply refuse to give my "real" name (like there is any way for them to check) to obtain a git account.
Despite what people say it was quite easy for me to obtain a wiki account I just followed the instructions and got one a week later (although you might have had something to do with that :3]
Hi,
Side note: I still wish there was an easier way to do this; I never bothered transferring documentation to GIT because of the added time / complexity vs. the Wiki WYSIWYG editor.
we are writing documentation in markdown now. IMHO, a much better choice than WYSIWYG because you can work much faster without caring how things look (if you are not sure about the syntax you can use a modern editor like Vim that highlights things accordingly). You should just try it, since I got used to it, it's like writing code, you can finally concen- trate on the contents. Having things in Git also makes it much easier to track changes and to have reviewed documentation. The Wiki was full of nonsense, so the review is really necessary.
Ditto
I edited and made a variety of very helpful wiki pages but even after the community voted to keep the wiki the powers that be got rid of it just the same.
You are confusing community with non-developer-only-active-on-the- mailing-list-not-much-contributing part of the community. At least that is how the votes against the switch were seen by the coreboot community.
When I have some extra cash I am going to create my own coreboot wiki website with a copy of the previous one since whomever is in charge no longer wishes to host it and I am not willing to transfer everything especially without an easy editor and ability to add images/charts etc...the latest mediawiki version has a top notch WYSIWYG editor!
There was another reason to abandon the Wiki that you seem to have for- gotten: Its contents aren't licensed. You can copy them but just be warned that it might be illegal in your jurisdiction.
Nico
-
Nico Huber -
Taiidan＠gmx.com -
Timothy Pearson