Jump to content

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
meina222 Senior Member

meina222

Posted
Posted
56 minutes ago, iGPU said:

 

As for BT/Wifi, I never got a PCIe card to work. I eventually swapped out the built-in card for macOS compatible card.

I almost gave up on the PCIe card as I couldn't figure how to get rid of the built-in one. Setting sudo nvram bluetoothHostControllerSwitchBehavior="never". and clearing the files containg "Bluetooth" in ~/Library/Preferences/ByHost  /Library/Preferences  to get rid of MacOS cached stuff did the trick for me. The command above disables the AX200 and allows for the PCIE to load. My AX200 was covered by a shroud and I didn't want to try and unscrew the board to remove it, but luckily above worked. Nothing else would work if you can't disable the AX200 in BIOS.

Link to comment
Share on other sites
tsongz Member

tsongz

Posted
Posted
11 minutes ago, meina222 said:

Setting sudo nvram bluetoothHostControllerSwitchBehavior="never". and clearing the files containg "Bluetooth" in ~/Library/Preferences/ByHost  /Library/Preferences  to get rid of MacOS cached stuff did the trick for me.

 

That's what I was missing - the second part of that. I had ran the previous command along with resetting nvram, but AX200 kept showing up. Despite that though, my BT worked and in System Preferences had Broadcom showing, while Hackintool showed AX200 still present. Tested it connecting to my AirPods successfully, but WiFi wasn't working. (while still having VMXNet port)

Link to comment
Share on other sites
meina222 Senior Member

meina222

Posted
Posted (edited)

You may also need to clear the network preferences plists. Don't recall which ones - google them. Wireless should work - this was the less problematic part for me.

 

Maybe try this https://apple.stackexchange.com/questions/284581/wipe-all-wifi-settings-from-macbook

 

It's OK for Hackintool to show AX200. You didn't unplug it. But MacOS should not load the BT driver for it. If you really want it fully removed you either can try BIOS or if not possible there (in my Designare that option doesn't exist) you can remove it out of its slot, but I'd leave it.

Edited by meina222
Link to comment
Share on other sites
meina222 Senior Member

meina222

Posted
Posted

Just upgraded to Big Sur Beta 4. Took really long. It succeeded and booted successfully, but MacOS setup assistant failed miserably. The whole thing is not very smooth still. Also my EFI is still saying 'Preboot' even though install seems to have finished. Once I login things work. Unlike BS beta 3 where I had to reinstall from scratch. So far setup assistant never succeeded for me.

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

iGPU

Posted
  • Moderators
Posted (edited)
6 hours ago, meina222 said:

I almost gave up on the PCIe card as I couldn't figure how to get rid of the built-in one. Setting sudo nvram bluetoothHostControllerSwitchBehavior="never". and clearing the files containg "Bluetooth" in ~/Library/Preferences/ByHost  /Library/Preferences  to get rid of MacOS cached stuff did the trick for me. The command above disables the AX200 and allows for the PCIE to load. My AX200 was covered by a shroud and I didn't want to try and unscrew the board to remove it, but luckily above worked. Nothing else would work if you can't disable the AX200 in BIOS.

 

I removed shrouds on TRX40 Designare and MSI mobos, but I did before assembly: not difficult, just a few screws. Once mobo is inside a case, it's a lot more work.

 

If you only want to disable BT, you can cut the power to the AX200. In fact, when I was using special kexts (early in this thread), I had to specifically pass USB power to get the AX200 working (that earlier post references the TRX40 Designare mobo if you look it up). BT from the AX200 worked really well; I think it had greater range than the macOS compatible pcb. But at the time there was no WiFi; I think the hackers have got that working now (but I haven't kept up with their progress).

 

On my current MSI mobo, the USB power is 0489:e07a, which comes from 48.00,3. When I look inside IORegistryExplorer, the swapped BT/Wifi card is appearing under AMD Matisse USB 3 (149c) at address 10,5. (On the Intel side, native BT/Wifi cards are inactivated with SSDT files; this might be another approach.)

 

*** UPDATE

 

I worked on an SSDT that will inactive BT/WiFi. You just have to determine the device address using IORegistryExplorer (IORE) and adjust the address inside the SSDT. Simple. To use, complete the address check described below and adjust the address inside the file SSDT-NoAX200.aml, enable the file in OpenCore and reboot. (To restore function: disable the SSDT in OpenCore and reboot.)

 

First the normal IORE. Locate the address where you find the BT/WiFi card under a USB device. (I've used another SSDT to rename addresses to RP0x.)

1198751101_ScreenShot2020-08-04at10_38_40PM.png.817cbb2872ed256af2b1663a0097d2a5.png

 

 

Next, adjust the SSDT so that its address matches your address in IORE from above step:

1640175981_ScreenShot2020-08-04at10_51_14PM.png.1cece52c9bfb5aad94423ba07fb974c6.png

 

 

Now to show how it works... the above device @10,5 gets collapsed.

1466780689_ScreenShot2020-08-04at10_24_56PM.png.17606dc4765ba1d25f4154a63bff3b35.png

 

 

Normal:

371363112_ScreenShot2020-08-04at10_40_40PM.png.d90f1fed3e501bdcdb7564853be311e0.png

 

Inactivated: no BT.

1889301700_ScreenShot2020-08-04at10_25_24PM.png.632bedb5fccdf6fe3f0fed1e5a59917d.png

 

Hackintool, normal:

1416385590_ScreenShot2020-08-04at10_43_41PM.png.6a23df2435596c66ecf064fa46e5e0b8.png

 

Hackintool after inactivation (the actual BT/WiFi card still shows up; but has no power):

853262718_ScreenShot2020-08-04at10_31_24PM.png.e3cc44c70473d266eb6946cbe03e3c0d.png

 

Hackintool after inactivation (BT entry is gone):

428291094_ScreenShot2020-08-04at10_26_07PM.png.c5b83a9fb2d63300910df8760fda9427.png

 

 

 

SSDT-NoAX200.aml.zip

Edited by iGPU
Added SSDT.
  • +1 1
Link to comment
Share on other sites
tsongz Member

tsongz

Posted
Posted

So I'm currently a little stuck. I can't seem to get WiFi working on the card, however, Bluetooth works, and I have my ethernet at en0, with internet connection.

 

I've tested several arrangements of the hostpci slot settings, having 'built-in' enabled in config.plist - tested it with all the different combinations of USB slots (which I believe only affects Bluetooth, not WiFi), have tested with kexts and without kexts and nothing's getting it to show up. 

 

Currently using the BCM4360 PCIe card in 01:00.0

 

Shows the Bluetooth being picked up from the card

image.png.4d9700c23ff05554472a8a9288e53884.png

 

Has WiFi information?

image.png.91a6205570e88a211199473b771302c3.png

 

Confirms Broadcom

image.png.7a2b62bb460ef3ad5e8420342f56504f.png

 

Confirming Device Path in Hackintool

image.png.867da101d615a7d52aec054107a44a52.png

 

Have tested with and without Kexts

image.png.cba7bf508ec689b488f9c572c56e818e.png

 

101.conf

  

hostpci0: 4b:00.0
hostpci1: 44:00.0,pcie=1
hostpci2: 43:00.0,pcie=1
hostpci3: 47:00.0,pcie=1
hostpci4: 47:00.3,pcie=1
hostpci5: 01:00.0,pcie=1

 

blacklist.conf

  

blacklist snd_hda_codec_hdmi
blacklist snd_hda_intel
blacklist snd_hda_codec
blacklist snd_hda_core
blacklist btusb
blacklist snd-usb-audio
blacklist bcma
blacklist xhci_hcd

 

vfio.conf 

options vfio-pci ids=1002:6863,1002:aaf8 disable_vga=1
# 47:00.1, 47:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
options vfio-pci ids=1022:149c
# 43:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242]
options vfio-pci ids=1b21:3242


# 4a:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1a8] (rev 03)
options vfio-pci ids=8086:f1a8



# 4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
#        Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
options vfio-pci ids=1987:5012



# 01:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
#        Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter [106b:0111]
#        Kernel driver in use: bcma-pci-bridge
#        Kernel modules: bcma
options vfio-pci ids=14e4:43a0



# 44:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
options vfio-pci ids=1d6a:07b1
# 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
options vfio-pci ids=1022:7901

 

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

iGPU

Posted
  • Moderators
Posted
9 minutes ago, tsongz said:

So I'm currently a little stuck. I can't seem to get WiFi working on the card, however, Bluetooth works, and I have my ethernet at en0, with internet connection.

 

I've tested several arrangements of the hostpci slot settings, having 'built-in' enabled in config.plist - tested it with all the different combinations of USB slots (which I believe only affects Bluetooth, not WiFi), have tested with kexts and without kexts and nothing's getting it to show up. 

 

Currently using the BCM4360 PCIe card in 01:00.0

 

Shows the Bluetooth being picked up from the card

image.png.4d9700c23ff05554472a8a9288e53884.png

 

Has WiFi information?

image.png.91a6205570e88a211199473b771302c3.png

 

Confirms Broadcom

image.png.7a2b62bb460ef3ad5e8420342f56504f.png

 

Confirming Device Path in Hackintool

image.png.867da101d615a7d52aec054107a44a52.png

 

Have tested with and without Kexts

image.png.cba7bf508ec689b488f9c572c56e818e.png

 

101.conf

  


hostpci0: 4b:00.0
hostpci1: 44:00.0,pcie=1
hostpci2: 43:00.0,pcie=1
hostpci3: 47:00.0,pcie=1
hostpci4: 47:00.3,pcie=1
hostpci5: 01:00.0,pcie=1

 

blacklist.conf

  


blacklist snd_hda_codec_hdmi
blacklist snd_hda_intel
blacklist snd_hda_codec
blacklist snd_hda_core
blacklist btusb
blacklist snd-usb-audio
blacklist bcma
blacklist xhci_hcd

 

vfio.conf 


options vfio-pci ids=1002:6863,1002:aaf8 disable_vga=1
# 47:00.1, 47:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
options vfio-pci ids=1022:149c
# 43:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242]
options vfio-pci ids=1b21:3242


# 4a:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1a8] (rev 03)
options vfio-pci ids=8086:f1a8



# 4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
#        Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
options vfio-pci ids=1987:5012



# 01:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
#        Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter [106b:0111]
#        Kernel driver in use: bcma-pci-bridge
#        Kernel modules: bcma
options vfio-pci ids=14e4:43a0



# 44:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
options vfio-pci ids=1d6a:07b1
# 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
options vfio-pci ids=1022:7901

 

 

 

Usually BT is the trickier of the two to get working. What may be happening is related to a pci-bridge problem like the TB AIC that isn't allowing the WiFi portion to work (or maybe you have interference from the built-in WiFi)?

 

Can you show us the results of lspci -nnk ?

 

While it may not have a major effect, I would comment out all blacklisted entries (then run update-initramfs -u -k all and reboot).

 

I'd also remove/disable some of the kext files:

kexts.png.909c2c38ff61828c2e3bc14f8d98f4d8.png

 

 

Finally, what are your entries for System Info / Network?

256358609_ScreenShot2020-08-04at11_22_28PM.png.482ce49b7eea3b4935fdffeb38c6f93a.png

 

 

 

Link to comment
Share on other sites
tsongz Member

tsongz

Posted
Posted

@iGPU 

 

Currently:

 

image.png.282f67311675edc03fc2769e7a62339c.png

image.png.b4037e4b3de219d16267baef23af8efe.png

 

Adding my lspci while I make the changes you suggested.

  

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: ASRock Incorporation Starship/Matisse Root Complex [1849:1480]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
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
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
        Subsystem: ASRock Incorporation FCH LPC Bridge [1849:ffff]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 [1022:1490]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 [1022:1491]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 [1022:1492]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 [1022:1493]
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 [1022:1494]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 [1022:1495]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 [1022:1496]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 [1022:1497]
01:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
        Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter [106b:0111]
        Kernel driver in use: vfio-pci
        Kernel modules: bcma
02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Kernel driver in use: vfio-pci
03: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
20:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
20:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
20:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
20:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
21:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Kernel driver in use: vfio-pci
22:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
        Kernel driver in use: ccp
        Kernel modules: ccp
22: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
22: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
40:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
40:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
40:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
40:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
40:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
40:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
40:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
40:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
41:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57ad]
        Kernel driver in use: pcieport
42:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
42:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
42:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
43:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242]
        Subsystem: ASMedia Technology Inc. Device [1b21:3242]
        Kernel driver in use: vfio-pci
44: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: vfio-pci
        Kernel modules: atlantic
45:00.0 Network controller [0280]: Intel Corporation Device [8086:2723] (rev 1a)
        Subsystem: Intel Corporation Device [8086:0084]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
46:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:8125] (rev 01)
        Subsystem: ASRock Incorporation Device [1849:8125]
        Kernel driver in use: r8169
        Kernel modules: r8169
47:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Kernel driver in use: vfio-pci
47: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: vfio-pci
47: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: vfio-pci
48: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
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 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1a8] (rev 03)
        Subsystem: Intel Corporation Device [8086:390d]
        Kernel driver in use: nvme
4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
        Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
        Kernel driver in use: vfio-pci
4c:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:1470]
        Kernel driver in use: pcieport
4d:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:1471]
        Kernel driver in use: pcieport
4e:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition] [1002:6863]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition] [1002:6b76]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
4e:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] [1002:aaf8]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] [1002:aaf8]
        Kernel modules: snd_hda_intel
4f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
50:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Kernel driver in use: vfio-pci
60:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
60:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
60:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
60:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Kernel driver in use: vfio-pci

 

Link to comment
Share on other sites
tsongz Member

tsongz

Posted
Posted

Also another note that may shine some insight. On the host, whenever the VM is started, it logs this error: 

pcieport 0000:00:01.1: AER PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

pcieport 0000:00:01.1: AER device [1022:1483] error status/mask=001000000/04400000

pcieport 0000:00:01.1: AER [02] UnSupReq     (First)

pcieport 0000:00:01.1: AER TLP Header: 34000000 010000010 000000000 883c883c

 

*not exactly confident on the 0's - typing this from an image

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

fabiosun

Posted
  • Author
  • Supervisor
Posted

@tsongzin these preliminary steps of your learning curve, I will suggest to understand well which  parameters in vfio.conf and in blacklist.conf inhibit your system to a proper use of shell in host

During tests, adding cards or moving it or only change some parameters in vm could produce problem to access to host from other pc

So our safe (without reinstalling all or unmounting/mounting spare gfx card is the chance to be able to modify things via shell

 

another matter for me is to understand why you block all that stuff and what kind of advantages you get from this type of configuration, with you I mean most of you who in part followed my guide 🙂

  • Like 1
Link to comment
Share on other sites
tsongz Member

tsongz

Posted
Posted

You have a very valid point, and I think that discussion is more meta and observing how most of us (at least in my own experiences) got here, and what we were told to do when first starting out, before we got here. When it came to PCIe passthrough with VFIO, it was very much - "make sure you blacklist things" as common knowledge (esp with GPUs), and more often than not, it worked. It was the most heavily emphasized 'fact' in regards to this. Most topics won't ever suggest "not unblacklisting" as a solution, and if so it's very rare.

 

So since it's the first things we learned, it's most likely an 'intuitive' thing to do. For example in earlier discussions around getting this specific BT/WiFi card to work, it was mentioned to blacklist the drivers. Then as it works, it tends to accumulate more than it gets removed. Currently, I don't have anything blacklisted. 

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

fabiosun

Posted
  • Author
  • Supervisor
Posted

687842829_Schermata2020-08-05alle11_53_27.png.9a0d270f504a96b9ce5535c9cf256d85.png

 

Beta 4 is here.

I have also installed Nvidia driver (patched) to have dual display and a minimal functionality on display graphics as I have had in Mojave or in Catalina

 

Installation notes

Same open core 060 latest release debug version with all kext and drivers updated

During first installation step I have used old Penryn args for VM config

 

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

meina222

Posted
Posted

@tsongz - can you check that wireless of broadcom is working in say Windows if you have one? Just to rule out some card issue. Wireless "should just work". The other step would be to check the IOMMU trees as @iGPU suggested. Let me know how it goes - I was hoping it would be more painless when I recommended that card, but it was BT indeed that was a pain for me.

 

Installed 5.8 + Beta 4 last night. All good. I rebuilt the pve-kernel image with proper ZFS patch - will post that on github over the weekend. Means I feel a bit safer to use patched official release of ZFS that only addressed the 5.8 incompatibility.

 

I was hoping 5.8 would fix sleep issues, where my host would fail to sleep with systemctl suspend or rtcwake -m mem. I doubt it's a Linux issue. I think Designare TRX40 has some BIOS issues that prevent proper sleep support. The AE_ALREADY_EXISTS messages at boot also didn't disappear. Gigabyte hasn't updated their BIOS since early March, but they rolled out a rev. 1.1 of their TRX40 boards with new BIOS.

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

iGPU

Posted
  • Moderators
Posted (edited)
7 hours ago, tsongz said:

After removing commenting out blacklist items, disabling kexts, full system reboot

image.png.10ce0c90cfe6cba7fe7140f354b18cb2.png

  

 

Do you have another Hackintosh to verify that the card works? Based on what I'm seeing, the PCIe holder is probably ok, but perhaps the actual Broadcom PCB is bad. I've read about bad Broadcom PCBs on other threads.

 

You could try adding this code to DeviceProperties in OpenCore (changing first line to the address you find in Hackintool):

Spoiler 

<key>PciRoot(0x1)/Pci(0x10,0x1)/Pci(0x0,0x0)</key>
	<dict>
	<key>AAPL,slot-name</key>
	<string>Built in</string>
	<key>built-in</key>
	<data>
	AA==
	</data>
	<key>device_type</key>
	<string>Network Controller</string>
	<key>model</key>
	<string>BCM4352 802.11ac Network Adapter</string>
	<key>name</key>
	<string>Broadcom BCM4352 BT / Wifi Adapter</string>
</dict>

 

 

 

Finally, did you try adding brcmfx-driver=2 to OpenCore boot argument? It might help.

 

 

Edited by iGPU
brcmfx-driver=2
Link to comment
Share on other sites
  • Supervisor
fabiosun Senior Member

fabiosun

Posted
  • Author
  • Supervisor
Posted

@all

I am trying to revert to old kernel version because I have seen a sort of instability I am not able to debug

Yesterday I have had a perfect day working with @meina222 compiled 5.8 kernel

today I have installed Big Sur beta 4 in a ssd disk I connect on an external data box

after that my high Sierra became unstable 

no clue if there is a relation

 

for now I can't reverse old kernel with method I use

the very weird thing is that in Catalina and in big Sur I have no problem

in High Sierra my 2 ten TB drive (exfat) are seen after some minutes..and some times system reboots itself

 

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

iGPU

Posted
  • Moderators
Posted
1 minute ago, fabiosun said:

@all

I am trying to revert to old kernel version because I have seen a sort of instability I am not able to debug

Yesterday I have had a perfect day working with @meina222 compiled 5.8 kernel

today I have installed Big Sur beta 4 in a ssd disk I connect on an external data box

after that my high Sierra became unstable 

no clue if there is a relation

 

for now I can't reverse old kernel with method I use

the very weird thing is that in Catalina and in big Sur I have no problem

in High Sierra my 2 ten TB drive (exfat) are seen after some minutes..and some times system reboots itself

 

 

So far, the 5.8 kernel seems stable on my set up. I've now left computer running for 24 hours with a couple of re-boots (to test the BT "SSDT-NoAX200" discussed above): no problems.

 

I'm still on BS ß2 as ß3 was unstable for me. (I may install ß4 on another drive this weekend; work keeps getting in the way. 😉)

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

fabiosun

Posted
  • Author
  • Supervisor
Posted

maybe I mess my high Sierra disk in some way..I am now on 5.7.8 and I have not weird instant reboot

 

I will try again to start with latest kernel because I know probably is a my own problem 🙂

by the way..I have never seen instant reboot in this rig..today about five times..only surfing with safari 🙂

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

meina222

Posted
Posted

@fabiosun

 

apt purge -y [kernel-to-remove] should work. You need to make sure you boot into a different kernel by enabling some timeout in grub so you can select advanced options. Let me spend some time on 5.8 before I can recommend it. It's a bit dangerous as Proxmox is not certified with it. I don't have any critical data connected to it.

Link to comment
Share on other sites
meina222 Senior Member

meina222

Posted
Posted

For the record - the AMD reset bug is still pretty much there in 5.8 - as expected. That sleep issue is preventing me from using the rtcwake trick though. I am starting to think how to engege Gigabyte support as my Ryzen 3700X X570-I sleeps fine with Ubuntu on 5.8

Link to comment
Share on other sites
mclarenf1 Junior Member

mclarenf1

Posted
Posted

I have followed the tutorial but when I launch the VM it just hangs on the Apple logo.  Then after a long while it says 'no VNC'.  I suspect the hanging on the Apple logo without installing OS X is the real issue.  Any ideas?  Thanks!!!

Link to comment
Share on other sites
meina222 Senior Member

meina222

Posted
Posted (edited)

Mine shows. How did you apply it to begin with? And did you try to remove it afterwards?

 

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@designare:~# pve-efiboot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
5.4.44-1-pve
5.4.44-2-pve
5.8.0-1-zen2
root@designare:~# 

 

 

I'd remove by:

 

1. Select lower kernel at boot

2. list existing edge kernels

 

dpkg --list| grep 'pve-edge*'

 

3. apt purge -y [the kernel you want from lust in 2]

 

e.g. in my case

 

pve-edge-kernel-5.8.0-1-zen2

 

Check that the headers are also removed:

 

Run 2. again. If you see pve-edge-headers-5.8.0-1-zen2  remove it with apt purge

 

Edited by meina222
  • Like 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.