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.
lm-sensors has 3.4.0 out since summer, although, their website seems to be currently down. I've downloaded the source from here and recompiled it with no changes to the SlackBuild. Seems to be working fine (I was hoping it would fix a bug I found with pwmconfig, but no luck). Per archive.org, these are the changes:
Code:
3.4.0 (2015-06-25)
documentation: Update the note about libsensors license
sensors.conf.5: Enhance the hysteresis documentation
sensors.conf.default: Add support for NCT6779 and NCT6791
libsensors: Get rid of arbitrary limit on per-type sensor count
Add support for temperature min and critical min hysteresis
Fix sparse warnings
sensors: Add support for temperature min and critical min hysteresis
fancontrol: Deal with moving hwmon attributes
Fix shell error when FCFANS is not set
Reduce memory consumption (#2391)
healthd: Avoid using external commands
sensors-detect: Add detection of ADC128D818
Add detection of AMD family 16h Kabini and Mullins
Add detection of ITE IT8620E and IT8623E
Add detection of TMP441, TMP442, LM95233, LM95234,
and LM95235
Add detection of NCT7802Y
Print kernel version and processor information
Add detection of NCT6792D
Add reference to nct6683 driver
Show that NCT6102D/6104D/6106D are supported by nct6775 driver
Show NCT5573D as compatible to NCT6776F with same chip ID
Document support for EMC1402, EMC1404, and EMC1424
Detect new revisions of EMC14xx
Add detection of EMC1422
Document driver support for TMP431 and TMP432
Add detection of TMP400 and TMP435
Add detection of IT8786E
Add detection of IT8780F
Add detection of IT8731F and IT8732F
Add detection of Intel 5500/5520/X58
Loosen detection rules for TS3000/TSE2002
Add detection of TSE2004 and TS3001
Document driver support for NCT7802Y
Add detection of NCT7904D
Add detection of IT8790E
Fix graphics cards detection (#2386, #2392)
Skip more addresses on graphics card I2C bus (#2392)
The problem is that rather than symlink libudev.so.0 to libudev.so.1 (which is just asking for problems with apps that expect some functions which were removed from .so.0), we rebuilt things which were linking libudev.so.0 to instead link libudev.so.1, which is the CORRECT way to do it.
True, though then again, I did willingly guinea pig myself.
Would it be too much to request a set of configure scripts for kernel 4.2.x or later tailored for Slackware be available in /testing.
This may be of some benefit to Intel, Nvidia, and AMD video hardware users. This doesn't mean we need xf86-video-amdgpu just yet, but it is supported with a DRM driver by kernel 4.2 and later for Radeon R9 series and later GPUs.
Here are new stable versions of the gimp-2.8.16 + babl-0.1.12 and gegl-0.3.0
I've successfully built them with the standard Slackware SlackBuild scripts, and they appear to run well on my slackware64-current.
Meanwhile, if anyone wish to test a development git-version of the gimp-2.9, here is my SlackBuild script that builds it into a separate directory, /opt/gimp-2.9 allowing to run the gimp-2.9 independently from the installed stable version of the gimp-2.8. However, I would not recommend yet that version for the next official Slackware 14.2.
Perhaps windowmaker-0.95.7 introduced to -current on Sat Nov 14 21:35:57 UTC 2015 should be reverted to windowmaker-0.95.6 introduced to -current on Tue Apr 21 23:44:00 UTC 2015.
The version of wmmenugen in windowmaker-0.95.7 causes a segmentation fault in both -64bit and -32bit versions that is not resolved by building the package from source.
Perhaps windowmaker-0.95.7 introduced to -current on Sat Nov 14 21:35:57 UTC 2015 should be reverted to windowmaker-0.95.6 introduced to -current on Tue Apr 21 23:44:00 UTC 2015.
The version of wmmenugen in windowmaker-0.95.7 causes a segmentation fault in both -64bit and -32bit versions that is not resolved by building the package from source.
Does it work if you apply the following patch and recompile using the slackbuild ?
Code:
diff --git a/util/wmmenugen.c b/util/wmmenugen.c
index 5839189..47e89f7 100644
--- a/util/wmmenugen.c
+++ b/util/wmmenugen.c
@@ -106,7 +106,7 @@ int main(int argc, char **argv)
parse_locale(NULL, &env_lang, &env_ctry, &env_enc, &env_mod);
terminal = find_terminal_emulator();
- for (i = 1; i <= argc; i++)
+ for (i = 1; i < argc; i++)
{
if (strncmp(argv[i], "-parser", 7) == 0 &&
(argv[i][7] == '=' ||
Here are new stable versions of the gimp-2.8.16 + babl-0.1.12 and gegl-0.3.0
I've successfully built them with the standard Slackware SlackBuild scripts, and they appear to run well on my slackware64-current.
Meanwhile, if anyone wish to test a development git-version of the gimp-2.9, here is my SlackBuild script that builds it into a separate directory, /opt/gimp-2.9 allowing to run the gimp-2.9 independently from the installed stable version of the gimp-2.8. However, I would not recommend yet that version for the next official Slackware 14.2.
I've got the babl update, but gimp-2.8.16 needs gegl-0.2.x, so that one will have to wait.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.