Tuesday, January 30th 2018
An EPYC Threadripper: Der8auer Gets EPYC CPU Working on X399 Motherboard
So, maybe it isn't really working - but at least the system boots up all the way to the BIOS memory checks, where it then stops emitting life signs. Der8auer went through a sort of blind process to discover that there is a particular ID pin on EPYC that when covered, allows the CPU to be booted up by a X399 motherboard (in this case, an ASUS X399 Zenith Extreme). ID pins are nothing new, and basically tell sockets whether or not they should be powering up a particular CPU.
So what exactly does this mean? Nothing much - only that the sockets and pinouts are the same. The approach towards detecting the ID pin was a crude, brute force one, appending a piece of electrical tape to different parts of the CPU, narrowing down the search for a single pin. When this particular pin was covered, standby power finally kept on, and the motherboard ran through some initial boot steps until stopping at the D0 memory boot code. Der8auer thinks that a "simple" BIOS switch on this TR4 motherboard to an EPYC motherboard's BIOS would suffice to get the EPYC CPU running on this Threadripper motherboard. Check out the full video after the break.
Source:
Der8auer's YouTube
So what exactly does this mean? Nothing much - only that the sockets and pinouts are the same. The approach towards detecting the ID pin was a crude, brute force one, appending a piece of electrical tape to different parts of the CPU, narrowing down the search for a single pin. When this particular pin was covered, standby power finally kept on, and the motherboard ran through some initial boot steps until stopping at the D0 memory boot code. Der8auer thinks that a "simple" BIOS switch on this TR4 motherboard to an EPYC motherboard's BIOS would suffice to get the EPYC CPU running on this Threadripper motherboard. Check out the full video after the break.
37 Comments on An EPYC Threadripper: Der8auer Gets EPYC CPU Working on X399 Motherboard
If it doesn't boot, it doesn't work imho.
so yep, it's working .... up to a certain point where it block :laugh: seriously... AMD is not even on the level of intel .... (although it would be logical to have EPYC and Threadripper on the same platform just like the i7/9 and Xeon on 2066) look at the AM4 prevision compared to the LGA 1151 actual trick (6700/7700 vs 8700 ) or ... just AMD and Intel sockets/chipset history ...
oh wait .... 0.5/10
you have a Threadripper CPU you don't actually need a EPYC CPU nor a new motherboard ... (also if you have a Zen then yep you need a new mobo ... tho you wouldn't even need a Threadripper CPU up to this point .... thus you wouldn't need a new mobo ... you could just wait till Zen refresh/2.0, they are not tricking users ... the users are tricking themselves ;) well at last the user who don't think a bit before deciding something )
A boot implies something booted. This is usually implied to mean something beyond firmware, at least as I was taught. The term comes from the idea of pulling one up by their bootstraps.
Stuck at boot translates in not working.
This might be something that can't be fixed, or it could be a simple BIOS hack will allow the board to initialize the memory controllers even though there isn't anything physically on the motherboard to use them. IDK
This does neither.
There are server boards and there are consumer boards, they are different things made for different tasks as are the cpu's made for them.
Both are equally new...
Its like being mad that you can't buy a Ford F-150 with the engine and gearbox of a Ford GT in it even though if you are handy it COULD fit.