crestiah
hope this makes sense.
Does that suggest that the delay is due to something in particular that changed between the two releases?
based on what i read here
https://stackoverflow.com/questions/10897087/multi-threaded-bios
https://stackoverflow.com/questions/27949362/create-a-thread-in-uefi
and a thread i read about the difference between dual core and quad core PC’s (sorry closed tab so cant point to it).
but basically im going to make an assumption or 2:
antix 16.1 probably uses uefi boot with single thread in mind. so in theory there would be next to no difference in the boot up process.( ie the quad core is probably only using 1-2 cores like the dual core in the inital boot process cores 3 and 4 sitting idle)
antix 17 uefi boot possibly includes MpService protocol (for lack of a better term “task delegator or multi threader” utilizes or makes use of the extra cores more efficently) “probably what gives me the saved state affect/feeling”.
so in the instance of the quad core
core 1 = boot processs with multi thread delegation
core 2 = start up hd/usb initialization
core 3 = start up video display
core 4 = any other components
all run in parallel arriving at user-space quicker.
in the case of the dual core
core 1 = boot process with single thread delegation that may be split to run on core 2.
core 2 = either idle or running a split of the single thread (Core 1 has to wait till core 2 finishes to move to next stage).
if grub2 uefi is setup for multi thread delegation as its preffered first option then its probably trying to pipe multithread exec code through a single thread pipe, this could be done at the same speed, except the dual core processor would need to be at least twice the speed of the quad core.
ie quad core 1.83ghz dual core 4ghz.
“pipe multithread exec code through a single thread pipe” by this im thinking uefi(multithread)/gpt piped through syslinux bios/mbr.
i would be curious to know if the syslinux component is booting with boot=quiet (usually means to me blank screen)
