Nice, i did not realize the boot LED's were on the Tomahawk. Agreed i do not need the hexadecimal LED. This makes the decision easier to say get the Tomahawk MAX. Thanks for pointing that out!If I were building a secondary system, say for my wife, I’d be okay with a b450, so long as it had built in WiFi. I don’t overclock her systems. I found the two hexadecimal diagnostic LEDs to be less useful than I thought they’d be. The four boot LEDs are enough, IMO.
Unfortunately, its not working for me yet. The sensors are working, but I can’t set a fan profile
Not working for me either on the Aqua, the sensors are picking up temperatures but not fan speeds. Looks like a nice little app for those who can use it though.Unfortunately, its not working for me yet. The sensors are working, but I can’t set a fan profile![]()
I wish he had started his own branch on GitHub so I could pull down the source and try to fix it for my own system. I may need to sign up on the LTT forum to talk to him - he seems most active there.Not working for me either on the Aqua, the sensors are picking up temperatures but not fan speeds. Looks like a nice little app for those who can use it though.
Bummer. Might be useful after some updates.Unfortunately, its not working for me yet. The sensors are working, but I can’t set a fan profile![]()
Gah, I can’t get into the bios, all I did last time was change the fan profiles. It boots straight to Windows. BwaHahahahahahaha, I think a bought the wrong motherboard
Edit: Had to clear cmos again. Man, this is the touchiest system I’ve ever built.
Also, keep the usb power on. Otherwise the mb won't get your keystrokesI never do.
AGESA 1004B has been out since November. All 3 of my AM4 boards (X470, B450) have been flashed to UEFI versions with that AGESA. No issues to report here, though some did note some (negative?) changes with PBO behavior, which is irrelevant to me as I disabled PBO on all my setups.New Matisse-only BIOS for my board released a few days ago... don't think I'll touch it though.
"Update AMD AGESA Combo-AM4 1.0.0.4 Patch B"
...anyone flash a similar BIOS and notice anything notable?
It's fine, unless you are looking to overclock your cpu - in which case it sucks (except for 3950x).New Matisse-only BIOS for my board released a few days ago... don't think I'll touch it though.
"Update AMD AGESA Combo-AM4 1.0.0.4 Patch B"
...anyone flash a similar BIOS and notice anything notable?
I've never changed the default bios settings for usb devices. Anyway, it was working fine. I changed some fan profiles in the bios and poof. Weird shit. I hope MSI comes out with a new bios before Zen 3 (and AMD improves on AGESA 1004B). I'd go back to 1003ABB, but there have been several other fixes added to the bios since then.Also, keep the usb power on. Otherwise the mb won't get your keystrokes
I guess I should count my blessings that my sound issue went away on its own. And I have not experimentedI've never changed the default bios settings for usb devices. Anyway, it was working fine. I changed some fan profiles in the bios and poof. Weird shit. I hope MSI comes out with a new bios before Zen 3 (and AMD improves on AGESA 1004B). I'd go back to 1003ABB, but there have been several other fixes added to the bios since then.
Being a tinkerer certainly has its downside. Congrats on your ‘magical' sound fixI guess I should count my blessings that my sound issue went away on its own. And I have not experimented![]()
Being a tinkerer certainly has its downside. Congrats on your ‘magical' sound fix![]()
Just curious, what sound chip?I still can't figure out what can possibly cause this. It was working for three days, then stopped working for 2 weeks or so then it started working again...
Maybe a Windows update? I've had them break things in the past, perhaps once in a while they go the other way too?I still can't figure out what can possibly cause this. It was working for three days, then stopped working for 2 weeks or so then it started working again...
No, the update didn't fix it. It fixed itself several days after update. Was not something logical.Maybe a Windows update? I've had them break things in the past, perhaps once in a while they go the other way too?
Optical audio cable? I have had them die over time as well. Probably from pushing the receiver too close to the wall and putting too sharp of a bend in it. Didn't show up as suddenly broken, but would seem to come and go at random.