#AMD Driver Symbol Server

1 messages · Page 1 of 1 (latest)

frigid zephyr
drowsy laurel
#

Okay, so found out, this falls into the gfx sw domain (my org)

#

a collague noted this was caused by an infra change, it's presently being worked on

#

but some code changes need to be made to said infra

frigid zephyr
#

Good to here its being worked on.

Was there a URL change for the history or was the symbol server just forgotten when the infra was changed?
The current symbol server does not have access to the Vulkan/OpenGL dlls due to the file structure change of the 25.20 branch

frigid zephyr
drowsy laurel
#

sorry meant to get back on that, my colleague looped me into the email thread though I was mostly too dumb to make sense of the full situation

frigid zephyr
drowsy laurel
#

can do when in done in the garage

frigid zephyr
#

@drowsy laurel any updates?

drowsy laurel
#

nothing so far

frigid zephyr
drowsy laurel
#

I saw, they suggested vanguard but the binary signature doesn't match any of our builds

#

had discussed this internally yesterday evening

#

perhaps it leaked from an oem 😅

frigid zephyr
#

Does AMD just monitor guru3d?

drowsy laurel
#

eyes everywhere

frigid zephyr
#

After the 25.6.1 incident

frigid zephyr
#

only 1 release on the symbol server, I'm guessing still Work in Progress

frigid zephyr
#

ok wow, there was no need to remove FSR 4.0.3, FSR 4.0.2 and 4.0.1 from the symbol server
I understand FSR 4.1.0 but not the others

#

only the 4.0.0 versions are left

#

this will affect the Linux community as they used the symbol server to do the FSR upgrade

#

Now they will need to find alternatives or to rehost the files

frigid zephyr
#

no changes for the amdxcffx64.dll stuff in the symbol server, at least pls fix by the start of 2027