Comment # 34 on bug 1118689 from Felix Miata

(In reply to Andreas Stenglein from comment #33)
> With "graphical boot" I mean the boot menu is in high-resolution. You can
> switch to textmode in Yast -> system -> bootloader -> tab: kernel parameter
> -> box: [] Use graphical console / Graphik-Konsole benutzen
> UnSelecting the bootloader "graphical console" is a sufficient workaround on
> my side.

I'm still not sure what you want from me here. Ever since Grub as an option was
terminated, the only time I see a YaST Bootloader screen on my own hardware is
during installation, where, except on UEFI systems, I customarily select to
install no bootloader. With the exception of UEFI, all Gnu Linux operating
systems here are booted using an openSUSE Grub 0.97 version, usually 0.97.194.

> To check if PTI is enabled on your fedora installation you have to look for
> a line
> Kernel/User page tables isolation: enabled
> in dmesg output.

dmesg | grep -i 'page table' and dmesg | grep -i isola both return null with
4.20.6-100.fc28.i686

> According your description your CPU supports 64bit, too.
> Did you try a 64bit operating system?

I don't know how to answer this. I have hundreds of bootable operating system
installations. Whether half or more are using 64bit kernels I have no idea. I
didn't do my first 64bit installation on any of my own PCs until around the
time openSUSE announced there would be no 32bit Leap. I think I have at most 4
PCs with both 32bit and 64bit installed, more than I care to have already, so I
intend to create no more purposely. Comment #29 & #32 host gx280 was selected
for the test that resulted in comment #29 because it has the fastest CPU clock
on hardware on which I have running 32bit versions of openSUSE and Fedora and
Debian, along with a gfxchip supported by a KMS Xorg driver, not because of its
CPU's optimal arch. None of my 64bit installations exhibit this bug.