#agesa — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #agesa, aggregated by home.social.
-
https://www.europesays.com/pl/336928/ AMD Ryzen 9 9950X3D2 Dual Edition – producenci płyt głównych wypuścili edycję UEFI do obsługi nadchodzącego procesora #agesa #aktualizacja #asrock #bios #cpu #gigabyte #max #MegX870eUnifyX #MSI #Nauka #NaukaITechnika #NaukaTechnika #PL #PłytaGłówna #Poland #Polish #Polska #Polski #procesor #Ryzen99950x3d2DualEdition #Science #ScienceAndTechnology #ScienceTechnology #Technika #Technology #uefi
-
Mit einem #AGESA-Update schließt #AMD endlich die kritische #Sicherheitslücke "#EntrySign", die alle Zen-#Prozessoren plagt. Erste Mainboardhersteller haben bereits ein #BIOS-#Update für Nutzer veröffentlicht. https://winfuture.de/news,150530.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Mit einem #AGESA-Update schließt #AMD endlich die kritische #Sicherheitslücke "#EntrySign", die alle Zen-#Prozessoren plagt. Erste Mainboardhersteller haben bereits ein #BIOS-#Update für Nutzer veröffentlicht. https://winfuture.de/news,150530.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Mit einem #AGESA-Update schließt #AMD endlich die kritische #Sicherheitslücke "#EntrySign", die alle Zen-#Prozessoren plagt. Erste Mainboardhersteller haben bereits ein #BIOS-#Update für Nutzer veröffentlicht. https://winfuture.de/news,150530.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Mit einem #AGESA-Update schließt #AMD endlich die kritische #Sicherheitslücke "#EntrySign", die alle Zen-#Prozessoren plagt. Erste Mainboardhersteller haben bereits ein #BIOS-#Update für Nutzer veröffentlicht. https://winfuture.de/news,150530.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Mit einem #AGESA-Update schließt #AMD endlich die kritische #Sicherheitslücke "#EntrySign", die alle Zen-#Prozessoren plagt. Erste Mainboardhersteller haben bereits ein #BIOS-#Update für Nutzer veröffentlicht. https://winfuture.de/news,150530.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
-
Modern motherboard firmwares (#BIOS for us oldtimers) are outright awful. Toggling a single option X on/off isn't necessarily binary. Enabling option X might enable other option Y (and maybe more) which will remain enabled even if you disable X again.
This makes it extremely difficult to do binary search on situations where some firmware option causes you trouble.
I was bit by this earlier today when I enabled AMD Precision Boost Overdrive on an AM4 system. The system would start to fail compile tasks randomly (and #Prime95 within second) when PBO was enabled. Confusingly disabling PBO did not result in a working system, but the system kept crashing. I updated the firmware to the latest version and the system became stable again. "Great, #AGESA update must've fixed the stability issue!", I naively thought. So I enabled PBO, system kept crashing, I disabled PBO, system kept crashing. Frustration ensued.
"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth". Enabling PBO pulls some other options which cause the stability issue, and disabling PBO doesn't disable them.
Sure enough, resetting BIOS to default, then enabling everything but PBO resulted in a stable system that is able to run Prime95 for hours. While it might be possible to figure out what this "extra" option causing the instability actually is, at this stage I was happy to just have a working system. It won't touch PBO on this box ever again.
-
Modern motherboard firmwares (#BIOS for us oldtimers) are outright awful. Toggling a single option X on/off isn't necessarily binary. Enabling option X might enable other option Y (and maybe more) which will remain enabled even if you disable X again.
This makes it extremely difficult to do binary search on situations where some firmware option causes you trouble.
I was bit by this earlier today when I enabled AMD Precision Boost Overdrive on an AM4 system. The system would start to fail compile tasks randomly (and #Prime95 within second) when PBO was enabled. Confusingly disabling PBO did not result in a working system, but the system kept crashing. I updated the firmware to the latest version and the system became stable again. "Great, #AGESA update must've fixed the stability issue!", I naively thought. So I enabled PBO, system kept crashing, I disabled PBO, system kept crashing. Frustration ensued.
"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth". Enabling PBO pulls some other options which cause the stability issue, and disabling PBO doesn't disable them.
Sure enough, resetting BIOS to default, then enabling everything but PBO resulted in a stable system that is able to run Prime95 for hours. While it might be possible to figure out what this "extra" option causing the instability actually is, at this stage I was happy to just have a working system. It won't touch PBO on this box ever again.
-
Modern motherboard firmwares (#BIOS for us oldtimers) are outright awful. Toggling a single option X on/off isn't necessarily binary. Enabling option X might enable other option Y (and maybe more) which will remain enabled even if you disable X again.
This makes it extremely difficult to do binary search on situations where some firmware option causes you trouble.
I was bit by this earlier today when I enabled AMD Precision Boost Overdrive on an AM4 system. The system would start to fail compile tasks randomly (and #Prime95 within second) when PBO was enabled. Confusingly disabling PBO did not result in a working system, but the system kept crashing. I updated the firmware to the latest version and the system became stable again. "Great, #AGESA update must've fixed the stability issue!", I naively thought. So I enabled PBO, system kept crashing, I disabled PBO, system kept crashing. Frustration ensued.
"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth". Enabling PBO pulls some other options which cause the stability issue, and disabling PBO doesn't disable them.
Sure enough, resetting BIOS to default, then enabling everything but PBO resulted in a stable system that is able to run Prime95 for hours. While it might be possible to figure out what this "extra" option causing the instability actually is, at this stage I was happy to just have a working system. It won't touch PBO on this box ever again.
-
Modern motherboard firmwares (#BIOS for us oldtimers) are outright awful. Toggling a single option X on/off isn't necessarily binary. Enabling option X might enable other option Y (and maybe more) which will remain enabled even if you disable X again.
This makes it extremely difficult to do binary search on situations where some firmware option causes you trouble.
I was bit by this earlier today when I enabled AMD Precision Boost Overdrive on an AM4 system. The system would start to fail compile tasks randomly (and #Prime95 within second) when PBO was enabled. Confusingly disabling PBO did not result in a working system, but the system kept crashing. I updated the firmware to the latest version and the system became stable again. "Great, #AGESA update must've fixed the stability issue!", I naively thought. So I enabled PBO, system kept crashing, I disabled PBO, system kept crashing. Frustration ensued.
"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth". Enabling PBO pulls some other options which cause the stability issue, and disabling PBO doesn't disable them.
Sure enough, resetting BIOS to default, then enabling everything but PBO resulted in a stable system that is able to run Prime95 for hours. While it might be possible to figure out what this "extra" option causing the instability actually is, at this stage I was happy to just have a working system. It won't touch PBO on this box ever again.
-
Modern motherboard firmwares (#BIOS for us oldtimers) are outright awful. Toggling a single option X on/off isn't necessarily binary. Enabling option X might enable other option Y (and maybe more) which will remain enabled even if you disable X again.
This makes it extremely difficult to do binary search on situations where some firmware option causes you trouble.
I was bit by this earlier today when I enabled AMD Precision Boost Overdrive on an AM4 system. The system would start to fail compile tasks randomly (and #Prime95 within second) when PBO was enabled. Confusingly disabling PBO did not result in a working system, but the system kept crashing. I updated the firmware to the latest version and the system became stable again. "Great, #AGESA update must've fixed the stability issue!", I naively thought. So I enabled PBO, system kept crashing, I disabled PBO, system kept crashing. Frustration ensued.
"When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth". Enabling PBO pulls some other options which cause the stability issue, and disabling PBO doesn't disable them.
Sure enough, resetting BIOS to default, then enabling everything but PBO resulted in a stable system that is able to run Prime95 for hours. While it might be possible to figure out what this "extra" option causing the instability actually is, at this stage I was happy to just have a working system. It won't touch PBO on this box ever again.
-
fyi #ASUS #AM4 #AM5 motherboard owners, the new BIOS just dropped
1. Updated to AMD #AGESA PI 1.2.0.1a.
2. Resolved the #SMM Lock Bypass and Sinkhole security vulnerabilities.
3. The control limit mode (cTDP to105W) was moved to a more accessible location for different processors.(ROG STRIX B650E-I GAMING WIFI link)
https://rog.asus.com/us/motherboards/rog-strix/rog-strix-b650e-i-gaming-wifi-model/helpdesk_bios/
-
CPU-Gerüchte: Ryzen-TDP-Upgrade kommt mit AGESA 1.2.0.2 Ende September (Update) https://www.computerbase.de/2024-09/cpu-geruechte-ryzen-tdp-upgrade-kommt-mit-agesa-1-2-0-2-ende-september/#update-2024-09-02T17:22 #Ryzen #Agesa #AMD
-
CPU-Gerüchte: Ryzen-TDP-Upgrade kommt mit AGESA 1.2.0.2 Ende September https://www.computerbase.de/2024-09/cpu-geruechte-ryzen-tdp-upgrade-kommt-mit-agesa-1-2-0-2-ende-september/ #Ryzen #Agesa #AMD
-
Updated my Asrock AM5 mainboard to the latest UEFI firmware version with AGESA 1.2.0.0a and nothing disastrous seemed to happen!
Many more custom settings are preserved which makes the updating far less painful 🙂
-
Looks like #Asrock has begun rolling out the UEFI and #AGESA 1.2.0.0a firmware updates for #Ryzen 9000 series CPU support 😁☺️
https://pg.asrock.com/MB/AMD/X670E%20PG%20Lightning/index.asp#BIOS
-
For anyone wondering the AMD AGESA ComboAM5 v1.1.0.3 update adds support for some CPU's intended for the Chinese market only.
If you are already up to date with earlier AGESA updates in your UEFI firmware there is no immediate need to update to this one 🙂
-
UEFI Firmware update successful 😀🎉
I am now on the latest AMD AGESA code and all of the UEFI settings which a firmware update resets have been set to sensible values.
So annoying that it does that but I assume it's necessary to do that between firmware versions.
The settings which need to be altered are:
- EXPO RAM Timings,
- SR-IOV,
- IO-MMU,
- Thunderbolt Support, and
- FCH Spread Spectrum
all of which need to be re-enabled apart from the latter which needs to be disabled.
If anyone needs a recommendation for an AM5 mainboard I can recommend the Asrock X670E PG Lightning.
It's one of the lower cost X670E boards and works very well.
-
AMD has issued a new BIOS/UEFI update to mitigate some issues regarding its API interface. If an attacker successfully exploits the vulnerabilities, they can cause a denial of service condition or perform privilege escalation.
For more: www.amd.com/en/resources/product-security/bulletin/amd-sb-7009.html
#infosec #cybersecurity #AMD #SPI #AGESA #BIOS #UEFI -
#AMD discloses slew of high severity #security #vulnerabilities for #Zen systems, from the original Zen chips to the latest #Zen4 #CPU, that attacks #BIOS chips, we finally have a #Zenbleed fix. AMD is patching the vulnerabilities through new versions of #AGESA, for #Zen2-based chips, in particular, many of these new AGESAs also patch Zenbleed, including #Epyc #Server chips https://bit.ly/3I1JKds https://www.tomshardware.com/pc-components/cpus/amd-discloses-slew-of-high-severity-security-vulnerabilities-for-zen-chips-that-attack-bios-chips-updates-aim-to-patch-bugs-finally-fix-zenbleed
-
#AMD discloses slew of high severity #security #vulnerabilities for #Zen systems, from the original Zen chips to the latest #Zen4 #CPU, that attacks #BIOS chips, we finally have a #Zenbleed fix. AMD is patching the vulnerabilities through new versions of #AGESA, for #Zen2-based chips, in particular, many of these new AGESAs also patch Zenbleed, including #Epyc #Server chips https://bit.ly/3I1JKds https://www.tomshardware.com/pc-components/cpus/amd-discloses-slew-of-high-severity-security-vulnerabilities-for-zen-chips-that-attack-bios-chips-updates-aim-to-patch-bugs-finally-fix-zenbleed
-
#AMD discloses slew of high severity #security #vulnerabilities for #Zen systems, from the original Zen chips to the latest #Zen4 #CPU, that attacks #BIOS chips, we finally have a #Zenbleed fix. AMD is patching the vulnerabilities through new versions of #AGESA, for #Zen2-based chips, in particular, many of these new AGESAs also patch Zenbleed, including #Epyc #Server chips https://bit.ly/3I1JKds https://www.tomshardware.com/pc-components/cpus/amd-discloses-slew-of-high-severity-security-vulnerabilities-for-zen-chips-that-attack-bios-chips-updates-aim-to-patch-bugs-finally-fix-zenbleed
-
#AMD discloses slew of high severity #security #vulnerabilities for #Zen systems, from the original Zen chips to the latest #Zen4 #CPU, that attacks #BIOS chips, we finally have a #Zenbleed fix. AMD is patching the vulnerabilities through new versions of #AGESA, for #Zen2-based chips, in particular, many of these new AGESAs also patch Zenbleed, including #Epyc #Server chips https://bit.ly/3I1JKds https://www.tomshardware.com/pc-components/cpus/amd-discloses-slew-of-high-severity-security-vulnerabilities-for-zen-chips-that-attack-bios-chips-updates-aim-to-patch-bugs-finally-fix-zenbleed
-
#AMD discloses slew of high severity #security #vulnerabilities for #Zen systems, from the original Zen chips to the latest #Zen4 #CPU, that attacks #BIOS chips, we finally have a #Zenbleed fix. AMD is patching the vulnerabilities through new versions of #AGESA, for #Zen2-based chips, in particular, many of these new AGESAs also patch Zenbleed, including #Epyc #Server chips https://bit.ly/3I1JKds https://www.tomshardware.com/pc-components/cpus/amd-discloses-slew-of-high-severity-security-vulnerabilities-for-zen-chips-that-attack-bios-chips-updates-aim-to-patch-bugs-finally-fix-zenbleed
-
AMD is revealing the first bits of code today, in it's transition from AGESa to the open-source OpenSIL platform for firmware
-
AMD is revealing the first bits of code today, in it's transition from AGESa to the open-source OpenSIL platform for firmware
-
AMD is revealing the first bits of code today, in it's transition from AGESa to the open-source OpenSIL platform for firmware
-
AMD is revealing the first bits of code today, in it's transition from AGESa to the open-source OpenSIL platform for firmware
-
AMD is revealing the first bits of code today, in it's transition from AGESa to the open-source OpenSIL platform for firmware
-
Ich blick’s nicht ganz. Sie lassen ein neues #Agesa schreiben, aber diesmal in OSS, was ist dann mit den ganzen proprietären Elementen darin, können die auf einmal dann doch OSS sein, hä?
#OpenSIL: AMDs Open-Source-Firmware erstmals verfügbar
https://www.golem.de/news/opensil-amds-open-source-firmware-erstmals-verfuegbar-2306-174977.html
-
Ich blick’s nicht ganz. Sie lassen ein neues #Agesa schreiben, aber diesmal in OSS, was ist dann mit den ganzen proprietären Elementen darin, können die auf einmal dann doch OSS sein, hä?
#OpenSIL: AMDs Open-Source-Firmware erstmals verfügbar
https://www.golem.de/news/opensil-amds-open-source-firmware-erstmals-verfuegbar-2306-174977.html
-
Ich blick’s nicht ganz. Sie lassen ein neues #Agesa schreiben, aber diesmal in OSS, was ist dann mit den ganzen proprietären Elementen darin, können die auf einmal dann doch OSS sein, hä?
#OpenSIL: AMDs Open-Source-Firmware erstmals verfügbar
https://www.golem.de/news/opensil-amds-open-source-firmware-erstmals-verfuegbar-2306-174977.html
-
Ich blick’s nicht ganz. Sie lassen ein neues #Agesa schreiben, aber diesmal in OSS, was ist dann mit den ganzen proprietären Elementen darin, können die auf einmal dann doch OSS sein, hä?
#OpenSIL: AMDs Open-Source-Firmware erstmals verfügbar
https://www.golem.de/news/opensil-amds-open-source-firmware-erstmals-verfuegbar-2306-174977.html
-
Ich blick’s nicht ganz. Sie lassen ein neues #Agesa schreiben, aber diesmal in OSS, was ist dann mit den ganzen proprietären Elementen darin, können die auf einmal dann doch OSS sein, hä?
#OpenSIL: AMDs Open-Source-Firmware erstmals verfügbar
https://www.golem.de/news/opensil-amds-open-source-firmware-erstmals-verfuegbar-2306-174977.html
-
https://linuxiac.com/amd-opensil-firmware/
"AMD revealed its plans to shift from AGESA to openSIL by 2026. This move represents a significant departure from the traditional approach to firmware development and could have substantial implications for the industry."
-
https://linuxiac.com/amd-opensil-firmware/
"AMD revealed its plans to shift from AGESA to openSIL by 2026. This move represents a significant departure from the traditional approach to firmware development and could have substantial implications for the industry."
-
https://linuxiac.com/amd-opensil-firmware/
"AMD revealed its plans to shift from AGESA to openSIL by 2026. This move represents a significant departure from the traditional approach to firmware development and could have substantial implications for the industry."
-
https://linuxiac.com/amd-opensil-firmware/
"AMD revealed its plans to shift from AGESA to openSIL by 2026. This move represents a significant departure from the traditional approach to firmware development and could have substantial implications for the industry."
-
https://linuxiac.com/amd-opensil-firmware/
"AMD revealed its plans to shift from AGESA to openSIL by 2026. This move represents a significant departure from the traditional approach to firmware development and could have substantial implications for the industry."
-
-
-
AMD сказали, что в ближайшее время должна выйти AGESA с исправлением нестабильной работы USB, которая проявлялась в виде отвалов USB порта, проблем с внешними аудиоинтерфейсами и прочим.
https://www.reddit.com/r/Amd/comments/m2wqkf/updated_agesa_coming_for_intermittent_usb/
Кстати, проблемы с внешними аудиоинтерфейсами - достаточно распространённая беда. Одну, очень похожую и может быть даже частично связанную я испытывал на себе. Для меня она была исправлена драйверами от Focusrite, но вот, например, другу, который сидит на одном из самых новых чипсетов повезло меньше и его проблема должна, по идее, решиться с обновлением AGESA.
Сложно не согласиться с @[email protected] в том, что принцип "выпустим сейчас, а потом в прошивках пофиксим" - это рак современности.
#AMD #USB #hardware #AGESA #BIOS #UEFI #firmware #audio #sound #bugs #log #news #reddit
