stevesr0
Hi crestiah and @736b69646f6f:
Thanks for comments.
Additional information.
The Lenovo is a newer machine with a 1.83 GHz quad core celeron and 8 gig of RAM and has UEFI system firmware. The Fuitsu has a dual core intel processor (T7250) running at 2 GHz and has 4 gig of RAM and BIOS firmware.
I have subsequently checked the times to boot with antix16 and the situation is different: BOTH computers boot in a reasonably short time and the Fujitsu boots FASTER than the Lenovo (24 vs 44 seconds). So, the move from 16 to 17 results in a small increase in boot time for the Lenovo (44 to 55 seconds) and a MASSIVE increase for the Fujitsu (24 to 319 seconds).
I have attached the bootcharts for antix16 to this reply.
My responses follow my quotes of your comments (” “) and are preceded by **.
crestiah 1:
“but basically im going to make an assumption or 2:
antix 16.1 probably uses uefi boot …antix 17 uefi boot possibly includes MpService protocol …if grub2 uefi is setup for multi thread delegation as its preferred 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 am ignorant about how the two bootloaders differ in their processes. I will seek to learn about this. Thanks for the references.
The motherboard hosts the hardware and firmware that runs BIOS or UEFI, not the disk drive. My Fujitsu doesn’t have UEFI, my Lenovo does. So the Fujitsu can’t boot via UEFI. I believe (from dolphin_oracle’s comment) that GRUB2 is used as the bootloader on a UEFI system even when running via LiveUSB.
“i would be curious to know if the syslinux component is booting with boot=quiet (usually means to me blank screen)”
**I believe so; I didn’t change the default
@736b69646f6f: (“@7”)and crestiah both indicate that the black screen is due to the boot running in quiet mode.
** I will change the option to a nonquiet one to view error messages flashing by. If that occurs too fast, I will check the /var/log file for the boot to see if the delay is explained.
@736b69646f6f: “Possibly an updated firmware is available from lenovo which would remedy the slow booting.”
** The Fujitsu is slow booting with 17 and there is no update to the BIOS that I can find.
Visit F2 bios setup and check whether you can manually choose device boot order, to “usb first, if present” or whatever option is available.
“Check /var/log/ or /var/log/live/ to see what error messages are being spewed to logfile during the 5 minute boot stall. Bootchart indicates “udev” is running for minutes. Struggling to find a driver? Bad/intermittent hardware errors?”
**I will look at those files.
“Something in the bootchart about set-console-width…. and same shown at right side of bootchart.
It’s not a solid line like that process was running the whole time. It gets interrupted, suspended, while udev it doing something else???”
**I see a number of processes that look like they stopped. I was looking at avahi-daemon for the same reason. Not obvious to me how to pick out the major blocks to boot from the chart.
“…typed a custom boot parameter,..”
**No.
“If the boot device is liveusb, I don’t understand how grub2 enters the picture. AFAIK, syslinux provides the liveboot efi bootloader and I see nothing on the syslinux.org site mentioning ability to tweak the behavior for “threads”.”
**According to Dolphin_Oracle, syslinux is used on liveUSB running on BIOS system, GRUB2 on UEFI. Thus, booting from the same liveUSB on my two machines uses different bootloaders.
“unetbootin…”
** Used rufus, running in Windows 10 to make all the liveUSBs.
responses to crestiah:
“anyway the idea was to lock/jail root to the start of the iso/img file, so anything you did or saved stayed inside that img file. as well as bypass the dos memmory limits.”
** I don’t know how respond to that suggestion.
- This reply was modified 4 years, 11 months ago by stevesr0.
- This reply was modified 4 years, 11 months ago by rokytnji.
