(solved) Bootloader takes too much time after switching to LTS kernel

kaushikgn · 2020-04-14 15:57:42

Hi
I installed Arch on dual boot with windows on an efi system.Everything was fine till i updated to LTS kernel using pacman.
After that i regenerated the grub config file like i did during installation. Mounted windows partition on an temp dir,ran os prober (which detected the windows efi part).
After that when im booting grub is not allowing me to select any of the two options ie, Advanced options where i can see the kernel,Windows. The up down keys is either frozen or grub has disabled selection.It just boots into the new kernel. Also the boot time has become longer and the font size in the terminal has become very small.
Pls,pls help me.I just installed it and people are saying to use an LTS kernel.Argghhh.
Thank you.

Last edited by kaushikgn (2020-04-17 18:59:29)

kaushikgn · 2020-04-14 17:06:12

Update : I disabled fast boot in bios and it resolved the problem.But bootloader takes awful lot of time with systemd-analyze reporting 18 seconds.And the resolution is really small.When i boot into the non-lts kernel ,5.6.3-arch-1 the bootloader is 6 seconds and resolution is fine.Any hope of resolving this?I cant see journalctl,command not found.Where can i start from.
Thanks for your help

maartenvanschagen · 2020-04-14 18:20:59

I'm not sure how to fix your main problem, I am a newbie myself too. But if you don't have access to the journalctl command for some reason you should still be able to find the logs. This archwiki page will tell you all about it https://wiki.archlinux.org/index.php/Systemd/Journal

kaushikgn · 2020-04-14 20:38:43

Im away from the maachine right now,but i think what i saw was it wasnt installed.Command not found....Thanks a bunch for the journalctl article.It will give me something to work on.I will get back,hopefully with something to work on.
Something more generic, any idea if journal logs will have the anything to dedebug bootloader , coming before initramfs?

maartenvanschagen · 2020-04-15 14:25:54

kaushikgn wrote:

Something more generic, any idea if journal logs will have the anything to dedebug bootloader , coming before initramfs?

I just checked, mine seems to start with bios and system information, thereafter I get the kernel command that was used. I don't see any grub debug messages, grub must create logs somewhere .

Head_on_a_Stick · 2020-04-15 18:03:57

kaushikgn wrote:

bootloader takes awful lot of time with systemd-analyze reporting 18 seconds.And the resolution is really small.

Is your hardware very new? Perhaps it isn't supported properly by the LTS kernel.

Might be best to change the title to reflect your current situation.

kaushikgn wrote:

I cant see journalctl,command not found

That seems unlikely, the journalctl(1) command is supplied by the systemd package. You can use strings(1) to read the journal logs directly (as mentioned on the ArchWiki page) or you can use --root= option with journalctl(1) from the live ISO image.

maartenvanschagen wrote:

grub must create logs somewhere

https://unix.stackexchange.com/question … ing-starts

kaushikgn · 2020-04-16 20:46:12

Thanks all. I have changed the title to something more appropriate.
My hardware is relatively new. Gigabyte ga ax 370 mobo. Ryzen 3 . I have an nvidia 4k card. There is no vga so I connect it to a 4k hd tv. So as head_on_a_stick mentioned could it be a case of something new added to the newer kernel that's missing in LTS one which could be the cause? Something I forgot to mention, I had to do a cmos reset to get in the bios. With fast boot enabled it would run into arch os. No matter how hard one pressed the key or just hold it down.
Maybe disconnecting the hard disk was better.?

I will have a go at the Logs as mentioned as soon as I get back.
Thanks a ton again

Slithery · 2020-04-16 20:54:52

kaushikgn wrote:

I just installed it and people are saying to use an LTS kernel.

Which people?

YCH · 2020-04-16 21:19:00

for analyze long boot time

systemd-analyze critical-chain

is good start. also

journalctl -b -k

(just glance it for some severe error message.)

kaushikgn · 2020-04-17 16:30:15

I changed the log level in grub to 5 and disabled quiet boot in grub.After that i could see the system was taking to much time to get dhcpd and wpa supplicant going on the network interface of the usb wifi adapter.After disabling those service its booting up normally.

I compiled the driver on the previous kernel version. Seems like i need to recompile the driver again with the new kernel and if it works then only i will be able to use the lts version i guess.Else falling back to the newer version of the kernel.
The font size is extremely small in the terminal.Any idea how to fix that?Before i can do anything i have to get the font back to normal size.Thanks.

Head_on_a_Stick · 2020-04-17 16:44:20

Please don't raise multiple issues in a thread.

Just this once:

kaushikgn wrote:

I compiled the driver on the previous kernel version. Seems like i need to recompile the driver again with the new kernel and if it works then only i will be able to use the lts version i guess.Else falling back to the newer version of the kernel.

https://wiki.archlinux.org/index.php/Dy … le_Support

kaushikgn wrote:

The font size is extremely small in the terminal.Any idea how to fix that?

https://wiki.archlinux.org/index.php/Li … sole#Fonts

If things are still unclear then please open a new thread for each specific problem and use a title that clearly describes the issue.

kaushikgn · 2020-04-17 18:57:37

My apologies, won't be doing that.
@maartenvanschagen : thanks for helping me out with that grub link. That helped in troubleshooting.
Thanks all for the tips and hints.

kaushikgn · 2020-04-17 19:28:19

Slithery wrote:

kaushikgn wrote:
I just installed it and people are saying to use an LTS kernel.
Which people?

This person for ex.
http://kroah.com/log/blog/2018/08/24/wh … uld-i-use/
I know it's not from the official arch wiki, but its
Greg Kroah-Hartman

Slithery · 2020-04-17 19:31:01

That post lists using the LTS kernel as the 3rd best option, whereas using the stock Arch kernel comes first.

Why do you think that you need to use the LTS kernel?

Arch Linux

#1 2020-04-14 15:57:42

(solved) Bootloader takes too much time after switching to LTS kernel

#2 2020-04-14 17:06:12

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#3 2020-04-14 18:20:59

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#4 2020-04-14 20:38:43

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#5 2020-04-15 14:25:54

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#6 2020-04-15 18:03:57

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#7 2020-04-16 20:46:12

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#8 2020-04-16 20:54:52

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#9 2020-04-16 21:19:00

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#10 2020-04-17 16:30:15

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#11 2020-04-17 16:44:20

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#12 2020-04-17 18:57:37

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#13 2020-04-17 19:28:19

Re: (solved) Bootloader takes too much time after switching to LTS kernel

#14 2020-04-17 19:31:01

Re: (solved) Bootloader takes too much time after switching to LTS kernel

Board footer