• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

HP 260 G1 - Realtek pcie gbe

Scheduled Pinned Locked Moved
Hardware Compatibility
3
6
2.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    richardh
    last edited by richardh Apr 21, 2016, 6:33 AM Apr 21, 2016, 12:29 PM

    Hi all,

    We are trying to upload a Windows 7 x64 image to Fog (Fog 1.1.2) from a HP 260 G1, however upon pressing F12 and waiting for fog menu to prompt us to register, it doesn’t actually get to the fog menu but just restarts.

    It gets to the point of iPXE Initializing devices … ok

    iPXE 1.0.0+ (1639) etc

    Configuring (net0 mac address). . . . . . and then restarts.

    I’ve read that it could be that the Kernel doesn’t support Realtek PCIE GBE Family Controller Series v2.59 however we have tried to specify different kernels but to no avail.

    Does anyone have any suggestions?

    Any help would be greatly appreciated and thank you in advance.

    Edit FOG works with all other PC’s currently on site and has for years, this is the first time we’ve encountered this problem.

    Richard

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Apr 21, 2016, 12:44 PM

      @richardh Is “Configuring (net0 mac address). . .” the last thing you see? Then it’s not the kernel but iPXE not liking the NIC I suppose. You can try using newer iPXE binaries. Here you find those from FOG 1.2.0: https://svn.code.sf.net/p/freeghost/code/tags/1.2.0/packages/tftp/ and here are the most current ones (using a totally different embedded iPXE script that might cause other troubles for you): https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • R
        richardh
        last edited by Apr 21, 2016, 12:49 PM

        Thanks for the suggestions will certainly give it a go now.

        I noticed something pop up very very quickly before it restarts so recorded on slow-mo and captured the error code.

        Error 0x040ee119.

        1 Reply Last reply Reply Quote 0
        • R
          richardh
          last edited by Apr 21, 2016, 1:17 PM

          OK we have managed to resolve the issue a different way. But we wouldn’t have got there without your help.

          We tried lots of combinations of DHCP option 67 undionly.*

          The way we resolved the issue was to change DHCP option 67 to ipxe.pxe.

          Many thanks Sebastian.

          Richard

          1 Reply Last reply Reply Quote 1
          • S
            Sebastian Roth Moderator
            last edited by Apr 21, 2016, 4:05 PM

            Just for clarification when others are reading this in the future: ipxe.pxe comes with native NIC drivers where undionly.* uses the NIC’s UNDI interface. Seems like the mentioned realtek NIC has a “buggy” PXE implementation which causes the undionly binary to fail…

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 2
            • G
              george1421 Moderator
              last edited by Apr 22, 2016, 3:12 PM

              Cross linking similar thread where ipxe.pxe solved the issue with the realtek nic.
              https://forums.fogproject.org/topic/7241/dhcp-failed-on-hp-prodesk-400-g2

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                5/6
                Last post

              204

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project