search

abdyfranco / next-loader

Next Generation EFI-Based Boot Manager designed for Intel Mac.
http://abdyfran.co/projects/next-loader
GNU General Public License v3.0
54 stars 15 forks source link

USB drive do not appear in the loader #18

Open PCasey212 opened 5 years ago

PCasey212 commented 5 years ago

Xserve 3.1. Successfully installed the Next Loader as the "master" boot loader of my system. OSX 10.11.6 load flawlessly.

Problem : the USB drive are no more bootable on the system. They do not appear on the loader. Have tried the 3 usb ports without success.

At this time, my OSX El Capitan install drive isn't recognize. Is it normal with Xserve or I failed something ?

kumowoon1025 commented 5 years ago

I think you might have to build it yourself for an Xserve... Some drivers work because Xserve3,1 is similar to MacPro5,1 I'm assuming but I'm also having trouble getting the drivers to load and mount everything

PCasey212 commented 5 years ago

Hi kumowwon1025,

Thank you for your reply. Since there is not help from the devs and this projects is simply dead, I removed the loader from my Xserve and continu to work with the normal Apple stuff.

Parallel isn't the best way but it is a working way...

abdyfranco commented 5 years ago

I installed an Xserve 2,1 on my Home Lab a week ago, I will check tomorrow if recognizes my macOS Sierra installation drive.

PCasey212 commented 5 years ago

Thank you for the answer. Keep me in touch !

josch1710 commented 5 years ago

Mac pro 3,1: Are there any progress on this issues? I really want to UEFI boot windows and I need the USB Drive for that. Also if I would go all-in on the GOP card, it would be an annoyance to boot from USB without this feature.

kumowoon1025 commented 5 years ago

@josch1710 Mac Pro? There shouldn't be any issues, unless you meant Xserve?

josch1710 commented 5 years ago

No, no. I know what I wrote: USB sticks, that would show up in the Mac boot screen wouldn't in NextLoader.

kumowoon1025 commented 5 years ago

@josch1710 Sorry for doubting you then, it must be because of the different chipset in a MacPro 3,1 than 5,1 (which the release is compiled for). Compiling on your own specifically to support the Mac Pro 3,1 with appropriate efi drivers should work better.