Cannot access KDE after updating kernel

[User]

Running Slackware15.0 installed to NVME drive on a new laptop using
UEFI/GPT.

After updating the kernel through slackpkg upgrade-all I get the
following warning:

"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).
Press the "Enter" key to continue."

After rebooting I can still log into Slackware but cannot launch KDE. I
get the following messages when typing 'startx'

xinit: giving up
xinit: unable to connect to Xserver: Bad file descriptor
xinit: server error

[Chris Elvidge]

Post by User
Running Slackware15.0 installed to NVME drive on a new laptop using
UEFI/GPT.
After updating the kernel through slackpkg upgrade-all I get the
"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).
Press the "Enter" key to continue."
After rebooting I can still log into Slackware but cannot launch KDE. I
get the following messages when typing 'startx'
xinit: giving up
xinit: unable to connect to Xserver: Bad file descriptor
xinit: server error

Is your kernel (uname -r) the updated kernel?
If not - elilo or grub? Try (as root)
elilo: use pkgtool/setup to update initrd and eliloconfig
grub: try grub-mkconfig -o /boot/grub/grub.cfg to update

[User]

Post by Chris Elvidge

Post by User
Running Slackware15.0 installed to NVME drive on a new laptop using
UEFI/GPT.
After updating the kernel through slackpkg upgrade-all I get the
"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).
Press the "Enter" key to continue."
After rebooting I can still log into Slackware but cannot launch KDE.
I get the following messages when typing 'startx'
xinit: giving up
xinit: unable to connect to Xserver: Bad file descriptor
xinit: server error

Is your kernel (uname -r) the updated kernel?
If not - elilo or grub? Try (as root)
elilo: use pkgtool/setup to update initrd and eliloconfig
grub: try grub-mkconfig -o /boot/grub/grub.cfg to update

Thank you for your help. I figured out how to get it working after
quite a bit of trial and error.

I upgraded from 5.15.19 to 5.15.27. (uname -r) was still showing
5.15.19 after rebooting. It got more complicated because I was no
longer able to mount the /boot/efi partition (unknown filesystem type
'vfat').

Essentially have to run mkinitrd (see /boot/README.initrd) and copy
initrid.gz and vmlinuz into /etc/efi/EFI/Slackware before rebooting.

Guru types lay out more sophisticated solutions here:
https://www.linuxquestions.org/questions/slackware-14/after-slackpkg-upgrade-all-upgrades-kernel-making-a-new-initramfs-is-necessary-but-not-automatic-right-4175709694-print/

[User]

Post by Chris Elvidge

Post by User
Running Slackware15.0 installed to NVME drive on a new laptop using
UEFI/GPT.
After updating the kernel through slackpkg upgrade-all I get the
"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). Press the "Enter" key to continue."
After rebooting I can still log into Slackware but cannot launch KDE.
I get the following messages when typing 'startx'
xinit: giving up
xinit: unable to connect to Xserver: Bad file descriptor
xinit: server error

Is your kernel (uname -r) the updated kernel?
If not - elilo or grub? Try (as root)
elilo: use pkgtool/setup to update initrd and eliloconfig
grub: try grub-mkconfig -o /boot/grub/grub.cfg to update

Thank you for your help.  I figured out how to get it working after
quite a bit of trial and error.
I upgraded from 5.15.19 to 5.15.27.  (uname -r) was still showing
5.15.19 after rebooting.  It got more complicated because I was no
longer able to mount the /boot/efi partition (unknown filesystem type
'vfat').
Essentially have to run mkinitrd (see /boot/README.initrd) and copy
initrid.gz and vmlinuz into /etc/efi/EFI/Slackware before rebooting.
https://www.linuxquestions.org/questions/slackware-14/after-slackpkg-upgrade-all-upgrades-kernel-making-a-new-initramfs-is-necessary-but-not-automatic-right-4175709694-print/

/boot/efi/EFI/Slackware

[Henrik Carlqvist]

Post by User
I upgraded from 5.15.19 to 5.15.27. (uname -r) was still showing
5.15.19 after rebooting.

The tricky part about upgrading the kernel is that it is not enough to
replace the kernel, you will also have to update the configuration of
your boot loader and different users choose different boot loaders.

Before applying patches it might be a good idea to read the changelog at
http://www.slackware.com/changelog/stable.php?cpu=x86_64

From that text:

-8<---------------------------------------------
+--------------------------+
Wed Mar 9 04:14:08 UTC 2022
patches/packages/linux-5.15.27/*: Upgraded.
These updates fix various bugs and security issues, including the
recently
announced "Dirty Pipe" vulnerability which allows overwriting data in
arbitrary read-only files (CVE-2022-0847).
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the
correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to
copy the
kernel and initrd to the EFI System Partition.
...
-8<---------------------------------------------

regards Henrik

[User]

Post by Henrik Carlqvist

Post by User
I upgraded from 5.15.19 to 5.15.27. (uname -r) was still showing
5.15.19 after rebooting.

The tricky part about upgrading the kernel is that it is not enough to
replace the kernel, you will also have to update the configuration of
your boot loader and different users choose different boot loaders.
Before applying patches it might be a good idea to read the changelog at
http://www.slackware.com/changelog/stable.php?cpu=x86_64
-8<---------------------------------------------
+--------------------------+
Wed Mar 9 04:14:08 UTC 2022
patches/packages/linux-5.15.27/*: Upgraded.
These updates fix various bugs and security issues, including the
recently
announced "Dirty Pipe" vulnerability which allows overwriting data in
arbitrary read-only files (CVE-2022-0847).
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the
correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to
copy the
kernel and initrd to the EFI System Partition.
...
-8<---------------------------------------------
regards Henrik

The following worked on lilo/elilo systems

# System running lilo
mkinitrd -c -k 5.15.27 -m ext4
lilo
reboot

# System running elilo
mkinitrd -c -k 5.15.27 -m ext4
eliloconfig
reboot

[Steve G]

Post by User

Post by Henrik Carlqvist

Post by User
I upgraded from 5.15.19 to 5.15.27. (uname -r) was still showing
5.15.19 after rebooting.

The tricky part about upgrading the kernel is that it is not enough to
replace the kernel, you will also have to update the configuration of
your boot loader and different users choose different boot loaders.
Before applying patches it might be a good idea to read the changelog at
http://www.slackware.com/changelog/stable.php?cpu=x86_64
-8<---------------------------------------------
+--------------------------+
Wed Mar 9 04:14:08 UTC 2022
patches/packages/linux-5.15.27/*: Upgraded.
These updates fix various bugs and security issues, including the
recently
announced "Dirty Pipe" vulnerability which allows overwriting data in
arbitrary read-only files (CVE-2022-0847).
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the
correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to
copy the
kernel and initrd to the EFI System Partition.
...
-8<---------------------------------------------
regards Henrik

The following worked on lilo/elilo systems
# System running lilo
mkinitrd -c -k 5.15.27 -m ext4
lilo
reboot
# System running elilo
mkinitrd -c -k 5.15.27 -m ext4
eliloconfig
reboot

Make sure you have DRI selected in the drivers selection for X. I forgot
that one before...