This is the utility HP service technicians use to burn system information to the motherboard. It’s called Rufus, and it quickly and easily makes bootable flash drives, which is how we are going to run the HP tattooing utility. It’s not too difficult, though.īefore you try the method below, see if this method works first, because it is less of a headache to deal with. I have found a way to do it yourself, although it does require a little finesse and following directions. HP says the only way to fix this issue is to pay a technician to repair the issue. This happens when a motherboard loses the information that’s “tattooed” onto it, or burned onto it.
CHANGE MOTHERBOARD SERIAL NUMBER HOW TO
How to Fix “System Board OOA” or “Missing System Information” or “Product Information Not Valid” HP If you found this information useful, you can subscribe to my blog (click at the “follow” button at the bottom) to be notified of new posts.I tried this on an HP DV6 1152tx notebook and it worked. Next time my ancient Linux box starts acting up I will be ready :-).
CHANGE MOTHERBOARD SERIAL NUMBER MANUAL
Let’s have a look at the available –type values:ĭmidecode: option '-type' requires an argumentĪs you see we can get information on various components of the system.Īnyway, having found out my original motherboard model, I could google for information about the beep codes, or download the specific motherboard manual from the Gigabyte‘s site. If I had wanted instead to print all the information regarding the motherboard I could have used the –type switch. I was not only interested in information about the motherboard, but the only thing that I cared about was the specific model. Notice that in this example I queried the system for very specific information. If I am looking for the motherboard model the string I need to use is baseboard-product-name:ĭmidecode -string baseboard-product-name Run –string without any arguments to find the possible string values:ĭmidecode: option '-string' requires an argument V, -version Display the version and exitįrom the above options the ones of interest if we want to query the system for a specific item (memory, motherboard, cpu, etc) are –string, and –type. from-dump FILE Read the DMI data from a binary file dump-bin FILE Dump the DMI data to a binary file
t, -type TYPE Only display the entries of given type s, -string KEYWORD Only display the value of the given DMI string h, -help Display this help text and exit d, -dev-mem FILE Read memory from device FILE (default: /dev/mem) If we run the dmidecode with the –help switch, though, we will find ways to check for more specific information: Running the dmidecode command on the console produced an extended amount of information, including the mother board model – which was what I was trying to find out. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. This will often include usage status for the CPU sockets, expansion slots (e.g. This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. One of such programs is dmidecode dmidecode reports a variety of information about the system hardware:ĭmidecode reports information about your system’s hardware as described in your system BIOS according to the SMBIOS/DMI standard. I needed to find out what the beep codes of the BIOS stood for, and for that I needed to know my motherboard model … I knew it was a Gigabyte, but I could not remember the exact model.Īn easy way to find out my exact memory board model would be to simply open the case and look at the sticker in the motherboard:-) Even easier would be to use one of the many programs available for Linux that query the system for hardware information. It would be a good idea, therefore, to do some research to be prepared if it happens again. Still this incident got me thinking: the beeping was warning me of some kind of issue with the hardware that might reappear soon, it is an old machine after all, and hardware failures are to be expected at some point. Luckily, after a few tries my computer wound up booting up and as of today it works flawlessly. This week my old Linux box refused to boot: for a few times when clicking the power button, I was confronted with a black screen and an annoying beeping.
0 kommentar(er)
