summaryrefslogtreecommitdiff
path: root/util/nvramtool/cmos_ops.h
diff options
context:
space:
mode:
authorFabian Groffen <grobian@gentoo.org>2023-05-13 22:21:48 +0200
committerMatt DeVillier <matt.devillier@amd.corp-partner.google.com>2023-08-08 16:02:01 +0000
commit6230d26ad108da328ae462762beb27284f061ea7 (patch)
treecf5d72651c0c33425281a12ddf998f9eb20ebaaf /util/nvramtool/cmos_ops.h
parenteb23fbeab0b02e6998467411e7d4faf62fda0f8a (diff)
mb/asrock/b75pro3-m: Drop destructive GPIO settings
Without setting these GPIO bits, you /can/ power on your board after powering it down again. This includes after cutting the power. The only way to recover from this is to pull the CMOS battery and cut the power for 15mins. Then make sure you don't do this GPIO trickery or you end up with the same state of basically an unresponsive "dead" mainboard. So flash the chip before you pull the battery. One small workaround I found when you like to flash from the system, is to press the power button with 1 second after you enable power to the board. In this small timeframe, apparently the superio chip didn't intialise/restore/gets set with the settings that make it never want to power on again. The other workaround is to connect the appriopriate pins on the ATX power connector to force power to the mainboard. Signed-off-by: Fabian Groffen <grobian@gentoo.org> Change-Id: I4c9df200ba3ec5f315ad3d184588551d29fa68ce Reviewed-on: https://review.coreboot.org/c/coreboot/+/75212 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Martin L Roth <gaumless@gmail.com>
Diffstat (limited to 'util/nvramtool/cmos_ops.h')
0 files changed, 0 insertions, 0 deletions