Rahul,
Try the following:
1. Go to:
http://linux.dell.com/repo/community/
And add the dell-community repo by following the instructions on that page.
2. Install the appropriate rpms:
[r...@localhost ~]# yum -y install libsmbios.x86_64
It will pull any dependencies it needs.
3. Load the modules:
*******************************
[r...@localhost ~]# lsmod | grep -Ei 'dell|dcd'
dell_rbu 41569 0
dcdbas 42225 0
*******************************
4. Start the change process.
Of the two values listed below, you have to activate the one that's false, and
it deactivates the one that's true. Here are the settings you get when the
"F1/F2 Prompt on Error":
[r...@localhost ~]# smbios-token-ctl
========================================================================
========
Token: 0x024d - unknown (unknown)
value: bool = true
Desc: unknown
========================================================================
========
Token: 0x024e - unknown (unknown)
value: bool = false
Desc: unknown
========================================================================
========
You can see that 0x024d (enabled) is set to true and 0x024e (disabled) is set
to false. Reboot and check the BIOS to confirm the setting is enabled. To
disable 0x024d you have to enable 0x024e:
********************************************
[r...@localhost ~]# smbios-token-ctl --set-string --token=0x024e --activate
Original Values
type: bool
value: false
Activating token...
New values
type: bool
value: true
********************************************
Then check the settings again:
[r...@localhost ~]# smbios-token-ctl
========================================================================
========
Token: 0x024d - unknown (unknown)
value: bool = false
Desc: unknown
========================================================================
========
Token: 0x024e - unknown (unknown)
value: bool = true
Desc: unknown
========================================================================
========
Next, reboot and make sure the settings take on all the compute nodes.
Thanks!
Brett
-----Original Message-----
From: linux-poweredge-bounces-Lists On Behalf Of Rahul Nabar
Sent: Sunday, February 07, 2010 5:54 PM
To: linux-poweredge-Lists
Subject: R410 stops during boot waiting for a keypress of F1 or F2
On some of my R410 servers the BIOS stops at a message:
"Press F1 to proceed or F2 to enter System Setup"
These are clustered machines so such a message just causes the whole
automated boot process to halt since they don't have a keyboard or
console attached where one presses this key. Is there a way to
automate changing this via sysconfg?
I found no clue in the Dell Deployment Guide. In the BIOS though there
is a setting that chooses whether or not the system halts on the
errors.
--
Rahul
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
