[solved] Re: Trying to deug initramfs boot delay

2022-02-23 Thread Michael Lange
Hi, thanks, Andrew and Charles for the replies. I finally managed to (sort of) fix the issue with the delayed boot. First, for the record, in case someone comes here via the archives: the ".enuineIntel.align.0123456789abc" file in the initrd appears to be quite normal (strange as it sounds - at

Re: Trying to deug initramfs boot delay

2022-02-22 Thread Andrew M.A. Cater
On Tue, Feb 22, 2022 at 09:19:14AM -0700, Charles Curley wrote: > On Tue, 22 Feb 2022 09:45:34 + > "Andrew M.A. Cater" wrote: > > > I think Charles Curley is also installing on one, too. > > I am installing on an Ideapad, a "Lenovo IdeaPad Yoga 13". I have not > seen anything like what the

Re: Trying to deug initramfs boot delay

2022-02-22 Thread Charles Curley
On Tue, 22 Feb 2022 09:45:34 + "Andrew M.A. Cater" wrote: > I think Charles Curley is also installing on one, too. I am installing on an Ideapad, a "Lenovo IdeaPad Yoga 13". I have not seen anything like what the OP, Michael Lange , describes. Indeed, my beastie boots very quickly. > > I

Re: Trying to deug initramfs boot delay

2022-02-22 Thread Andrew M.A. Cater
On Tue, Feb 22, 2022 at 12:50:13AM +0100, Michael Lange wrote: > Hi, > > I installed bullseye (32-bit) onto a Lenovo IdeaPad 100S laptop. The > system generalliy runs fine, however there is a minor nuisance with a > delay of about 40 sec. at the begining of the boot process at the > "Loading

Re: Trying to deug initramfs boot delay

2022-02-21 Thread Christian Britz
On 2022-02-22 00:50 UTC+0100, Michael Lange wrote: > First, when I run lsinitramfs on the initrd in use, the first items of > the command's output are: > > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/.enuineIntel.align.0123456789abc >

Trying to deug initramfs boot delay

2022-02-21 Thread Michael Lange
Hi, I installed bullseye (32-bit) onto a Lenovo IdeaPad 100S laptop. The system generalliy runs fine, however there is a minor nuisance with a delay of about 40 sec. at the begining of the boot process at the "Loading initial ramdisk..." stage. Trying to debug this I found two things that