A detour about the methodology in programming
(Sorry for a detour, which follows, but I think I had to make it.)
You're attacking your problem from a wrong angle. Programming is not about finding a random package, trying it, seeing it failing and turning for help; it's rather about inventing a general approach to solving the problem at hand and then trying to figure out what are there to solve it.
For instance, in your case, it might easily be not fruitful to search for "BIOS+information+golang" because it's too narrow.
Instead, try to figure out
- How to get any information about a system on Windows.
- How to do that in Go.
While this is boring, I have to recommend reading this seriously: this will really help you getting your future programming challenges solved.
The problem at hand
OK, now back to your problem.
On Windows, the standard way to obtain information about a system is querying the so-called Windows Management Instrumentation (or WMI for short) subsystem.
Once you know this, you should dig into these two directions:
What WMI calls do you need to perform to get the information which is of interest to you.
This one is easily searcheable. The first hit I got doing that is this which I'd say is a pretty good start.
How to do WMI calls from Go.
This one can be done in two ways:
So, if I were you, I'd first code up whatever the WMI calls suit my needs using VBS or JScript (or whatnot) on WSH and then "ported" that solution to Go using any of the described approaches.