Download: https://www.suse.com/products/desktop/download/ SUSE Linux Enterprise Desktop is the market's onlyenterprise-quality Linux desktop ready for routine business use.Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leadingusability, seamless interoperability with existing IT systems, anddozens of essential applications—all at a fraction of the price ofproprietary operating systems. It comes bundled with the latestversions of leading applications such as LibreOffice officeproductivity suite, Mozilla Firefox web browser, and Evolutionemail and calendar suite. In addition, it integrates with MicrosoftSharePoint and Novell Teaming for group collaboration and supports awide range of multimedia file formats, wireless and networkingstandards, and plug-and-play devices. Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktopalso provides an environmentally friendly IT experience (Green IT) andan error-proof desktop. Finally, SUSE Linux Enterprise Desktop offers unparalleled flexibility. Youcan deploy it on a wide range of thick client devices (includingdesktops, notebooks, netbooks, and workstations), on thin clientdevices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop,your business can dramatically reduce costs, improve end-usersecurity and increase workforce productivity. New Features # 5.1 Desktop 5.2 Security 5.3 Server 5.4 Systems Management 5.5 Kernel and Toolchain 5.6 Other Changes and Version Updates 5.1 Desktop # GNOME 2.28 GNOME was updated to version 2.28 with SP1, only selected packages got an update for SP2 or SP3. KDE 4.3 SUSE introduced KDE 4 with SUSE Linux Enterprise Desktop 11 as an innovative free software desktop and applications such as the Konqueror web browser, the Dolphin file manager, the Okular document reader, the System Settings control center and more. KDE was updated to 4.3.4 version with SP1. This new version of KDE is built on KDE Libraries which provide easy access to resources on the network by means of KIO and advanced visual capabilities through Qt4. Phonon and Solid. Customers migrating from SUSE Linux Enterprise Desktop 10 using KDE are getting a new user experience in version 11 Service Pack 1 and later. We recommend backing up your user home directory when upgrading from SUSE Linux Enterprise Desktop 10. (Partly based on http://www.kde.org/announcements/4.0/ .) X.org 7.4 The X server libraries were updated to version 1.6.5. The client libraries were kept the same, except for libgl. 5.1.1 fbdev Driver Needs Reboot After Resolution Changes # SaX2 offers to change the resolution even for the fbdev driver.Because this is controlled via a VGA kernel option, rebooting isneeded after resolution changes. In other words: Modificationswill take effect the next time the graphics system is restarted;in some cases a reboot of the machine is needed. 5.1.2 LibreOffice Replaces OpenOffice.org # Since SUSE Linux Enterprise Desktop 11 SP1, Openoffice.org has been replaced with LibreOffice. If you perform an upgrade, manual interaction is needed, otherwise you will stay with the old OpenOffice.org packages. Future updates will only be prepared and published for LibreOffice. Some parts of the documentation packages still mention 'OpenOffice.org'. 5.2 Security # 5.2.1 Switch repomd from sha to sha26 # The update repository integrity used by SUSE is ensured by a GPG signature and the checksums of the YUM repomd XML metadata. SUSE Linux Enterprise 11 so far used sha1 as intermediate checksum, which should no longer be used. With SUSE Linux Enterprise 12 and SUSE Linux Enterprise 11 SP4 we start to use sha256 for the XML integrity handling and so get rid of the old sha1 hashing methods. If you have tools parsing the XML metadata yourself, please verify they can handle also the newer sha256 hashes. 5.2.2 PAM Configuration # The common PAM configuration files (/etc/pam.d/common-*) are now created and managed with pam-config. 5.3 Server # 5.3.1 numactl and libnuma # numactl and libnuma have been updated to the latest version. This update comes with many bug fixes and some new features that are especially important for large NUMA systems, e.g.: IO affinity support New option to memhog to disable transparent huge pages Show distances on machines without a node 0 5.4 Systems Management # Improved Update Stack SUSE Linux Enterprise Desktop 11 comes with an improved update stack and the command line tool zypper to manage the install/update packages and repositories. Enhanced YaST Partitioner Extended Built-in Management Infrastructure CIM enablement with SFCB CIMON. 5.5 Kernel and Toolchain # GCC 4.3.4 glibc 2.11 Linux kernel 3.0 5.6 Other Changes and Version Updates # EVMS2 Replaced with LVM2 Default Filesystem The default file system in new installations was changed from ReiserFS to ext3 with SUSE Linux Enterprise Desktop 11. A public statement can be found at http://www.suse.com/products/server/technical-information/#FileSystem . Samba 3.4.3 UEFI Enablement on AMD64 SWAP over NFS Python 2.6.0 Perl 5.10 Ruby 1.87 5.6.1 /etc/os-release # In addition to the /etc/SuSE-release file the file /etc/os-release is now available. /etc/os-release is a cross-distribution standard to identify a Linux system. For more information about the syntax, see the os-release man page ( man os-release ). 6.1 General Update Notes # 6.1.1 Lower Version Numbers in SUSE Linux Enterprise 11 SP4 Than in Version 11 SP3 # When upgrading from SUSE Linux Enterprise Server or Desktop 11 SP3 to version 11 SP4, you may encounter a version downgrade of specific software packages, including the Linux Kernel. SLE 11 SP4 has all its software packages and updates in the SLE 11 SP4 repositories. No packages from SLE 11 SP3 repositories are needed for installation or upgrade, not even from the SLE 11 SP3 update repositories. Note It is important to remember that the version number is not sufficient to determine which bugfixes are applied to a software package. In case you add SLE 11 SP3 update repositories, be aware of one characteristic of the repository concept: Version numbers in the SP3 update repository can be higher than those in the SP4 repository. Thus, if you update with the SP3 repositories enabled, you may get the SP3 version of a package instead of the SP4 version. This is admittedly unfortunate. It is recommended to avoid using the version from a lower product or SP, because using the SLE 11 SP3 package instead of the SP4 package can result in unexpected side effects. Thus we advise to switch off all the SLE 11 SP3 repositories, if you do not really need them. Keep old repositories only, if your system depends on a specific older package version. If you need a package from a lower product or SP though, and thus have SLE 11 SP3 repositories enabled, make sure that the packages you intended to upgrade have actually been upgraded. Summarizing: If you have an SLE 11 SP3 installation with all patches and updates applied, and then migrate off-line to SLE 11 SP4, you will see a downgrade of some packages. This is expected behavior. 6.1.2 Migrating to SLE 11 SP4 Using Zypper # To migrate the system to the Service Pack 4 level with zypper, proceed as follows: Open a root shell. To refresh all services and repositories, run: zypper ref -s To install package management updates, run: zypper patch Now it is possible to install all available updates for SLES/SLED 11 SP3; run again: zypper patch Now the installed products contain information about distribution upgrades and which migration products should be installed to perform the migration. Read the migration product information from /etc/products.d/*.prod and install them. Enter the following command: grep 'product' /etc/products.d/*.prod A sample output could be as follows: productsle-sdk-SP4-migration/product productSUSE_SLED-SP4-migration/product Install these migration products (example): zypper in -t product sle-sdk-SP4-migration SUSE_SLED-SP4-migration Run suse_register -d 2 -L /root/.suse_register.log toregister the products in order to get the corresponding SP4 Updaterepositories. To avoid a dependency conflict enable the SLED11-Extras repository with: zypper mr -e SLED11-Extras On SLES this extra step is not needed. Run zypper ref -s to refresh services and repositores. Check the repositories using zypper lr. Disable SP1, SP2, and SP3 repositories after the registration and enable the new SP4 repositories (such as SP4-Pool, SP4-Updates): zypper mr --disable repo-alias zypper mr --enable repo-alias Also disable repositories you do not want to update from. Then perform a distribution upgrade by entering the following command: zypper dup --from SLES11-SP4-Pool --from SLES11-SP4-Updates \ --from SLE11-SP2-WebYaST-1.3-Pool --from SLE11-SP2-WebYaST-1.3-Updates Add more SP4 repositories here if needed, e.g. in case add-on products are installed. For WebYaST, it is actually SLE11-SP2-*, because there is one WebYaST release that runs on two SP code bases. Note If you make sure that only repositories, which you migrate from, are enabled, you can omit the --from parameters. zypper will report that it will delete the migration product and update the main products. Confirm the message to continue updating the RPM packages. To do a full update, run zypper patch. After the upgrade is finished, register the new products again: suse_register -d 2 -L /root/.suse_register.log Run zypper patch after re-registering. Some products do not use the update repositories during the migration and they are not active at this point of time. Reboot the system. From https://www.suse.com/releasenotes/x86_64/SUSE-SLED/11-SP4/
From https://www.suse.com/releasenotes/x86_64/SUSE-SLED/12/ free Download: https://download.suse.com Release Notes These release notes are generic for all SUSE Linux Enterprise Desktop 12 based products. Some parts may not apply to particular architectures or products. Where this is not the case, the respective architecture is listed explicitly. Manuals can be found in the docu directory of the installation media, or in the directory /usr/share/doc/ on the installed system (if installed). Publication date: 2014-10-10 , Version: 12.0.20141010 1 SUSE Linux Enterprise Desktop 1.1 What's New? 1.2 Documentation and Other Information 1.3 How to Obtain Source Code 1.4 Support Statement for SUSE Linux Enterprise Desktop 1.5 Derived and Related Products 1.6 Security, Standards, and Certification 2 Installation and Upgrade 2.1 Installation 2.2 Update-Related Notes 3 Infrastructure, Package and Architecture Specific Information 3.1 Architecture Independent Information 3.2 AMD64/Intel64 64-Bit (x86_64) Specific Information 4 Driver Updates 4.1 Storage Drivers 4.2 Network Drivers 5 Packages and Functionality Changes 5.1 New Packages 5.2 Updated Packages 5.3 Deprecated Functionality 5.4 Changes in Packaging and Delivery 6 Technical Information 6.1 Kernel Limits 6.2 File Systems 7 Legal Notices 1 SUSE Linux Enterprise Desktop SUSE Linux Enterprise Desktop is the market's only enterprise-quality Linux desktop ready for routine business use. Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leading usability, seamless interoperability with existing IT systems, and dozens of essential applications—all at a fraction of the price of proprietary operating systems. It comes bundled with the latest versions of leading applications such as LibreOffice office productivity suite, Mozilla Firefox web browser, and Evolution e-mail and calendar suite. In addition, it integrates with Microsoft SharePoint and Novell Teaming for group collaboration and supports a wide range of multimedia file formats, wireless and networking standards, and plug-and-play devices. Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktop also provides an environmentally friendly IT experience (Green IT) and an error-proof desktop. Finally, SUSE Linux Enterprise Desktop offers unparalleled flexibility. You can deploy it on a wide range of thick client devices (including desktops, notebooks, netbooks, and workstations), on thin client devices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop, your business can dramatically reduce costs, improve end user security and increase workforce productivity. SUSE Linux Enterprise Desktop 12 has a 7 years life cycle.The current version (GA) will be fully maintained and supported until 6 monthsafter the release of SUSE Linux Enterprise Desktop 12 SP1. 1.1 What's New? Note: Fix Status of the GNU Bourne Again Shell (bash) Given the proximity of the SUSE Linux Enterprise 12 release to the publication of the “ shellshock ” series of vulnerabilities in the GNU Bourne Again Shell (bash), we want to provide customers with information on the fix status of the bash version shipped in the SLE 12 GA release: CVE-2014-6271 (original shellshock) CVE-2014-7169 (taviso bug) CVE-2014-7186 (redir_stack bug) CVE-2014-7187and non-exploitable CVE-2014-6277 non-exploitable CVE-2014-6278 Up-to-date information is available online: https://www.suse.com/support/shellshock/ . SUSE Linux Enterprise Desktop 12 introduces a number of innovative changes. Here are some of the highlights: Robustness on administrative errors and improved management capabilities with full system rollback based on btrfs as the default file system for the operating system partition and SUSE's snapper technology. An overhaul of the installer introduces a new workflow that allows you to register your system and receive all available maintenance updates as part of the installation. New core technologies like systemd, replacing the time honored System V based init process. GNOME 3.10, giving users a modern desktop environment with a choice of several different look and feel options, including a special SLE Classic mode for easier migration from earlier SUSE Linux Enterprise desktop environments For users wishing to use the full range of productivity applications of a Desktop with SUSE Linux Enterprise Server, we are now offering the SUSE Linux Enterprise Workstation Extension Integration with the new SUSE Customer Center, SUSE's central web portal to manage Subscriptions, Entitlements, and provide access to Support. For users upgrading from a previous SUSE Linux Enterprise Desktop release it is recommended to review: Section 1.4, “Support Statement for SUSE Linux Enterprise Desktop” Section 2.2, “Update-Related Notes” Section 6, “Technical Information”
Nowadays, it is quite common and popular to have two dedicated graphic cards in laptop: usually, one is intergrated (eg: intel HD4xxx ) and the other is indepedent (eg: Nvidia GTX xxx). Such strategy can save laptop energy if we use integrated card for document task; while we can switch to independent one if dedicated CG work needed. ( If you are going to use the Nvidia dedicated card only, you would be interested in configuring it by Nvidia OPtimus from here . ) Neither downloading nvidia.run driver file from official website nor install from Linux distribution repository works for nvidia graphic cards. Those old methods usually lead to xserver behave abnormally even one cannot enter GUI anymore. Here showed some useful steps towards installing NVIDIA optimus driver for openSUSE in Dell M3800 laptop: Environment graphic card: Intel HD4600+Nvidia K1100M OS: openSUSE 13.2, SLE 12 Steps Update the system via Yast or zypper up -- it is important to make sure that the system is fully updated before continuing. If you are using Virtualbox and other tools need to recompile Linux kernel, it is better to install them before the following steps. Make sure Optimus is * enabled * in the laptop's BIOS setting 1. Get rid of all NVIDIA-related packages : zypper se nvidia zypper rm ... Get rid of bumblebee, primus, dkms, dkms-nvidia, dkms-bbswitch if you've installed before 2. Get rid of all mentions of nvidia in /etc/sysconfig/kernel 3. Make sure xf86-video-intel package is installed zypper if xf86-video-intel 4. add the line blacklist nouveau to /etc/modprobe.d/50-blacklist.conf add option nouveau.modeset=0 to the end of boot loader option from Yast--boot loader--Boot Loader option--optional kernel command line parameter 5. mkinitrd 6. reboot your system At this stage, we are running on Intel HD integrated card and we should login into the SUSE GUI environment KDE/GNOME without any problem. 7 .Install 'powertop' package and note power consumption (must be on battery for power consumption to be shown) zypper in powertop 8. Install the 'devel_kernel' pattern zypper in -t pattern devel_kernel 9. Add bumblebee repository through YAST or zypper command: zypper ar http://download.opensuse.org/repositories/X11:/Bumblebee/openSUSE_13.2/ bumblebee SUSE Linux Enterprise 12 users can add the following repository: http://download.opensuse.org/repositories/X11:/Bumblebee/SLE_12/ 10. i nstall necessary software : zypper in bbswitch bumblebee dkms nvidia-bumblebee nvidia-bumblebee-32bit primus VirtualGL-devel VirtualGL-32bit 11. enable dkms and bumblebeed at booting systemctl enable dkms systemctl enable bumblebeed 12. Add current user to video and bumblebee groups through YAST or command line usermod -A video your_user_name usermod -A bumblebee your_user_name 13. reboot your system 14. check the status of your bumblebee services systemctl status bumblebeed bumblebeed.service - Bumblebee C Daemon Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled) Active: active (running) since Thu 2014-05-22 20:31:08 CEST; 46min ago Main PID: 1693 (bumblebeed) CGroup: /system.slice/bumblebeed.service ├─1693 /usr/sbin/bumblebeed └─2763 Xorg :8 -config /etc/bumblebee/xorg.conf.nvidia -configdir... 15. run your software for testing: optirun ~/bin/pymol This Executable Build integrates and extends Open-Source PyMOL 1.7.0.5. Detected OpenGL version 2.0 or greater. Shaders available. Detected GLSL version 4.40. OpenGL graphics engine: GL_VENDOR: NVIDIA Corporation GL_RENDERER: Quadro K1100M/PCIe/SSE2 GL_VERSION: 4.4.0 NVIDIA 334.21 Adapting to Quadro hardware. tips: Dell M3800 uses QHD screen and the resolution is 3200x1800 which lead to window icon and font unvisuable. It is better to install xrandr to scale the screen. xrandr --output eDP1 --mode 3200x1800 --scale 0.75x0.75 caution: It is highly recommened that update your system only once. If the OS is updated frequently especially updating the keneral, it will destroy dkms and bumblebee. In this case, one have to reinstall nvidia optimus driver again. issuse : ( 1 )if the kernerl was updated, reinstallation of bumblebee I got an error saying something about nvidia.ko missing,just ingore it. editing /etc/modprobe.d/50-bbswitch.conf load_state from 0 to -1: cat /etc/modprobe.d/50-bbswitch.conf options bbswitch load_state=-1 unload_state=1 reboot the system, and bumblebee should work fine now. ( 2 ) most software work fine except VMD, it may failed with messages: libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast WARNING: The OpenGL rendering context obtained on X display :8 is indirect, which may cause performance to suffer. If :8 is a local X display, then the framebuffer device permissions may be set incorrectly. this problem can be solved by making soft link of libGL**.** pointing to the latest Nvidia library: from /usr/lib/nvidia/libGL* /usr/lib64/nvidia/libGL* to /usr/local/lib /usr/lib /usr/local/lib64 /usr/lib64 (3) To run nvidia-settings, one should use the following command line: optirun nvidia-settings -c :8 ( 4 ) In the latest SLED 12 SP3 x64 OS, some 32 bit library is not avaible which won't afffect the Bumblebee performance. However, the kernel may not be correct complied by zypper command line which lead to a lot of heats after booting to the system. This problem can be solved by recompiling kmp with the following steps: cd ~/ mkdir bbswitch cd bbswitch wget http://download.opensuse.org/repositories/X11:/Bumblebee/SLE_12_SP3_Backports/src/bbswitch-0.8-28.1.src.rpm rpmbuild --rebuild bbswitch-0.8-28.1.src.rpm su - cd /home/username/rpmbuild/RPMS/x86_64/ zypper in *kmp*
Words from SUSE developer: "We plan to have a call together with each Beta release, where we highlight some topics. Let me invite you to the Kick Off call in our Beta Test, where SUSE Linux product managers will present new features in SLE 11 SP3..."
Compiling Desmond from source code seems to be the most challenging work that I've ever found especially the latest V3.4. Fortunately, it was successfully compiled these days. During the sampling test, 2 CPU can even get up to 4 ns /day with NVE ensemble for a typical membrane system which is really amazing. OS: SUSE Linux Enterprise 11 SP2 GCC: 4.3.4 (system implemented) Boost: 1.49 (installed from SUSE system tool YAST) Sqlite: 3.7.6 (system implemented) Python: 2.6.7 (self compiled) numpy: 1.5.0 (self compiled) scons: 1.2 (self compiled) Antlr: 3.2 (self compiled) Pcre: 8.21 (self compiled) openMPI: 1.4.3 (self compiled) after compiling the all above necessary tools and libraries, it would be necessary to configure proper Python environment before compiling Desmond: setenv PYTHONPATH /soft/python-2.6.7 alias scons /soft/python-2.6.7/bin/scons alias python /soft/python-2.6.7/bin/python The configuration file user-conf.sample.py are following: # Boost ; boost_prefix = ' /usr/include/boost' EXTRA_INCLUDE_PATH += ' /usr/include' EXTRA_LIBRARY_PATH += ' /usr/lib64' EXTRA_LINK_FLAGS += ' -Wl,-rpath,/usr/lib64' EXTRA_LIBS += ' -lboost_iostreams -lboost_thread' # ANTLR, used in MSYS EXTRA_INCLUDE_PATH += ' /soft/desmond-3.4/libantlr3c/include' EXTRA_LIBRARY_PATH += ' /soft/desmond-3.4/libantlr3c/lib' EXTRA_LINK_FLAGS += ' -Wl,-rpath,/soft/desmond-3.4/libantlr3c/lib' EXTRA_LIBS += ' -lantlr3c' # PCRE, used in MSYS EXTRA_INCLUDE_PATH += ' /soft/desmond-3.4/pcre-8.21/include' EXTRA_LIBRARY_PATH += ' /soft/desmond-3.4/pcre-8.21/lib' EXTRA_LINK_FLAGS += ' -Wl,-rpath,/soft/desmond-3.4/pcre-8.21/lib' EXTRA_LIBS += ' -lpcre' # SQLITE - used in MSYS EXTRA_INCLUDE_PATH += ' /usr/include' EXTRA_LIBRARY_PATH += ' /usr/lib64' EXTRA_LINK_FLAGS += ' -Wl,-rpath,/usr/lib64' EXTRA_LIBS += ' -lsqlite3' # MPI WITH_MPI = 1 mpi_prefix = ' /soft/openmpi-1.4.3' MPI_CPPFLAGS = " -I%s/include -pthread -DOMPI_SKIP_MPICXX" % mpi_prefix MPI_LDFLAGS = " -L%s/lib -Wl,-rpath,%s/lib" % (mpi_prefix,mpi_prefix) # Python # DESRES installs Python and numpy in separate path locations; your installation # will likely install numpy somewhere in the Python path hierarchy python_prefix = ' /soft/python-2.6.7' numpy_prefix = " /soft/python-2.6.7/lib/python2.6/site-packages" EXTRA_INCLUDE_PATH += ' %s/include/python2.6' % python_prefix EXTRA_LIBRARY_PATH += ' %s/lib' % python_prefix EXTRA_LINK_FLAGS += ' -Wl,-rpath,%s/lib' % python_prefix EXTRA_INCLUDE_PATH += ' %s/numpy/core/include' % numpy_prefix EXTRA_LIBRARY_PATH += ' %s/numpy/core' % numpy_prefix EXTRA_LINK_FLAGS += ' -Wl,-rpath,%s/numpy/core' % numpy_prefix EXTRA_LIBS += ' -lboost_python -lpython2.6' Now we can compile and install Desmond with following command: scons --user-conf=user-conf.sample.py PREFIX=/soft/desmond-3.4/desmond -j4 scons --user-conf=user-conf.sample.py install PREFIX=/soft/desmond-3.4/desmond -j4 If everything goes well, we should see the following from terminal: scons build done Testing: setenv DESMOND_PLUGIN_PATH /soft/desmond-3.4/desmond/lib/plugin set path=(/soft/desmond-3.4/desmond/bin $path) desmond --include ./share/samples/dhfr.cfg \ --cfg boot.file=./share/samples/dhfr.dms \ --cfg mdsim.plugin.eneseq.name=dhfr.eneseq diff dhfr.eneseq ./share/samples/dhfr.eneseq.reference the values printed should be correspond to steps 160 and 200 and should be identical to the final few lines of values obtained when running the first parallel simulation. parallel testing: setenv DESMOND_PLUGIN_PATH /soft/desmond-3.4/desmond/lib/plugin set path=(/soft/desmond-3.4/desmond/bin $path) mpirun -np 2 desmond \ --include ./share/samples/dhfr.cfg \ --cfg boot.file=./share/samples/dhfr.dms \ --cfg mdsim.plugin.eneseq.name=dhfr.eneseq.2 \ --destrier mpi diff dhfr.eneseq.2 dhfr.eneseq The first commands sets an environment variable that determines where Desmond will search for its dynamically loaded plugins. Using the instructions above there are one or two plugins built that contain 'destriers'. Destriers implement communication protocols in Desmond with the default protocol being one for a single processor. The second command runs two mdsim.exe processes using the Open MPI job launcher orterun and the Desmond 'mpi' destrier. The third command again compares the results obtained from the parallel run with those of the serial run. Note,that in general these results will be different.
The installation of DiscoveryStudio 3.5 on nowadays kernel 3.x Linux may not works well and the official site only suggest the kernel2.6 Linux OS including RHEL 4.x 5.x and SLE (SUSElinux entperise)10. However, the kernel 3.X Linux OS improved a lot on speed and it would be nice if DS3.5 could work in nowadays new kernel machine. For SUSE LINUX ENTERPRISE 11 SP2, it always claimed the following errors when we try to submit jobs: ----------------------------error------------------------------ Error while parsing script or executing script outside of subroutines. Can't load '/soft/Accelrys/PP8.5/apps/scitegic/dscore/server/lib/libMdmDiscoveryScript.so' for module MdmDiscoveryScript: /usr/lib/libfontconfig.so.1: undefined symbol: FT_Select_Size at /soft/Accelrys/PP8.5/apps/scitegic/core/packages_linux32/perl/perl-5.8.9/lib/5.8.9/i686-linux-thread-multi/DynaLoader.pm line 226. at /soft/Accelrys/PP8.5/apps/scitegic/dscore/lang/perl/Utilities/ConvertToMol2.pm line 15 Compilation failed in require at /soft/Accelrys/PP8.5/apps/scitegic/dscore/lang/perl/Utilities/ConvertToMol2.pm line 15. BEGIN failed--compilation aborted at /soft/Accelrys/PP8.5/apps/scitegic/dscore/lang/perl/Utilities/ConvertToMol2.pm line 15. Compilation failed in require at (eval 12) line 4. BEGIN failed--compilation aborted at (eval 12) line 4. Error calling function Error during call to function pilot::setup::scriptingSetup PerlScript::HandleError: Pipeline Pilot exception rethrown PerlScript::Call: Pipeline Pilot exception rethrown CComponentPerlPlugin::onInitialize: Pipeline Pilot exception rethrown - Convert file to mol2 (Perl (on Server)) - error during Initialization phase CProtocolBaseImpl::GetNextStartNodeForNewData: Pipeline Pilot exception rethrown CProtocolBaseImpl::SetUpComponentStack: Pipeline Pilot exception rethrown CProtocolRtc::onProcess: Pipeline Pilot exception rethrown CProtocol::onProcess: Pipeline Pilot exception rethrown - Create and Read File (Subprotocol) - error during Data Record Processing phase CProtocolStd::onProcess: Pipeline Pilot exception rethrown CProtocol::onProcess: Pipeline Pilot exception rethrown - DS Molecule Reader (DS Molecule Reader) - error during Data Record Processing phase CProtocolStd::onProcess: Pipeline Pilot exception rethrown CProtocol::onProcess: Pipeline Pilot exception rethrown CComponentRunner::CallOnProcess: exception caught, calling onFinalize before rethrow Protocol Dock Proteins (ZDOCK), user albert: Pipeline Pilot exception caught Protocol Dock Proteins (ZDOCK), user albert: Protocol failed: Pipeline Pilot error Pipeline Pilot Server version 8.5.0.200 Server OS: Linux dream 3.0.42-0.7-default #1 SMP Tue Oct 9 11:58:45 UTC 2012 (a8dc443) x86_64 x86_64 x86_64 GNU/Linux The error message received are caused by a missing system library on linux machine. The required system libraries for a 64-bit SuSE 11 machine are: compat-libstdc++ (x86_64) expat-32bit (x86_64) fontconfig-32bit (x86_64) freetype2-32bit (x86_64) glibc-32bit (x86_64) libdrm-32bit (x86_64) libgcc (x86_64) libstdc++ (x86_64) Mesa-32bit (x86_64) mozilla-nspr-32bit (x86_64) pam-32bit (x86_64) unixODBC-32bit (x86_64) ( by default, this library is not installed ) xorg-x11-libs-32bit (x86_64) xorg-x11-Xvfb (x86_64) zlib-32bit (x86_64) However if all the libraries are installed - the libraries require the 32-bit version of the library even on a 64-bit version of Linux - it require the following steps work out: rename the PP installation directory/linux_bin/libfreetype so that the system libfreetype is used instead.
It is definitely a completely nightmare of macOS for computational work: Schrodinger software is so slow in apple and the "talbe" menu even cannot be open; VMD always crashed as soon as it start; there is no Discoverystudio version under macOS.... For computational purpose, we need a Linux OS. Unfortunately, nowadays Linux especially with new kernel have many problems with the hardware drivers which mainly comes from the Linux kernel compatibility with Mac machine. The most common issue is the stacked black screen complaining: ACPI Kernel panic as soon as we press "installation" by inserting the Linux DVD. This happen to almost all nowadays Linux distribution including: SUSE Linux Enterprise 11 SP2, openSUSE (11.4, 12.x), Redhat 6.X, Scientific Linux 6.X and Ubuntu 12.x. Many threads online advised to add options on intallation booting such as: noacpi or apic=off or inremap=off or intel_iommmu=off The installation dialogue may pop up after adding those mentioned options, but you will find that your mouse, touch pad and keyboard either internal or external doesn't work at all. And you are headache about what to do next. I've also tried many times and finally find a reasonable solution for it: we can first add one of the above options in the initial installation, of course we have to be sure at least either external or internal keyboard should work otherwise we cannot finish the following step. after installation we can login to Linux and press command+F1 to open a terminal fetch a new Linux kernel compile it. Here I suggest stable released version: 3.6.2 which I confirmed that it works well for the "kernel panic" issue under SUSE Linux Enterprise 11 SP2. This new kernel can be obtained by command: wgethttp://www.kernel.org/pub/linux/kernel/v3.0/linux-3.6.2.tar.bz2 and here is the steps for compiling: we can download it and unzip it to /usr/local/src before compiling, we need to install libncurses5-dev ftp://invisible-island.net/ncurses/ after that it can be compiled by command: make oldconfig make menuconfig make -j4 make modules_install install Run this command mkinitrd -o initrd .img-kernelversion kernelversion" (For SUSE or Redhat based distros, you need not create initrd, as it is created by default) remembering to replace kernelverison with the version number of the kernel you build. Finally we can edit our grub option: vi /boot/grub/menu.lst You will find the new kernel was added in the grub menu.lst, and it also contains options like: noapic or acpi=off we can delete such options and reboot system: init 6 You'll find that your not only your mouse, external and internal keyboard work, but also your apple magic wireless mouse works fine. The final step is configure the GPU driver which may requries Bumblebee since macBOOK Pro contains two GPU: intel HD4000 and nvidia GT650M. This can be done following this tutorial: https://wiki.archlinux.org/index.php/Bumblebee#Installing_Bumblebee_with_Intel_.2F_nvidia
It is of great importance to backup our system so that it would be very helpful when it is cracked or reinstalled. The System Backup module in SUSE Linux YAST enable us to finish this task easily. click manually backup give some basic parameters and click Next.... Now Backup begin Please wait in patient,and it would take some time for this process to be finished For system recovery, just click System Restoration from YAST
标签: SUSE
