Jump to content

Rocket88

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by Rocket88

  1. 3 hours ago, fabiosun said:

    Problem we have also in Proxmox

     

    For people using internal Realtek audio

    try to connect a speaker jack on green backplate output 

    Do a cold boot

    See if you see your Realtek 2.0 device
    then disconnect this jack reboot (cold boot is better) and see

     

    this is unsolved problem for MSI board (or config problem) with trx40 Pro 10 g and MSI creator (@pavo tested this for me )

    Gigabyte and Asus users could do this test?

    thank you

    Asrock TRX40 Creator: I have the same problem. The only way I have been able to get audio, so far, is to use a Sabrent USB audio jack. (This was the same issue that I used to have with my x99 Intel hack).

  2. Hi Ploddles, 

     

    I had the same issue. I had a bluetooth keyboard laying around and I was able to connect with it. This is with the built in Asrock Creator Bluetooth chip and your EFI. I could not make the mouse work, so I moved my mouse to a different USB port and that worked. I managed to install Catalina 10.15.6 with your EFI, modified with my serial number and MacPro7,1 and by downloading Catalina to my USB thumb drive with the following command:  sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

     

    I am currently in the process of doing the same thing with Big Sur.

     

    Note: Bluetooth only worked for me that first time when my Hack could not find a keyboard. 

  3. My Build is Asrock TRX40 Creator, MSI Vega 64. I have had no problems with random reboots. I tried installing a program called Camo Studio that would allow me to use my iPhone camera on my Hack. It did not work. If fact it would not even come up. I have not had any other issues with other programs. iMessage works for me. It did not work with Proxmox.

    I don't use any graphics programs, so I can't say if they work. All in all, I am pretty happy with bare metal. I will probably try Big Sur this weekend.

  4. My board is the Asrock TRX40 Creator. I used EFI-v061-08-09-20-BareMetal-public that was posted on this website and set ncpi=0x2000. I also set CSM off and 4G enabled.  IT WORKS !!!!! I can boot like a real Mac. Most everything that I care about works. I have sound running with a Sabrent USB dongle. I have not tried directly yet. Even iMessage works. Things that don't work for me are sleep, bluetooth, WiFi.  My hack seems to be running quieter also, I think. I have activity monitor running and it appears to be loafing. At idle, only 3 cores have any bars. All of my USB ports appear to be working, unlike with Proxmox.  I am absolutely impressed. Thanks guys!!!!!!

    Screen Shot 2020-08-12 at 8.26.20 PM.png

    Screen Shot 2020-08-12 at 8.15.59 PM.png

    Screen Shot 2020-08-12 at 8.21.40 PM.png

    • Like 2
  5. Watercooler: I picked the Thermaltake Floe Riing 360 TR4 because it had the large TR4 surface area and the fans looked pretty cool. This device is heavily flawed though. If you wire it like the drawings show, it will only cool decently when you are running  Windows. The software is horrible. The hardware does not remember any fan settings like a Corsair model. It is expensive. I paid $250 U.S.

     

    If you go with this unit, you will need to rewire the fans to have the motherboard control them. Also you need to make sure that the motherboard is pumping the unit at 100%. Under Proxmox, you will not be able to change the fan colors without performing some sort of rewiring. I did not bother. Mine defaults to spinning colors and that is good enough for me.

  6. 9 minutes ago, Rox67er said:

    Which video card do you use? Do you load lilu.kext and whatevergreen.kext in OpenCore? Should solve most HDMI / Displayport output issues.

     

    I am using a single MSI Vega64 card in the first slot. I have lilu.kext and whatevergreen.kext installed and I am running OpenCore 0.58

    I had to add this line to grub to make the video pass thru:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt amd_iommu=on video=efifb:off"

     

    To start my VM, I either need another computer or I set onboot: 1 in my 100.conf file

    • +1 1
  7. 21 hours ago, Rox67er said:

    I checked running Proxmox disk on the USB-C port and passing the 47:00.1 and 47:00.3 USB Controllers. (As long as I block bluetooth / wifi MacOs works fine, as soon as I try to load the intelUSB kext my Aquantia controller gets messed up. My wifi/BT upgrade has not arrived yet...)

     

    However, in this config I can only boot the VM once. If I shut down and then start the VM again, it locks up with the 99 error on the motherboard. It may be related to older AGESA / BIOS since we are still on 1.0.0.3 B if I understand correctly, Fabiosun has been on 1.0.0.3 C and is now on 1.0.0.4.

     

    Could also be the reset bug for the Radeon VII.

    I am getting the 99 error on my Asrock TRX40 Creator also. I thought it was just me. I get this error approximately every 3rd time I power up. This includes booting with Windows by hitting F11 on startup. To make the error go away, I have to unplug (or power off) the power supply, start the computer, which drains the capacitors, plug in the power supply, and then start again. Everything works great after that. The other issue that I can't seem to solve is Proxmox will only start on HDMI, not DisplayPort.  

  8. 13 hours ago, iGPU said:

    In follow up, I transferred the 3970X to a new MSI Creator. Things looked really good (although, this is my first MSI product and BIOS rather different than ASUS and GB and ASRock). But after 30 min, the same error codes began. Exact same error codes and then it crashed.

     

    So I have a bad CPU. Interestingly, it started out okay, but then gradually got worse and worse. Fortunately, I had 3 days left to do an exchange, so I'll get a replacement 3970X next week.

     

    I am wondering if you have a heat problem with your CPU. My cooler is the Thermaltake Floe Riing 360 TR4, which has issues, especially if you are not running windows. Their software that controls fan speed only runs when Windows is running (and not REAL TIME). You can tell if this is the issue if the FAN speed stays constant. You should hear the FAN speed going up and down as you do different things. My solution was to rewire the fans so that the motherboard controls the fan speed. I still used the Thermaltake controller for powering the  LEDs and for visualizing the fan speed when running windows. BE SURE TO CUT THE BLUE WIRE (PWM) GOING TO THE CONTROLLER!!!! 

    We want the motherboard to control the PWM signal. I apologize for my very rough drawings.

     

    Floe Connector.png

    Floe Wiring.png

    • Like 1
  9. 12 hours ago, Driftwood said:

    @Rocket88

     

    Can you give me EXACT installation details below. Is cron part of Proxmox Debian? Do we need to install anything with 'Get' . Please type out exact method to install and how to copy it to snippets, when I run 'Crontab -e ' I get an editor, where do I go from there?

     

    Sorry Im a Linux noob!

     

    Simple directions (hopefully) for installing the shutdown program.
    1. Create the directory /var/lib/vz/snippets
       This is done by typing mkdir /var/lib/vz/snippets
    2. Unzip shutdown.out.zip.
    3. Copy shutdown.out to /var/lib/vz/snippets
       Use Filezilla to do this. See previous posts on Filezilla.
    4. Type:  crontab -e
    At the bottom of the file that appears, add this line:
    @reboot /var/lib/vz/snippets/shutdown.out &

    Be sure to hit return after this line.

    Save your work by typing CNTL-X. and Y

    5. Reboot your machine.

    6. After you verify shutdown works, add the following line to your 100.conf file so that 
    the computer will start your VM on power up (after about 1.5 minutes from power up)
    onboot: 1

     

    Good luck!

     

     

     

  10. I finally got "Shut Down ..." to power down the hardware. I wrote a program to poll the Virtual Machines and if nothing is running, a shutdown command is generated.

    Included is the source file and the executable (shutdown.out) which uses cron on power up and runs until Shut Down... is selected in the menu bar. 

     

    /* #########################################################################

    # shutdown.c

    # Powers down your Hackintosh when "Shut Down..." is selected.

    #

    # 1. Put this program (shutdown.out) in "/var/lib/vz/snippets"

    # 2. Set cron to run the shutdown program by typing:

    #

    #  crontab -e           <<<<<<<<< This is used to edit cron jobs

    #

    #  @reboot /var/lib/vz/snippets/shutdown.out &        <<<<<<<<<<< shutdown.out will start on power up

    #

    #

    #  --------------------------------------------------------------------------------

    #  To build this executable, type gcc shutdown.c, then rename a.out to shutdown.out

    #      (Don't forget to copy shutdown.out to /var/lib/vz/snippets)

    #

    #  Version 1.00000000    Rocket88   5/25/2020

    #

    #############################################################################

    */

    shutdown.c.zip shutdown.out.zip

    • Like 2
    • +1 1
  11. After a week of messing around, I finally got my Threadripper 3970x, TRX40 Creator, MSI Radeon Vega 64 to work. I only have one video card.

    Here are the changes I had to make:

    /etc/default/grub:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on textonly video=amdgpu video=efifb:off"    <<< I need efifb:off or I get the BAR 0 error.

    *** Note: My monitor will not show anything past the Ramdisk message with video=efifb:off" set

     

    /etc/modprob.d/vlio:

    # Make vfio-pci a pre-dependency of the usual video modules
    softdep amdgpu pre: vfio-pci           <<< Not sure if this is still needed


    options vfio-pci ids=1002:687f,1002:aaf8 disable_vga=1
    options kvm_amd avic=1                <<< Not sure if this is still needed

     

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

    hostpci0: 03:00,pcie=1,x-vga=on,romfile=MSI.RXVega64.8176.170719.rom    <<< romfile goes in   /usr/share/kvm/

    *** Set the boot flag. Without the boot flag set, the display hangs up after the Ramdisk message.

     

    I also made the following BIOS changes, and I have not checked yet to see if they are still needed:

     

    1.     SR-IOV Support. 

    2.     In bios under Advanced\AMD CBS\NBIO Common Options

       a.     Enable AER Cap

       b.     Enable ACS Enable.  (not visible until a. is done)

       c.      Turn on ARI

     

     

    Now when I power up the machine, It jumps to the PROXMOX screen, then I can click on the icon of my MacOS, and then I can boot up my new AMD Macintosh. 

    Things I need to do:

    1. Create a hook script for powering down my hardware. For example something that periodically checks to see if the vm is running and if not, send "shutdown -h now" command. 

    2. Everything else. I have days (weeks) of tinkering to do.

     

    Once again I would like to thank all of you for your posts!!!!

     

     

    • Like 1
  12. Thank you for all of your efforts. I am in the process of getting my AMD 3970x, Asrock TRX40 Creator, MSI Vega 64 running correctly. Currently I am using Opencore 0.57. It works on my 2013 iMac remotely, but GPU pass thru does not work and my pass thru monitor goes blank. It never goes to the login screen. There is much for me to try. 

    For transferring files, I have found that FileZilla works great. You can FTP between your Host and guest computers.

    https://filezilla-project.org/

    • Like 1
  13. Hello MacOS86.it

     

    I am also in the preliminary stages of my next Hackintosh. I am trying to verify that I can bring up Proxmox 6.1 / Catalina on an 2013 27" iMac. I picked this machine because it was sitting around. Proxmox loads just fine, but I have not been able to get my Virtual Machine to boot just yet. Once I get this working, I will order the parts for my 3970x Hackintosh.  

     

    My current Hackintosh is an i7-6950x / Gigabyte GA-X99 Designare EX that has been running since 2016. 

     

    I would like to thank fabiosun for all of his hard work. I have been following him for months now.

    • Like 1
    • +1 1
×
×
  • 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.