Нашёл в просторах интернета интересную утилиту от American Megatrends (AMIBIOS). Правит DMI зону на ноутбуках и настольных компьютерах. Сам использовал для правки серийников на Asus N53JQ (MAC не правит). Версия 1.25.
https://ami.com/products/bios-uefi-tool
… utilities/
Desktop Management Interface Edit (DMIEdit)
DMIEdit is a scriptable command line utility for DOS, Microsoft Windows®, Linux and the UEFI shell. The Desktop Management Interface Editor for Aptio enables developers to modify strings associated with platform SMBIOS tables (System, Base Board, Chassis, OEM string, etc). In manufacturing, use DMIEdit to embed platform serial numbers, UUID and license keys into the SMBIOS table, which identifies platforms to management software.
Supported Products:
Aptio V
Aptio 4
AMIBIOS 8
Utilized on the manufacturing line and for system provisioning, DMIEdit™
is designed to modify platform-specific data located in the SMBIOS data
structures on a computer’s Read-only Memory (ROM) chip:
•
System (Type 1)
•
Base Board (Type 2)
•
Chassis (Type 3)
•
OEM String (Type 11)
•
System Configuration Options (Type 12)
The SMBIOS data tables store platform specific information such as serial
numbers, Universally Unique Identifier (UUID), asset tags, sensor data
and any other information detailed by the System Management BIOS
Specification. The tables provide a standardized information database for
higher level platform management structures.
The SMBIOS specification is published by the Distributed Management Task
Force, an industry organization that gathers hundreds of industry players
and organizations to define the basic management structures supporting
interoperability among systems from different vendors.
The DMTF undertook the first desktop management standardization
effort by publishing the Desktop Management Interface (DMI) in 1994,
and subsequently absorbed the DMI BIOS, a joint effort between BIOS
vendors and system vendors. The SMBIOS specification was published
in 1999. SMBIOS does not completely supplant DMI, but in practice the
enumerations of various values within the SMBIOS tables are identical to
the corresponding value maps in DMI groups and Common Information
Model (CIM) classes.
The SMBIOS specification is now at version 2.5. SMBIOS tables are utilized
by many DMTF defined management structures, such as the Common
Information Model (CIM) and the Desktop and mobile Architecture for
System Hardware (DASH) initiative. DASH will completely supplant DMI
going forward.
AMI’s DMIEdit utility enables OEM manufacturers to change SMBIOS
data after the BIOS has already been flashed, in order to equip different
production batches or systems with appropriate information.
DMIEdit does not run on the ROM image prior to flashing; it’s actually
stored in the “general purpose non-volatile” (GPNV) section of the system
flash part.
AMI markets three versions of the DMI utility, which fit different production
environments. AMIDEDOS, AMIDEWIN and AMIDELINUX provide command
line and script input methodology for Microsoft® DOS, Windows® and
Linux, respectively.
DMIEdit is an easy-to-use Windows GUI utility that displays the complete
list of SMBIOS data, names and types. The user will effortlessly modify the
SMBIOS data and write the updated information on the BIOS ROM chip.
У вас нет доступа для просмотра вложений:
1. Пожалуйста авторизуйтесь или зарегистрируйтесь.
2. Вы должны иметь 15 (ПЯТНАДЦАТЬ) или более сообщений.
3. У нас можно купить доступ к файлам.
Soon after setting up fancy new asset management tool you realized that all your clone PCs show up with identical info. Fixable, but requires a lot of work. One more reason to go with name brand instead.
Everything below comes from ubcd4win.com forum and is written by member named Jotnar. I’m duplicating it here so I can find it quickly myself when needed and just in case that forum post disappears in future.
—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—8<—
The ASUS boards all had an AMI BIOS and you need DMI editing tools specific to that vendor (AMI) in order to set the asset tags. IBM/Lenovo are kind enough to include them in their BIOS packages so it was just a matter of finding out which ones had which tools.
AMI has two main DOS tools to do the editing: DMI_BXX.EXE (older) and AMIDEDOS.EXE (newer). Depending on the age of your motherboard one might work better than the other.
DMI_B44.EXE
==================== DMI Editor V2.00.44 ======================= Usage : dmi_b44 </p|/s|/u|/a|/g|/n|/o|/sco # String> /p : get DMI using PnP functions /s : get DMI using memory search /u : set UUID /g : get informations in Type 1 and 2 /n : set Type 1 and 2 using the data which get from parameter /g /o # : set #th OEM String in Type 11 /sco # : set #th String of System Configuration Options in Type 12 /iv : setup BIOS Version in Type 0 /sm : setup Manufacturer in Type 1 /sp : setup Product Name in Type 1 /sv : setup Version in Type 1 /ss : setup Serial Number in Type 1 /sk : setup SKUNumber in Type 1 /sf : setup Family in Type 1 /bm : setup Manufacturer in Type 2 /bp : setup Product Name in Type 2 /bv : setup Version in Type 2 /bs : setup Serial Number in Type 2 /cm : setup Manufacturer in Type 3 /cv : setup Version in Type 3 /cs : setup Serial Number in Type 3 /ca : setup Asset Tag Number in Type 3 /co : setup OEM-Defined data(Hexadecimal) in Type 3 Example: dmi_b44 /ss 012345678 ---- set serial number(Type 1) to "012345678" dmi_b44 /cm "AMI" ---- set manufacture(Type 3) to "AMI"
Get it here: http://download.leno…ios/42j947a.iso
It’s in the floppy emulation boot sector image
AMIDEDOS.EXE
+---------------------------------------------------------------------------+ | AMIDEDOS - AMIBIOS DMI Editor for DOS | | Copyright (C)2008 American Megatrends Inc. All Rights Reserved. Ver.1.32 | +---------------------------------------------------------------------------+ | Usage: AMIDEDOS <DMS File Name> | | Or | | AMIDEDOS <Command> | | Or | | AMIDEDOS [Option1] [Option2]... | | ------------------------------------------------------------------------- | | Commands: | | --------- | | /ALL [FileName] Output SMBIOS stringd to screen/file. | | /DMS [FileName] Create configuration file. | | /DUMP # [#] [#]... Read Type # data. | | /DUMPALL [FileName] Output all SMBIOS data to screen/file. | | | | Options: | | -------- | | /IV ["String"] Read/Write BIOS version in Type 0. | | /ID ["String"] Read/Write BIOS release date in Type 0. | | /SM ["String"] Read/Write System manufacture in Type 1. | | /SP ["String"] Read/Write System product in Type 1. | | /SV ["String"] Read/Write System version in Type 1. | | /SS ["String"] Read/Write System Serial number in Type 1. | | /SU [16 Bytes] Read/Write System UUID in Type 1. | | /SU AUTO Generates system UUID automatically and update Type 1. | | /SK ["String"] Read/Write System SKU number in Type 1. | | /SF ["String"] Read/Write System family in Type 1. | | /BM ["String"] Read/Write Baseboard manufacture in Type 2. | | /BP ["String"] Read/Write Baseboard product in Type 2. | | /BV ["String"] Read/Write Baseboard version in Type 2. | | /BS ["String"] Read/Write Baseboard Serial number in Type 2. | | /BT ["String"] Read/Write Baseboard Asset Tag in Type 2. | | /CM ["String"] Read/Write Chassis manufacture in Type 3. | | /CT [1 Byte] Read/Write Chassis type in Type 3. | | /CV ["String"] Read/Write Chassis version in Type 3. | | /CS ["String"] Read/Write Chassis Serial number in Type 3. | | /CA ["String"] Read/Write Chassis Tag number in Type 3. | | /CO [4 Bytes] Read/Write Chassis OEM-defined value in Type 3. | | /OS [<Number> <"String">] Read/Write OEM string in Type 11. | | /SCO [<Number> <"String">] Read/Write Sys. Configuration Op. in Type 12.| | | | Note: | | 1. The expression enclosed by <> means it is a mandatory field. | | 2. The expression enclosed by [] means it is an optional field. | | 3. A command without parameter means it is a read command. | | 4. A command with necessary parameter means it is a write command. | +---------------------------------------------------------------------------+
Get it here: http://download.leno…s/5ojt33usa.zip
Before:
Manufacturer: System manufacturer Model: System Product Name Serial Number: Chassis Serial Number Asset Tag: Asset-1234567890 Motherboard: ASUSTeK Computer INC. PXX Motherboard Serial: ASUS-123456789
After:
Manufacturer: White Box Manufacturer Model: White Box Model Serial Number: White Box Serial Number Asset Tag: AssetTag Motherboard: ASUSTeK Computer INC. PXX Motherboard Serial: XXXXXXXXXXXXXX **Tools and Commands to Set Asset Tags** BIOS Manufacturers AMI DMI20_44.EXE /ca "Asset Tag" AMIDEDOS.EXE /CA "Asset Tag" AMIDEWIN.EXE /CA "Asset Tag" AMIDELNX /CA "Asset Tag" DMIDOS.EXE /ca "Asset Tag" DMIEDITEFI.EFI /ca "Asset Tag" DMIEDITWPE.EXE /ca "Asset Tag" DMIEDIT.EXE (WINGUI Tool) Phoenix SMBCFG.EXE /type 03 08 "Asset Tag" SMBCFG32.EXE /type 03 08 "Asset Tag" PHLASH16.EXE /DPC "Asset Tag" /MODE=1 SFLASH16.EXE /DPC "Asset Tag" /MODE=1 WINPHLASH.EXE /DPC "Asset Tag" /MODE=1 WINPHLASH64.EXE /DPC "Asset Tag" /MODE=1 *Note for the PHLASH16/SFLASH/WINPHLASH Tools: You need the BIOS file in order for this to work. Award DMICFG.EXE /type 03 08 "Asset Tag" SMBCFG.EXE /type 03 08 "Asset Tag" SMBCFG32.EXE /type 03 08 "Asset Tag" Insyde FLAS-HIT.EXE /D 03 08 "Asset Tag" *Note that this only works for some versions of FLAS-HIT. This is from V6.06.05 (10/31/07) (Really from 2009). PC/Motherboard Manufacturers Acer DMITOOLS.EXE /wa "Asset Tag" Asus DMICFG2.EXE (GUI Tool) DMIFLASH.EXE /T0308:"Asset Tag" (/T0304?) AFLASH2.EXE /DPC:"Asset Tag" Compal DMI.EXE /WA "Asset Tag" DMITOOLS.EXE /WA "Asset Tag"" Compaq CPQTAG.EXE modify asset "Asset Tag" Modify in BIOS Settings HP CMI and VBscript (Maybe?) Dell Desktops ASSET209.COM "Asset Tag" Modify in BIOS Settings OMCI and VBScript Dell Laptops ASSETQNT.EXE /A:"Asset Tag" ASSET.EXE "Asset Tag" ASTAG.EXE /w "Asset Tag" FASSET.EXE "Asset Tag" ASSTASUS.EXE "Asset Tag" Modify in BIOS Settings OMCI and VBScript Dell Servers (EFI) ASSET.EFI -a "Asset Tag" Modify in BIOS Settings OMCI and VBScript Fujitsu SERIALNO.EXE ChAT.write="Asset Tag" HP BCMDMI.EXE /CA "Asset Tag" Modify in BIOS Settings HP CMI and VBScript IBM EXTRMDMI.EXE asset "Asset Tag" DDMI.EXE --type=03 --offs=08 "Asset Tag" Intel OEMDMI.EXE /CA "Asset Tag" OEMDMI2.EXE /CA "Asset Tag" ITOOKIT.EXE install -smbios -ini=DMI.INI DMI.INI [System] INIVersion=2.7 [SMBIOS.Values] ChassisAssetTag=$PROMPT$, Enter Chassis Asset Tag VARDMI.EXE /VAR dmiinfo.txt dmiinfo.txt [CHASSIS INFORMATION] AssetTagNumber=Asset Tag VARDMI2.EXE /VAR dmiinfo.txt dmiinfo.txt [CHASSIS INFORMATION] AssetTagNumber=Asset Tag NEC DMISS2.EXE /pc "Asset Tag" Panasonic AssetTag.exe Pegatron SU.EXE -type 3 /WRDMI 08 "Asset Tag" WDMI.EXE /CA "Asset Tag" Quanta MFGSMB -Q -CA "Asset Tag" MPRW.EXE /Wasset "Asset Tag" QDMI30A.EXE (GUI Tool) Sony SONYDMI.EXE /T0308:"Asset Tag" (/T0304?) Toshiba ASSETTAG.EXE /SA "Asset Tag" DMIRED.EXE /CA "Asset Tag" SMB268.EXE /CAT "Asset Tag" So that should cover most everything. Most tools need to run from DOS (as in a bootable floppy or USB key). The ones that run under Windows should be rather easy to figure out since they usually have a "W", "WIN" or "32" in the name. If the PC/Motherboard manufacturer specific tools don't work then the generic BIOS manufacturer tools might. If it still doen't let you set the Asset Tag, make sure you're running the latest version of the BIOS for the machine. My whitebox with the Phoenix BIOS wouldn't let me update the Asset Tag field until I'd updated the BIOS (I guess one of the fixes was to make that field writable). As to where to find these tools? They come with some (not all) of the BIOS updates that the manufacturers put out. They might also be found on the manufacturer's ftp sites or provided on the discs that come with your system or motherboard. --8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--
Новичок
Зарегистрирован: 08.10.2019
Пользователь #: 172,307
Сообщения: 4
Источник
Smbios 0x16 error supermicro
Профиль | Отправить PM | Цитировать
Добрый день, появилась такая проблема.
Есть сервак, при перезагрузке из-под винды, сервак не хочет стартовать, пищит (5 коротких, 1 длинный), а на экране Intel Reference Code Execution с кодом 02. Судя по бипам — проблемы с памятью. Однако с кнопки ресета всё стартует норм., далее постоял 2 часа и завис. Конфигурация следующая:
— Supermicro X11SSL-F (2 PCI-E x8, 1 PCI-E x16, 4 DDR4 DIMM, Video, Dual Gigabit LAN);
— QuadCore Intel Xeon E3-1240 v5, 3700 MHz (37 x 100);
— 2хKingston 8GB DDR4 PC4-17000 [KVR21E15D8/8];
— Два зеркала на встроенном контроллере Intel.
Перезагружался, т.к. устанавливал последние обновления от MS за сентябрь. ОС — 2008R2. Здесь аналогичная проблема, только память другая. Также натыкался ещё на несколько подобных случаев. Снёс все установленные обновы (кроме обновки для ie11), а именно: KB3184471, KB3177186, KB3175024, KB3184122, KB3185911. И всё ребутнулось успешно. Кто-н имел дело с похожим?
Судя по бипам — проблемы с памятью. »
——-
ВНИМАНИЕ ознакомьтесь, прежде чем создать тему! Процессор — мозг компьютера, блок питания — сердце и печень.
Это сообщение посчитали полезным следующие участники:
Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.
Smbios 0x16 error supermicro
Профиль | Отправить PM | Цитировать
Добрый день, появилась такая проблема.
Есть сервак, при перезагрузке из-под винды, сервак не хочет стартовать, пищит (5 коротких, 1 длинный), а на экране Intel Reference Code Execution с кодом 02. Судя по бипам — проблемы с памятью. Однако с кнопки ресета всё стартует норм., далее постоял 2 часа и завис. Конфигурация следующая:
— Supermicro X11SSL-F (2 PCI-E x8, 1 PCI-E x16, 4 DDR4 DIMM, Video, Dual Gigabit LAN);
— QuadCore Intel Xeon E3-1240 v5, 3700 MHz (37 x 100);
— 2хKingston 8GB DDR4 PC4-17000 [KVR21E15D8/8];
— Два зеркала на встроенном контроллере Intel.
Перезагружался, т.к. устанавливал последние обновления от MS за сентябрь. ОС — 2008R2. Здесь аналогичная проблема, только память другая. Также натыкался ещё на несколько подобных случаев. Снёс все установленные обновы (кроме обновки для ie11), а именно: KB3184471, KB3177186, KB3175024, KB3184122, KB3185911. И всё ребутнулось успешно. Кто-н имел дело с похожим?
Судя по бипам — проблемы с памятью. »
——-
ВНИМАНИЕ ознакомьтесь, прежде чем создать тему! Процессор — мозг компьютера, блок питания — сердце и печень.
Это сообщение посчитали полезным следующие участники:
Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.
Источник
SuperMicro X10SL7-F
grep137
Dabbler
Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).
I ran Memtest86+ 5.01 for 17 hours on the default settings and it found no errors. However, when I looked at the Event Logs in the BIOS it showed (see below). I’ve only had the machine powered on fewer than 10 times (on for only 1 — 5 hours each time, except for the 17 hour memtest) since I put it together. Is this normal, or is DIMMA1 faulty?
DATE: | TIME: | ERROR CODE: | SEVERITY: | DESCRIPTION:
05/05/14 | 01:20:30 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 03:08:27 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 06:48:06 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 09:34:40 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/18/14 | 11:48:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/15/14 | 11:32:58 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/22/14 | 15:21:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0
Sir.Robin
Where are you getting your memory, if you don’t mind me asking?
Sent from my iPad using Tapatalk
I have Kingston for my primary system. My secondary will run on Crucial ECC initially. Might exchange that later.
Have you checked CPU then? Bent pins?
Sir.Robin
Ziferius
Dabbler
Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).
I ran Memtest86+ 5.01 for 17 hours on the default settings and it found no errors. However, when I looked at the Event Logs in the BIOS it showed (see below). I’ve only had the machine powered on fewer than 10 times (on for only 1 — 5 hours each time, except for the 17 hour memtest) since I put it together. Is this normal, or is DIMMA1 faulty?
DATE: | TIME: | ERROR CODE: | SEVERITY: | DESCRIPTION:
05/05/14 | 01:20:30 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 03:08:27 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 06:48:06 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 09:34:40 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/18/14 | 11:48:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/15/14 | 11:32:58 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/22/14 | 15:21:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0
Interesting. That seems like an aweful lot, but that’s why we run ECC. it catches and fixes that.
Cyber jock is definitely proved right (yet again) why ECC is so important.
Источник
Supermicro BMC watchdog-caused reboots
I’ve recently acquired a SuperMicro X10SLL-F motherboard, which has a built-in BMC (Aspeed AST2400 chip). I want to use built-in watchdog controller when running linux on server (gentoo hardened).
I enabled watchdog function in bios then switched motherboard jumper from hard-reset to NMI (watchdog timeout action, for testing purposes to avoid rebooting). About soft — I installed and added to default runlevel watchdog program (sys-apps/watchdog) which is configured to ping watchdog device (/dev/watchdog, which is present) every 10 seconds. Watchdog timeout is set to 250 seconds.
Programs apparently see watchdog hardware (ipmitool with openipmi enabled):
However, after certain amount of time I get (with good «current countdown» values reported by programs above):
Which is NMI, apparently caused by watchdog timeout. Little less than a minute after that machine hard-reset happens.
Where is a problem and which direction should I dig to?
EDIT: kernel messages related to ipmi:
EDIT: I tried to use bmc-watchdog with configuration «-u 4 -p 2 -a 0 -F -P -L -O -i 300 -e 10». So only SMS/OS time is in use, pre-timeout interrupt is set to NMI, timeout action is set to NONE:
But this led to no change at all.
EDIT. Also when I trigger watchdog timer with echoing x00 to /dev/watchdog and then kept it untouched — system is correctly rebooted after default 10 second timeout. So watchdog works good but at exactly 350 seconds from startup system reboots.
EDIT. I checked BMC system event log (SEL) and found this after reboot:
What is interesting here — is that event marked as «status only». And even so, system is rebooted. When I trigger watchdog timeout intentionally, logs are different:
Источник
Adblock
detector