Package Details: atlas-lapack 3.10.2-3

Git Clone URL: (read-only)
Package Base: atlas-lapack
Description: Complete LAPACK and BLAS implementation using optimised ATLAS routines
Upstream URL:
Licenses: custom:blas, custom:lapack, custom:atlas
Conflicts: atlas-lapack-base, blas, cblas, lapack
Provides: atlas-lapack-base, blas, cblas, lapack=3.6.0
Submitter: ilpianista
Maintainer: giniu
Last Packager: giniu
Votes: 80
Popularity: 0.480940
First Submitted: 2008-04-24 01:36
Last Updated: 2016-02-25 10:53

Required by (153)

Sources (6)

Latest Comments

bartbkr commented on 2016-04-16 17:27

I was finally able to get this working. The reason that the build was failing was that the maximum CPU frequency was being limited by the BIOS. I had to tuhrn off the max CPU freq limit set by the BIOS and ensured that the maximum frequency was that allowed by cpupower, namely 2.401GHZ.


bartbkr commented on 2016-04-10 17:11

Right, I tried to make it clear from my initial post that I've already done what was instructed on that page and the linked SE answer. I am still getting the "CPU Throttling is enabled!" error.

Some output:

$ cat /sys/devices/systemt/cpu/cpu*/cpufreq/scaling_governor

$ cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us
hardware limits: 400 MHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.80 GHz, 1.70 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 700 MHz, 500 MHz, 400 MHz
available cpufreq governors: ondemand performance
current policy: frequency should be within 400 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: 2.10 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes

morealaz commented on 2016-04-09 16:34

for disabling CPU Throttling.

bartbkr commented on 2016-04-09 14:49

I have Intel Core i5 processor. I've confirmed that now using the acpi_cpufreq driver and intel_pstate=disable on boot. scaling_governor for all four cores is set to performance.

I am still getting the "CPU Throttling is enabled!" error and cannot build. Any suggestions?

greyltc commented on 2016-02-27 12:07

My cpu scaling driver is intel_pstate. By default I'm using the performance governor. Can anyone give me a tip on how to compile this package *without* having to reboot?

giniu commented on 2016-02-25 14:36

@arojas - yes, but provides+conflicts is good anyway in this case I think.

arojas commented on 2016-02-25 12:00

No package should depend on atlas-lapack-base. If some do, it's a bug and should be fixed. Packages should depend on atlas-lapack, atlas-lapack-base is provided as a generic implementation in the repos so that official packages (such as sagemath) can depend on atlas-lapack, but it should be clear that atlas-lapack is the 'right' package to use.

giniu commented on 2016-02-21 07:00

Hi - I will deal with providing atlas-lapack-base together with next upstream release (when this package was built, there was no atlas-lapack-base yet). It will come soon.

budgerigar commented on 2016-02-20 23:31

Maybe there should be a provide for atlas-lapack-base because some packages depend on it which is a official package, and atlas-lapack can replace it.

seanl commented on 2016-02-19 04:59

See for how to turn off cpu throttling if you are using intel_pstate. (TL;DR: boot with intel_pstate=disable, then modprobe acpi-cpufreq, then cpupower frequency-set -g performance).

I did this, and it's no longer aborting due to cpu throttling, but now I'm having a strange problem (64 bit):

cd bin/ ; ./xatlas_build -1 0 -a 1 -l 1
Can't recognize 'make IArchDef.grd
' as an internal or external command, or batch script.

Is it using the wrong shell or something?

All comments