Location of Force_PXE_Enable token on various Dell servers

Jordan_Hargrave at Dell.com Jordan_Hargrave at Dell.com
Wed Aug 1 15:23:25 CDT 2007


Try using token 0x4022 for enabled and 4023 for disabled.

--jordan hargrave
Dell Enterprise Linux Engineering



-----Original Message-----
From: libsmbios-devel-bounces at lists.us.dell.com on behalf of Plead Insanity
Sent: Wed 8/1/2007 2:51 PM
To: libsmbios-devel at lists.us.dell.com
Subject: Location of Force_PXE_Enable token on various Dell servers
 
Hi,

I'm working on developing an automatic server deployment system for our
datacenter.  To that end it would be extremely handy to be able to
access the 0x0093 token (Force_PXE_Enable) which provides the following
functionality:

"The next time the BIOS boots the system, the first PXE-capable device is inserted as
the first device in the boot sequence.  Enabling this value causes this
operation on the next boot only, and does not cause a change in the
system's defined boot sequence.  The BIOS chooses the first PXE-capable
device as the system's onboard network controller, if present and
enabled, or the first bootable network device found in the system's
standard PCI search order â?" whichever comes first."

But, I've found that this only works on certain types of Dell Hardware.
Is it possible that this particular token was moved to another location
on certain hardware and if so, do you happen to know where, or how I can
find out?

Cheers,

-Jay



On a Dell Dimension 3100:

# /usr/sbin/getSystemId
Libsmbios:    0.12.1
System ID:    0x01C4
Service Tag:  ******
Express Service Code: ******
Product Name: Dell DV051
BIOS Version: A04
Vendor:       Dell Inc.
Is Dell:      1

# /usr/sbin/tokenCtl --token 0x0093
This binary is not completed or fully debugged.
 Please do not use this unless you are working on finishing it. :-)

 Token ID: 0x93
 Is Active: yes


On a PE SC430:

# getSystemId 
Libsmbios:    0.13.6
System ID:    0x01AE
Service Tag:  *****
Express Service Code: *****
Product Name: PowerEdge SC430
BIOS Version: A02
Vendor:       Dell Inc.
Is Dell:      1

#  tokenCtl --token 0x0093
This binary is not completed or fully debugged.
 Please do not use this unless you are working on finishing it. :-)

 Token ID: 0x93
 Is Active: no
 

On a Dell PowerEdge 860:

# getSystemId
Libsmbios:    0.13.6
System ID:    0x01E6
Service Tag:  ******
Express Service Code: ******
Product Name: PowerEdge 860
BIOS Version: A03
Vendor:       Dell Computer Corporation
Is Dell:      1


# tokenCtl --token 0x0093
This binary is not completed or fully debugged.
 Please do not use this unless you are working on finishing it. :-)

Token ID: 0x93

An Error occurred. The Error message is: 
    tried to dereference non-existent token

Problem reading or writing tag. Common problems are:
    -- Password-protection in the BIOS.
       Try using the '--password' option to specify the BIOS setup password.

    -- Insufficient permissions to perform operation.
       Try running as a more privileged account.
          Linux  : run as 'root' user
          Windows: run as 'administrator' user

    -- dcdbas device driver not loaded.
       Try loading the dcdbas driver
          Linux  : insmod dcdbas
          Windows: dcdbas driver not yet available.

(the dcdbas driver is statically compiled in, and querying other memory
locations is working fine).


On a Dell Poweredge 2950:

# getSystemId 
Libsmbios:    0.13.6
System ID:    0x01B2
Service Tag:  ******
Express Service Code: ******
Product Name: PowerEdge 2950
BIOS Version: 1.3.7
Vendor:       Dell Inc.
Is Dell:      1

# tokenCtl --token 0x0093
This binary is not completed or fully debugged.
 Please do not use this unless you are working on finishing it. :-)

 Token ID: 0x93

 An Error occurred. The Error message is: 
     tried to dereference non-existent token

_______________________________________________
libsmbios-devel mailing list
libsmbios-devel at lists.us.dell.com
http://lists.us.dell.com/mailman/listinfo/libsmbios-devel



More information about the libsmbios-devel mailing list