I installed El Capitan and have run into issues with loading audio units for Native Instruments. The workaround is to go into system recovery and type csrutil disable, which enable you to load an old version of the aulvaltool. I am booting off an external firewire drive, and everytime i boot into system recovery and try to use the command, it replies "command not found". I tried specifying the volume/csr/bin to no avail. Any ideas?
I am not a programmer- I just back everything up, and if I crash the drive, I just reinstall and start over..
Any help would be appreciated. Also if anyone has downloaded the new 10.11.1 beta, curious if it fixes this problem.
Thanks.
Follow these step by step instructions:
reboot
as you hear the Apple Chime press COMMAND+R
you will be in the Recovery mode
from the upper MENU select Terminal
you're booting from your internal drive recovery mode, so:
A) el capitan is on your internal drive
• type /usr/bin/csrutil disable
B) el capitan is on your external drive
• type /Volumes/TYPE_THE_EXTERNAL_DRIVE_NAME/usr/bin/csrutil disable
And you're done. Then you probably know how to proceed from the NI forum.
Related
I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04.
But got stuck at this error.
E0520 11:06:29.866803544 5261 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"#1589952989.866791260","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
checkValid: hw configs not eq
I got the solution from this article:
So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.
Don't ask why this works, but it seemed to solve it for me.
Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04
Seems a GPU issue, try :
sudo ubuntu-drivers autoinstall
Or (or both) change graphic emulated performance to software if your emulated device allow it.
Had same issue with linux mint android studio ..
Hope it will help.
Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.
What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.
To delete the snapshots:
rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot
To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:
Edit quickbootChoice.ini, for example:
vi ~/.android/avd/<AVD name>/quickbootChoice.ini
The only line there should be:
saveOnExit = true
If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:
$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot #Pixel_API_29 &
(Or find a way to do this through Android Studio)
A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).
I am trying to install redhat (rhel8) in virtualBox 6.1 on a windows 10 64 bit Home edition machine.
I verified the checksum of the iso file after download and its correct (I compared the checksum against another friend iso file who is able to install properly), still I am getting exception like
dnf.exceptions.error some packages from local repository have incorrect checksum
I even tried to run troubleshooting, but it raise exceptin like
failed to start media check on /dev/sr0 virtualbox
I have downloaded the iso files from multiple places and every time it gives me the same exception.
Any help is highly aprreciated.
Finally I found the reason for the above error.
Virtual Box uses virtualization to run multiple Operating Systems and in one system (let's say a windows machine) only one of the application will be allowed to use system virtualization capability.
So we have to disable any manual virtualization if performed in the system.
So we can disable virtualization by following ways:
Search for “Turn Windows features on or off” in the Start menu, hit
the Enter key to open the Windows Features window. Here, scroll down
to Hyper-V and disable it by clearing checkbox next to it. Then click
OK
Disable Hyper-V by using command.
Press Windows logo key + X, then hit A to run Command Prompt as administrator. In Command Prompt window, type
bcdedit /set hypervisorlaunchtype off
and hit Enter key to execute this command.
Finally restart system.
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I have created emulator in android studio and create little application in it. When i run it gives me an error[See image 1]. When i googled, it told me that your system does not support virtualization. But my system suport it. [See image 2].
Now my question is that when my system support virtualization then why i cannot run my app in emulator. Also please help on this following error too.
1-Intel HAXM is required to run this AVD.
2-Your CPU does not support NX.
Please anyone help to resolve this issues, thanks in advance
(Source of answer here)
First off, download Coreinfo, extract the zip in your Downloads folder, then run CMD (Not as admin), and type in:
cd Downloads
cd Coreinfo
coreinfo
Then, you should get a list of text. Scroll up/down until you find NX. If there's - next to NX, then it isn't enabled or it isn't supported. If there's * and you still get the error, then you're doing something else wrong.
Then, check if NX and VT-x are enabled in BIOS:
If not, enable it. If you don't see an option, then your CPU doesn't support NX.
After you enable it, do the first step again. You should now see *, which means NX is enabled:
OK, so I would like to install openSUSE 13.2 64bit with my USB (want to install it, not to use LiveCD - so i downloaded installation 4.7GB iso). I have used Universal USB Installer 1.9.5.7 to create installation media. Everything worked without problem. When I boot from it, first a openSUSE screen shows up with options Install, Upgrade, Something-I-Don't-Remember and Check installation media. If I choose Install, terminal shows and at the end it says that it is launching "openSUSE installation program". After that, a graphically stunning screen with header "linuxrc" (seems to be responsible for launching installer) shows up and asks me to insert installation media and then press Yes to continue. If I click yes, it shows again, if I click no, it shows me another screen with options Install, Check disk integrity, Reboot and so on... I choose install and it asks for source medium. Options are CD/Network/HDD. However, I want to install it from an USB.
So, my question is: What am I doing wrong? Because I got that feeling that after choosing Install in the first screen (that one with openSUSE background), something else should happen instead of showing up linuxrc. Like launching or whatever. Or should I use another app to "burn" my ISO on USB?
Ok i just managed to make it work.
I am using ISO downloaded today morning (5.November 2014 at 13:11) and ImageWriter ( http://www.mediafire.com/download/9haeauu9sq8xtkx/ImageWriter.exe ). And it seems to work. If you get error about writeToDisk, close the program and launch it as Administrator (i mean it, right click and select run as administrator, it asks you for admin password even if you launch it with doubleclick but it won't work). Then find your file (it shows only *.*raw files in open dialog so you will have to just start writing iso file name in Open bar), choose right device and it will do the hard work. If it finishes with "Sucess" message box, restart PC and boot from USB. Then select Installation.