I've done an upgrade on my -current installation and got the new 4.19.9 kernel.
During boot, some errors popped up stating that modules could not be load for kernel 4.19.8, and as a result my wireless keyboard does not work and i'm unable to debug much more. I also get the welcome message "Welcome to Linux 4.19.8", which is weird.
What could be going wrong here? I haven't switched to the generic version, i ran lilo after the upgrade, tried also repairing from a chroot from the installation media, but no luck.
I see some users here reporting issues with the new kernel but seem unrelated to mine (mostly for newer amd gpu).
Lesson learned: blacklist the working kernel packages

You do not updated properly your bootloader, and was loaded the previous 4.19.8 kernel.

Probably you use LILO, because something like that can happen because LILO read the kernel directly from hard drive, in a sectors base.

You are still lucky, because the deleted kernel file was not overridden yet by another file written and you managed still to boot with whatever success.

My suggestion is to boot from a live system and to fix your bootloader.

Thanks for the reply, but i'm not sure where to go from here.
I already tried to fix my bootloader from the live cd with no luck, if i look in /boot i see that vmlinuz is indeed pointing to the huge kernel 4.19.9, shouldnt it be enough?

What bootloader you use? LILO?

You are kind then to show me your /etc/lilo.conf ?

I had a similar adventure in the past, so I will try to help you.

yes i'm using lilo, here's my config

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" "

boot = /dev/sda
#compact # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255


# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
# Linux bootable partition config ends

Assuming that /boot/vmlinuz points to the proper kernel and you booted from one of live systems made by AlienBOB, as root from that live you should run
Then you should reboot the system.

Please note that with "#" I made some comments about steps, they aren't commands.

2 members found this post helpful.

okay solved for the moment! that didnt't do trick, i already tried it before. What did the trick was to unplug the hard-drive. I recently got an ssd and moved my installation there, formatting the hard disk for storage usage.
Could be that lilo was still somehow looking in there for something?
Thanks luckycyborg for the help!

Probably the (hard drive) devices order was changed after adding your SSD. E.g. /dev/sda was renamed as /dev/sdb or whatever.