SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Maybe this is more broadly useful on x86 hardware, but I personally haven't seen such cases (if they exist, then the remainder of this post is to be ignored), so I think this would be a good case for mozes to add a package to Slackware ARM which isn't in the x86 tree.
According to documentation, it is too late to load microcode as in post #216. Microcode must be loaded using early microcode update driver support in the kernel (if not possible via BIOS).
According to documentation, it is too late to load microcode as in post #216. Microcode must be loaded using early microcode update driver support in the kernel (if not possible via BIOS).
This. The old (Late) processor microcode reloading has issues. Don't use it.
Maybe this is more broadly useful on x86 hardware, but I personally haven't seen such cases (if they exist, then the remainder of this post is to be ignored), so I think this would be a good case for mozes to add a package to Slackware ARM which isn't in the x86 tree.
Hi Rob,
I2C Tools is very useful for monitoring parameters on PC motherboards and embedded systems. Such as voltages, temperatures, fan speeds, etc. It can also be invaluable for troubleshooting I2C and SMBus issues. I'll grant you that it's perhaps more useful on sbc ARM devices, but I still believe there's many applications for it on x86 architecture and therefore a good thing to have available for any Slackware system.
According to documentation, it is too late to load microcode as in post #216. Microcode must be loaded using early microcode update driver support in the kernel (if not possible via BIOS).
According to that README you also need a kernel compiled with CONFIG_MICROCODE_EARLY, which is nowhere to be found in 4.14.
Don't get me wrong, I don't have a NIH syndrome - I'll give a warm welcome to any versatile, working and sustainable solution for loading CPU microcode updates in Slackware.
... working and sustainable solution for loading CPU microcode updates in Slackware.
Current process works here ... on both an older i5 and a newer one.
[ 0.000000] microcode: microcode updated early to revision 0x1c, date = 2015-02-26
[ 0.000000] Linux version 4.14.13 (root@cx601525-ag2) (gcc version 7.2.0 (GCC)) #12 SMP PREEMPT Wed Jan 10 11:05:08 CST 2018
following the update to mpfr and the bump in .so-version, the new version of libmpfr needs to be added to aaa_elflibs as gawk is used by the package management scripts.
following the update to mpfr and the bump in .so-version, the new version of libmpfr needs to be added to aaa_elflibs as gawk is used by the package management scripts.
It should be feasible to sed-ify the scripts filelist.awk, install-new.awk, cutpkg.awk and pkglist.awk instead.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
