Driftwood
-
Posts
457 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Events
Downloads
Everything posted by Driftwood
-
ASRock TRX40 Creator official 1.70 firmware - looks like it includes the 1.68 beta test we had a few weeks before this release. https://www.asrock.com/mb/AMD/TRX40 Creator/#BIOS
-
Sorry Ryzen master. Changed it. So when you guys are installing youre going through the same process as before, placing the ISO within the Proxmox for install. Have you tried installing, by booting into VM, hit f2 at Proxmox screen, insert USB Install Big Sur Boot Beta disk, select the BS boot disk (USB) in its 'BIOS',then booting from it and selecting the Install Mac OS Big Sur?
-
@fabiosun@Rox67erI am currently running the 'lower voltage' O/C settings in BIOS to achieve constant 4.0 Ghz clock speed running 51% avg on idle to 75% under regular GFX work stress. 95% still switches off the system if overstressed (think Davinci Noise reduction Temporal/Spatial noise reduction tab!) Are you saying if you run AMD Master once on Windows and the PBO stuff that you can achieve regulated clock speeds accordingly where needed inside the Mac OS VM ? or do you have to boot windows, do AMD Master, then soft reboot and go into Proxmox to keep the AMD Master settings going?
-
Is everyone using 6.2.6 Proxmox? And use Backup Server? Its been updated today.
-
Its to do with Big Sur getting Aquantia working on boot for beta 2. ASRock wont install from USB beta 2 Flash, it appears. Ive done quite a bit on the write up, but Im still fine tuning so once Im happy Ill finish it. Then theres work... Pavo did a write up some time ago on his github btw
-
Big Sur: Looks like the MSI is devoid of problems unlike the ASRock @iGPU Pavo and I are trtying to get an emulated boot going on the ASRock like hes done on his MSI. Plus, hes working on a Aquantia fix.
-
Had same problem @iGPU If you verbose you will get it hanging on screen 2.
-
Im able to restart Ok inside Mac Prox without Radeon problems. Summit to do with the latest Updates in Proxmox I guess. Also got my front side USBs working without grief to the audio. Just tried a discounted RME AIO DSPe card in the machine. No life in it though. Tried Mac, Windows, BIOS, editing PCIe lane speeds, etc... so this is DOA and Im sending it back and may have to pay for a retail priced one 😞 Determined to get it working though. If the FW card works, this should.
-
I have dual Noctua Air fans running and on Davinci Noise Reduction temporal and Spatial tests anything over +6 and +2 temporal frames running constant for 3 minutes causes cpu/gpu fault tolerance shutdowns. Definitely need to look at freezing this cpu and maybe the GPUs! Ive been trying this Big Sur install and I also am getting the inability to even 'Install MacOS Beta' from USB to a SSD. I have three kexts loading inc. the virtualSMC (I know u dont need this), latest Lilu, and AGPMInjector.kext ....and getting this:- It looks like its getting messed up over threads expecting 1 and getting 64?! or an ACPI problem.
-
My firewire/Fireface 800s are fine without crackle and pops on the main. I think if I push plugins then problems occur but its like any other system. Certainly Im running quite a few sample libraries and its fine. Im just trying to get better latency now 🙂 If you really want to test your GFX GPU forget the benchmarks. Use Davinci Resolve's temporal and spatial denoiser tabs to truly test how good they are working 🙂
-
Probably going to still use my fireface 800s in Stand-Alone mode. Im about to try out a cheap HDSPe AIO card I picked up from a dealer. It should work and give me some indication as to how much better latency in realistic circumstances I can pull off. If it goes fairly well I could be tempted for the higher spec card! I think she has been reliant on groups like this to get her stuff going! LOLz
-
It looks like it should work. Incidentally, Ive been looking at upgrading to a PCIe RME card. What is the latest and greatest? Some test here for latency. https://www.gearslutz.com/board/music-computers/618474-audio-interface-low-latency-performance-data-base.html with a massive thread going up to present day. I hope this transpires well to VMs. Cheers
-
Thanks for the tip @iGPU got the Apanage 'Renesas' USB hub today and working well.
-
Also the installer for Big Sur goes to 'Do you want to create ISO?' you say yes and then it makes a Mojave ISO!?
-
So this option seems to work for Big Sur on VM Assistant):- Download Big Sur full Installer(dp1): /Users/username/Downloads/VM_Assistant -dbs This one goes back to VM Assistant menu only /Users/username/Downloads/VM_Assistant --downloadbigsure Is it because of typo? Maybe @Gengik84 left an 'e' on the end of BigSur!?
-
Just ordered one. Thanks for the tip.
-
@fabiosun Your configs in Proxmox for Big Sur the same ? Im keen to have a go at this in readiness for Big Sur release, so any more info required to get our 3970x boards working the better. Perhaps a new guide?
-
So are you running Big Sur Proxmox and what steps with OC?
-
Nice. Did you install onto another vm using the a virtual install partition? or have you found a novel way of doing the installl? @Rox67er Did you take a look at how Dmesg is currently monitoring the USB devices? Lots of red errors on the USB stuff. Asrock mentioned to me the following in a email: "You could try another setting for Deep Sleep in BIOS > Advanced > ACPI Configuration. Or try BIOS > Advanced > AMD CBS > CPU Common Options > Power Supply Idle Control > Typical (if available)." You went through that lot though didnt you?
-
Yeah, Im kind of at the same opinion and have emailed ASRock.
-
Pretty much - yes, as in my diagram some posts back. lower one is usb2 top right usb 3
-
@Rox67er So messing with Hardware tab I can discover which ports at least are the USB 3s and which are the 2s. The two right hand side (on my case) are USB 3 and the two left are USB2. Then of course you have the other USB-C port. these cant be passed through properly especially if you have the BT pass thru via Hardware TAB in Proxmox.s So it looks like we're left with trying to find stability of the ports on 48:00.1 (1/2 rear/ 1/2 fromnt usb3) and 48:00.3 (probably front usb 2). Have you found out which address is front USB-C port yet?
-
you will be surprised.. if you do want a "definitive" job in this task..try to put on each usb an usb pen 3 and an usb 2 pen..and see how system detects it (if) Probably will be! Guess we can always use Proxmox Hardware tab to learn of every device specific address you plug in and then just pass it.. like the BT problem was overcome this way! @fabiosun did u try passing from Proxmox Hardware tab the HD audio address (maybe Linux detects its as pulse audio) ?
-
@iGPU Yes, but our ASRocks are different layout as @fabiosun has just mentioned. 48:00.1 is rear panel (2 USB ports) a BT power, and LED connectors. 48:00.3 is probably the four front panel USBs and definitely HD Audio! There is a also a front side USB-C which could be attributed to this controller... or the ASMedia. We have a ASMedia USB-C connector on the back (last port in my layout picture posted a few days back) at definitely 44:00! The fun of these mobo layout designs! 🙂 I am currently going through all the ASRock board ports to identify front panel USB and revise my mobo layout diagram.
-
@iGPU Interesting discoveries.... On mine, 48:00.3 is HDaudio (that weird USB one). 48:00.1 is rear USB, BT and LED functions. Im not sure if 48:00.3 is perhaps USB front panel also? (anyone tried?) Broadcom Wifi works out of the box without doing anything as its Apple supported. I'm passing all the other USB controllers without problems. I've turned passthru off again and just used @Rox67er method of passing BT using Proxmox 'Add USB Device' on the 'Hardware' section of the VM, and now no glitches. And that's a strange address for BT isnt it @Rox67er!!!?!!!
