@sebastian-roth Thanks for this reply.
I will try un inventory task to check bi-directional data exchange.
Luc.

@george1421 said in FAQ page in WIKI should be updated:

@Luc-Novales So let me understand even with the 486 kernel it does not boot, I would expect an error message as in the picture provided.

I made a report of actions in initial thread more adapted…
Black screen and blinking cursor after vesamenu

Thx,
Luc.

Ok update on this thread so we can put it to bed.

I built 2 custom FOS Linux kernels the fist was targeted to a 486 and the second was targeted to the Geode processor. Bot would throw the issue with an unstable clocksouce. We could only see this error when we change the linux kernel logging level to 7. After some google fu and attempting a few kernel parameters that dealt with the clocksouce I found a references to apci=off. That was the actual parameter that solved the kernel boot errors. The OP was then able to run a deployment in debug mode to completion.

So while the actual problem isn’t in line with the thread subject. The issues were this.

The standard FOS Linux kernel has a minimum supported level of processor of i586. I had to build a custom kernel with a minimum processor level of i486 to get the kernel to boot.

Because of the hardware we had to specifically turn off acpi in the kernel using the kernel parameter of apci=off