@Foglalt It’s slated for 1.5.6 I believe, but you can manually download them for the time being.

It’s just the init files you need I think.

@jcabuco You can UEFI boot with secure boot disabled.

Secure boot and bitlocker are unrelated. They can be enabled irrespective of the other.

@Sebastian-Roth Looks good! Don’t think we thoroughly tested Linux at the time, not surprised it needed to be improved.

Change 0-1 to 0-9 over at https://github.com/FOGProject/fogproject/commit/71844d48ea00581f28ce56c28a8a63fc6166c38b

You can do working branch as well of course.

@george1421 The problem is for new kernels we need to update the kernel headers. Programs built against that (such as the programs in the init files) require the minimum supported kernel of those headers to run.

In practice, it will often work anyway, but sometimes the changes make it impossible, nothing that can really be done about that from our side afaik.

Yes, there’s a small mistake in the regex for the new password check. The whole password thing is getting a bit of a tune up.

More details here: https://github.com/FOGProject/fogproject/commit/244b239641d8ff602e97441d1d6658e71e9593b0#commitcomment-32148121

I think adding dhclient -r to /images/postdownloadscripts/fog.postdownload might work.

@arnaudrigole I am glad you found a solution that worked for you, though I’m still interested in trying to at least guess at why the other partition scheme gave problems.

Was there a difference in disk size in the SATA vs nVME SSDs?

Perhaps the nVME SSD is smaller and the OEM partitition at the end of the disk was out of range, though we’d expect a different error for that.

How is the multicast task started on the client? Scheduled per host through the Web GUI?

@greezy said in problem ACPI error:

ACPI Exception: AE_NOT_FOUND

What’s between brackets after AE_NOT_FOUND? (screenshot would be helpful)

Also… does it capture/deploy properly regardless of these errors?

FOG version would be nice to know too.