Just to clarify, you're speaking of booting on the ISO after having copied it on an USB key... and you refer to the Syslinux bootloader where you decide whether you boot in live mode or you install a new Kali system. Is that correct?

I seek clarifications because you mention grub but at the same time you modify stdmenu.cfg which is a syslinux file.

Also can you let me know if you have the same problem with this ISO image:
http://archive.kali.org/kali-daily-images/kali-linux-light-rolling-amd64.iso

Thank you.

@rhertzog: yes, i've downloaded the iso and created a bootable usb stick out of it. yes its syslinux .. my mind was stuck with it being grub.. sorry for the confusion.

So to clarify: "the Syslinux bootloader hangs / does not respond to input when booting a macbook pro mid 2015 retina with the supplied graphical configuration as in the 2.0 release. after removing the nice graphic tweaks in EFI/BOOT/stdmenu.cfg, the syslinux bootloader is responsive to user input and allows to choose a boot option and execute this option."

I will try with the new iso tonight.

i cannot open this iso on my mac nor boot from it. in comparison to the other iso (the one including the live distribution), this one does not have a second partition with the EFI files on it.

btw. checksums would be great.. I have this sha1:
d116bc36437dedbd4b2c0b75d87d8acfc7f3e64d kali-linux-light-rolling-amd64.iso

Gah, that was an unexpected regression. Thanks for letting us know. Can you check again tomorrow with the new ISO that will be available then? TIA. (Today's image has the same problem)

Ok I check the latest file with server timestamp >~ 20-Jan-2016 04:00

btw. it would really be nice if kali could make the cd like ubuntu, where everything is in one partition and I could - at least on the usb stick - change everything. That way I could also add additional firmware easily to the firmware folder

I've tried
kali-linux-light-rolling-amd64.iso and kali-linux-next-amd64.iso
both don't contain a "mountable file system."

Did you try to the 2016.1 ISO that we released recently?

I just tried with the 2016.1 full iso ( kali-linux-2016.1-amd64 )

• I was able to create a bootable usb-stick
• when trying to boot the stick, the screen stayed black
• i then changed EFI/BOOT/stdmenu.cfg
  • I commented out the follwing lines
    #menu background splash.png <-- this is probably the most important one
    #menu vshift 10
    #menu hshift 4
    #menu width 70
    #menu margin 5
    #menu rows 10
    #menu helpmsgrow

After saving the file and rebooting to the stick, I could see the boot menu (just with grey background and white text, but at least it was usable) and selected the live version.

I was able to boot kali live, I was able to join a wifi and use the system.

Unfortunately I was not able to put my wifi adapter into monitoring mode ( I wanted to play with airmon-ng ) ... not sure if I would need a special firmware for my adapter to be usable for this.

So to summarize: After changing the stdmenu.cfg file, I can boot into the live version of kali / use the boot menu as expected.

I think the problem with the splash image has something to do with the retina display of the mac, but thats just a guess.

Hello, i have a problem when i try to boot, i install refind , but dose't work, when i try to boot say "No system" bootable or something like that , black screen try to boot but nothing, press any key to continue, but nothing happen,i have Macbook Pro 2009, please help me thank you

Admin-rhertzog

• where i can send you some picture please.
  i need help, i make usb bootable same way like domdorn
  -i pass the black screen by chose graphical install ,
  -i already install refind ,
  • i make a partition after complete install , i try to boot the sytem, nothing happen it say " operating system not found "
    -i can see partition in disk utility byt i can't mount
    I have macbook pro 2009 early
    thank you!
    P.S i try both system normal and light same problem, i can't acces the system even live, ....

At this point, I think it's unlikely we will be able to deal further with this request. So I'm closing the ticket. Hardware support issues are difficult to deal.