Impossible to login with root:toor ?
Am I crazy ? Start live USB fresh from ISO Kali 1.1.0, login as root, typing toor as passowrd et replay is "Login Incorrect"
We may help ?
Printable View
Impossible to login with root:toor ?
Am I crazy ? Start live USB fresh from ISO Kali 1.1.0, login as root, typing toor as passowrd et replay is "Login Incorrect"
We may help ?
Thanks, Very helpfully ..
installation stops when it reaches 9% while copying data to HD..
pleaes help!
for me all ok, thanks :)
I did try to install my non-PAE - Kali from USB but after the installation went OK, Grub or Lilli could not be installed (whyever).
If I try grub-install /dev/sda after chroot /mnt I get the error grub: command not found.
Meanwhlie I added Grub4Dos with a puppy-USB.iso but at booting without USB on sda1 I get the error:
[ 1.784307] --- end] kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]
[ 32.187475] random: nonblocking pool is initialized
As Grub can not be installed on nonPAE-Hardware even with non-PAE-Kali.iso (what is a bug).
What shall I do ? Please help !
the process for install kali is not so critical. it is very easy process and only needs proper guidence and some small time. a small mistake can harm your laptop. you can follow this post. post published in may 2015 so there are less chances of error and tested on windows platform. please go to http://moonkinghackersclub.blogspot....rtual-box.html
Recompiled kernel on live USB won't boot; trouble with GRUB ?
I am a newbie to Kali. I have a live install on a 16GB USB, kernel 3.18.0-kali3-686-pae, that I have been running on a Dell Inspiron for a few months. This always boots fine, although when I created it GRUB installed some code into the boot partition on the HDD. (Ideally I had wanted a stand alone live USB that started via the one-time boot menu and a standalone PC that booted directly to WinXP ).
I have now recompiled and installed a new kernel on the same USB stick following the instructions given at https://Informationtreasure.wordpres...i-linux-kernel. The commands given there worked for me while those in the Kali docs did not. The new kernel is called 3.18.6.
When I try to boot to 3.18.6 I get the splash screen and then see
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
Loading, please wait...
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- check root delay= (did the system wait long enough?)
- check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sdb1 does not exist. Dropping to a shell!
and then it tells me some modprobe modules are missing:
i8042
atkbd
ehci-pci
ehci-orion
ehci-hcd
uhci-hcd
ohci-hcd
usbhid
And then I am dropped to BusyBox. I have sat at the (initramfs) prompt for minute and then typed "exit" but I do not escape from BusyBox, I just get more (initramfs) prompt, one after the other. I have done some googling around and tried the "all_generic_IDE" and "replace UUID with /dev/sdb1 etc" style fixes in grub.cfg but they did not solve my problem.
On the USB under /boot I can see two config files, two initrd.img files, two system.maps and two vmlinuz files with either 3.18.0 or 3.18.6 added to the name. There is one grub.cfg file under /boot/grub that contains the two scripts shown below. I have substituted /dev/sdb1 for the original UUIDs in the linux lines.
menuentry 'Kali GNU/Linux, with Linux 3.18.6' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 9d56b544-4352-4342-bb7a-147b4cfe3c0f
echo 'Loading Linux 3.18.6 ...'
linux /boot/vmlinuz-3.18.6 root=/dev/sdb1 ro forcepae quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.6
}
menuentry 'Kali GNU/Linux, with Linux 3.18.0-kali3-686-pae' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 9d56b544-4352-4342-bb7a-147b4cfe3c0f
echo 'Loading Linux 3.18.0-kali3-686-pae ...'
linux /boot/vmlinuz-3.18.0-kali3-686-pae root=/dev/sdb1 ro forcepae quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.0-kali3-686-pae
}
I have not reproduced above the two Kali recovery mode scripts, that appear identical to each other, or the WInXP script.
The 3.18.0 kernel was installed using GRUB while the instructions I followed for 3.18.6 used GRUB2. I can also see a Vmlinuz and a initrd.img file in the filesystem folder right at the bottom of the page in file manager. Oddly, I cannot find these two files in a terminal. Adding ABC to the end of their file names did not prevent 3.18.0 from booting.
Can anyone tell me what to do to make the 3.18.6 kernel boot ?
I had exactly the same problem. I built a live USB with kernel 3.18.0-kali3-686-pae. In the middle of this process I was asked to choose a 'username' (the default was 'kali') and provide a username password, and a second password to use with MySQL.
I could not log in with root:toor or username:username password. Eventually I found I could log in with root:username password. Not immediately obvious, but it worked.
Asus z97-pro(wifi ac) and M.2 SSD issue.
Did anybody manage to install Kali on M.2 SSD disk?
..............
I am trying whole day and nothing. Only errors.....
ata1: hard resetting link
or
...............
sata link down (sstatus ffffffff scontrol ffffffff)
I have feeling that Kali cant see my M.2 SSD hard disk!
Any advice.