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

Hi,
We use FOG to deploy training room at ENAC.
To monitor the process with promotheus, we plan to deploy some images in dry-run mode to preserve hard disk and compact-flash memories and to reduce test image size.
Parsing documentation I didn’t see :

1. Command line interface to engage task in FOG and to get their status.
2. Dry-run mode to simulate :
   1. upload image
   2. deploy image

Any link to help ?

Thanks,
Luc.

@Sebastian-Roth said in Black screen and blinking cursor after vesamenu:

@Luc-Novales Don’t want to sound rude but how many of those panel PCs do you have? If it’s just a handful of them you might be way faster installing/cloning them manually using other means of deployment instead of trying to get FOS Linux to rnu on this kind of mul-functioning hardware.

Today It’s the only reason to maintain an old server this an old version of clonezilla. All other stuff of our equipment in our learning rooms are managed on newer server with FOG. It should be better to integrate these panel PC too

Search the forums for “rcu_sched detected stalls on CPUs/tasks”…
I will…

In your signature :

…way more we need people to test things, update documentation…

Solving this problem, learning to compile new kernel… is perhaps the only way I have to update documentation and contribute to FOG

@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.

Hi,
I have to report some actions to explain where I am now.

Using IPXE

After a lot of tries 2 weeks ago, yesterday, I decide to compile IPXE “from scratch”, using a clean clone of ipxe git repository.

Applying “486 patch”

After removing definition TIVOLI_VMM_WORKAROUND in configuration file general.h as defined in the forum of ipxe “486er hangs on boot with iPXE floppy”, I obtain an USB boot media (ipxe.usb) to launch ipxe command and test FOG menu.

Compiling FOG IPXE

Compiling IPXE using IPXE part of the WIKI and applying “486 patch” (above) allow to obtain an undionly.kpxe usable with this panel PC.

Loading FOG menu

Configuring DHCP server to load new undionly.kpxe doesn’t load menu but allow to chain it manually.
Select “CLient System Information (Compatibiliy)” load effectively bzImage32 and stop with the message “This kernel requires an i686 CPU but only detected an i586 CPU”.

Using adapted linux kernel to i586

Trying to compile custom kernel, I opened another thread and George send me a bzImage file adapted to i486 (see FAQ page in WIKI should be updated).

Boot from FOG menu

Chain manually boot.php with MAC address parameter boot and the result is here

Fog menu for this host is here

TODO

• Determine why undionly.kpxe doesn’t load menu
• Determine why kernel loop on RCU grace-period stack dump.

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

@Luc-Novales Kernel building is now part of the init building process

https://github.com/FOGProject/fos is the github branch if you want to check it out.

I believe George sent you a chat message (top right) with the kernel he made though.

Yes, I have this kernel and I return to the initial post Black screen and blinking cursor after vesamenu, is better to resume my actions.

@Sebastian-Roth said in FAQ page in WIKI should be updated:

@Luc-Novales said in FAQ page in WIKI should be updated:

I should solve this problem, compiling a custom linux kernel and I downloaded linux-4.19.68 sources, but it seems that config file is not present in FOG sources as defined in Building a Custom Kernel. There is no kernel part in FOG sources, where can I find this config file ?

Sorry about this but it’s just another old wiki article - too bad! Here is the most current one and I believe this is up to date and should work: https://wiki.fogproject.org/wiki/index.php/Build_TomElliott_Kernel#Build_TomElliott_Kernel_for_FOG_0.33b_and_newer

Ok, I will try it later, now I test the kernel provided by George ;-).

Thx,
Luc.

Hi George,

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

@Luc-Novales This is an issue with the bzImage32 kernel that we ran across a few weeks ago. I can’t remember where the issue stood. This system was listed as a 486 if I remember correctly.

Yes an AMD Geode LX @500mhz.
An old panel PC used in operational equipment.

I just looked in my dev environment and I looks like it was setup to build a compatible FOS kernel. Let me rebuild it then I will have you try it to see if it works with your processor. It should take just a few minutes to compile. If it works OK then we’ll have to talk to the devs to see if there is any value adding it to the main branch. I’m seeing this as a one off situation. If its decided to not add to the main branch then you can continue to use bzImage486 without issue even after FOG updates.

Thanks, I’m waiting for your kernel to solve my problem and I think that it should be interesting to update the section Building a Custom Kernel to allow user to debuig this part too. I could try to update it if I have information to make it.

Thx,
Luc.

Hi there,
I may have to update some pages in the WIKI relative to building a custom kernel).
Could you enable a acces for my account ?

Thx,
Luc.

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

@Luc-Novales But fog now auto detects what kernel to use. If you have a system that is 64 bit but the manufacturer has pinned it as 32 bit (as in some inexpensive tablets) you can just update the kernel parameter in the host definition instead of swapping the bzImage/bzImage32 files. There are better and easier ways to go about it with FOG 1.2.0+ than with the really old versions of FOG.

It doesn’t works.
In my last reply of Black screen and blinking cursor after vesamenu, I said that trying for FUN your menu (Only for reference), load effectively bzImage32 and stop with the message “This kernel requires an i686 CPU but only detected an i586 CPU”.

Here the screenshot of this error :

There is the same result using the menu boot.php and select “CLient System Information (Compatibiliy)”.

I should solve this problem, compiling a custom linux kernel and I downloaded linux-4.19.68 sources, but it seems that config file is not present in FOG sources as defined in Building a Custom Kernel. There is no kernel part in FOG sources, where can I find this config file ?

Thx,
Luc.