Distro - Ubuntu 20.04.2 LTS x86_64
System Specs -
RAM: 8G
CPU: AMD Ryzen 5 3550H with Radeon V
GPU: AMD ATI 05:00.0 Picasso
GPU: NVIDIA GeForce GTX 1650 Mobile
Running only android studio works just fine but when i try to just open my firefox it becomes too much for the system and it makes the whole system slow like can't even open my terminal. I have to press and hold my power button to shutdown and reboot.
By using top - %CPU even shown 600.3 which is insane!!!
Related
can RTOS like Nucleus and Zephr be installed in VM ware
Is it possible to install in VM ware. I like to learn RTOS and if there is any smaller version of some RTOS that can be easy to learn then that will be great. and do They have image file like iso or do I need to compile the code with make
System info
Model name: Intel(R) Core(TM) i5-2450M CPU # 2.50GHz
CPU op-mode(s): 32-bit, 64-bit
Architecture: x86_64
Android emulator boots, but shows black screen thereafter.
adb shell works, connecting to the emulated device and giving root access etc without an issue. I've googled everything I can think of, and tried all sorts of stuff. If you have a suggestion I haven't tried, I'd love to hear it.
Things I've tried:
Delete and reinstall Android studio (basicly, find $HOME | grep -i "android" | xargs rm -rf, though manually so as not to kill my projects)
X86, X86_64, and "armeabi-v7a" ABI's
Turn on/off using host GPU support/emulation
Changing memory amount (1.5, 2, 4GB)
Different API levels (21, 25, 26)
Rotate device's virtual screen to force a redraw
Remove hardware from virtual device (camera)
Creating fresh, brand-new flutter app to run on it.
(app doesn't run.
claims device is "offline" when I try to run it, despite having shell access and connecting with adb just fine)
Swearing a lot.
Phoning a friend.
Hardware I'm running on:
AMD FX(tm)-8350 Eight-Core Processor
32GB RAM
NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
Linux herb 4.15.0-42-generic #45~16.04.1-Ubuntu SMP Mon Nov 19 13:02:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Xfce4 (I hate gnome & kde and it's stupid useless eyecandy & bloat)
ZFS file system (2TB capacity 653GB w/ 256G Flash drive configured as cache/zlog)
Emulator DOES show the boot screen, either B&W "Android" or fancier google logo depending on the API level. After a few minutes, it goes to a black screen, and refuses to show anything else unless I cold boot it again.
HAXM is not installed. It's not only intel-only, but also windows/mac only, and I'm running linux on an AMD processor.
I,m running Intel Core i3, 4 GB Ram, 32bit, HAXM Version 7.2.0
Android emulator: Nexus 5X API 28
I give the following command in the terminal:
E:\Android_SDK\emulator>emulator #Nexus_5X_API_28
HAX is working and emulator runs in fast virt mode.
VCPU shutdown request (Shows the same about 15 times)
emulator: WARNING: Not saving state: emulator hasn't finished booting.
VCPU shutdown request
Tried all the methods but none of them helped.
For me, reinstalling intel haxm and it worked perfectly.
I had exact the same problem in Windows 10. The only solution I could find was that running emulator in terminal with administrator mode.
Good luck!
I'm writing an application that needs to run on a Beaglebone Black running Angstrom Linux. The shipped linux on this board already comes with node, but it is a very early version (0.12.7). So I tried to use a newer version. I went to the node.js website and downloaded this archive (node version 4.6.1 Linux binaries for ARMv7). When I extract the package on the Beaglebone and try to run node, I get a strange error:
root#ivt:/sdcard/node-v4.6.1-linux-armv7l/bin# ./node -v
-sh: ./node: No such file or directory
sdcard is an ext4 partition on the SD card that I use (the card is ok, I can also run another node project from the same partition with the old node version).
Why does this error occur and what does it mean? The node executable in the directory mentioned above seems to be ok:
root#ivt:/sdcard/node-v4.6.1-linux-armv7l/bin# file node
node: ELF 32-bit LSB executable, ARM, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x2b816f446e6e77cabfa4c3303376c05a5f90ff2a, not stripped
This should be ok for this board, I think:
root#ivt:/sdcard/node-v4.6.1-linux-armv7l/bin# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 990.68
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Generic AM33XX (Flattened Device Tree)
Revision : 0000
Serial : 0000000000000000
What am I doing wrong || what am I missing?
You can upgrade the Node.js version of a BeagleBone by installing Debian 8.7.
All BeagleBone Debian images (after 2016-11-06) have Node.js v4.x as default. I upgraded from Debian 8.6 (Node.js v0.12.17) to Debian 8.7 (Node.js v4.7.2).
Here is how you can do it:
Download a 4GB SD LXQT image from the weekly snapshots. Note: The image names contain BBB for BeagleBone Black or BBBW for BeagleBone Black Wireless (example BBBW-blank-debian-8.7-lxqt-4gb-armhf-2017-01-15-4gb.img.xz)
Decompress the image (from .img.xz to .img). If on Windows you can use 7-Zip to do it.
Turn the image into an eMMC flasher image. In order to do this you need to check the contents of /boot/uEnv.txt in the .img file. It is important that the line about the "eMMC Flasher" is not commented. It should look like: cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3-bbbw.sh.
Write the image to a microSD card. If on Windows you can use Win32 Disk Imager.
Power off your BeagleBone (by physically disconnecting the USB/power cable)
Plugin the microSD card
Hold the Boot Switch (near the microSD card slot) and, while holding this button, insert the USB/power cable. Keep holding the Boot Switch until the User LEDs start to flash.
Wait until the User LEDs stop blinking and all 4 User LEDs are on. This process can take 5-25 minutes depending on the image used.
Disconnect the USB/power cable.
Remove the microSD card. Otherwise, you will end up flashing the eMMC again.
Power on your BeagleBone Black.
Here is an overview of the BeagleBone (with buttons & LEDs):
Don't be afraid of the amount of steps. It's actually straightforward. There are also official guides about the latest firmware images and installing the latest software.
I am trying to run my OpenCL application at my Intel CPU and Nvidia GPU at the same time for load balancing purposes. But i have the problem that only the Nvidia Plattform is detected.
I use this cl.hpp call:
std::vector<cl::Platform> m_platforms;
cl::Platform::get(&m_platforms);
My system setup:
Linux Arch 3.14.6-1-ARCH
Intel Haswell 4770K
Nvidia 250GTS
installed packages:
nvidia-libgl 337.25-1
opencl-nvidia 337.25-1
nvidia 337.25-1
nvidia-utils 337.25-1
mesa 10.2.1-1
opencl-headers12
intel-opencl-sdk 2014R1-2
opencl-icd 1.2.11.0-4
Both platforms (Intel, Nvidia) have there .icd files in /etc/OpenCL/Vendors. So I don't know what i can try to finally get an Intel CPU OpenCL platform recognized. Maybe you have some ideas?
For now, it would be best to uninstall both of these packages (intel-opencl-sdk and intel-opencl-runtime) and install beignet from the community repository.
sudo pacman -S --needed beignet
The package provides the same functionality and allows you to use the Intel GPU cores also.
I can confirm that it coexists well with other OpenCL platforms such as that provided by NVIDIA, as tested on an Optimus-capable ASUS G750JM. Currently switching via bbswitch and offloading GL-renders via PRIME and primus.
Some pipelines (pyrit) can use OpenCL simultaneously on both platforms, boosting the performance noticeably.
I found an additional package called "intel-opencl-runtime". The intel-opencl-sdk contains the icd file, but it seems not to be enough to be able to run OpenCL apps with the Intel platform. To be able to run OpenCL using the Intel platform it was necessary to also install the above mentioned runtime package.