Difference between revisions of "Matlab"

From ArchWiki
Jump to: navigation, search
(General installation)
(License: invalid machine id)
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
[[Category:Mathematics and science]]
 
[[Category:Mathematics and science]]
{{Article summary start}}
+
{{Related articles start}}
{{Article summary text|This article contains information about the installation, configuration and use of MATLAB.}}
+
{{Related|Octave}}
{{Article summary heading|Related}}
+
{{Related|Sage-mathematics}}
{{Article summary wiki|Octave}}
+
{{Related|Mathematica}}
{{Article summary wiki|Sage-mathematics}}
+
{{Related articles end}}
{{Article summary wiki|Mathematica}}
+
{{Article summary end}}
+
 
+
 
From the [http://www.mathworks.com/products/matlab/ official website]:
 
From the [http://www.mathworks.com/products/matlab/ official website]:
  
Line 15: Line 12:
 
{{Note|Versions earlier than MATLAB R2013a are not compatible with Java 7. When installing an older version, first install {{Pkg|libxp}} and {{AUR|jre6}}.}}
 
{{Note|Versions earlier than MATLAB R2013a are not compatible with Java 7. When installing an older version, first install {{Pkg|libxp}} and {{AUR|jre6}}.}}
  
64-bit MATLAB 2013a+ should install fine with the install script provided by MATLAB, without any additional packages.
+
MATLAB 2013a+ should install fine with the install script provided by MATLAB, without any additional packages.
  
 
To install from an iso file:
 
To install from an iso file:
Line 70: Line 67:
  
 
== Troubleshooting ==
 
== Troubleshooting ==
As one installs Matlab, it might complain that it can't find a package, for the most part just look at the package name and then install it with [[Pacman]], or in the case of x86_64 there are some libraries only in [[AUR]].
+
As one installs Matlab, it might complain that it cannot find a package, for the most part just look at the package name and then install it with [[Pacman]], or in the case of x86_64 there are some libraries only in [[AUR]].
  
==== License: invalid machine id ====
+
=== Install-Time Library Errors ===
 +
* Make sure that the symlink {{ic|bin/glnx64/libstdc++.so.6}} is pointing to the correct version of {{ic|libstdc++.so.xx}} (which is also in the same directory and has numbers where 'xx' is). By default, it may be pointing to an older (and nonexistent) version (different value for 'xx').
 +
 
 +
* Make sure the device you're installing from is not mounted as {{ic|noexec}}
 +
 
 +
* If you downloaded the files from Mathworks' website, make sure they are not on an NTFS or FAT partition, because that can mess up the symlinks. Ext4 or Ext3 should work.
 +
 
 +
=== License: invalid machine id ===
 
The installer may complain about an invalid machine id, because it is looking for a network interface named eth0 to get a MAC address for activation, while new Arch Linux setups do not have a network interface called eth0 (systemd uses [http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames Predictable Network Interface Names]).  
 
The installer may complain about an invalid machine id, because it is looking for a network interface named eth0 to get a MAC address for activation, while new Arch Linux setups do not have a network interface called eth0 (systemd uses [http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames Predictable Network Interface Names]).  
  
To fix this [[rename network interfaces|change the name of the interface]].
+
The optimal solution is to create a dummy network interface named eth0 with the MAC address of the network device in use (wireless or wired) when you activated MATLAB. First, get that MAC address using {{ic|ip link}} Next, create the following file:
 +
 
 +
{{hc|/etc/systemd/system/matlab.licensing.service|<nowiki>
 +
[Unit]
 +
Description=Dummy network interface for MATLAB
 +
Requires=systemd-modules-load.service
 +
 
 +
[Service]
 +
Type=oneshot
 +
ExecStart=/sbin/ip link set dev dummy0 name eth0
 +
ExecStart=/sbin/ip link set dev eth0 address 00:00:00:00:00:00
 +
 
 +
[Install]
 +
WantedBy=multi-user.target
 +
</nowiki>
 +
}}
 +
 
 +
Replace 00:00:00:00:00:00 with your MAC address.
 +
 
 +
Then make the script run on boot:
 +
 
 +
# systemctl enable matlab.licensing
 +
 
 +
Finally, set the dummy module to load on boot by creating the following file:
 +
 
 +
{{hc|/etc/modules-load.d/dummy.conf|<nowiki>dummy</nowiki>
 +
}}
 +
 
 +
==== Rename Interfaces ====
 +
 
 +
A less preferable option is to [[rename network interfaces|change the name of the interface]].
  
 
The machine id should now be different than 000000000000 and you should be able to install and activate MATLAB without problems.
 
The machine id should now be different than 000000000000 and you should be able to install and activate MATLAB without problems.
  
==== Resolving start warnings/errors ====
+
=== Resolving start warnings/errors ===
  
 
* Even if all needed libraries are installed, Matlab when starting can still report some missing libraries. This is resolved by symbolic linking of needed libraries to directories that Matlab checks at start-up. For example, if Matlab triggers error/warning about missing {{ic|/lib64/libc.so.6}} library, this can be resolved by:
 
* Even if all needed libraries are installed, Matlab when starting can still report some missing libraries. This is resolved by symbolic linking of needed libraries to directories that Matlab checks at start-up. For example, if Matlab triggers error/warning about missing {{ic|/lib64/libc.so.6}} library, this can be resolved by:
Line 89: Line 123:
 
  export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk/jre
 
  export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk/jre
  
==== MATLAB crashes when displaying graphics ====
+
=== MATLAB crashes when displaying graphics ===
  
 
To identify this error, start MATLAB with
 
To identify this error, start MATLAB with
Line 107: Line 141:
 
  sudo ln -s /usr/lib/libstdc++.so.6
 
  sudo ln -s /usr/lib/libstdc++.so.6
  
==== Blank/grey UI when using DWM/Awesome ====
+
=== Blank/grey UI when using DWM/Awesome ===
  
 
wmname LG3D
 
wmname LG3D

Revision as of 23:23, 12 January 2014

From the official website:

MATLAB is a high-level language and interactive environment for numerical computation, visualization, and programming. Using MATLAB, you can analyze data, develop algorithms, and create models and applications. The language, tools, and built-in math functions enable you to explore multiple approaches and reach a solution faster than with spreadsheets or traditional programming languages, such as C/C++ or Java.

General installation

Note: Versions earlier than MATLAB R2013a are not compatible with Java 7. When installing an older version, first install libxp and jre6AUR.

MATLAB 2013a+ should install fine with the install script provided by MATLAB, without any additional packages.

To install from an iso file:

# modprobe loop
# mount -o loop matlab.iso /mnt/
# /mnt/install

Additionally, install xorg-fonts-100dpi, xorg-fonts-75dpi, and xorg-fonts-type1 so fonts are displayed properly in figures.

Create Desktop and Menu Shortcuts

If you choose Custom in Installation Type, the symlink will be created automatically. Otherwise, you may need to manually create a symlink in /usr/local/bin to make it easier to launch in terminal:

# ln -s /{MATLAB}/bin/matlab /usr/local/bin

To create a menu item, we need to get a icon first:

# curl http://upload.wikimedia.org/wikipedia/commons/2/21/Matlab_Logo.png -o /usr/share/icons/matlab.png

Then create a new .desktop file in /usr/share/applications with following lines:

/usr/share/applications/matlab.desktop
#!/usr/bin/env xdg-open
[Desktop Entry]
Type=Application
Icon=/usr/share/icons/matlab.png
Name=MATLAB
Comment=Start MATLAB - The Language of Technical Computing
Exec=env -u _JAVA_OPTIONS matlab -desktop -nosplash -r "cd('%d'); edit '%f'"
Categories=Development;
MimeType=text/x-matlab;

The Exec command line is composed as follows:

  • -desktop is a flag needed to run matlab without a terminal.
  • -nosplash is a flag preventing the splash screen from showing and taking up a temporary space in your task bar.
  • env -u _JAVA_OPTIONS prevents the creation of a .java.log-file in your home directory by unsetting $_JAVA_OPTIONS. Java prints all options set this way to stdout, and matlab treats everything in stdout as error worth a log.
  • -r '...' executes matlab code on startup:
    1. cd('%d') This changes the working directory of matlab to the opened file’s directory.
    2. edit '%f' This spawns an editor tab for the file.

You can also put this .desktop file in the ~/Desktop directory to create a shortcut.

More details see MATLAB - Community Ubuntu Documents

Install supported compiler

In order for Matlab to work with C code (needed for simulink) it is necessarry to install a supported compiler. Install gcc44AUR from the AUR.

Then edit ${MATLAB}/bin/mexopts.sh and replace all occurances of CC='gcc' with CC='gcc-4.4' and CXX='g++' with CXX='g++-4.4'. Afterwards run

mex -setup

in Matlab and select the mexopts.sh file.

Troubleshooting

As one installs Matlab, it might complain that it cannot find a package, for the most part just look at the package name and then install it with Pacman, or in the case of x86_64 there are some libraries only in AUR.

Install-Time Library Errors

  • Make sure that the symlink bin/glnx64/libstdc++.so.6 is pointing to the correct version of libstdc++.so.xx (which is also in the same directory and has numbers where 'xx' is). By default, it may be pointing to an older (and nonexistent) version (different value for 'xx').
  • Make sure the device you're installing from is not mounted as noexec
  • If you downloaded the files from Mathworks' website, make sure they are not on an NTFS or FAT partition, because that can mess up the symlinks. Ext4 or Ext3 should work.

License: invalid machine id

The installer may complain about an invalid machine id, because it is looking for a network interface named eth0 to get a MAC address for activation, while new Arch Linux setups do not have a network interface called eth0 (systemd uses Predictable Network Interface Names).

The optimal solution is to create a dummy network interface named eth0 with the MAC address of the network device in use (wireless or wired) when you activated MATLAB. First, get that MAC address using ip link Next, create the following file:

/etc/systemd/system/matlab.licensing.service
[Unit]
Description=Dummy network interface for MATLAB
Requires=systemd-modules-load.service

[Service]
Type=oneshot
ExecStart=/sbin/ip link set dev dummy0 name eth0
ExecStart=/sbin/ip link set dev eth0 address 00:00:00:00:00:00

[Install]
WantedBy=multi-user.target

Replace 00:00:00:00:00:00 with your MAC address.

Then make the script run on boot:

# systemctl enable matlab.licensing

Finally, set the dummy module to load on boot by creating the following file:

/etc/modules-load.d/dummy.conf
dummy

Rename Interfaces

A less preferable option is to change the name of the interface.

The machine id should now be different than 000000000000 and you should be able to install and activate MATLAB without problems.

Resolving start warnings/errors

  • Even if all needed libraries are installed, Matlab when starting can still report some missing libraries. This is resolved by symbolic linking of needed libraries to directories that Matlab checks at start-up. For example, if Matlab triggers error/warning about missing /lib64/libc.so.6 library, this can be resolved by:
# ln -s /lib/libc.so.6 /lib64
  • Matlab R2011b with an up-to-date Arch Linux (as of March 12, 2012) fails on startup with the familiar "Failure loading desktop class." A solution is to point Matlab to the system JVM (confirmed to work with the jdk7-openjdk package):
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk/jre

MATLAB crashes when displaying graphics

To identify this error, start MATLAB with

LIBGL_DEBUG=verbose matlab

from the terminal and try to collect OpenGL information with opengl info from the MATLAB command prompt. If it crashes again and there is an output line like

libGL error: dlopen /usr/lib/xorg/modules/dri/swrast_dri.so failed 
(/usr/local/MATLAB/R2011b/bin/glnxa64/../../sys/os/glnxa64/libstdc++.so.6: 
version `GLIBCXX_3.4.15' not found (required by /usr/lib/xorg/modules/dri/swrast_dri.so))

then the problem is that MATLAB uses its own GNU C++ library, which is an older version than the up-to-date version on your Archlinux system. Make MATLAB use the current C++ library for your system by

cd /usr/local/MATLAB/R(your release)/sys/os/glnxa64
sudo unlink libstdc++.so.6
sudo ln -s /usr/lib/libstdc++.so.6

Blank/grey UI when using DWM/Awesome

wmname LG3D

OpenGL Acceleration

Once Matlab is installed type the following in the interpreter:

>> opengl info

The output should be similar to the following:

Version         = 2.0 Mesa 7.8.2
Vendor          = Advanced Micro Devices, Inc.
Renderer        = Mesa DRI R600 (RV710 9552) 20090101 x86/MMX/SSE2 TCL DRI2
MaxTextureSize  = 4096
Visual          = 0xcb (TrueColor, depth 24, RGB mask 0xff0000 0xff00 0x00ff)
Software        = false
# of Extensions = 107

Driver Bug Workarounds:
OpenGLBitmapZbufferBug    = 0
OpenGLWobbleTesselatorBug = 0
OpenGLLineSmoothingBug    = 0
OpenGLClippedImageBug     = 0
OpenGLEraseModeBug        = 0

This will vary with card you are using, but the important part is "Software = false". If it's not "false" for you, then there is a problem with your hardware acceleration.

NVIDIA

With an NVIDIA card, the output should be similar to this:

>> opengl info
Version         = 2.1.2 NVIDIA 177.82
Vendor          = NVIDIA Corporation
Renderer        = Quadro NVS 140M/PCI/SSE2
MaxTextureSize  = 8192
Visual          = 0x21 (TrueColor, depth 16, RGB mask 0xf800 0x07e0 0x001f)
Software        = false
# of Extensions = 144

Driver Bug Workarounds:
OpenGLBitmapZbufferBug    = 0
OpenGLWobbleTesselatorBug = 0
OpenGLLineSmoothingBug    = 0
OpenGLClippedImageBug     = 1
OpenGLEraseModeBug        = 0

With the NVIDIA card all it required to start working was to copy the libGLU.so from the Matlab installed library ${MATLAB}/sys/opengl/lib/glnx86/libGLU.so to /usr/lib directory. Note that in x86_64 this might be a different directory.

Note: Although, not thoroughly tested, using lib32-nvidia-utils seems to work as well.