You are not logged in.
Hi,
I recently installed Arch Linux on my new computer and, strangely, the computer freezes for a moment before the bootloader counts down. I'm surprised by this because before installing Arch, Windows 8 would launch within a couple of seconds (I have a SSD disk).
Here's the output of systemd-analyze:
Startup finished in 3.076s (firmware) + 11.176s (loader) + 1.477s (kernel) + 15.204s (userspace) = 30.935s(note that the bootloader's timeout is 5 seconds, so the loader freezed more than 6 seconds.)
I've had the same issue with Gummiboot and GRUB. I'm not familiar yet with debugging/analyzing tools, could someone help me to dig into this bug?
Thanks!
Edit: maybe a useful info: my computer is a Toshiba Satellite Z30t
Last edited by lawrent (2015-01-23 21:32:32)
Offline
Install gummiboot (if it isn't running already), set the "timeout" to zero in loader.conf then hold down the space bar during boot-up, press "t" and set the timeout to zero from the gummiboot menu.
What is the `systemd-analyze` output when you reboot again?
Related threads:
https://bbs.archlinux.org/viewtopic.php?id=192521
https://bbs.archlinux.org/viewtopic.php?id=192272
Jin, Jîyan, Azadî
Offline
note: pressing "t" at the gummiboot menu increments gummiboot's timeout, pressing "T" decrements it.
After disabling gummiboot's menu (pressing "T" till countdown is zero), systemd-analyze gives
Startup finished in 3.141s (firmware) + 6.112s (loader) + 1.665s (kernel) + 1.987s (userspace) = 12.905 si.e. the loader still takes the main part of the setup.
Last edited by lawrent (2015-01-24 11:13:43)
Offline
Try making a manual NVRAM entry using efibootmgr & boot from that, see if that has a delay as well.
https://wiki.archlinux.org/index.php/EF … bootmgr.29
If there is still a delay, I think it must be down to your firmware...
Jin, Jîyan, Azadî
Offline
What is your
$ efibootmgr -vdo it good first, it will be faster than do it twice the saint ![]()
Offline
$ efibootmgr -v
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,000B,0009,0008,0007,0005,0004,0000,0003,0001
Boot0000* HDD/SSD ACPI(a0341d0,0)PCI(1f,2)SATA(0,0,0)
Boot0001* LAN2 ACPI(a0341d0,0)PCI(19,0)MAC(MAC(b86b2348eb80,0)
Boot0002* LAN1 BIOS(80,0,30)........................E..............................................
Boot0003* LAN1 ACPI(a0341d0,0)PCI(19,0)MAC(MAC(b86b2348eb80,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000
Boot0004* Windows Boot Manager HD(2,200800,32000,a6e7aee1-3752-11e4-a1c7-b86b2348eb80)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...0................
Boot0005* Windows Boot Manager HD(2,200800,32000,a6e7aee1-3752-11e4-a1c7-b86b2348eb80)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0007* Syslinux HD(1,800,200000,a6e7aedb-3752-11e4-a1c7-b86b2348eb80)File(\EFI\syslinux\syslinux.efi)
Boot0008* Syslinux HD(1,800,200000,a6e7aedb-3752-11e4-a1c7-b86b2348eb80)File(\EFI\syslinux\syslinux.efi)
Boot0009* Syslinux HD(2,200800,32000,a6e7aee1-3752-11e4-a1c7-b86b2348eb80)File(\EFI\syslinux\syslinux.efi)
Boot000A* Linux Boot Manager HD(2,200800,32000,a6e7aee1-3752-11e4-a1c7-b86b2348eb80)File(\EFI\gummiboot\gummibootx64.efi)
Boot000B* grub-uefi HD(2,200800,32000,a6e7aee1-3752-11e4-a1c7-b86b2348eb80)File(\EFI\grub-uefi\grubx64.efi)I guess all those entries come from the trial-and-error I went through when installing my bootloader. Could it be possible that they are responsible for my setup delay?
Offline
It's possible --you can remove unwanted entries using:
# efibootmgr -b xxxx -BJin, Jîyan, Azadî
Offline
Thanks for the tip! Not much time to test right now, but I'll try it out
Offline
The BIOS timeout is 1 second, I don't know whether it's related to gummiboot. Do the other boot loaders respect their timing ?
PS, see whether this may help you.
Last edited by TheSaint (2015-01-25 03:03:18)
do it good first, it will be faster than do it twice the saint ![]()
Offline
Just removed some unnecessary entries (the 3 Syslinux ones, the second Windows one and the grub-uefi one) and systemd-analyze still gives me 6seconds spent on the booter.
I read your PS, TheSaint:
- Tried adding a /boot/loader/entries/windows.conf, no effect. (Except that now I have an additional Windows option on Gummiboot's menu.)
- Updated the BIOS' firmware (via Windows), no effect.
- the guy wonders if the problem comes from the Ubuntu installer he used to resize his disk. I used GParted, but I'd be surprised that it's the cause of the problem.
- timeout is set to 0 in /boot/loader/loader.conf
About https://bbs.archlinux.org/viewtopic.php?id=192272 you first mentioned, Head_on_a_Stick,
/boot/EFI/Boot/bootx74.efi and /boot/EFI/gummiboot/gummiboot.efi are identical
I'll try to make a boot option manually with efibootmgr next time, now it's time to go to job.
Offline
Booting win8 was by the mean of fastboot option in the BIOS, I think.
Very similar you may achieve if you use to hibernate Arch to disk.
do it good first, it will be faster than do it twice the saint ![]()
Offline
I tried making a boot entry directly with efibootmgr, (cf https://wiki.archlinux.org/index.php/EF … bootmgr.29 ). No boot menu on screen this time but still the 6 seconds delay…
Is there a log of what is done during the boot part of the setup, to see if there's an error occurring?
Last edited by lawrent (2015-01-31 09:03:02)
Offline
If it still occurs with a direct NVRAM entry, then it's because of your firmware -- you could try updating it but I think you can only do that sort of thing from Windows.
Does your firmware have an option for "Intel Fast Start"?
This requires a special partition on the hard drive and cannot be used with GNU/Linux; you could try disabling that, it may be searching for the extra partition in those six seconds.
Jin, Jîyan, Azadî
Offline
BIOS has already been updated from Windows
Found "Intel(R) Rapid Start Technology" option in the Setup Utility, disabled it, didn't fix my delay.
Offline
I think the delay is after the kernel loaded. That's why is shown by the journal.
do it good first, it will be faster than do it twice the saint ![]()
Offline
Same problem on a Toshiba laptop - similar setup, dual booting between Arch and Windows.
Offline
No updates about this issue? It's not something that really bothers me since I rarely reboot, but anyway I'd love to find a solution.
Offline
my ivybridge with gummiboot.
me@~: systemd-analyze
Startup finished in 7ms (firmware) + 158us (loader) + 4.322s (kernel) + 2.989s (userspace) = 7.320s
me@~: It is microsecond.
Offline
Similar issue on my Toshiba Z30 with GRUB:
Startup finished in 5.148s (firmware) + 11.447s (loader) + 1.357s (kernel) + 2.449s (userspace) = 20.403s
Did anyone find the reason?
Offline