[ 0.376484] ACPI FADT declares the system doesn’t support PCIe ASPM, so disable it
[ 0.494328] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[ 0.497502] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
On next reboot, I can check the BIOS, if there’s any config option
I tried ‘powertop --auto-tune’ some days ago. The power consumption dropped a bit, but I some NICs became unresponsive…and there were some SATA errors.
Haven’t investigated further. Happy, the system is up and running
Today I added a X520-DA2 NIC as well. Just took me around three overtime hours to get this thing running again, since it was stuck at the BMC boot again, after unplugging the system. The system was powered down for more than 8 hours before unplugging it, so it’s got nothing to do with some wait time.
I got it back up by clearing the cmos again, but after changing the boot order in BIOS it seems to have crashed when saving the BIOS. Just displayed a _ in the top left corner of the screen for about 15 minutes. Another reboot later it got stuck at the splash screen and wouldn’t even let me into the bios. Had to re-flash the BIOS using the BMC to get it working again.
After some try- and error runs changing various settings in the BIOS I finally got it running and booting kinda reliable again. Disabled the network stack in BIOS as well as the onboard NIC.
I also noticed this! I don’t know what’s going at Gigabyte but it seems they don’t know thier arse from their elbow…or how to make a stable workstation motherboard. My latest issue is I (stupidly) set the IPMI management port to shared - now it’s gone. Does’t matter what I do. Can’t find a way to reset the IPMI. No jumper on board, “ipmitool mc reset cold” didn’t work and I don’t know the RAW commands to switch it from shared to dedicated. Never had so many problems with a single motherboard.
But to actually answer your question - no, I think it will be just fine. I will be doing the same when proxmox supports the igpu. But you should submit a ticket to support to see what they say. You may get a reply sometime this quarter
Hi @Ardillon - Thank you for mentioning this I had tried this before and forgot about it, but I tried it again last night but could not see any change. I tried without power, with power and shutdown, and turned on - no change. It’s strange that it’s not in the manual. Maybe they did not ‘connect’ it or program it? Did anyone successfully use it?
I tried the above command and it worked once, it got the web interface running again with same IP and login details (what exactly did it reset?!) so I changed it back to dedicated and now it’s broken again. What’s weird is that currently the MLAN and other port lights are dead until you have at least two port plugged in. And this includes add in LAN cards and even USB NIC adapters. The BMC takes over any LAN capable device! How this is even possible I have no idea. So right now, I think my only choice is to RMA the board again. But I will push for a refund, I’m done with this board.
Hopefully this puts a smile on some of your faces - motherboard is fine, my eyes are not. I had the server on a table outside the rack and used two identical cables to connect it to the switch in the rack, they were much longer than needed and I had the whole rats nest / cable salad thing going on. It turns out that somehow the ends got mixed up and I was plugging it into itself and forming a loop with the same cable. Genius
Sorry Gigabyte for the bad rep. #facepalm
Cables marked; lesson learnt.
My second board is also going back to the dealer / Gigabyte tomorrow.
I guess we have to wait some more weeks again without a working system. Too bad it’s the only board compatible with DDR4 ECC and socket 1700, otherwise I’d gladly switch. Throwing away DDR4 and buying DDR5 for another 350+€ is unfortunately not an option.
The Answer from Gigabyte:
The difference between revision 1.0 and 1.1 is that revision 1.1 supports Raptor Lake CPU but revision 1.0 not. It may cause the hardware unable to boot up or other problem when MW34-SP0 (1.0) updated BIOS to F09. The latest BIOS version is F05 for MW34-SP0 (1.0). If there is any problem while using the product, please contact your supplier (where you bought this product) and let them help you to do further examination.
Well I am running F09 on 1.0 now, guess I will not be able todo anymore BIOS updates. Kind of wish I never bought this motherboard.