Jump to content
This Topic

Proxmox VE OSX Guide discussion

fabiosun

By fabiosun
in General

 Share

Recommended Posts

Recommended

Posted by fabiosun,

as info for all..it is possible to boot in bare metal or in Proxmox with the same bios settings   Bad..very bad news..Our (mine) trx40 has not a native NVRAM For now I am not be able to activate my Nvidia Web drivers in High Sierra so I can't do a computation with GPU test CPU is the same Under load in CB20 I see 360 watt of power draw 🙂 Used AMD Per Gadget tools to monitor it   this thread for Bare Metal discover or simply to talk about :9  

Bare Metal TRX40 discussion thread

Recommended by fabiosun

  • Like

1 reaction

Go to this post
Driftwood Senior Member

Driftwood

Posted
Posted (edited)
  On 5/14/2020 at 3:16 PM, AllubzV said:

The MacPro7,1 also utilizes multiple GPU's (basically Radeon VII, the Radeon Pro Duo = 2x 40cu Radeon VII which has 36cu), but it's not CrossFire anymore. AMD's recent Pro cards have a variant of Infinity Fabric (like the SLI / CF connector, but $100-200). macOS doesn't mind multiple GPU's, and it sees them typically as separate units, but allows them to work in tandem if the application supports it.

Expand  

Im currently running MacPro 1,1 do you think Ill be better served running MacPro7,1 for this threadripper 3970x and radeon VII  pair? About to begin passthrough of everything outside of the GFX cards. Hoping to see performance gains in NVMEs and rest.

 

By the way, if you have dual GPU use PCIe lane 0 and 2 (first and third slot) Both will guarantee x16 speed.

Edited by Driftwood
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

@Driftwood I asked before

post if you want

your vm config

your lspci -nnk output

your modules file

your kvm.conf file..and all thing could be useful

motherboards are different and you have a radeon which could be more problematic...but solutions could be similar for others controller..

Stay for now with Imacpro1.1

@AllubzV I think did an example to explain that more GPU are possible also in real Mac (and obviously in our hackintosh)

 

  • Like 1
Link to comment
Share on other sites
Driftwood Senior Member

Driftwood

Posted
Posted (edited)

Ok guys here's my system before I begin the main passthru configs. Only pass thru'd a pair of Radeon VII GPUs so far. There's a bit of tidying up to to do and add the 2nd MP600 to the box. Enjoy!

 

/etc/pve/qemu-server/101.conf 

 

  Reveal hidden contents

 

etc/default/grub

  Reveal hidden contents

 

/etc/modprobe.d/kvm.conf
 

  Reveal hidden contents

 

/etc/modprobe.d//blacklist.conf

  Reveal hidden contents

 

/etc/modprobe.d//vfio.conf
 

  Reveal hidden contents

 

./iommu.sh

  Reveal hidden contents

 

dmesg –kernel

 

  Reveal hidden contents

 

find /sys/kernel/iommu_groups/ -type l

  Reveal hidden contents

 

Anything else you need to know let me know!

 

Proxmox Screens: Hardware & OptionsHARDWARE Proxmox .jpg

Proxmox OPTIONS.jpg

Edited by Driftwood
added 2nd nvme, changed sata 2 to 0 (Mac boot), and added sata 1 - the other nvme, changed boot order in Proxmox bios
  • Like 1
Link to comment
Share on other sites
Driftwood Senior Member

Driftwood

Posted
Posted

Oh and my 'lspci -nnk'

 

  Reveal hidden contents

 

  • Like 1
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted 
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
        Subsystem: ASRock Incorporation FCH SMBus Controller [1849:ffff]
        Kernel driver in use: piix4_smbus
        Kernel modules: i2c_piix4, sp5100_tco

03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e]
        Kernel driver in use: vfio-pci
        Kernel modules: amdgpu
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel

05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c]
        Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff]
        Kernel driver in use: xhci_hcd


23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e]
        Kernel driver in use: vfio-pci
        Kernel modules: amdgpu
23:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel

25:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c]
        Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff]
        Kernel driver in use: xhci_hcd
25:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:d102]
        Kernel modules: snd_hda_intel

43:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01)
        Subsystem: Phison Electronics Corporation Device [1987:5016]
        Kernel driver in use: nvme
44:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242]
        Subsystem: ASMedia Technology Inc. Device [1b21:3242]
        Kernel driver in use: xhci_hcd
45:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
        Subsystem: ASRock Incorporation AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1849:d107]
        Kernel driver in use: atlantic
        Kernel modules: atlantic
48:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486]
        Kernel driver in use: xhci_hcd
48:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c]
        Kernel driver in use: xhci_hcd
49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
        Kernel driver in use: ahci
        Kernel modules: ahci
4a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
        Kernel driver in use: ahci
        Kernel modules: ahci
4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01)
        Subsystem: Phison Electronics Corporation Device [1987:5016]
        Kernel driver in use: nvme

@Driftwoodin my experience you can pass all of these listed above

using previous FLR posted Kernel patch

It is also possible to have some problem if you use sata or nvme disk (for proxmox installation)..I use ASMedia usb 3.2 type controller for Proxmox so  I do not share with proxmox my sata or nvme controller when VM starts, and I pass entire sata/nvme controllers to boot in "vanilla" OSX/Windows VM

I would like also to suggest to comment amdgpu,radeon and nouveau lines in blacklist.conf to have a more friendly AMD system (you can run command from this instead to use another pc/device to modify things)

 

if you try..be prepared to solve possible problems 🙂

 

  • Like 1
Link to comment
Share on other sites
lvtz Junior Member

lvtz

Posted
Posted (edited)
  On 5/15/2020 at 6:23 AM, fabiosun said:

.I use ASMedia usb 3.2 type controller for Proxmox so  I do not share with proxmox my sata or nvme controller when VM starts

Expand  
  1. I understand that you have installed Proxmox on the USB stick?
    1. It's ASMedia usb 3.2 expansion card yes? And what USB stick you use with this? Can you provide also model number for expansion card?
    2. This solution is better than creating a virtual file on nvme disk, which will be used for both Proxmox and macOS?
    3. Will this solution affect macOS performance?
  On 5/15/2020 at 6:23 AM, fabiosun said:

if you try..be prepared to solve possible problems 🙂

Expand  

 

What kind of problems can these be?

 

I am sorry for such a large number of questions, but I want to know and understand the topic as best as possible, and I would not like to write too much in this thread.

 

Currently, I am waiting for the delivery from Amazon, I bought an additional Nvme disk, as soon as it comes, I start my adventure.

Edited by lvtz
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

Hi @lvtz

USB controller is integrated on my motherboard and in the main guide I show where I connect my "proxmox" disk.

in 1) and 2) question you mix some different subject..

 

to install Proxmox you have to create an USB Pen (CD/DVD or what you desire) to install it

Then you can choose a disk to install Proxmox (proxmox = linux)

I have chosen an external USB disk..why? in this way I have all others controller (sata, NVME, and so on to pass to my VM)

 

Best solution is to have your guest OS system in a separate drive from Proxmox disk

ie

if you have now a working OSX on your system you can use it with only a proper EFI to boot with it..

if you instead install OSX on a file, you can have it on your Proxmox disk..in my opinion it is better to use Proxmox disk only for few things and leave all other OSX separated from it

 

so you need:

1) an USB/CD/DVD for iso installation file

2) boot from this one and from here you have to configure Proxmox (5 minute of your time)

3) in there you choose disk fr proxmox installation (in my case an external disk on back USB)

4) then you can create following the instructions your VM

if you have an existing OSX on a separate disk you can try to "pass" that disk..I did for my NVME High Sierra 

 

Be prepared to solve different problems..but when you succeed in this task you will be happy 😉

 

 

  • Like 2
  • Thanks 1
  • +1 1
Link to comment
Share on other sites
lvtz Junior Member

lvtz

Posted
Posted

@fabiosun :

 

Thank you for your help, and patience.

So it's an important thing to focus on a good class and fast external USB SSD disk ,or average external SSD USB disk or USB stick will be enough too?

 

If I understand correctly, dedicated disk for the Proxmox and OpenCore is important until running macOS from Nvme, so only the initial boot of Proxmox can be slower?

 

I wonder if I should invest in a better disk for Proxmox + OC, or is it enough a medium class 😃

Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

proxmox start very fast..and when you have your system well calibrated you can start in automatic way also your VM

so you click on your power button and you reach your OSX desktop 🙂

for proxmox I have a SSD Samsung 840 Pro in a cheaper external enclosure 🙂

in my test I have had also for proxmox a cheaper laptop 2.5 '' mechanical hd...

 

in my opinion if you do not use 100000000 VM you can use a small disk for proxmox..so you can also backup entirely in a flash..then you can have different disk with different OSX as a real pc/hack/Mac 

@lvtz have you a working OSX in this system or it is your first experience?

 

  • Like 2
Link to comment
Share on other sites
lvtz Junior Member

lvtz

Posted
Posted

@fabiosun - For some time I have configured OSX, but in a traditional way (using OpenCore and many patches and kexts). I am quite happy, but I am irritated by some random situations or the fact that everything is not necessarily working properly - after all, AMD is not an officially supported processor. That is why I became interested in this method for preparing OSX.

 

I haven't tried Proxmox yet, I'm still researching and tracking your threads and posts (I study theory, time for practice soon!). I ordered SB-ROCKET-NVMe4-1TB yesterday because I have one more free space on the motherboard - now I'm waiting until Monday for delivery. So far I have Win10 (on PX-512M9PeG), and macOS Catalina + EFI via OpenCore (on second PX-512M9PeG).

 

I am wondering whether or not to make the PX-512M9PeG format which is now macOS and then install Proxmox + OC there. But on the other hand this disk is 512 GB and if Proxmox is installed on it, it will be largely unused. I don't know what to do now 😅 I have a dilemma about whether to use a USB external disk or maybe the current Nvme 512 GB.

Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

If you have windows installed you can use it

in my case I use grub bootloader (proxmox) to boot and decide what I want use

you have to find a solution for you 

better for you I mean 👍

  • Like 2
Link to comment
Share on other sites
lvtz Junior Member

lvtz

Posted
Posted

Finally, I decided to buy an additional 120 GB SATA SSD (CT120BX500SSD1) to install Proxmox + OC on it. (OMG! How many disks will I have in my build... Nvme (3), HDD (2), SSD (1) 😂)

 

At this moment, I think I know everything (in theory). I will probably write again here when I start the configuration... Well, unless everything goes smoothly without any issues 😄 Anyway, I will let you know.

 

Thanks again for your help. Have a nice weekend!

  • Cross Finger 1
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

I would like to share something that could be useful for Full PCi tab lovers in about my Mac / System Report /PCI

 

from Proxmox shell (this naming for path is for latest 6.2 proxmox VE installation:

 

nano /usr/share/qemu-server/pve-q35-4.0.cfg

you will see: 

  GNU nano 3.2                              /usr/share/qemu-server/pve-q35-4.0.cfg                                        

#[device "ehci"]
#  driver = "ich9-usb-ehci1"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1d.7"

#[device "uhci-1"]
#  driver = "ich9-usb-uhci1"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1d.0"
#  masterbus = "ehci.0"
#  firstport = "0"

#[device "uhci-2"]
#  driver = "ich9-usb-uhci2"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1d.1"
#  masterbus = "ehci.0"
#  firstport = "2"

#[device "uhci-3"]
#  driver = "ich9-usb-uhci3"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1d.2"
#  masterbus = "ehci.0"
#  firstport = "4"

#[device "ehci-2"]
#  driver = "ich9-usb-ehci2"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1a.7"

#[device "uhci-4"]
#  driver = "ich9-usb-uhci4"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1a.0"
#  masterbus = "ehci-2.0"
#  firstport = "0"

#[device "uhci-5"]
#  driver = "ich9-usb-uhci5"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1a.1"
#  masterbus = "ehci-2.0"
#  firstport = "2"

#[device "uhci-6"]
#  driver = "ich9-usb-uhci6"
#  multifunction = "on"
#  bus = "pcie.0"
#  addr = "1a.2"
#  masterbus = "ehci-2.0"
#  firstport = "4"

# FIXME: Remove this audio0 device at the next possible time
#     see: https://pve.proxmox.com/pipermail/pve-devel/2019-July/038417.html
#          https://pve.proxmox.com/pipermail/pve-devel/2019-July/038428.html
#[device "audio0"]
# driver = "ich9-intel-hda"
# bus = "pcie.0"
# addr = "1b.0"


[device "ich9-pcie-port-1"]
  driver = "pcie-root-port"
  x-speed = "16"
  x-width = "32"
  multifunction = "on"
  bus = "pcie.0"
  addr = "1c.0"
  port = "1"
  chassis = "1"

[device "ich9-pcie-port-2"]
  driver = "pcie-root-port"
  x-speed = "16"
  x-width = "32"
  multifunction = "on"
  bus = "pcie.0"
  addr = "1c.1"
  port = "2"
  chassis = "2"

[device "ich9-pcie-port-3"]
  driver = "pcie-root-port"
  x-speed = "16"
  x-width = "32"
  multifunction = "on"
  bus = "pcie.0"
  addr = "1c.2"
  port = "3"
  chassis = "3"

[device "ich9-pcie-port-4"]
  driver = "pcie-root-port"
  x-speed = "16"
  x-width = "32"
  multifunction = "on"
  bus = "pcie.0"
  addr = "1c.3"
  port = "4"
  chassis = "4"


##
# Example PCIe switch with two downstream ports
#
#[device "pcie-switch-upstream-port-1"]
#  driver = "x3130-upstream"
#  bus = "ich9-pcie-port-4"
#  addr = "00.0"
#
#[device "pcie-switch-downstream-port-1-1"]
#  driver = "xio3130-downstream"
#  multifunction = "on"
#  bus = "pcie-switch-upstream-port-1"
#  addr = "00.0"
#  port = "1"
#  chassis = "5"
#
#[device "pcie-switch-downstream-port-1-2"]
#  driver = "xio3130-downstream"
#  multifunction = "on"
#  bus = "pcie-switch-upstream-port-1"
#  addr = "00.1"
#  port = "1"
#  chassis = "6"



[device "pcidmi"]
  driver = "i82801b11-bridge"
  bus = "pcie.0"
  addr = "1e.0"

[device "pci.0"]
  driver = "pci-bridge"
  bus = "pcidmi"
  addr = "1.0"
  chassis_nr = "1"

[device "pci.1"]
  driver = "pci-bridge"
  bus = "pcidmi"
  addr = "2.0"
  chassis_nr = "2"

[device "pci.2"]
  driver = "pci-bridge"
  bus = "pcidmi"
  addr = "3.0"
  chassis_nr = "3"

[device "pci.3"]
  driver = "pci-bridge"
  bus = "pcidmi"
  addr = "4.0"
  chassis_nr = "4"

In there I commented many lines (old USB related) , this to have a better and clean situation in PCI device output in app like dpcimanager or Hackintool 

My tries it is always related to acquire a perfect functionality on internal audio I miss 😉

with this emu vm config I achieve this:

1404958750_ScreenShot2020-05-16at08_44_47.png.865893bc56fb38c53ec925c7c490918f.png

 

so a bunch of EHCI and UHCI device are not loaded anymore in my system..and functionality of it seems to be the same.

From picture above you can see some stuff also passed from the pve-q35-4.0.cfg file, I mean QEMU PCI-Pci bridge.. I am trying if is possible to avoid also some of this loading.You see also other stuff (first 6 lines) it seems not present in this file..

Main task/goal could be to inject here some devices we have in our rig? We will see

 

Previous situation without commenting those lines:

1171634402_ScreenShot2020-04-14at1_39_41PM.png.ee14281b11c85901674246cb786d44fb.png.e712cb5a76b290ed6797cb908b891ba0.png

 

here less controllers passed..it is a VM I use to test so I pass few devices!

 

DO NOT DO IT IF YOU PASS USB MOUSE OR KEYBOARD OR OTHER DEVICE AS A SINGLE USB IN WEB INTERFACE

  • Like 1
  • +1 3
Link to comment
Share on other sites
Rox67er Senior Member

Rox67er

Posted
Posted
  On 5/4/2020 at 12:52 AM, Driftwood said:

Anyone tried a Radeon VII?

 

Expand  

Yes, works. I have Asrock TRX40 Creator and Radeon VII. Need to work around the GPU reset bug though. (If you stop the VM and start again the Radeon VII will not initialise, need to reboot the host)

I found a working trick with a start hookscript: (this will briefly stand-by the host before starting the VM and it works to reset the GPU)  

root@ryzen:/var/lib/vz/snippets# more reset-gpu.pl
#!/usr/bin/perl

# Hook script for PVE guests to reset AMD GPU before VM start
# qm set 100 -hookscript local:snippets/reset-gpu.pl

use strict;
use warnings;

print “HOOK: ” . join(‘ ‘, @ARGV). “\n”;

# First argument is the vmid

my $vmid = shift;

# Second argument is the phase

my $phase = shift;

if ($phase eq ‘pre-start’) {

print “HOOK: $vmid is stopped.\n”;
system(“rtcwake -m mem -s 3”);

} else {
print “HOOK: got unknown phase ‘$phase’\n”;
}

exit(0);

 

  • Like 1
Link to comment
Share on other sites
Driftwood Senior Member

Driftwood

Posted
Posted (edited)
  On 5/17/2020 at 10:12 PM, Rox67er said:

Yes, works. I have Asrock TRX40 Creator and Radeon VII. Need to work around the GPU reset bug though. (If you stop the VM and start again the Radeon VII will not initialise, need to reboot the host)

I found a working trick with a start hookscript: (this will briefly stand-by the host before starting the VM and it works to reset the GPU)  

root@ryzen:/var/lib/vz/snippets# more reset-gpu.pl
#!/usr/bin/perl

# Hook script for PVE guests to reset AMD GPU before VM start
# qm set 100 -hookscript local:snippets/reset-gpu.pl

use strict;
use warnings;

print “HOOK: ” . join(‘ ‘, @ARGV). “\n”;

# First argument is the vmid

my $vmid = shift;

# Second argument is the phase

my $phase = shift;

if ($phase eq ‘pre-start’) {

print “HOOK: $vmid is stopped.\n”;
system(“rtcwake -m mem -s 3”);

} else {
print “HOOK: got unknown phase ‘$phase’\n”;
}

exit(0);

 

Expand  

I can only 'restart' fine from macos, but 'shutdown' will cause the aforementioned bug. Where do you run that from shell console

?

 

Edited by Driftwood
answer properly
Link to comment
Share on other sites
AllubzV Junior Member

AllubzV

Posted
Posted

@fabiosun I also could now passthrough the "USB" Audio Device, due to the updated kernel patch that we were looking for before. I'm still having trouble with the actual sound, it's loud screeches / scratches / noise, nothing you'd like to listen to. Did I miss something, or are you at the same point still?

Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

@AllubzVif you read I said before

only problem I have

i think is an OS X driver problem because with same proxmox setting in a window vm it is perfect

patch is useful to pass controller but it is also possible to pass without

i have asked @pavo to insert 148c address for us (trx40 user) but as I said not useful to solve

@iGPU has a working usb Dac audio, but in my case I have no others usb to test..only cheaper ones

and these have the same problem

  • Like 1
Link to comment
Share on other sites
  • Moderators
iGPU Senior Member

iGPU

Posted
  • Moderators
Posted

Yes, I'm using the Audient EVO4 (USB DAC) without any problem.

 

I am giving up, for now, on TB. Based on what I've tried and the response from the Proxmox forum, it is not possible (at this time, as they said) to pass-through a TB device.

 

On a related issue, has anyone passed-through a BT/Wifi card (like the Fenvi) that's commonly used on Hackintosh builds? When I try, it seems to pass, but is not active on the Mac side (I've included what I believe are its associated USB devices). I know it's a good card as I pulled it from a working build. I can pass and use the on-board BT with special kext files; but the Wifi portion of the AX200, does not yet work, so not ideal for full Mac functionality. I realize that a BT card swap is possible, but BT with the AX200 is more powerful. On other Hackintoshes, I use the native BT from the mobo and supplement with Wifi from the Fenzi card for a nice combination.

 

One significant problem that's cropped up for me it a prolonged boot, but only when using a pass-through GPU. I've not been able to sort it out for over one week now. (I initially did not see this, but now occurs no matter the GPU.) The Apple progress bar hangs about 2/3 of the way (after the screen flashes off then back on) and sits there for about 90 sec, then it progresses to login. However, about half the time after login, I have no USB connection. I tried with and without the recent trimming of devices discussed here, but of no help. (I do like having the devices trimmed.) The late boot problem seems like a GPU related matter, but using WEG or not using WEG has no effect, nor does injecting or not injecting DeviceProperties.

 

 

Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

Mmmmh maybe you have to revert to a not patched kernel?

my booting time is very fast and all usb controller are on without problem 

I have opened a thread on proxmox forum for audio problem

but it is hard to explain and I do not think is a proxmox problem because with same distro config a Windows vm is working perfectly 

 

usb part of your thunderbolt is working?

  • Like 1
Link to comment
Share on other sites
  • Moderators
iGPU Senior Member

iGPU

Posted
  • Moderators
Posted (edited)
  On 5/18/2020 at 7:59 PM, fabiosun said:

Mmmmh maybe you have to revert to a not patched kernel?

my booting time is very fast and all usb controller are on without problem 

I have opened a thread on proxmox forum for audio problem

but it is hard to explain and I do not think is a proxmox problem because with same distro config a Windows vm is working perfectly 

 

usb part of your thunderbolt is working?

Expand  

 

I'm not using patched kernel; I tried PAVO's but was getting a green screen. I  am using Proxmox 6.2. I will re-check verbose mode. Thanks.

 

TB USB did pass, but was not functional. Even when passing NHI portion, TB drivers started to be loaded on the macOS side, but again, not functional.

 

***

 

After adding -v to OpenCore boot arg, the verbose portion went fast, then the Apple logo appeared and started the progress bar. The progression stopped at about 25%, with no more words appearing, then suddenly went to login screen after 60 sec or so. So this didn't help to figure out the prolonged boot problem.

 

Then after running for 10 to 15 min, it locks up. I'll try turning off WEG as lock-ups after 15 min is commonly seen on Intel platforms when running WEG and Radeon VII GPUs.

 

***

 

After testing above, I  was suspicious of AppleALC. Leaving WEG and AppleALC disabled, the progress bar no longer paused, but still took a long time to boot. Maybe an issue of newer AppleALC kext breaking something as I had updated various kexts (I'd made so many changes, it is difficult to isolate one). Newest version used  was v1.4.9.

 

This was the problem: AppleALC. Using an older version from Oct, 2019 fixed the problem (v1.4.3): boot went rapidly. I don't know when in the updates the problem started. I may test tomorrow different ones, but I'm avoiding v1.4.9 and suspicious of v1.4.8 until tested.

 

update: 5/19/20:

Re-tested to the above issue with different versions of AppleALC and now the older versions are giving the same delay. I now don't know what is going on. It is curious that sometimes changing WEG, AppleALC or DeviceProperties which inject Radeon VII SoftPowerTable data affect this prolong boot. It must be related to the GPU. Further investigation needed on my part.

 

update: 5/21/20:

the problem was erratic because the main macOS was corrupted. See this post for clarification.

Edited by iGPU
added verbose & AppleALC info
  • Ok 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.