AMD Microcode patch error on installing ESXi 5.1

Discussion in 'PC Hardware' started by mrgigo, Sep 15, 2012.

  1. mrgigo

    mrgigo MDL Novice

    Sep 15, 2012
    2
    0
    0
    #1 mrgigo, Sep 15, 2012
    Hi Folks,

    I'm new to the forum, so before posting a mod request to the AMI section, I thought I would bounce this off everyone in the hardware section.

    I have an Inventec server ISR1300-2F-2210. It is running dual processors. The two processors are AMD Opteron 2356 Quad-Core CPUs. It has the nVidia NFP3500 chipset It is running AMI BIOS core 08.00.14

    I decided to "re-purpose" the server for an ESXi 5.1 Host.

    When loading ESXi 5.1 I get a purple screen that says I need to update the processor microcode to min patch level 65

    Of course I had no idea what that meant, so I hit google. Apparently, the system BIOS takes care of that. So I searched for BIOS updates. However, InventecESC web site is gone. I cant find any BIOS for this server, anywhere.

    That brought me here.

    If I provide the BIOS ROM file from the server, can this processor microcode patch be "mod'd" into the provided ROM file?


    Thanks-a-many,
    -MrGiGo
     
  2. Michaela Joy

    Michaela Joy MDL Crazy Lady

    Jul 26, 2012
    4,068
    4,649
    150
    #2 Michaela Joy, Sep 16, 2012
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mrgigo

    mrgigo MDL Novice

    Sep 15, 2012
    2
    0
    0
    #3 mrgigo, Sep 16, 2012 (OP)
    Hi Miki,

    Thanks for the welcome.. and.. thanks for the possible lead.. unfortunately the lead did not pan out.

    I read it. I'm not trying anything like what he did. I'm simply placing the ESXi 5.1 CD-ROM in to the server's drive, and attempting to install ESXi to the local hard disk. It doesn't get real far into the install before it halts with the message I must update the CPU's microcode to a min patch level of 65.

    I found a place on the net where "if I were loading RedHat", I could have the OS patch the microcode in a volatile way. BIOS would be more of a non-volatile solution.

    Still hoping for help here,
    -Tom