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 seemed suspicious to me, but
I do not know, if these might really be responsible for the delay.

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
kernel/x86/microcode/GenuineIntel.bin

Now, ".enuineIntel.align.0123456789abc" looks odd to me, can this
possibly be normal? Or is it possible that somehow this file name is
malformed and causes trouble while trying to apply the microcode?


Second, when I add the "debug" option to the kernel command line and look
at the /run/initramfs/initramfs.debug file, I find the following:

+ '[' -f /root/etc/fstab ]
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ '[' / '=' /usr ]
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ '[' /boot/efi '=' /usr ]
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ continue
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ '[' none '=' /usr ]
+ read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ return 1


I guess this has something to do with the system trying to detect the
available hard drive partitions, which somehow at some point seems to
fail.
I don't really know what the function that is responsible here tries to
do, but it looks like a lot of lines to me for the three partitions on the
laptop's drive (output of lsblk:

NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk2      179:0    0 29,1G  0 disk 
├─mmcblk2p1  179:1    0  100M  0 part /boot/efi
├─mmcblk2p2  179:2    0  3,4G  0 part [SWAP]
└─mmcblk2p3  179:3    0 22,9G  0 part /
mmcblk2boot0 179:256  0    4M  1 disk 
mmcblk2boot1 179:512  0    4M  1 disk 

cont. of /etc/fstab:

# / was on /dev/mmcblk1p3 during installation
UUID=ba9bd08f-5a25-4e42-95a4-ce0fa41be38d /               ext4
errors=remount-ro 0       1
# /boot/efi was on /dev/mmcblk1p1 during installation
UUID=78BA-12AF  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/mmcblk1p2 during installation
UUID=e1016bf0-5a98-4269-9e94-01ec54f1d541 none            swap
sw              0       0

)

Does anyone have a clue if either of these two things might be the
problem here, or -if not- what else I could try to identify the problem's
source?

Thanks in advance, and have a nice day,

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It is a human characteristic to love little animals, especially if
they're attractive in some way.
                -- McCoy, "The Trouble with Tribbles", stardate 4525.6

Reply via email to