• Moderator

    @joyboy11111 I personnally think it would be quicker to just update the pxe boot file to see if that addresses the issue.

    But it you want to update fog, it looks like you might have the git install files in that screen shot. So change into the fogproject directory then issue the following command git pull that should update the installer files. Then change into the bin directory and run ./installfog.sh script. It should remember the settings you made the last time you installed fog. The installer will stop half way through asking you to go to the website and update the database. Then don’t forget to go back to the linux console to finish the install.


  • This post is deleted!
  • Moderator

    @joyboy11111 said in HP Elitebook 840 G7:

    60 6d 3c 79 b0 f4

    OK we have correlation between linux and Windows. So the kernel at fault here is iPXE. Since you have and older install of FOG you probably have older versions of iPXE. Let me get the link so you can download 1.5.9’s version. Lets see if we replace iPXE we get the right mac address.

    Edit OK lets grab ipxe.efi and undionly.kpxe from here: https://github.com/FOGProject/fogproject/tree/master/packages/tftp those files should replace the files by the same name in /tftpboot directory on the FOG server. Swap out the files, go in and tweak the mac address on the test host you created so it doesn’t match, then pxe boot into the fog ipxe menu see if its registered or not, we need to get iPXE mac address to match what windows and linux say.

    I know there are hardware specific ipxe drivers too you might try. Also there is a generic driver for uefi (akin to undionly.kpxe) called snponly.efi. You might try that one too to see if we can get it to match the inventoried mac addresses.

    I do have to say I have not seen this issue before. So this is unique.


  • @george1421

    When I do ipconfig /all the physical address is 60 6d 3c 79 b0 f4

  • Moderator

    @joyboy11111 said in HP Elitebook 840 G7:

    6c:02:e0 mac company codes comes back to HP
    60:64:3c comes back as invalid
    Edit bifocals and sideways reading doesn’t give good answers.
    60:6d:3c mac company code is Luxshare Precision Industry Company Limited

    FYI the first 6 characters of the MAC identifies the nic manufacturer.

  • Moderator

    @joyboy11111 Sorry I just added this to a previous post:

    Secondly if you take that usb nic to a windows computer and insert it, what MAC address does windows see? We need to figure out which kernel is giving us false information.


  • @george1421

    That is the address of the network adapter. The actual mac address I added as a host manually was 6c:02:e0:05:2a:5d

  • Moderator

    @joyboy11111 so does the mac address for enp55xxx match what inventory says or what iPXE is seeing (what you entered for the test system in fog?

    Secondly if you take that usb nic to a windows computer and insert it, what MAC address does windows see? We need to figure out which kernel is giving us false information.


  • @george1421 FOG.jpg

    Sorry I did not realize the information was not captured.

  • Moderator

    @joyboy11111 what about the ip a s command. That is kind of what I want to focus on immediately.


  • Moderator

    @joyboy11111 said in HP Elitebook 840 G7:

    I did try to do a regular capture and it gave me a legit error. Could not mount because the disk contains a unclean file system. I assume just because of all the bios changes, power on and off I have just corrupted win 10 so badly it just needs to have a fresh copy of windows installed.

    This is something you can fix. What happens with windows is shutdown is not actually a power off shutdown. In windows 10 term its actually an enhanced sleep mode which leave files open and the dirty bit set. So before a capture we recommend you do one of these things.

    1. Let sysprep power off the computer after its done. sysprep will properly close open files for cloning.
    2. Use shutdown -s -t 0 to power off the computer.
    3. Disable fast startup, reboot then shutdown via the start menu.

    NOW back to the issue at hand.

    lets start with ip a s and post a screen shot of the error here

    Then the lspci and lsusb output.

    What we need to find is where is the mac address coming from that iPXE is reporting? Is there multiple network adapters? Is there some other kinds of monkey business going on?


  • @george1421

    WOW that made progress. Ok with those steps I can get to debug capture. Did you want me to run the command lspci -nn | grep -i net from below?

    I did try to do a regular capture and it gave me a legit error. Could not mount because the disk contains a unclean file system. I assume just because of all the bios changes, power on and off I have just corrupted win 10 so badly it just needs to have a fresh copy of windows installed.

  • Moderator

    @joyboy11111 said in HP Elitebook 840 G7:

    . It captures the laptop SN and all the other data. I assigned an image to it, created a capture task, FOG wont capture it, just keeps bringing me to the host not registered.

    Boy we always seem to get the difficult ones. So a little bit more on what is going on behind the screen. iPXE (undonly.kpxe or ipxe.efi) is picking the mac address of the network adapter that is pxe booting computer. That is reporting one mac address. This is the mac address you see on the screen in the ipxe menu when it says not registered. Record that mac address from the FOG iPXE screen. Now when FOS Linux starts (bzImage) and its seems to be detecting a different mac address (because inventory says one thing, and iPXE says something else).

    I think I understand how this might be happening but not the why part.

    So what I want you to do next is to take that mac address that is on the iPXE screen and manually register a test computer using that MAC address. Then deploy a debug capture task to that test computer. We may get some different error messages but I want to get to the FOS Linux command prompt to see if we can find out what is going on here (like there is 2 network adapters and iPXE is selecting the wrong one)


  • @george1421

    Just to recap:

    840 G6 & G7
    I did this for both laptops exact steps. I just deleted that network adapter as a host. Plugged it into a 840 g6, tried to do a quick host registration. FOG goes through the steps. The adapter mac address shows up as a host in FOG. It captures the laptop SN and all the other data. I assigned an image to it, created a capture task, FOG wont capture it, just keeps bringing me to the host not registered. Does not kick an error like partitions or image is not clean, can not capture. Killed the task. Created a debug capture task. FOG keeps on going and brings me to the menu showing host is not registered. Through that menu I can deploy a existing image to both the G6 and G7. But through a scheduled task I can not capture, or deploy.

    I know previously I said I got to the debug task on the G6, but now I can not. That might have been on the old kernel before I got 5.6.18 installed. That is water under the bridge.

  • Moderator

    @joyboy11111 Interesting, in that this network adapter works with the G6 for imaging?

    So we don’t head in too many directions all at once, follow my last post first.

    I do have to say some of the newer Realtek 8152/8152 nics need a patch driver to work. I have this as a one off kernel, BUT lets not do too many things at once. If the official FOG kernels work we should stick with them because they have been tested and proven to work for most all hardware.


  • Moderator

    @joyboy11111 said in HP Elitebook 840 G7:

    When I boot, FOG goes right passed the debug command (never loads) prompt and goes to the FOG menu of host is not registered, boot from hard disk etc. I took a video with my phone but it would not upload.

    On a side note, I left the task active and booted a 840 G6 with the same dongle and, it came right into the debug screen

    Rereading this makes me think a little differently now. If that same network adapter works in a G6 but note G7 then its not the kernel driver for the network adapter.

    What I also find strange is that the network adapter has a different MAC address from the G6 to G7. On the G7 when you boot into the ipxe menu it should tell you the mac address iPXE sees on the screen. On some of the newer bios (uefi firmware) there is a mac address pass-through option. In this case it makes the usb adapter transparent to the target computer, where you get the mac address of the PC itself as if the network adapter was built into the G7 directly.

    So with this new understanding, on the G7 go ahead and register that computer using the normal process. Then schedule a new task using the MAC address detected during the registration process. The system may be working as designed, just not as we might expect. It is actually working better than on the G6 because that makes the mac in the nic irrelevant.

  • Moderator

    @joyboy11111 ok just get me the windows hardware ID of this usb network adapter and I can trace it to the linux driver then.


  • @george1421 When I boot, FOG goes right passed the debug command (never loads) prompt and goes to the FOG menu of host is not registered, boot from hard disk etc. I took a video with my phone but it would not upload.

    On a side note, I left the task active and booted a 840 G6 with the same dongle and, it came right into the debug screen.

352
Online

7.8k
Users

14.8k
Topics

139.5k
Posts