Issue: Unable to use
Dell Command | Configure after reinstallation/upgrade
Description: Dell command | Configure may not work after reinstallation/upgrade
on Ubuntu Desktop 16.04 because
dcdbus module may not be loaded
during reinstallation.
Resolution: Load the module
by running the following command:
insmod <filename>
Issue: Windows 7 does
not recognize the digital signature validity
Description: If the system is not connected to internet, Windows 7 does not recognize
the digital signature validity of Dell Command | Configure installation
file.
Resolution: Connect the system to internet
and validate the digital signature.
Issue: BIOS interface
not found
Description: While running Dell Command |
Configure, the following error message might be displayed:
BIOS
Interface not found
.
Resolution: Uninstall
HAPI using the
hapiuninstall.bat script available in the
HAPI folder, and install it again using the
hapiinstall.bat script available in the same folder.
Issue description:
Do not use the infile or outfile options in the .ini file.
Issue description:
Dell Command | Configure supports only single-byte characters for
asset set operation.
Resolution: If the user has a
different locale, change the keyboard layout to English before using
the asset option.
Issue: TPM related
tokens can be modified independently
Description: Dell
Command | Configure does not control the dependencies among the various
TPM PPI option. For example, it is possible to change the
TPM PPI
ACPI
option through Dell Command | Configure even when TPM is
not
On.
-
NOTE: There is no negative impact due to this on the BIOS.
Issue: Dependent options
are not working as configured in UEFI mode for for Legacy Option ROM
and Secure Boot
Description:
- Dell Command | Configure allows enabling Legacy Option
ROM when Secure Boot is On.
- Dell Command | Configure allows disabling Legacy Option
ROM when Boot mode is Legacy.
- Dell Command | Configure allows enabling Secure Boot
when Legacy option ROM is enabled and boot mode is UEFI.
- Dell Command | Configure does not allow enumerating
Secure Boot when it is disabled.
-
NOTE: There is
no negative impact due to this on the BIOS. This issue will be addressed
in the upcoming BIOS versions.
Issue: Blinkpsu1led
and Blinkpsu2led missing in the .ini file or SCE
Description: Blinkpsu1led and Blinkpsu2led will not be present in the .ini file
or SCE as they are enable-only tokens and they are active only for
few seconds. These tokens cannot be modified using GUI.
Issue: advsm option
displays the status as Other
Description: If any of the fans
is not working, the advsm option displays the status as
Other.
Issue: Advance Battery
Charge and Peak Shift Charge options display Disable
Description: Platforms that do not support Advance Battery Charge option, when
advbatterychargecfg option is enumerated, the system displays the
option as Disable.
Platforms that do not support
Peak Shift Charge option, when
peakshiftcfg option is
enumerated, the system displays the option as
Disable.
Issue: Temperature
probe in Advanced System Management option displays as Unknown
Description: On some platforms that support
Advanced System
Management
option, temperature probe of all the sensors displays
as
Unknown.
-
NOTE: This issue will be addressed in the upcoming BIOS versions.
Issue: On some of the
platforms that support Advanced System Management option, temperature
probe of Memory sensor 2 displays the current status as Non-Critical
instead of Normal.
-
NOTE: This issue is addressed
in the upcoming BIOS versions.
Issue: On some of the
platforms that support Advanced System Management option, when you
set non-critical upper threshold values for cooling device, the CLI
indicates that the action failed; however, setting the same is successful.
Issue: Unable to configure
ASM (advsm) BIOS options in .ini file/SCE
Description: While configuring ASM (advsm) option using .ini file, or SCE, Setup
password or System password should not be set or modified.