Does anyone know what underlying OS components are needed, to be able to manually run a BIOS update package downloaded from support.dell.com? For example, I've got two NFS-root bootable images, both based on RHEL 7.3, using the same kernel/initrd. I've got one image, which I want to use to update BIOS Firmware, etc., but I get this (excerpt):
> [root@m7stage-1-2 ~]# ./BIOS_VCKYF_LN_2.5.2.BIN -f -q > Collecting inventory... > ... > > Executing update... > WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER PRODUCTS WHILE > UPDATE IS IN PROGRESS. > THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! > . > Enough contiguous physical memory is not available to perform the BIOS > update running under this Operating System. Reboot and try again. > > [root@m7stage-1-2 ~]# But when I boot the same node onto the other image, it works (excerpt) > [root@m7stage-1-2 ~]# ./BIOS_VCKYF_LN_2.5.2.BIN -f -q > ... > Executing update... > WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER DELL PRODUCTS WHILE > UPDATE IS IN PROGRESS. > THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! > ............................................................................................ > The system should be restarted for the update to take effect. > [root@m7stage-1-2 ~]# The obvious question is, "well, what's different between the two images?" To which I can only say ... "a whole lot." That's the point. I'm hoping for some guidance here. So far, I'm comparing kernel module list (lsmod output), as well as RPM package lists (eg. rpm -qa | sort), but I'm having trouble isolating the critical difference, among all the long list of differences. -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
