If that is just an issue of this board and the early implementation of IPMI then no sweat.
If it is something else like “oh KDE just didn’t implement it right” or “to deal with IPMI the interface needs to know it exists and the IP of that” then I think we should follow up on it.
IPMIView is a GUI-based software application that allows administrators to manage multiple target systems through BMC.
I’m not sure yet about setting up the IPs for IPMI. I’ve set them to the loopback at the gateway and 127.0.0.10 as the static address. I can at least ping it now.
Reboot the machine,
On to BIOS
In to page IPMI set address STATIC not dynamic
Enter static address from you network (10.20.30.40/24)
In to BIOS managed first LAN = shared whit IPMI port
Save & Reboot
Plug cable on to IPMI dedicate port and probe ping address
If OK brouser → address
Well in retrospect that was the easiest of things to do.
Set it up in the bios with an IP in your address range.
Stick a network cable between the diagnostic port and the currently used port.
Log on with the browser to that address
Done!
No messing with a second computer needed.
Just as windows user migrating things…
I get into more mess by “research” because the research rarely is for this specific platform or this OS combination. And you fall into a myth of “complexity” that doesn’t actually exist.
It might be possible with a bridge as well. Pretty had to bet the speed of a network cable loop.
Am I to understand that you are only now controlling the fan speeds via IPMI?
Because if so, I must say that I was under the impression that you do and yet your fans are noisy.
It turns out that all the other things are being done, not what is needed.
Have you never used Supermicro IPMI before?