Question How to get MAC ADDRESSES on PCB

Apr 26, 2023
6
0
10
Hi all,
I missing the label on pcb.
How to get mac id on pcb by the other way?
My mb is x99 extreme4 asrock.
I need writter mac id to fix error.

9acd648d9fc9e1383f00bbad11d58b2cc16563c1.jpeg


aa7414814aaec14bc630756b0737ca9fec904706.jpeg
 
Assuming you are running windows, open a command prompt and type:
Code:
ipconfig /all
It should show a list of all your network adapters along with their physical addresses.

If you changed your mac address, either on the network adaptor or via the windows registry, then see this article for how to recover your original mac address:
 
Last edited:
Assuming you are running windows, open a command prompt and type:
Code:
ipconfig /all
It should show a list of all your network adapters along with their physical addresses.

If you changed your mac address, either on the network adaptor or via the windows registry, then see this article for how to recover your original mac address:
I already write physical network but it not success. Because using win7, almost this way no effect my issue.
 
The OS shouldn't have any role when it comes to physical network address. Maybe the bios battery are dead.
It does. Some network adapters have no mac address, it's assigned by the OS. Some adapters have a mac address that can be altered. While yet other have one, that can't be changed, but a copy taken on first discovery by the OS, then used by the OS and the copy may be changed by the OS.

In windows the physical address is stored in the registry, and it is the registry entry that is reported by ipconfig. And users or apps can change the address in the registry. It's been a while since I looked into this and I am too lazy to test it atm.

Ie. use this and scan for registry change when I use the Rename method:

Or check this one for Linux:

Or this one:
 
Last edited:
Typically the MAC address is programmable in the NIC itself, and having something like the MAC address tied to volatile memory is a bad idea.

Not really sure what the thing is complaining about, though a casual glance at the interwebs tells me this message sometimes pops up after a BIOS update.