-
Hello guys, I'm trying to dualboot kali and win10 but after finishing the install of kali without an error I get an error when i choose to boot kali from the grub menu but i can boot win10. The error am getting is the following:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device)
- Missing modules (cat /proc/modules; ls /dev)
-
Try this
Win32Disk Imager, I believe works best with .img, so try UNetbootin for your .iso.
-
I am a Computer Information Systems college student. Very new to Kali as I have only watched someone demonstrate it's power briefly. I want a live USB to investigate it's tools and become familiar with the operating system. However, I have been very unsuccessful at creating a live USB. I am running windows 10 currently, I am booting in UEFI, and I tried recently to use Rufus to write to the USB. I have verified the checksums and they are all correct. Secure Boot is disabled but, I just can't seem to get it to work. I don't even get a boot from USB option when I F12 to boot options. If someone could help me out that would be greatly appreciated.
-
After using Win32DiskInstaller I get the message, "USB needs to be formatted before use" junk! I keep getting this message and when I try and boot. Computer doesn't even recognize a USB device to boot from. I am using UEFI and secure boot is disabled. I verified the checksums and everything matches. Please help, anyone!
-
Hello,
I've decided I've needed to join this forum after frustratingly following the instructions for Kali Linux USB install for OS X and unable to proceed with imaging the ISO file on a USB device. I type in "sudo dd if=kali-linux-______-amd64.iso of=/dev/disk_ bs=1m" in the Terminal, but then I am asked for a password. Nothing in the instructions given on website state there is a password. What Am i doing wrong?
-
Hello I have a toshiba satellite L850-I2011, I was hoping to dualboot windows 7 and kali linux 2016.1 rolling edition so, I followed the instructions on kali website and when i booted from usb to do the gparted thing it gave me an error gnome display manager dosen't work. I have an amd graphic card. So,I don't know what to do and i dont want to take risk because around a week ago I was trying to do the same thing and it formatted my local disk c as ext4 file so i had to format my hard drive than start over. Fortunately I recovered my data through DRW and I want to do it again
-
Hello,
I got a frustrating issue with the latest iso (2016.01-kernel 4.5) when imaging to USB. I am not imaging the iso directly instead I install it in virtualbox vm. Configure it to my own need then convert it to raw and then imaging to USB using dd but booting failed where /sbin/init could not be found, it seems that the /dev/sda1 partition is mounting in a different mount point than / but I cannot figure out what is the issue. Could not find any clue with Google so I am asking forums for help. Anyone seen this issue already ?? Note when imaging the 2016.1 iso directly to USB in live or persistence it is fine and same procedure done with kali iso from end of last year (kernel 4.0) booted correctly also.
-
I was able to install Kali Linux live USB and set up a persistence partition. While doing the updates it seems to hang on an IPv6 addressconf netdevup saying the link is not ready. How can I fix this? It boots just fine still from the Kali live version and I have network connectivity.
-
toor is the default root password on these installs
-
I've done the USB install of 2016.1 on Windows and from in Kali Live, with and without persistence, it all works great.
Except, every install changes the partition size to 2.66GB, not enough room to run updates, it crashes every time. How do I expand this partition? I've tried GParted and it says that boot partition is not available, regardless if I'm booted to it, or another install. I've taken the USB to Win7 and Win10 and can't change the partition. If I wipe the USB and create new 10GB partition, the install process puts it back to 2.66.
How do I allow updates on a USB Live install if I can't expand this partition?