Huh, ASrock says the sleep issue is an AM5 platform requirement. See thread on reddit here. I suspect they're wrong but...
Can anyone with a non-ASRock board comment if your PC can go to sleep and wake from sleep?
After my troubles, I would say memory.
AMD launches. Still not as bad as B350 at launch but they're tryingGigabyte and MSI users chiming in here. https://community.amd.com/t5/processors/sleep-mode-not-available-when-expo-is-enabled/td-p/548658
I suspect they are right that it doesn't work now for any vendor and also suspect that AMD will fix it with an AGESA update eventually.
AMD launches. Still not as bad as B350 at launch but they're trying
Hammertime
ST = 6000mhz
MT = CCD0 @ 5700mhz | CCD1 @ 5450mhz
Large custom loop watercooling. (4 pumps + MO-RA3 420 + NexXxoS Monsta Full Copper 400mm + 10L water among other things)
nevermind the "1.61" vcore, its a readout bug.. Highest voltage used was 1400mv.
Maybe wait for 7800X3D?I'm wondering how noticeable a 7700X/X670E setup would be over my existing 10700K/Z490 for 4K gaming. It looks impressive but the total upgrade cost is quite high (especially the boards/memory) if the improvement will only be marginal. I'm also a bit concerned about my VR headset's compatibility with AMD platforms.
I registered my X670E Aorus Master and it still lists only 3 years.Anyone see Gigabyte extended warranty from 3 years to 5 on some of their 670 motherboards. Seems like a good deal if your motherboard shopping. I am still waiting for stock of B650 boards.
Only problem I have is lots of boards do not have Display port 2.0 yet. Would be nice to see that as well as more usb 4 connections on midrange boards.
Here is a link to the Gigabyte announcement!
GIGABYTE Offers 5-Year Extended Warranty For New X670 Motherboards
TAIPEI, Oct. 6, 2022 /PRNewswire/ -- With the launch of AMD AM5 X670 motherboards, GIGABYTE, the world's leading computer brand, announces today that all customers in North America region purchasing new GIGABYTE andwww.benzinga.com
I haven't seen much main stream press pick this up yet, but with revenue down I would not be surprised if more motherboard do the same.
R81Z3N1
The Real Question is... Will you be able to access the BIOS and Disable AVX-512 And run a few test for me?? Will you?? Uh?ASUS has the ITX motherboard in stock. I cancelled my Newegg order and ordered direct. Next Day shipping, so should have it pretty quick.
Come on, that's enough begging for today.Will you be able to access the BIOS and Disable AVX-512 And run a few test for me??
I am not done Beseeching for the day.Come on, that's enough begging for today.
How exactly Intel implements disabling of AVX-512? Is it just setting CPU flags? If it is just flags only, the AVX512 should work on AlderLake if forced to execute AVX512 code regardless of CPU flags. Similar to Zen1 and FMA4. Otherwise I would imagine they have to handle at decoder level to trap AVX-512 instruction and trigger exception. This would require the decoder to support disabling the AVX512 Instructions. I am not sure AMD would implement such a functionality to their decoder since many instructions are direct decode and not micro coded.The Real Question is... Will you be able to access the BIOS and Disable AVX-512 And run a few test for me?? Will you?? Uh?
They do it through microcode. I think this is in later bios revisions. It also happens where there are e-cores present.How exactly Intel implements disabling of AVX-512? Is it just setting CPU flags? If it is just flags only, the AVX512 should work on AlderLake if forced to execute AVX512 code regardless of CPU flags. Similar to Zen1 and FMA4. Otherwise I would imagine they have to handle at decoder level to trap AVX-512 instruction and trigger exception. This would require the decoder to support disabling the AVX512 Instructions. I am not sure AMD would implement such a functionality to their decoder since many instructions are direct decode and not micro coded.
Have you checked and see if AVX-512 can be disabled from BIOS?They do it through microcode. I think this is in later bios revisions. It also happens where there are e-cores present.
But this is a Zen 4 builders thread, nothing to do with Intel.
I am not going to do that, I am USING the AVX-512 for quite a while longer. 24/7. Distributed computing.Have you checked and see if AVX-512 can be disabled from BIOS?
Is micro code in the sense MicroCode ROM? To do that through micro code ROM, all the AVX512 instruction has to be micro coded. But I don't think all the AVX512 instruction are micro coded. Only complex and rarely used instruction are micro coded (I am more familier with AMD architecture than Intel so my understanding here might be incorrect). Most commonly used instructions are directly decoded to 1 or 2 u-ops. Only at decode stage the CPU will know about the instruction being decoded. Having another logic to already complex decode unit just for the purpose of disabling AVX512 seems wasteful. This is same for Intel and AMD.They do it through microcode. I think this is in later bios revisions. It also happens where there are e-cores present.
But this is a Zen 4 builders thread, nothing to do with Intel.
I do not understand your reply. Someone was asking how Intel disabled avx-512, and I said through micro code, and I think that applied to a bios update. AMD has no such plan to disable avx-512.Is micro code in the sense MicroCode ROM? To do that through micro code ROM, all the AVX512 instruction has to be micro coded. But I don't think all the AVX512 instruction are micro coded. Only complex and rarely used instruction are micro coded (I am more familier with AMD architecture than Intel so my understanding here might be incorrect). Most commonly used instructions are directly decoded to 1 or 2 u-ops. Only at decode stage the CPU will know about the instruction being decoded. Having another logic to already complex decode unit just for the purpose of disabling AVX512 seems wasteful. This is same for Intel and AMD.
He didn't mean disabling AVX-512 permanently. He meant, how does the BIOS handle disabling AVX-512 by the user? But yeah, I think JustViewing is going too deep under the hood for usAMD has no such plan to disable avx-512.