This issue is “several layers deep”.
Ultimately I’m trying to recover a boot of an Ubuntu system that was working on a MacPro 5,1 using OCLP but has stopped working. Now I have started a thread running on OCLP Discord server but that has run into the sand. I also have a thread running on Stack Exchange Ask Ubuntu as I was blocked from posting questions on this Ubuntu Discourse server using my new account. This block on my Discourse account seems to be lifted – so I will try this environment for support queries.
This issue is different from, but closely related to, the other threads I have running on other sites.
Where I am at now. I have a Ubuntu Linux system in a USB caddy.
-
The Ubuntu system boots fine on a Lenovo intel i5 machine when boot order attempts USB devices first.
-
When I use this disk plugged into the front of the MacPro 5,1 USB port, the disk is recognised by the OCLP 2.0.2 boot picker (a bit like grub I’m guessing) but boot fails with following error messages.
Could not read /EFI/ : Invalid parameter
Error: could not find boot options: Invalid parameters
start_image() returned Invalid Parameter
OC: Boot failed – Invalid parameter
OCB: StartImage failed – Invalid Parameter
The OCLP admins state (paraphrasing accurately and fairly, I hope) that “these error messages indicate the problem is with my Linux disk not OCLP” .
-
I have tried using boot-repair described here: https://unixhint.com/failed-to-open-efi-ubuntu-invalid-parameter/ as the page describes fixing Ubuntu boot errors when “invalid parameter “ appears at boot attempt.
-
The boot repair fails – and the diagnostic created is in the following pastebin: pastebin link Scanning the boot-repair diagnostic log it looks like the Windows 10 system on an internal disk, the Ubuntu system in the USB caddy and the internal disks in a Windows 10 storage space are all recognised.
-
From the information in the boot-repair diagnostic log, are there any changes I can make to the boot files on the Ubuntu Linux system disk that might make the disk bootable on the MacPro 5,1?
1 Like
Line 84 - BIOS/UEFI firmware: FBKTA1AUS(1.161) from LENOVO
You have run the boot-repair report on your Lenovo PC.
Can you run the report on the PC where you have the problem?
You can add the the boot-repair utility while running a “Try Ubuntu” live session.
1 Like
I can’t boot the MacPro using an Ubuntu disk or USB stick - that’s the problem I’m trying to fix.
I would have thought running boot-repair on a PC would have given enough information about the organisation of the various files and folders , such as /EFI/ , to help diagnose the problem.
These are my thoughts on this matter.
Ubuntu on the drive in the external caddy will boot when plugged into the Lenovo machine.
Ubuntu on the drive in the external caddy will not boot when plugged into the MacPro machine. The problem must be with OCLP (Open Core Legacy Patcher) despite what the experts say.
This method of running Ubuntu on a MacPro was working but now it is not. What did you do to get it working in the first place? What has changed since then. An upgrade to OCLP?
Boot Repair will re-install Ubuntu boot files to the right places. There is no need to do that because Ubuntu is loading when plugged into the Lenovo machine. The necessary boot files are in the right places.
But not for the MacPro machine. Therefore I conclude that the MacPro machine must be looking in the wrong place. OCLP is not finding the Grub files.
This is all I can offer. Regards
Is this an Ubuntu OS installed on the internal disk of your MacPro?
Hi . I addressed the setup in earlier posts and just wanted to focus on boot-repair to see if that could dig me out of this problem. However, I’m happy to address your questions. In short I believe the issues are in OCLP but I am getting no positive suggestions from there.
Let me be clear. In no way am I knocking OCLP or the people who support it. I think it is an amazing effort to keep perfectly usable and useful Mac hardware in use.
This method of running Ubuntu on a MacPro was working but now it is not. What did you do to get it working in the first place? What has changed since then. An upgrade to OCLP?
You are spot on. The MacOS system was booting from a disk with 2.1.2 OCLP. As I understand OCLP plays a similar role to the traditional MacOS boot picker - but is needed for recent MacOS due to issues with video card support. The OCLP 2.1.2 load time went from a few seconds to over 90 seconds. After researching and “fiddling” I reverted the OCLP version to 2.0.2 and this fixed the OCLP boot time to a few seconds again but I lost the ability to boot Ubuntu. So I thought it was an OCLP issue (“what did you change last , sir?”). However, OCLP support is adamant it is a Ubuntu Linux issue. Hmmm.
Boot Repair will re-install Ubuntu boot files to the right places. … Therefore I conclude that the MacPro machine must be looking in the wrong place. OCLP is not finding the Grub files.
I agree with you completely … but with a lack of suggestions from the OCLP side I was (as I anticipated, vainly) looking to “fix” the Linux disk - which I agree with you isn’t broken. I have asked on the OCLP Discorse for guidance how the OCLP attempts to load Grub - but even though the OCLP documentation is thorough on most things, I haven’t been able to find anything definitive on this vital “hand-over” process from OCLP to grub. I have asked for information on how OCLP “hands over” to Grub2, so I might be able to edit the appropriate OCLP configuration file(s) - and haven’t received anything.
This is all I can offer. Regards
I appreciate the time you have spent trying to help.
I have thought about reinstalling Linux Ubuntu on a new disk - but I was trying to save all the work on my bootable Linux system. The benefit of Linux on the MacPro 5,1 is the Bluetooth and USB drivers all work with the original MacPro hardware and the video and USB 3.1 card I have added. I might bite the bullet and rebuild a new Linux Ubuntu disk, reinstall all my apps and just abandon Mac OS - I was just keeping it bootable so when I am forced to use a Mac, I have some familiarity with the UI.
Thanks again.