0

I resized my Macs SDD to have 45 GB of MS-DOS FAT, I burned the Kali .iso to my USB and installed Kali on the 45GB Free space where I set it as ext4 and /(root) filesystem.

However I skipped the GRUB bootloader as I read it won't be able to recognize macOS, leaving only Kali linux (of course this can be solved, but I'm not sure if I have working Wifi on the Linux).

Now this is my problem: when I reboot, it will reboot into macOS, when I hold alt, it only shows macOS even though I put KL on the 45 GB free space.

How can I make it so that I can boot with rEFInd into Kali (and macOS)?

My diskutil list

 #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         205.8 GB   disk0s2
   3:       Microsoft Basic Data                         44.9 GB    disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +205.8 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD            95.3 GB    disk1s1
   2:                APFS Volume Preboot                 45.8 MB    disk1s2
   3:                APFS Volume Recovery                517.0 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

disk0s1 is obviously listed as EFI. When I try this it says:

sudo diskutil mountdisk /dev/disk0s1
One or more volume(s) failed to mount
  • Try sudo diskutil mount disk0s1. – David Anderson Jan 20 at 3:45
  • I tried this and it works to mount, but it still won't pick up rEFInd as the bootloader. Just loads up macOS – fire2247z Jan 20 at 14:57
  • First of all, rEFInd is not a boot loader. It is a boot manager. Grub is a boot loader. Since you can mount this volume, can you update your answer and post the output from the command ls /Volumes/EFI/EFI. – David Anderson Jan 20 at 15:04
  • rEFInd simply tells the Mac firmware what file to load and execute on the next boot, then reboots the Mac. On the other hand, Grub actually loads files and executes them. Normally, what is suppose to happen when using rEFInd and linux on a Mac is this: Firmware loads and executes rEFInd, rEFInd tell firmware to load and execute Grub, computer reboots, firmware loads and executes Grub, Grub loads and executes linux. – David Anderson Jan 20 at 15:19
  • ls: /Volumes/EFI/EFI: No such file or directory, I tried ls /Volumes and it only lists Macintosh HD but since you're saying GRUB actually loads up Linux, I assume I'll have to change the MBR to HBR so it'll load up my macOS too(unless it can work with refind)? I've ruined it a couple of times, and got it to work once which was like a year ago(I deleted KL before I updated my macOS, now I'm kinda trying to get it on my system again), even though I didn't do anything after I installed Linux. – fire2247z Jan 20 at 15:48

You must log in to answer this question.

Browse other questions tagged .