Binary Buddha
Contributor
- Joined
- Mar 6, 2016
- Messages
- 126
Caveat: I'm noob at working with motherboards like this!
So I just upgraded my motherboard from an MSI X58M to a Supermicro MBD-X9SRH-7F-O.
Now I'm not able to reach it via network once completed booting. I keep getting the following splashing the crap out of the monitor before and after I login via console..
So the first question is... how do I make AFP stop splashing the crap out the display so I can see what I'm doing.
The second question is... Is there some funny network config thing I need to do now that I switched motherboards? I know in the GNU Linux world the static network configs are tied to mac addresses. FreeNAS doing the same thing somewhere?
I've tried rebooting it a couple times hoping the OS would default the NIC1 to DHCP or something.
Don't know if it's related, but somehow the board itself has an IP that leads to some supermicro login to something. I'm assuming it's that IPMI thing.
So I just upgraded my motherboard from an MSI X58M to a Supermicro MBD-X9SRH-7F-O.
Now I'm not able to reach it via network once completed booting. I keep getting the following splashing the crap out of the monitor before and after I login via console..
Code:
afpd No suitable network config for TCP socket afpd main: No servers configured
So the first question is... how do I make AFP stop splashing the crap out the display so I can see what I'm doing.
The second question is... Is there some funny network config thing I need to do now that I switched motherboards? I know in the GNU Linux world the static network configs are tied to mac addresses. FreeNAS doing the same thing somewhere?
I've tried rebooting it a couple times hoping the OS would default the NIC1 to DHCP or something.
Don't know if it's related, but somehow the board itself has an IP that leads to some supermicro login to something. I'm assuming it's that IPMI thing.
Last edited by a moderator: