LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-11-2018, 10:23 AM   #211
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,239

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452

libwebp-0.6.1:

https://github.com/webmproject/libwe...ster/ChangeLog
http://downloads.webmproject.org/rel...p-0.6.1.tar.gz
 
Old 01-11-2018, 10:53 AM   #212
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,239

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
xine-lib-1.2.9:

http://www.xine-project.org/home
https://sourceforge.net/projects/xin...2.9/README.txt
http://sourceforge.net/projects/xine...b-1.2.9.tar.xz
 
1 members found this post helpful.
Old 01-12-2018, 12:57 PM   #213
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,239

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
mpc-1.1.0:

https://gforge.inria.fr/scm/browser.php?group_id=131
https://ftp.gnu.org/gnu/mpc/mpc-1.1.0.tar.gz

Last edited by gmgf; 01-12-2018 at 01:00 PM.
 
Old 01-12-2018, 01:12 PM   #214
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 157

Rep: Reputation: 40
I2C Tools 4.0

https://i2c.wiki.kernel.org/index.php/I2C_Tools
https://www.kernel.org/pub/software/...ols-4.0.tar.xz
 
Old 01-12-2018, 02:30 PM   #215
chemfire
Member
 
Registered: Sep 2012
Posts: 176

Rep: Reputation: Disabled
Have not had much time to look into the issue but Joe is segfaulting in current. Seems to be something with syntax highlighting changes because you can open the file fine if its created in some other editor.

In a file with an .sh extension writing something like

if [ "${FOOBAR}" = "

It will crash when you open that second quote.
 
Old 01-13-2018, 05:03 PM   #216
shastah
LQ Newbie
 
Registered: Dec 2017
Posts: 11

Rep: Reputation: Disabled
CPU Microcode update

Not sure how helpful this is for others, but that's what I have plugged into rc.S
Code:
$ cat /etc/rc.d/rc.microcode 
#!/bin/sh
# /etc/rc.d/rc.microcode: load CPU microcode
#
# Disclaimer: currently supports Intel CPUs only.
#
# Modern CPUs allow their microcode to be updated at runtime.
# It's not persistent, so it should be done on every boot.
# Normally it should be applied via BIOS update, but motherboard
# manufacturers tend to end support for their products quite soon,
# so modern Linux kernels have a mechanism to do it from the OS
# level.
#
# For Intel CPUs, make sure you have the latest microcode
# placed in /lib/firmware/intel-ucode/
#
# You probably want to skip this (by making this script
# non-executable, ie. chmod 644 /etc/rc.d/rc.microcode)
# in virtual machines and containers.
#

# This tries to recognize CPU vendor looking at /proc/cpuinfo
# and run appropriate function to update microcode.
microcode_update() {
  if egrep -q '^vendor_id[[:space:]]*: GenuineIntel$' /proc/cpuinfo 2>/dev/null ; then
    microcode_update_intel
  else
    # TODO: add detection and handling of other vendors
    echo "Error: unsupported CPU vendor"
    return 1
  fi
}

# Microcode update procedure for Intel CPUs. Needs kernel
# with CONFIG_MICROCODE_INTEL, sysfs mounted, and microcode
# put in /lib/firmware/intel-ucode/
microcode_update_intel() {
  if [ ! -e /lib/firmware/intel-ucode/ ]; then
    echo "Error: microcode path missing: /lib/firmware/intel-ucode/"
    return 1
  fi
  if [ ! -e /sys/devices/system/cpu/microcode/reload ]; then
    echo "Error: microcode reload interface missing."
    echo "       Is your kernel compiled with CONFIG_MICROCODE_INTEL?"
    return 1
  fi
  CURRENT_MICROCODE=$(cat /sys/devices/system/cpu/cpu0/microcode/version 2>/dev/null)
  echo "Updating CPU microcode (from $CURRENT_MICROCODE)..."
  echo 1 > /sys/devices/system/cpu/microcode/reload
}


case "$1" in
  start|reload)
    microcode_update
    ;;
  *)
    echo "Usage: $0 {start|reload}"
esac
$
 
6 members found this post helpful.
Old 01-13-2018, 08:09 PM   #217
FlinchX
Member
 
Registered: Nov 2017
Distribution: Slackware Linux
Posts: 112

Rep: Reputation: Disabled
Quote:
Originally Posted by shastah View Post
Not sure how helpful this is for others, but that's what I have plugged into rc.S
Code:
$ cat /etc/rc.d/rc.microcode 
#!/bin/sh
# /etc/rc.d/rc.microcode: load CPU microcode
#
# Disclaimer: currently supports Intel CPUs only.
#
# Modern CPUs allow their microcode to be updated at runtime.
# It's not persistent, so it should be done on every boot.
# Normally it should be applied via BIOS update, but motherboard
# manufacturers tend to end support for their products quite soon,
# so modern Linux kernels have a mechanism to do it from the OS
# level.
#
# For Intel CPUs, make sure you have the latest microcode
# placed in /lib/firmware/intel-ucode/
#
# You probably want to skip this (by making this script
# non-executable, ie. chmod 644 /etc/rc.d/rc.microcode)
# in virtual machines and containers.
#

# This tries to recognize CPU vendor looking at /proc/cpuinfo
# and run appropriate function to update microcode.
microcode_update() {
  if egrep -q '^vendor_id[[:space:]]*: GenuineIntel$' /proc/cpuinfo 2>/dev/null ; then
    microcode_update_intel
  else
    # TODO: add detection and handling of other vendors
    echo "Error: unsupported CPU vendor"
    return 1
  fi
}

# Microcode update procedure for Intel CPUs. Needs kernel
# with CONFIG_MICROCODE_INTEL, sysfs mounted, and microcode
# put in /lib/firmware/intel-ucode/
microcode_update_intel() {
  if [ ! -e /lib/firmware/intel-ucode/ ]; then
    echo "Error: microcode path missing: /lib/firmware/intel-ucode/"
    return 1
  fi
  if [ ! -e /sys/devices/system/cpu/microcode/reload ]; then
    echo "Error: microcode reload interface missing."
    echo "       Is your kernel compiled with CONFIG_MICROCODE_INTEL?"
    return 1
  fi
  CURRENT_MICROCODE=$(cat /sys/devices/system/cpu/cpu0/microcode/version 2>/dev/null)
  echo "Updating CPU microcode (from $CURRENT_MICROCODE)..."
  echo 1 > /sys/devices/system/cpu/microcode/reload
}


case "$1" in
  start|reload)
    microcode_update
    ;;
  *)
    echo "Usage: $0 {start|reload}"
esac
$
I really hope this together with relevant packages from SBo gets merged into -current and also gets its own README file, so the next stable Slackware release will make it easier to stay patched against Intel CPU bugs.
 
Old 01-13-2018, 08:29 PM   #218
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,963

Rep: Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698
So, also the AMD owner shall apply the Intel microcode, in your opinion?
 
Old 01-13-2018, 08:32 PM   #219
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 827

Rep: Reputation: Disabled
Hi,

@FlinchX
@shastah

Do you know that the microcode can be easily loaded in Slackware as early as the kernel is being loaded?
All the stuff is there already.

(Well, except for intel-microcode package, which I maintain at SBo ;-)).

--
Best regards,
Andrzej Telszewski
 
2 members found this post helpful.
Old 01-13-2018, 08:33 PM   #220
shastah
LQ Newbie
 
Registered: Dec 2017
Posts: 11

Rep: Reputation: Disabled
Quote:
Originally Posted by Darth Vader View Post
So, also the AMD owner shall apply the Intel microcode, in your opinion?
Trying to be a smarta$$, eh? How about you go and actually read the snippet I posted?
Oh, and you don't have to apologize, I don't care about opinions of people who can't even be bothered to read comments.
 
1 members found this post helpful.
Old 01-13-2018, 08:35 PM   #221
shastah
LQ Newbie
 
Registered: Dec 2017
Posts: 11

Rep: Reputation: Disabled
Quote:
Originally Posted by atelszewski View Post
Do you know that the microcode can be easily loaded in Slackware as early as the kernel is being loaded?
All the stuff is there already.

(Well, except for intel-microcode package, which I maintain at SBo ;-)).
Yes, and that's useful - although method for doing this differs depending on bootloader used, initrd or not, etc. Hence that snippet. On a second thought, maybe I shouldn't have posted it in this particular thread.
 
Old 01-13-2018, 08:36 PM   #222
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,963

Rep: Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698
Honestly, I do not see why the Intel owners should be favored.

Also, Intel itself recommends the load of the microcode early via initrd (or embedded in kernel), and the method of later loading is not recommended and experimental.

Maybe it works for you, BUT it can well NOT work for thousand others.

Last edited by Darth Vader; 01-13-2018 at 08:39 PM.
 
1 members found this post helpful.
Old 01-13-2018, 08:39 PM   #223
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,753

Rep: Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637
Quote:
Originally Posted by Darth Vader View Post
So, also the AMD owner shall apply the Intel microcode, in your opinion?
The script detects the CPU type and quits if it isn't "GenuineIntel". If the script was included, it could be an optional script to be enabled by the admin at the end of installation.
 
Old 01-13-2018, 08:51 PM   #224
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,963

Rep: Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698Reputation: 698
Quote:
Originally Posted by bassmadrigal View Post
The script detects the CPU type and quits if it isn't "GenuineIntel". If the script was included, it could be an optional script to be enabled by the admin at the end of installation.
Sorry, but I do not see how checking for "/sys/devices/system/cpu/microcode/reload" presence can detect a "GenuineIntel" ...

That sysfs path is so generic and the Linux kernel works in so many CPU types, that I doubt that check is enough.

Precisely there is a huge room for improvements in that script.

Last edited by Darth Vader; 01-13-2018 at 08:52 PM.
 
Old 01-13-2018, 11:09 PM   #225
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,753

Rep: Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637Reputation: 2637
Quote:
Originally Posted by Darth Vader View Post
Sorry, but I do not see how checking for "/sys/devices/system/cpu/microcode/reload" presence can detect a "GenuineIntel" ...

That sysfs path is so generic and the Linux kernel works in so many CPU types, that I doubt that check is enough.

Precisely there is a huge room for improvements in that script.
Are you not looking at the whole script? There's a grep that checks the vendor_id from /proc/cpuinfo first to determine if it is an Intel before it does any microcode stuff.

Code:
if egrep -q '^vendor_id[[:space:]]*: GenuineIntel$' /proc/cpuinfo 2>/dev/null ; then
First it runs the microcode-update() function, which does an if/else on if the cpu is a GenuineIntel from the vendor_id field of /proc/cpuinfo. If it does detect it, the script will then run the microcode-update-intel() function.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 04:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:20 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration