Posts made by michaeloberg

@george1421 @Sebastian-Roth

Just wanting to update this post as it’s been a while. I have been working with HP support and they still have not fixed this issue (expect for the previously mentioned installer that only works in Windows).

I hope everyone has a Great Holiday Season and a Happy New Year!

I will continue to work off and on until January 5th when we return to school. If I don’t get anywhere with HP prior to that, I won’t be updating this.

Thanks again!

Michael

@george1421
I am not able to deploy an image to this machine, it shows “attempting to check in”

I also tried to do this by manually imaging (PXE Booting, then choosing deploy image) to no avail, it repeats the username/password 3 times then brings me to the FOG Compatibility menu and when I choose show MAC address it still shows the Dongle MAC:

In Debug mode using ip a s it shows the system MAC.

@george1421

The test results are below, circled in red is the system MAC (not the dongle).

@george1421

Thank you for the explanation and work on this. You mentioned to download the init_macset and place it in the /var/www/html/fog/service/ipxe directory. I have the file downloaded to my computer, how do I go about transferring that to my FOG Server? When I was downloading and testing kernels, I did that directly in the cli of the FOG server through Putty from the shared google drive.

TIA,

Michael

@george1421
Update - HP has a Mac Address Management software they had me install in the Windows environment that worked, however it doesn’t do anything for FOS or Deepin. The program is called hpmamsrv.exe.

Here is the software: https://ftp.hp.com/pub/softpaq/sp95501-96000/sp95997.exe

I have requested more information after relaying that this issue is not resolved as it doesn’t work for the Operating Systems.

I will let you know when I hear back from HP.

Michael

@george1421

I opened a ticket with HP on Friday, they escalated it and still haven’t heard back. I will update the post as soon as I hear from them.

Michael

@george1421
I will let you know when I hear back from HP, have a good weekend.

Mike

@george1421

OK, downloaded rt-opts2 kernel and ran the same commands as before, here is the output and verification snapshot of the opts2 kernel:

@tom-elliott @george1421

Hopefully I did this correctly. I used Tom’s commands and then changed the kernel parameters in the GUI and then at the debug prompt ran ip addr to get the MAC, it both instances it pulled the Dongle Address (3c:18:a0:cb:3f:b7).

Here is the confirmation of the kernel for rt-v215 followed by the ip addr and the grep -i -e firmware /var/log/message command:

Here is the confirmation of the kernel for rt-opts followed by the ip addr and the grep -i -e firmware /var/log/message command:

@george1421

Thanks for the update, one question I have is what/how do I apply the new kernel t once I download it? Before I was always downloading and applying them with this command:

cd /var/www/html/fog/service/ipxe
mv bzImage bzImage.orig
mv bzImage32 bzImage32.orig
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32
chown www-data:www-data bzImage
file bzImage**

For the no-cdc_ther and 5.15 kernels, you had me type:

wget https://fogproject.org/kernels/bzImag-5.15.5
wget https://fogproject.org/kernels/bzImage-no-cdc_ether

And then change the kernel parameters in the GUI.

Thank you,

Michael

@george1421

Sounds good and thank you. I have opened a ticket with HP as well, they escalated this to tier II engineering and am waiting for a call back.

I did update the BIOS on the computer from 1.06.03 to 1.06.04 and verified the NIC and Dongle have the latest firmware and even re-flashed the Dongle.

Here is the output from doing the command uname -a (keep in mind I still have bzImage-5.15.5 in the Host Kernel field in the GUI).

@george1421

Followed the steps you mentioned and when putting the kernel in for the host as bzImage-no-cdc_ether here are the screenshots of the boot and ip a s results:

Then I changed the parameter to bzImage-5.15.5 and here are the screenshots of the boot and ip a s results:

You can see in both cases the dongle address is display and not the System Address.

@sebastian-roth
Willing to try the latest 5.10.83 Kernel, but wondering how I do that.

In CLI, I normally do the following to update to the latest Kernel:

cd /var/www/html/fog/service/ipxe
mv bzImage bzImage.orig
mv bzImage32 bzImage32.orig
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32
chown www-data:www-data bzImage*
file bzImage*

Since you have given me a web address, how to I modify the syntax above to pull the latest Kernel from https://fogproject.org/kernels/bzImage-no-cdc_ether

I have really tried learning Linux, I have bought a book, watched videos and searched forums. Not everything is universal across the board for Linux. Please have patience as this is a very basic question but I’m afraid I don’t know how to update the Kernel.

Thank you,

Michael

@george1421
I mean that it passes the Dongle MAC through iPXE.

@sebastian-roth
In the simplest way to describe the overall issue I am having with these HP Probooks would be to state - “MAC Address passthrough works through iPXE but not any higher level Operating Systems - Linux, FOS, or Windows.”

Breaking it down as to what we have done and tried, I don’t know what the next step would be. We have a new server, updated iPXE, tried different Operating Systems, removed variables (Wi-Fi), is it possible that new computers aren’t meant to be imaged or maintain a static MAC address but take the MAC of the USB-Type C Dongle as the intent for these in corporate networks would be for them to remain with the computer and not on a rack meant for imaging?

I tested these Dongles on an HP Elitebook 845 G8 with the USB C and not integrated NIC and it worked. These were the units I was supposed to get, but do to the pandemic and industry shortages I had to get the Probooks because I found 515 of them in stock.

This is extremely frustrating and I know it isn’t anyone’s fault, but none-the-less mind boggling.

Is the current state and future of imaging mass quantities of computers over? I have been doing this for over 23 years. Altiris when I worked for Gateway Computers, Norton Ghost, Novell ZENworks, WDS, and for the last 7 years FOG. Never have I struggled this much.

And @george1421 - disabling the host based MAC, then PXE booting does nothing - shows this (shows the Dongle MAC):

Sorry a bit of a rant there, just trying to open my thought process up on what it could be or not meant to…

Thanks,
Michael

@george1421 @Sebastian-Roth

So I disabled the Wi-Fi card in the BIOS:

iPXE still shows the BIOS (System MAC):

FOG still show the Dongle MAC:

So I removed the Wi-Fi Card:

Same thing, here is the MAC on the card and it matches ipconfig in windows:

ipconfig from earlier:

@sebastian-roth

Here is a screenshot of the NICs, Red Line is the Dongle and Blue Line is the Wi-Fi:

iPXE is showing the MAC of the System as indicated in the BIOS:

iPXE:

@george1421 Here is the output of the command ip a s

NOTE the 3c:18a:cb:3f:b7 is the MAC of the HP Dongle:

@george1421
I ran two separate commands:

1. The first one was lspcl - nm | grep -i -e “net”
   This gave me this output:

2. The second command was lsusb ip a s
   This gave me this output:
   

I may be confused as you mentioned this:

Which I did on two separate lines in the CLI from the # prompt.

Let me know if this was incorrect.

Michael

@george1421
Below is the output: