edit: installed kali 1.1.0 lastnight...
ls /dev/mmc*
mount /dev/mmcblk0p1 /boot//dev/mmcblk0 /dev/mmcblk0p1 /dev/mmcblk0p2
ls /boot
all your over clocking options for config.txt are in the links i provide...bcm2708-rpi-b.dtb bootcode.bin fixup_cd.dat kernel7.img overlays start_x.elf
bcm2708-rpi-b-plus.dtb cmdline.txt config.txt fixup.dat kernel.img start_cd.elf
bcm2709-rpi-2-b.dtb COPYING.linux fixup_x.dat LICENCE.broadcom start.elf
i just wanted to share... i have not tested but here it is... insert your kali installed sdcard into your labtop, you will see 2 partitions... /dev/sdc1 and /dev/sdc2, you will notice some files exist in sdc1... bootcode.bin and start.elf, write your config.txt here... the links i provide will show all options for config.txt
kali /boot folder is empty
https://github.com/raspberrypi/firmw...ee/master/boot
http://www.raspberrypi.org/documenta.../config-txt.md usefull document for boot options
http://elinux.org/RPiconfig more info
As it's an embedded platform, the Raspberry Pi doesn't have a BIOS like you'd find on a conventional PC. The various system configuration parameters, which would traditionally be edited and stored using a BIOS, are stored in an optional text file named config.txt. This is read by the GPU before the ARM CPU (and Linux) is initialised; therefore it must be located on the first (boot) partition of your SD card, alongside bootcode.bin and start.elf. This file is normally accessible as /boot/config.txt from Linux and must be edited as root; but from Windows or OS X it is seen as a file in the only accessible part of the card. If you need to apply some of the config settings below, but you don't have a config.txt on your boot partition yet, then simply create it as a new text file.
