HP DC 7800's Deployment fails with newer kernels.
-
I have seen this posted before and my solution to make it work with the 7800’s and newer EFI network booting was to use an older FOG kernel from the web interface. I forget which one it was.
One thread mentioned using ACPI=OFF in the kernel parameters but this prevents EFI network book.
The 7800’s will make it to the fog menu but fail to deploy so I have set up a group named Legacy that uses the ACPI=OFF parameter. No way to test this yet. I am not on sight to test any of this ATM.
Like other members here there are a couple of DC5800’s those do not even make it to the boot menu but that isn’t really important.
Is there some other parameter I should use that would allow both?
Depending on which kernel I use;
I’ll see this.
Other kernels this;
https://forums.fogproject.org/topic/12924/hp-dc7800-network-boot?_=1587929349627
And as mentioned before using an older kernel from a year or so ago, I don’t have any problems with the 7800 and can EFI network book from other workstations. But there has to be something I’m missing that is preventing me from using the latest FOG kernel.
Any ideas?
Thank you.
I love FOG
-
@Fog_Newb said in It looks like FOG is working with Ubuntu 20.04 LTS:
So… Was the fix going to 1.5.2 init?
It had nothing to do with the inits. That specific case you cited was because the kernel was stalling on startup. Technically the inits were not in use at that point in the booting process. We had to turn off the acpi to solve the specific issue with that specific firmware on that system. For the DC 7800s I would use that kernel parameter setting in the host’s specific configuration and leave the default not there. The issue/problem is when you first register the DC7800 it will crash because that kernel parameter is not there, so manually registering and then placing
acpi=offin the host properties will make it work.Understand that is a workaround an issue with the dc7800s specifically. FOG doesn’t have the capabilities to dynamically add or remove kernel settings. It would be a cool feature, but really difficult (almost impossible) to program.
-
The DC7800’s can register without any kernel parameters on the new kernels. They just can’t have an image deployed on them.
Why isn’t it a problem with the older kernels?
-
@Fog_Newb said in HP DC 7800's Deployment fails with newer kernels.:
Why isn’t it a problem with the older kernels?
Only the linux kernel developers would be able to answer that. FOG only uses official linux kernels and they are kept current with what the linux kernel developers release.
Since the dc7800s will boot and register with the newer kernels then I would suggest that you use a FOG set group to assign the older kernel to just the 7800s so they image correctly. You can rename the older kernels so they are unique to that release and keep bzImage current with fogs version.
-
@Fog_Newb said in HP DC 7800's Deployment fails with newer kernels.:
The DC7800’s can register without any kernel parameters on the new kernels. They just can’t have an image deployed on them.
Can you please take a picture of the actual error on screen when deploying so we can try to help further investigation?
-
Hello,
Thanks everyone.
The error messages were in the links to the others posts. But it is cool now, I went in last night and tested.
Since the DC7800’s can make it to the fog menu I created a new group that adds acpi=off to the kernel parameters and add the dc7800 to that group.
EDIT: Oh woah, I see there is already a newer version of the dev branch. I’m still on 1.5.8.32
-
@Fog_Newb I am still not convinced you need the
acpi=offkernel parameter as you said that it does register properly. Both registration and deploy use the same Linux environment…The error messages were in the links to the others posts.
This is not of much help. Often error messages seem to be “the same as” but actually are not if you look closely. To be able to help we need a picture of the error on the screen of your machines!
