ACPI Error during Image capture

[brian.mainake]

Hello,

I was wondering if anyone ran into this issue before or if anyone have any idea how to fix this.

I’m attempting to capture an Image from a Surface Laptop 5 with Windows 11 but during the capture I suddenly get this error over and over again: “ACPI Error: No handler or method for GPE, disabling event”.

I read a couple of articles similar to this issue and use “acpi=off” for the kernel parameter/argument but it just stuck when downloading the bzimage right before it goes to capture and won’t proceed.

Weirdly enough, this is only happen to this specific laptop. Surface Pro seems to work just fine.

My FOG version is 1.5.9.

I’ll take any advice or suggestion to resolve this. Thanks in advance!

[Sebastian Roth]

@brian-mainake ACPI errors printed on screen cause actual trouble only in very rare occations. Take a picture of what you see on screen. Does it go beyond the ACPI stuff or just stops there?

[brian.mainake]

@Sebastian-Roth It just stops there because it won’t proceed one way or another.

Here’s the image of the error I got.

Weird that I’m getting an error when uploading image here but here’s the image with the error: https://postimg.cc/hh4CV40v

[george1421]

@brian-mainake As Sebasitan said those ACPI messages are typically nuisance messages and typically do not impact the quality of image deployment.

We can try to turn off acpi to see if that addresses the issue or not. In the host definition for this target computer, there is a kernel parameter field. Enter the following into that field acpi=off safe the definition and then…

I’m suspecting that the acpi messages are a distraction from the real error. Lets boost the logging level of FOS linux. In the FOG WebUI->FOG Settings->FOG Configuration Hit the expand all button. Search for Logging If I remember right the default logging level is 4. Change that to level 7 save the fog configuration.

Now schedule a deployment. You should see a bunch of text now on the pxe booting computer related to its booting. This may give us an idea of what is really happening.

Also make sure the firmware is updated on the target computer too.

Finally what is the manufacturer and model of the computer that’s doing this.?

[brian.mainake]

@george1421 Hmm the Web UI is a bit different from what you’re describing. But I do see under FOG Boot Settings > Kernel Log Level = 4. Is that similar to what you’re referring to?

I’m gonna try this then. The laptop I’m having issue with is a Microsoft Surface Laptop 5.

[george1421]

@brian-mainake said in ACPI Error during Image capture:

FOG Boot Settings > Kernel Log Level = 4.

That’s what happens when you use your memory of the settings and not the actual values. Yes the kernel log level. Set it to 7 and the kernel will be very verbose when it boots. The real error message should be displayed,

The other thing I didn’t see mentioned here was the version of the FOS Linux kernel you are using. WebUI->FOG Configuration->Kernel update. You should make sure you are running 5.15.x series. If you have FOG 1.5.9 your kernel may still be of the 4.19.x series if you have not updated it.

[brian.mainake]

@george1421 I’ll be damned, pardon my french.

So I guess I was just not patient enough. You guys were right, the acpi error has nothing to do with this other than distracting it from the real process.

After changing the log to level 7, I noticed at some point it says its resizing right before the acpi errors take over. I realized its not stuck, its just taking a while to proceed bc resizing always takes a little longer when capturing image.

So I just let it sit there and eventually it proceeds on capturing the image. It doesn’t look pretty with all the acpi errors but it still does what it suppose to do.

Thank you @george1421 and @Sebastian-Roth for helping on this.