• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

*** AMD "Zen" thread (inc AM4/APU discussion) ***

Quite interesting. Possibly going to see a good number of people switching to Linux?

Linux support still isn't there which is a shame. I tried it out a few months ago and couldnt get my sound card (creative soundblaster z) working as there are no linux drivers for it. Games support is getting better but theres still a lot of games that don't support linux.
 
Quite interesting. Possibly going to see a good number of people switching to Linux?
I almost certainly will when Ryzen's IOMMU groups are sorted. I plan to get a Vega GPU anyway, leaving my current one as a spare. When I come to upgrade the rest of my system (likely with Zen+) I'll go Linux + Windows VM for games. However, I know I can do this because of many years of experience with Linux at work and university. I wouldn't really recommend Linux for anyone with no experience.

Actually this gives me an idea. Has anyone with a Ryzen CPU tried installing Linux and then setting up a Windows 10 VM with the core configuration set to 2 sockets / 4 cores per socket / 2 threads per core? This might make Windows 10 treat the two CCXs better and stop throwing data around between them unnecessarily. Would be interesting to see performance benchmarks with this configuration and a standard 8c/16t configuration!
 
Last edited:

What I don't get is that Microsoft, Intel and AMD all along stated that they were never going to be support Ryzen and Kaby in W8 or earlier yet everyone kicking off now they finally confirmed it's done.

When Kaby was first announced they said no support other than through W10. All the lead up to Ryzen both AMD and Microsoft stated W10 was the only official support for the chip.

No point getting angry when it was already stated and people chose to ignore it because it was working a thing time.

Things move on.
 
What would the command be in objdump to check?

Just tried on Win and those bins I linked didn't actually work for me, what did work was the MinGW installer https://sourceforge.net/projects/mingw/

It's pretty easy to use, select the 'mingw32-base' package for install, I installed it to C:\MinGW

Then in C:\MinGW\bin there is an executable called objdump. Invoke it without arguments (or with -H, or --help) for the help.
C:\MinGW\bin>objdump
Usage: objdump <option(s)> <file(s)>
Display information from object <file(s)>.
At least one of the following switches must be given:
-a, --archive-headers Display archive header information
-f, --file-headers Display the contents of the overall file header
-p, --private-headers Display object format specific file header contents
-P, --private=OPT,OPT... Display object format specific contents
-h, --[section-]headers Display the contents of the section headers
-x, --all-headers Display the contents of all headers
-d, --disassemble Display assembler contents of executable sections
-D, --disassemble-all Display assembler contents of all sections
-S, --source Intermix source code with disassembly
-s, --full-contents Display the full contents of all sections requested
-g, --debugging Display debug information in object file
-e, --debugging-tags Display debug information using ctags style
-G, --stabs Display (in raw form) any STABS info in the file
-W[lLiaprmfFsoRt] or
--dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,
=frames-interp,=str,=loc,=Ranges,=pubtypes,
=gdb_index,=trace_info,=trace_abbrev,=trace_aranges,
=addr,=cu_index]
Display DWARF info in the file
-t, --syms Display the contents of the symbol table(s)
-T, --dynamic-syms Display the contents of the dynamic symbol table
-r, --reloc Display the relocation entries in the file
-R, --dynamic-reloc Display the dynamic relocation entries in the file
@<file> Read options from <file>
-v, --version Display this program's version number
-i, --info List object formats and architectures supported
-H, --help Display this information
the -d flag prints the assembly for your file. E.g. for firefox I can do
Code:
C:\MinGW\bin>objdump -d "C:\Program Files (x86)\Mozilla Firefox\firefox.exe" > ff.txt
then you can look in the txt file for any instructions you like, e.g. vfmadd as per https://en.wikipedia.org/wiki/FMA_instruction_set (For the record firefox doesn't contain any.)
 
What I don't get is that Microsoft, Intel and AMD all along stated that they were never going to be support Ryzen and Kaby in W8 or earlier yet everyone kicking off now they finally confirmed it's done.

When Kaby was first announced they said no support other than through W10. All the lead up to Ryzen both AMD and Microsoft stated W10 was the only official support for the chip.

No point getting angry when it was already stated and people chose to ignore it because it was working a thing time.

Things move on.


Who's getting angry? could it be Microsoft because windows 7 is beating the hell out windows 10?
I'm now off to buy a 6th gen Intel.
 
What I don't get is that Microsoft, Intel and AMD all along stated that they were never going to be support Ryzen and Kaby in W8 or earlier yet everyone kicking off now they finally confirmed it's done.

When Kaby was first announced they said no support other than through W10. All the lead up to Ryzen both AMD and Microsoft stated W10 was the only official support for the chip.

No point getting angry when it was already stated and people chose to ignore it because it was working a thing time.

Things move on.

Your missing the point, so much, the point is a dot to you.

There is no physical reason the CPU won't run other OS's, its purely as the video said, microsoft trying to log every little thing you do and heavily spy on you, the issue is massive corporation abusing its customers - abusive strong arming a customer using your information and life for others personal gain is literally '1984'

However I bet it won't be long before a hacker changes this - no matter what MS try to do, the OS Kernal is x64 bit universal - you can't make a processor that runs a 40 year old code base immune to all code thats based on x64/x86
 
Just tried on Win and those bins I linked didn't actually work for me, what did work was the MinGW installer https://sourceforge.net/projects/mingw/

It's pretty easy to use, select the 'mingw32-base' package for install, I installed it to C:\MinGW

Then in C:\MinGW\bin there is an executable called objdump. Invoke it without arguments (or with -H, or --help) for the help.
C:\MinGW\bin>objdump
Usage: objdump <option(s)> <file(s)>
the -d flag prints the assembly for your file. E.g. for firefox I can do
Code:
C:\MinGW\bin>objdump -d "C:\Program Files (x86)\Mozilla Firefox\firefox.exe" > ff.txt
then you can look in the txt file for any instructions you like, e.g. vfmadd as per https://en.wikipedia.org/wiki/FMA_instruction_set (For the record firefox doesn't contain any.)

Ah I get an error, maybe because it's 64bit? Also so many associated files with Premiere.

C:\Users\Johnny\Downloads\obj\bin>objdump -d "C:\Program Files\Adobe\Adobe Premiere Pro CC 2015\Adobe Premiere Pro.exe" > test.txt
objdump: C:\Program Files\Adobe\Adobe Premiere Pro CC 2015\Adobe Premiere Pro.exe: File format not recognized
 
Just got my 1800x and Crosshair up and running.

For some reason all I see most of the time is 3.7Ghz on all cores, I saw 4.1 for a millisecond once and that's about it.

Any ideas ? All stock settings
 
Ah I get an error, maybe because it's 64bit? Also so many associated files with Premiere.

C:\Users\Johnny\Downloads\obj\bin>objdump -d "C:\Program Files\Adobe\Adobe Premiere Pro CC 2015\Adobe Premiere Pro.exe" > test.txt
objdump: C:\Program Files\Adobe\Adobe Premiere Pro CC 2015\Adobe Premiere Pro.exe: File format not recognized
Yep was just about to say that - I get the same on the 64 Linpack exe.
 
What I don't get is that Microsoft, Intel and AMD all along stated that they were never going to be support Ryzen and Kaby in W8 or earlier yet everyone kicking off now they finally confirmed it's done.

When Kaby was first announced they said no support other than through W10. All the lead up to Ryzen both AMD and Microsoft stated W10 was the only official support for the chip.

No point getting angry when it was already stated and people chose to ignore it because it was working a thing time.

Things move on.
Two things have changed: firstly, this isn't "not supporting Ryzen/Kaby Lake on Windows 7/8.1" any more. This has now become "if you have Ryzen/Kaby Lake we are going to intentionally disable update functionality on Windows 7/8.1". Those are very different IMO. Secondly, some reviewers note (in some cases much) better gaming results with Ryzen using Windows 7 compared to Windows 10. Yet now, Windows 7 can't be used without losing update functionality.
 
Just got my 1800x and Crosshair up and running.

For some reason all I see most of the time is 3.7Ghz on all cores, I saw 4.1 for a millisecond once and that's about it.

Any ideas ? All stock settings

All core boost is 3.7ghz, single core to 4.1ghz.

Try running single threaded Cinibench and you should see one core boost to 4.1ghz.
 
They do exist...

D8x5OUth.jpg

:o Give

I'm quite a fan of the uppercutting eagle.

Love the matte black/grey. Whole board looks nice.

I can't believe how many mobo makers are jumping on the bandwagon of the massive MASSIVE plastic heat traps over the IO.

Nothing wrong with covering the VRM heatsinks right?

Its nice though. No?


LOL at the end credits.
 
What I don't get is that Microsoft, Intel and AMD all along stated that they were never going to be support Ryzen and Kaby in W8 or earlier

Funny stuff.

The issue is putting in code to disable updates for older OS if they use new hardware.

So it's not "it wont work" it's we're gonna check the hardware and if we we don't like it we disable updates.

That's not lack of support that's deliberate blocking.
 
Back
Top Bottom