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

    Acer N4640G

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    2
    2
    1.1k
    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.
    • J
      jmeyer
      last edited by jmeyer

      Hello,

      I have speak of this with Thomas but I don’t want to make him spend too much time on my problems.

      We have received 3 type of Acer computer this year X2640g, X4640G and N4640G.
      Both X are working fine with undionly.kkpxe but N isn’t.
      N is only working with ipxe.pxe.
      Thomas asked us to use the 10s delay pxe boot file since he thinks it’s because RSTP that is disabled on switches but problem remain the same.

      Here are the 2 screenshot using undionly.kkpxe.
      First is normal one, second is 10s delay one.

      0_1479889352346_2016-11-22.jpg

      0_1479889366793_2016-11-22 (1).jpg

      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        We have received 3 type of Acer computer this year X2640g, X4640G and N4640G.
        Both X are working fine with undionly.kkpxe but N isn’t.
        N is only working with ipxe.pxe.

        This tells me that the ‘N’ system is a uefi system and the ‘X’ systems are bios (legacy) systems. You must use the right iPXE kernel with the proper firmware or it won’t work.

        As for the error above. It appears that the undionly kernel can see the network adapter, but not communicate on the network. I too suspect that this is a spanning tree issue. The problem is that spanning tree takes 27 second to begin forwarding traffic. The 10 second delay kernel is not sufficient to bridge this gap. Its best to enable one of the fast spanning tree protocols on this switch port. OR as a test, place a dumb switch between this target computer and the building switch. This dumb computer will keep the building switch port in the forwarding state while the target computer boots. If inserting the dumb (unmanaged switch) between the building switch and the target computer works, then you do have a spanning tree issue.

        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
        • First post
          Last post

        208

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project