Black screen and blinking cursor after vesamenu
-
Just as a follow up on this. The bzImage32 is configured to require a 686 as the minimum processor: https://github.com/FOGProject/fos/blob/master/configs/kernelx86.config#L251
I’ve reconfigured my build environment and changed the minimum processor to 486 and I’m rebuilding the bzImage32 file for i486. Understand two things. 1. This is not an official FOG Project kernel since its not coming from one of the Developers. 2. I have no idea if it will work because I don’t have a 486 machine to test it on.
When its done compiling I’ll post a link so you can download it and try it.
Also on my syslinux configuration, Its been almost 8 years since I’ve worked with syslinux so I guessed at most of the entries. You WILL need to adjust it to replace the entire variable
$myfogip
with the IP address of your fog server to make it work correctly. It will take about 20 minutes to finish the new kernel build. -
Here is the link to the 486 version of the FOS Linux kernel: https://drive.google.com/open?id=1xSR5MIPoOTFDQNFpHs7flRUnjHqnJS-W
I’m going to suspect that you will have issues with the inits (virtual hard drive), but lets take one step at a time. Since I’ve given this a new name “bzImage486” you will need to update the syslinux menu too.
[edit] I just looked at the buildroot package and the default arch is set for i386 so the inits should work with this 486 kernel.
-
@Luc-Novales We have an answer in the iPXE forum. I just compiles a debug enabled binary. Find that here: https://fogproject.org/ipxe/01_undionly.kpxe
Copy into
/tfttpboot
on your FOG server and give it a try. Take a picture if you get more messages on screen. -
@Sebastian-Roth Is there a minimum processor level within the iPXE binaries, akin to where the kernel has minimum level supported processor?
-
@george1421 said in Black screen and blinking cursor after vesamenu:
Is there a minimum processor level within the iPXE binaries, akin to where the kernel has minimum level supported processor?
Not sure about that. I don’t think so as iPXE doesn’t use modern CPU features much I guess and would therefore run on plain old 386 I suppose. But not exactly sure.
-
@Luc-Novales Still waiting for you to test
01_undionly.kpxe
! Please let us know. -
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 hereTODO
- Determine why undionly.kpxe doesn’t load menu
- Determine why kernel loop on RCU grace-period stack dump.
-
@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.
Search the forums for “rcu_sched detected stalls on CPUs/tasks”…
-
@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
-
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
-