artem: Sorry if there was any confusion. Like Plagman said, we've never supported vesafb; it used to be the case that it happened to "just work", but now it doesn't. We're trying to figure out what happened, but since we don't understand exactly what happened yet, we can't promise that it will be fixed. Even if we do end up fixing it, please don't take that as a sign that we support non-VGA consoles.
ltmon: This is still showing up in your dmesg:
[ 4.086429] uvesafb: NVIDIA Corporation, NVIDIA Quadro FX 880M
[ 4.086436] , Chip Rev , OEM: NVIDIA, VBE v3.0
[ 4.137836] uvesafb: VBIOS/hardware doesn't support DDC transfers
[ 4.137842] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 4.138236] uvesafb: scrolling: redraw
[ 4.298646] Console: switching to colour frame buffer device 106x30
[ 4.299447] uvesafb: framebuffer at 0xcf000000, mapped to 0xffffc90011c00000, using 8000k, total 14336k
[ 4.299449] fb0: VESA VGA frame buffer device
It doesn't look like your kernel command line explicitly requests the framebuffer console (unlike the previous kernel command line, which is still visible in the old logs, and did explicitly configure uvesafb), and I'm not really sure where it's coming from. Try removing the "splash" option from your command line. If that doesn't help, maybe try blacklisting uvesafb and vesafb in /etc/modprobe.d and rebuild your initrd.