Morning guys and gals!
First and foremost, I hope everyone is well during these times. To be brief, I am currently having trouble running R.exe (x64) on my Windows 10 Pro Insider Preview (20190.1000 Build). I have set the Environment Variable Path to the (x64) folder numerous times to check, but Rterm loads forever then closes.
I have gotten the 32 bit (i386) version to work, but I was hoping for any insight why this could possible be an issue. I'm open to all suggestions!
P.S. I should also note that it appears that the R Plugin for PyCharm does not work with the x64 bit version of R!
EDIT: My bad! The R runtime is v4.0.2. I also have v4.0.0 and v3.6.2 installed. Either way, in all runtime versions, only the 32 bit version works!
I have device which has following configuration:
Chipset architecture - Intel NM10 express
Processor - Atom D2550 Dual Core
Display - DVI
Volatile Memory - 2GB DDR3
Storage - 16GB
Objective: Device should run yocto embededded OS successfully
What I have done,
Downloaded three required yocto layers for warrior branch i.e. 1. poky 2. meta-openembedded 3. meta-intel
Modified local.conf with MACHINE ??= "intel-core2-32"
Ran source poky/oe-init-build-env
Generated .hddimg by bitbake core-image-minimal
Flashed .hddimg to thumb drive through dd command
Attached thumb drive to device and I could see BOOT and INSTALL option, upon clicking any of them nothing happens(not even logs) i.e. Blank screen
Troubleshooting I tried out are,
Tried to boot lubuntu and it was successful
Replaced kernel & initrd of lubuntu with yocto's one and booting was successful which indicates there is no issue with kernel or initrd in .hddimg generated by yocto
Tried some experiment with syslinux as well but didn't work out
The .hddimg types are quite outdated these days, and meta-intel has also switched to wic Their README includes very good information on how to create boot- and installable images here and here.
Short summary of it:
for booting, use the .wic-file
for building an installer, setup image and bootlader config according to documentation, then use .wic-file
I am working in a MacBook Pro (15 inches, mid 2010), OSX El Capitan (10.11.6), 2.4 GHz Intel Core i5, 8 GB 1067 MHz DDR3
Today I tried to update from R-3.3 to R-3.4.0. I downloaded the R-3.4.0.pkg from https://cran.r-project.org/ site. After downloading I checked the MD5 checksum for the R-3.4.0.pkg image and it was the same than in the r-project website. I executed the file by double-clicking and everything appear to work fine, at the end it said that everything was installed with no problem.
The problem I have is that the old R.app was removed from my application folder but the new (R-3.4.0) does not appear in the application folder either.
I tried to download and install the GNU Fortran 6.1 and then reinstall R but nothing changed.
I tried to look for a solution in google and this forum but did not find any clue of what to do. I hope I am not missing any stupid detail or making a rookie mistake.
Thanks for your help,
Alfonso
I was able to get the R.app from http://r.research.att.com/ I got there from the r-project website.
I chose "Mac OS X GUI rev. 7362 for R 3.4.x el-capitan-Debug.dmg" instead of "Mac OS X GUI rev. 7362 for R 3.5.x el-capitan-Debug.dmg" since to the best of my knowledge there is no R-3.5 available yet.
I do not understand why the app did not install directly from R-3.4.0.pkg but apparently this works. I leave this answer just in case is useful for someone.
Thanks for the comments!
Alfonso
I recently started using ubuntu 14.04 (Dual booting with win 8.1).
It was working fine until I ran the following code on the terminal:
sudo apt-get install nautilus-open-terminal
I just wanted he "Open terminal here" option :P
Since then, its been hanging a lot. Every time this happens, I put my laptop to sleep and open it again, and its fine.
But it's really annoying (It must have hung like two times while typing this).
What should I do??
Thanks in advance
This problem is caused by nvidia drivers .. You can do two things. Either switch from nvidia drivers to nouview or bumblebee drivers. Or you can select the intel power saving mode in nvidia drivers.there might be some problem in selecting the powersaving mode. If there is problem you need to set update-alternatives. Or switch from nvidia drivers
I am trying to start working with OpenCL. I have two NVidia graphics card, I installed "developer driver" as well as SDK from NVidia website. I compiled the demos but when I run
./oclDeviceQuery
I see:
OpenCL SW Info:
Error -1001 in clGetPlatformIDs Call
!!!
How can I fix it? Does it mean my nvidia cards cannot be detected? I am running Ubuntu 10.10 and X server works properly with nvidia driver.
I am pretty sure the problem is not related to file permissions as it doesn't work with sudo either.
In my case I have solved it by installing nvidia-modprobe package available in ubuntu (utopic/multiverse). And the driver itself (v346) was installed from https://launchpad.net/~mamarley/+archive/ubuntu/nvidia
Concretely, I have installed nvidia-opencl-icd-346, nvidia-libopencl1-346, nvidia-346-uvm, nvidia-346 and libcuda1-346. Not sure if they are all needed for OpenCL.
This is a result of not installing the ICD portion of Nvidia's openCL runtime. The ICD profile will instruct your application of the different openCL implementations installed on the system as multiple implementations from different vendors can coexist. Whe your application does not find the ICD information it gives the Error -1001.
Run your program as root. In case of success: you have trouble with cl_khr_icd- extension to load the vendor driver.
If you not running X11, you have to create device files manually or by (boot-)script:
ERROR: clGetPlatformIDs -1001 when running OpenCL code (Linux)
Same problem for me on a Linux system. Solution is to add the user to the video group:
# sudo usermod -aG video your-user-name
Since I just spend a couple of hours on this, I thought I would share:
I got the error because I was connected to the machine per remote desktop (mstsc). On the machine itself everything worked fine.
I have been told that it should work with TeamViewer by the way.
Dont know if you ever solved this problem, but I had the same issue and solved it in this post: ERROR: clGetPlatformIDs -1001 when running OpenCL code (Linux)
Hope it helps!
I have solved it in Ubuntu 13.10 saucy for intel opencl by created link:
sudo ln -s /opt/intel/opencl-1.2-3.2.1.16712/etc/intel64.icd /etc/OpenCL/vendors/nvidia.icd
I just ran into this problem on ubuntu 14.04 and I could not find ANY working answers anywhere online including this thread (though this was the first to show up on google). What ended up working for me was to remove ALL previous nvidia software and then to reinstall it using the .run file provided on the nvidia website. Installing the components through apt-get seems to fail for some reason.
1) Download CUDA .run file: https://developer.nvidia.com/cuda-downloads
2) Purge all previous nvidia packages
sudo apt-get purge nvidia-*
3) Install all run file components (you will likely have to stop X or restart in recovery mode to run this)
sudo sh cuda_X.X.XX_linux.run
This is because OpenCL has the same brain damaged one library per vendor setup that OpenGL has. A likely reason for the -1001 error is that you have compiled with a different library than the linker is trying to dynamically load.
So see if this is the problem run:
$ ldd oclDeviceQuery
...
libOpenCL.so.1 => important path here (0x00007fe2c17fb000)
...
Does the path point towards the NVidia-provided libOpenCL.so.1 file? If it doesn't, you should recompile the program with an -L parameter pointing towards the directory containing NVidia's libOpenCL.so.1. If you can't do that, you can override the linker's path like this:
$ LD_LIBRARY_PATH=/path/to/nvidias/lib ./oclDeviceQuery
For me, I was missing the CUDA OpenCL library, Running sudo apt install cuda-opencl-dev-12-0 solved it.
You should get number of platforms, allocate the memory for platforms, again get this platforms and then create context from this platform. There is good example:
http://developer.amd.com/support/KnowledgeBase/Lists/KnowledgeBase/DispForm.aspx?ID=71
This might be due to querying clGetPlatformIDs by multiple threads at the same time