Now I installed the AMD APP SDK 3.0 and try to check if it is installed successfully.When I use cmd and clinfo command, it displays information but with an error terminated finally.It makes me confused. The picture as follows.
The clinfo.exe error
I don't know how to solve with it. Before I run the command clinfo, I can use CodeXL Teapot sample and debug and analysis it. After I run the clinfo command, CodeXL Teapot sample also crashed. When I unistall AMD APP SDK 3.0, the clinfo command has no error and CodeXL is also recovered.
My system is windows 10 X64, GPU is AMD FirePro W7100,AMD APP SDK is X64.
Who can give me some advice?
Related
I have debian 11 installed in wsl2 on windows 10. I use the dotnet cli tools in visual studio and cmd windows but much prefer the linux syntax. The sdk commands are not exposed to wsl apparently as I get "bash: command dotnet not found" errors. Because WSL is essentially mapping linux commands to windows I don't think I should be installing the dotnet sdk again for linux, but can't really find any confirmation of that. Anyone here doing this who can advise? Just don't want to have to maintain two sets of the dotnet sdk if WSL does not require it.
The sdk commands are not exposed to wsl apparently as I get "bash: command dotnet not found" errors.
That's because WSL does not run Windows executables - it is, after all, a Linux subsystem.
I don't think I should be installing the dotnet sdk again for linux
You have two choices:
Use the Windows subsystem (drop WSL),
install the Linux applications you want to run.
I am trying to install latest Meteor 1.6 using Chocolatey on windows.
My Windows configurations is
Processor - core i7, 2nd gen, 2.2 Ghz
RAM - 8 GB,
System Type - 64 bit
I also used below command in COMMAND PROMPT to start with installation,
choco install meteor -y --execution-timeout 10000
still I am facing below issue.
meteor v0.0.2 [Approved]
meteor package files install completed. Performing other installation steps.
Downloading meteor 64 bit
from 'https://packages.meteor.com/bootstrap-link?arch=os.windows.x86_64'
Progress: 4% - Saving 8.12 MB of 171.74 MB
Download of meteor-bootstrap-os.windows.x86_64.tar.gz (171.74 MB) completed.
ERROR: Chocolatey expected a file at 'C:\Users\HP\AppData\Local\Temp\chocolatey\
meteor\0.0.2\meteor-bootstrap-os.windows.x86_64.tar.gz' to be of length '180086547' but the length was '8552029'.
The install of meteor was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\meteor\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- meteor (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\meteo r\tools\chocolateyinstall.ps1'.
See log for details.
I suggest do not use Windows CMD, better use Power Shell and the issue will be resolved.
Chocolatey is behaving very strange as you can see my question with error log.
Below is the success I got using Power Shell
I have just attempted the installation of the meteor package on my own virtual machine, and I can tell you that the installation was indeed successful.
Looking at the log, it would appear that the download of the tar.gz did not complete successfully, and as a result, the file is not the same size as it was expected based on the response headers.
Best advice would be to try the installation again.
I had exactly the same problem (same error message while installing meteor 1.6 on windows cmd shell runnning in admin mode) until i tried installing with powershell running in admninistrator mode and suspending windows defender. Hope this helps.
I would suggest making the timeout value about 100000. This will at least save you from the occasional termination of the download process due to maybe changes in internet speeds.
I am trying to run a Qt application under EGLFS with Linux Mint on a Macbook Pro.
I have:
Configured and compiled Qt with all the needed flags and dependences.
Tried to run the app with X11 turned off.
Used kms integration.
Installed all the Mesa drivers ( I have an intel GPU ).
Even compiled EGL myself.
But it keeps saying "Unable to create EGL Display".
Does anyone knows what am I missing ?
P.S For example I can run weston-launch which I believe it runs over drm-egl.
I had the same problem like you. I have solved it by:
Building Qt with "-opengl desktop" switch.
Making conf file with my displays (look at: http://doc.qt.io/qt-5/embedded-linux.html at section "eglfs with eglfs_kms backend") inside application directory
Exporting QT_QPA_EGLFS_KMS_CONFIG=conf
Then switch to free tty and run application with -platform eglfs argument.
I have spent dozens of time looking for the solution. I gave up.
I use Qt 5.3 for development and I build cross platform solution.
My MacbBook Pro runs Mac OS X 10.9.3 Mavericks.
My project successfully runs in ios-simulator and desktop builds.
But I couldn't deploy it to neither AVD nor real Android Device.
Here is the logs:
Building the android package failed!
-- For more information, run this command with --verbose.
Generating Android Package
Input file: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/android-libxxx.so-deployment-settings.json
Output directory: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/android-build
Application binary: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/libxxx.so
Android build platform: android-19
Install to device: emulator-5554
19:43:56: The process "/Applications/Qt/5.2.1/android_armv7/bin/androiddeployqt" exited with code 14.
Error while building/deploying project xxx (kit: Android for armeabi-v7a (GCC 4.8, Qt 5.2.1))
When executing step 'Deploy to Android device'
19:43:56: Elapsed time: 02:13.
Do you have any ideas?
Solved.
The issue was:
I set incorrect path to ant executable.
Qt was not able to build android app and for sure deploy it.
Now I am able to run app on the device, but still can't run app with emulator.
Good luck.
I get the error CL_DEVICE_NOT_AVAILABLE when running this sample code. However, unlike in that question, my CPU, the Intel Core 2 Duo E8500 CPU, appears to be supported. I've made sure to link against the Intel version of the OpenCL libraries, since I also have the Nvidia libraries installed. Why is this error occurring?
The Intel OpenCL SDK 2013 required SSE 4.2. From what I can tell (here) the Intel Core 2 Duo E8500 CPU only has SSE 4.1
"CL_DEVICE_NOT_AVAILABLE" is the error you get when you try to create an OpenCL device on an unsupported CPU.
The good news for you is that the Intel OpenCL SDK 2012 works on SSE 4.1; you should uninstall the 2013 SDK and use the 2012 SDK instead (or get a newer CPU).
"CL_DEVICE_NOT_AVAILABLE" has nothing to do with the SDK. It's due to the OpenCL device driver which is part of the video card device driver.
It's common to confuse the SDK and the OpenCL device driver. You develop the host code with the SDK but the kernel is compiled and run through the device driver. I often develop with the Intel SDK but I run my kernels on the CPU using the Intel video driver or the AMD Radeon drivers and on the GPU using the Nvidia video drivers (GTX590). I have all three video drivers installed in Windows. You don't have to have an AMD video card to instal the Radeon drivers.
So in your case you can use the AMD drivers to run your kernel on the CPU. They are much less restrictive than Intel's.
On windows I get faster results running my Kernel on my Sandy Bridge CPU using the Intel OpenCL drivers than AMD. However, on Linux the AMD driver runs my kernel faster on my Intel CPU than the Intel driver does.
I encountered this error while creating a tutorial on how to install hashcat on Ubuntu 18.04; I've included the instructions below for Installing OpenCL™ Runtimes for Intel® Processors - Option A (Recommended)- feel free to review my full gist on GitHub. Hope that helps!
Installing OpenCL™ Runtimes for Intel® Processors
Installing OpenCL™ Runtimes for Intel® Processors - Option A (Recommended)
Check your CPU system processor architecture by running sudo lscpu to identify the class of CPU e.g. "Intel (R) Core (TM) i7-7700 CPU # 3.60Ghz"- alternatively, you can go to Settings > Details which will also reveal the CPU-family (e.g. Intel (R) HD Graphics 630 (Kaby Lake GT2)).
Go to the Intel Developer Zone and scroll down to the corresponding download link for your system; assuming you're running Ubuntu 18.04 and have a Intel Core-class CPU, scroll down to "Linux* OS Ubuntu* 16.04.x (deb)" and click on the Github link for 18.46.11837 Runtimes to access the runtime-packages to download.
There should be instructions within the aforementioned Github repo- or you can proceed with the following in the next steps.
cd ~/Desktop
mkdir neo
cd neo
sudo wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-gmmlib_18.4.0.348_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-core_18.44.1060_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-opencl_18.44.1060_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-opencl_18.46.11837_amd64.deb
Install the packages by running sudo dpkg -i *.deb.
Restart the system by running sudo reboot.
Installing OpenCL™ Runtimes for Intel® Processors - Option B
Go to Intel OpenCL Runtimes website and scroll down to the bottom of the page to Download Intel CPU Runtime for OpenCL Applications 18.1 for LINUX OS (64-bit only).
After downloading the OpenCL Runtimes for Intel Processors, cd ~/Downloads
Run sudo tar -xzf l_opencl_p_18.1.0.013.tgz to unpack the tgz file- please note, the OpenCL file version may update since the time as of this gist (ie as of this gist, the version is 18.1.0.013.)
cd l_opencl_p_18.1.0.013
Run sudo ./install.sh
A welcome screen is prompted- hold-down the "Enter" key until able to input select "2" for "I do NOT consent to the collection of my Information"
Hit "1"
Hit "1"
Hit "Enter" and then restart the computer.
If any additional Intel OpenCL errors are encountered after testing hashcat, go to section 'Installing OpenCL™ Runtimes for Intel® Processors - B'- if not, proceed with section "Testing Hashcat"