Jump to content

meina222

Donator
  • Posts

    449
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by meina222

  1. @Ploddles - you won't be the only one waiting, mate. I can't afford to spend any time on this before the weekend - I am sure going from like 11.1 to 11.4 and from OC 6.3 to 6.8 on a different BIOS (due to resizeBAR) will take me longer than installing the new beta itself.
  2. @Ploddles - what version of OC are you using? Do you mind sharing your latest config plist so I can diff with mine as I have not touched the Hack in months due to selling my 5700XT. Time to try rebooting this project with the 6900XT.
  3. Good I kept my 6900XT. Time to move it from my mini ITX back into the Threadripper but before that I need to catch up with all the MMIO BIOS changes and OC updates. Does anyone know if Big Sur 11.4 requires version of OC later than 6.3? I think that's when I stopped updating it.
  4. Finally got a chance to retest the 3090 FE (single GPU as I don't have studio but used free version 17.1). 66 Blur nodes - 27-28fps 6 TRN nodes - 31-32 fps.
  5. @jncasey I have not checked the MMIO map, but I am 100% it did as my PCI id's changed and I upgraded from a non-standard BIOS f4h, which had already different maps compared to f4c and f4l. Also f4p is coming with its own annoying issues such as increased boot time (cycling longer through codes, especially the dreaded 9A about which there is a thread on the Gigabyte forum) and also I use Proxmox - now when rebooting the host after a VM that owned a USB controller shuts, the board gets stuck on 9A and refuses to post back (reset would not work, one needs to shut off power to get that USB to initialize). I raised an issue to Gigabyte. For many, this 9A code became a no-post issue even w/out Proxmox based on the feedback on the Gigabyte board. Resize BAR is not enabled on the 3090s as far as I can tell. This, however, is more likely NVIDIA's fault - they do not list TRX40 and Threadripper Castle Peak as being added to Resizable Bar support - seems the driver itself has to support this. https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/#:~:text=New+GeForce+RTX+graphics+cards,graphics+cards+starting+in+March.?ncid=afm-chs-44270&ranMID=44270&ranEAID=TnL5HPStwNw&ranSiteID=TnL5HPStwNw-14DiO6CW5Ks.pbuyh7AETA In short: I would not upgrade to f4p and I am considering rolling back to f4h (depending on what Gigabyte says - I don't have much faith in them releasing a quick fix, their BIOS development is terribly slow).
  6. Despite enabling above 4G and Resize BAR to Auto, nVidia control panel still claims Resizable BAR is a 'No' . So did Gigabyte really enable anything? p.s. Looks the fault maybe Nvidia's https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/#:~:text=New+GeForce+RTX+graphics+cards,graphics+cards+starting+in+March.?ncid=afm-chs-44270&ranMID=44270&ranEAID=TnL5HPStwNw&ranSiteID=TnL5HPStwNw-14DiO6CW5Ks.pbuyh7AETA Why not include support for Threadripper and TRX40?
  7. 😞 24fps using 66 blur nodes. However I noticed my 2nd GPU was only 5% core usage and when I tried to enable 2, it told me I am being too cheap.
  8. Ultimately I managed to finish the install by passing the target nvme to my Windows VM and running the initial install from the installer iso from there, then finishing on the bare metal itself. What a mess. @fabiosun Yes, I decided to keep the 2 3090 FE cards I got a few weeks back at MSRP. Was debating re-selling one or both, but decided to do some GPU compute learning. Set them up in SLI (not sure if that helps with any apps), but took me a while to install them as I didn't want any water cooling and struggled to find a case to run them in Slot 2 and 4 (settled on a BeQuiet 900 Pro in inverted layout and some minor mods - picture is upside down for some reason). I wanted to keep my x16 slot free for my 4x4x4x4 raid NVMEs. Was a challenging re-do of my build. Finally done with Windows baremetal - what benchmarks would you like to see?
  9. @fabiosun, So this 'solution' almost worked for me, but just in the end during the "updating" (after copying all files) phase it still failed with the same error and I could not boot from the target drive still. This trick certainly did something as before the installer could not even start copying the installation files. Other people suggest that one needs to unplug all drives but the target nvme and try the install, but I am not disassembling my entire system because of this. I even tried to install from an old SSD instead of USB as the installation drive - same issue. This is an almost laughable situation - how is one supposed to do a clean Windows install? Do they even test these chipsets before they release them? The irony is Gigabyte officially supports only Windows - if you ever try to point out you have Linux, they will not answer your concerns, yet Linux is the one system that works reliably on this board, except for the USB re-initialization issues when released by VMs.
  10. BIOS f4p is a major PITA for the Designare. I can no longer reboot my Proxmox host w/out hanging w BIOS code 9A. I need to power cycle the PC by turning it off (reset does not work). Something with the release of USB controller by guest VM does not play nicely with the re-initialization of BIOS. Total garbage, lots of people are complaining by f4p on the Gigabyte US forum. To top if off (not related to f4p as the same happens on f4h) - I was shocked to find out today I am unable to install Windows 10 bare metal. I never had Windows 10 outside of a VM attempted on this motherboard, so I wanted to try my dual GPU 3090 setup for ML (I have pretty much stepped away from MacOS for the time being till Radeon 6000 cards get drivers) and shockingly the setup failed - both latest Win 10 iso and 2004 versions. This person describes the same problem plus a proposed crazy solution, which almost worked but not quite. I can't believe I cannot install Windows in 2021 on a PC chipset that has been out for more than a year now. Gigabyte, AMD and Microsoft suck 😠. https://answers.microsoft.com/en-us/windows/forum/all/windows-10-fresh-install-fails/f9614ae4-6dbd-4715-9a81-8586b16dfaf7
  11. @Driftwood, I noticed this limitation a while ago - on the Gigabyte BIOS-es this causes D4 PCI resource allocation error and refuses to boot. I never researched the exact topology/PCI lanes, but the TRX40 chipset is definitely not as good as the Intel Xeon ones for many PCI devices. On this topic, as of now, WRX80 is available, which should have 7 x16 PCI slots, but unfortunately requires you to also swap your Threadripper for a Threadripper Pro.
  12. You can run your memory more stably at 3200mhz CL16 and tight timings than 3600mhz CL18 and get better performance as the IF won't be overclocked beyond spec. Threadripper sweet spot is 3200mhz.
  13. @Jaidy, This is a memory corruption error. At some point one of your processes (Google Chrome Helper) requested to allocate memory, which the kernel tried to handle and failed a sanity check. If this is not reproducible it could be due to issues with memory instability or just bad luck. It is hard to know for sure what's happening based on the error alone. Cosmic rays, random memory errors or overclocking instability are possible. You are running 256G of memory at 3600mhz. This is a very ambitious overclock on such size with the Threadripper platform. Since your memory has no error-correction, I wouldn't be shocked if you get memory errors but you just get lucky enough they don't cause kernel or application panics. Linus Torvalds famously (in his usual 'colorful' style) commented on the lack of unbuffered ECC memory and how important he thinks it is to avoid random occasional crashes or even malicious attacks: https://www.phoronix.com/scan.php?page=news_item&px=Linus-Torvalds-ECC I would recommend you scale back your overclock to 3200mhz (you don't lose much of performance on this platform) which matches the officially stable IF of 1600mhz of Threadripper. I have a hard time running 256GB stable at 3600mhz even though my memory is rated (same brand).
  14. @Arrakis - wow - so I don't how long it took to load the clip, but it was definitely more than a minute - I left it alone and minimized the window and when I checked 20 min later it was there. This is really bad in practice. So on the Windows VM it's averaging only 21 fps after a long run. It only uses 190w which is about 60-70% of the cards TDP and card doesn't get hot at all.
  15. Now that I read this, I am pretty sure I did not wait long enough or didn't switch around the right way. I will revisit tonight. Backed up atm.
  16. @Ploddles - do you ever have an issue with the media being "blank"? Do you think a full reinstall is warranted?
  17. I still have problems. I didn't try waiting for long time yet. Weird thing is that the 1st time I ran it, I saw the video but didn't capture the frame rate. I still wonder what the issue is. May retry tonight by reinstalling resolve
  18. Yes that too but they are not easy to get. I have more 6000 than I use now lol. Tested the 6900XT in gaming - it's pretty good.
  19. FYI besbuy has FE 3090 in stock right now https://www.bestbuy.com/site/nvidia-geforce-rtx-3090-24gb-gddr6x-pci-express-4-0-graphics-card-titanium-and-black/6429434.p?skuId=6429434 Pick up only - if you order in NYC, I can pick it up for you and ship it to a board member if you trust me (long shot I know, but thought I'd offer). I managed to put 2 orders w pickup in NYC local store Jan 9.
  20. It wasn’t a bad motherboard as I suspected but crappy bios programming. Flashing f4h with default cms on makes uefi bios cards non postable in slot 3. Stripped all slots and moved my nvidia 240 in slot 1 - voila, posted.
  21. More bad news - I tried to upgrade the desisgnare’s bios to f4k as now I no longer use thunderbolt in slot 4, so figured shouldn’t stay on the unofficial f4h. But I was getting some weird errors in Linux and that coincided with da Vinci going black on this project after it seemed to run once so rolled back. I’ve done this flash several times back and forth while debugging thunderbolt and pcie resource isssues without a glitch. This time after the rollback, pc rebooted as usual and started cycling thru the codes and then got stuck on code B2 - no post, black screen. Did cmos button reset - same. Did power down then power up and hold power button to try load backup bios - same B2 code after some cycling. Swapped the 6900XT for an old 240GT t rule out GPU (slot 3 now to aid air flow), same issue. Did I somehow brick my bios? Is full disassembly and qflash my only resort ?
  22. I am starting to wonder if there is any defect with the Radeon 6900XT I got related to the failure to play the file in DaVinci resolve project you shared. I installed Resolve on Fedora Linux to rule out some Windows VM driver issue, and I have the same problem. How do I troubleshoot this Resolve? When I relink or replace the file, I get a blank unplayable track. Btw I installed Resolve 17 beta. Could that be the problem? Although the more likely explanation is user error / inexperience w Resolve.
  23. Do you mean "Tutorial - Tracking" MOV file? I tried. Nothing. The weird thing is that I was able to see the frames about an hour ago but had to head out and when I came back I restarted and it was blank. Stepping aside for 15 min ... Will try again in a bit.
×
×
  • 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.