python3-numpy won't compile

Petri Kaukasoina · 11-19-2023, 07:58 AM

Or, a LEGACY BIOS system using lilo. If the Linux root partition is /dev/sda1 then

Code:

mount /dev/sda1 /mnt
mkbindmounts
chroot /mnt
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.117 | bash
/sbin/lilo
exit
umount /mnt
reboot

TheNutCase · 11-19-2023, 08:00 AM

Quote:

Originally Posted by Petri Kaukasoina

Didn't slackpkg inform you about this after the kernel upgrade? Depending on usage of lilo.conf, it outputs one of these:

Your kernel image was updated, and your /etc/lilo.conf indicates the use of an initrd for at least one of your kernels. Be sure to regenerate the initrd for the new kernel and handle any needed updates to your bootloader.
Your kernel image was updated. Be sure to handle any needed updates to your bootloader (possibly as simple as running /sbin/lilo).
Your kernel image was updated, and lilo does not appear to be used on your system. You may need to adjust your boot manager (like GRUB) to boot the appropriate kernel (after generating an initrd if required).

The first one (if I remember correctly).

Petri Kaukasoina · 11-19-2023, 08:01 AM

Quote:

Originally Posted by TheNutCase

The first one (if I remember correctly).

Then it's a LEGACY BIOS system with lilo and initrd.

TheNutCase · 11-19-2023, 01:03 PM

Thank you.