I wanted to install arch Linux on my usb and run it with my Mac. But when I format the drive to FAT-30, and use “guid partition table”, and next try to put the iso with Etcher, on my usb, my drive gets “uninitialized”, in the diskUtility app and I can’t do anything with it. I tried restarting the Mac, replugging the usb, nothing changes. Any help would be appreciated :)
Related
I have virtualbox running an Os X 10.11 El Capitan VM and I want to be able to boot my computer into OS X, but I can't figure out how to create a usb that my computer will successfully boot to or try to install mac to install to a partition. I've tried transmac and much googling. I was wondering if there is a way to use my existing .vdmk file to boot to a partition on my computer or if there is another solution.
I have heard about two possible solutions (but I never try them):
First - you can try convert your .vdmk file into an iso image, and then boot to a partition on your computer.
Second - you can try clone your .vdmk file using Clonezilla (http://clonezilla.org/) and then boot from It.
Hope it works for you.
Goal
I was attempting to install Elastix 4.0 on a home PC via a Bootable USB, but never had any luck getting it to install past the CentOS7 part (it kept giving me a "Warning: /dev/root does not exist" error).
What I've Tried
My main PC is Windows 10 Pro, so after downloading the latest Elastix 4.0 .iso from "http://www.elastix.com/en/downloads/" (Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso) I used UNetbootin to create my Bootable USB for Elastix 4.0. I put the now Bootable USB into the PC I want to put Elastix 4.0 on and started it up.
It gave me the "Install Elastix 4" menu, so I hit enter and waited. Then the install proceeded to do its checks for CentOS7, but ended up getting stuck and gave me an error message "dracut-initqueue[580]: Warning: Could not boot." and "Warning: /dev/root does not exist".
This is where I am stuck and cannot proceed.
EDIT #1: I signed up for the Elastix forms, and someone else also had this issue. They said they downloaded the .iso and used Rufus to make a Bootable USB, and then booted the installation using the Troubleshooting -> Install CentOS 7 using Basic Graphics ... but according to them, that apparently corrupted something else and then they opted to just use a DVD.
EDIT #2: I tested this, and making a Bootable DVD of the .iso does work great for local machines. Installing it via a VM also seems to work without hassle. As a personal goal, I would like to get this working via a Bootable USB.
Research
I did some research but a lot of the solutions I've noticed are using the dd command in Linux to make a Bootable USB for just CentOS7 because it is (was?) known that UNetbootin did not properly make a Bootable USB for CentOS7, and I can't seem to find anything that would assist in making the Elastix 4.0 .iso work properly via a Bootable USB. I did try other tools such as Rufus 2.7, Win32 Disk Imager, ISO2USB, and dd for Windows, though most rendered my USB not bootable at all (Rufus worked OK, but still got stuck at the CentOS7 part). Also, installing via a CD/DVD is not ideal, as I have no CD/DVD drive (and I want to see if I can get this working via a Bootable USB drive).
There seem to be a few guides out there for trying to create a Bootable USB for Elastix 2.x, but nothing for Elastix 4.0. Reviewing those, it looks like the guides reference some files that do not exist in the new .iso (ex: ks_default.cfg). Still, my issue pertains mainly to the CentOS7 error I'm getting so I don't think this is related.
Any assistance with this is appreciated, and if you require more information from my end just let me know. I'm willing to try / re-try anything.
Thank you in advance.
http://henrysittechblog.blogspot.ru/2014/01/install-elastix-from-usb-step-by-step.html
Look for this line, but it may change:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Change it to:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=sdb1:/dev/sdb1:/ks/anaconda-ks.cfg quiet
Hi there i solve this problem 80%.
i did some manual change at line:
inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Mine:
inst.ks=scsi:/dev/sdb1:/ks/anaconda-ks.cfg quiet
hd is not recogniced by Centos7.
made my usb bootable with rufus 2.9
then open isolinux.cfg with notepad++
just change the line
inst.ks=hd:sdb1:/ks/anaconda-ks.cfg quiet
where sdb1 used to say cdrom
I have a BeagleBone Black development board. When I initially bought it, I set it up on my Mac and was able to ssh into it without any problem. Then, I followed a tutorial once for sharing the internet of my Mac with the BeagleBone using USB and since then I was unable to SSH into my BeagleBone from my Mac. I tried updating the HornDis driver and it didn't solve anything.
What happens is that my Mac (Mavericks) detects the BeagleBone drive, but it doesn't show up in the network interface. Hence, I can't ssh into the BeagleBone at all. I tried installing both the FTDI and HornDis driver over and over and it didn't solve the problem.
I really need it to work on my Mac and I'm kind of lost at this point. Any help would be really appreciated. I can't reinstall the OS in the BeagleBone because I have some very important project work installed and working in that BeagleBone and don't want to reinstall all those packages again.
Thanks.
I have solved this problem by resetting the SMC and the PRAM. Here are the details if someone needs it:
Reset the SMC and PRAM
SMC Reset:
Shut down the MacBook Pro.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if it's not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.
PRAM:
Shut down the MacBook Pro.
Locate the following keys on the keyboard: Command, Option, P, and R.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
After following the above two steps I plugged in the BeagleBone and it was detected in the network interface. I was then able to successfully ssh into it.
I got a beaglebone black version and downloaded the starterware for example code. I can build .bin file but I have no idea how to make it work in the board. I put the MLO and modify 'gpioLedBlink.bin' name to 'app' and put them into SD card. Open the power, I know beaglebone didn't get into the original linux, but it only open USER LED 012, but there no led blink. I think the program didn't really work.
How should I solve this problem? And how can I use gdb to debug the program?
Another question is that there is no ttyUSB* when I plug the usb. How should I get the linux information when beagle black get into the original linux. THX.=)
Use Uboot and loady to load your binary over serial (default address is 0x8020 0000). Once it has loaded, go 0x80200000.
GL.
I am using USRP2 with RFX2400 Daughterboard. I plan to use the USRP2 for my project.
I downloaded the FPGA (bin) and the Firmware image and through the SD Card burner, I write it to a SD Card.
But I am not able to use the USRP2.
I connect the USRP2 to the Ubuntu system (Direct Connection through Ethernet). I run find_usrps and get the system error:
" No USRPS found"
Also, when I run und_find_devices, I get the error "No UHD devices found".
Please let me know if I am missing some obvious steps. When I turn on the USRP2, only LED F turns on.
I donot see the boot sequence as mentioned here: Youtube
Thanks
Kiran
This is an old question and wonder if you still have the problem?
Did you install the UHD driver?
Did you veryify that it works properly?
Do you have a GbE that is compatible with GR?