• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.

‎03-07-2017 02:27 PM

HP Recommended
Product: HPE ProLient ML10 GEN 9
Operating System: Other

Trying to setup a HPE ProLient MS10 Gen 9 system.  The AMI Aptio (UEFI) Setup Utility, v2.17.1254, is configured as follows:

 

Advanced
    Network Stack Configuration (UEFI)
        disabled
        enabled (Preboot Execution Environment  - followingnot optioned if disabled)
            Ipv4 PXE support (enable/disable)
            Ipv6 PXE support (enable/disable)
            PXE boot wait time
            Media detect count

    CMS Configuration (Compatibility Support Module Configuration)
        CMS Support (enable/disable)
        CMS16 module version 07.79 (static)
        Boot option filter
            Legacy only
            UEIF only

    WHEA (Windows Hardware Error Architecture Support) disabled
    
    CPU configuration (many options here)
        Hyper-threading disabled

 

 

OS is FreeBSD v10.1 (and previous versions). . .have been working for 15 years+ on BIOS booting system.  OS does boot under CMS legacy mode.  Problem is ifconfig (FreeBSD command line utility)does NOT recognize and/or report the onboard NIC.  All services that require ethernet interface will not/can not communicate via the NIC -- no DNS, NTP, SMTP/POP3,  SSH, etc. 

 

I have read from other HP web pages that this is because a "driver" is not installed.   Well, Drivers are installed in the FreeBSD kernel, so where else should such a dirver be installed?   AMI is no help . . ."not my problem, contact HP".  HP is virtually impossible to contact. 

 

System is unsuable.  What to do?

(Not sure that thisis the best board for help, but only option from the list.)

 

1 REPLY 1

‎03-07-2017 04:49 PM

HP Recommended

Hi:

 

You may also want to post your question on the HPE Community Support Forum -- ML Servers section...

 

https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264#.WL9G8-QzXGg

Was this reply helpful? Yes No
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.