CentOS - Nov 2020 - why does virtual console start affect graphical start up?

Hello all--

I have 3 CentOs 8 kernels insalled on my new machine --

1. 4.18.0-193.14.2.el8_2.x86_6

2. 4.18.0-193.19.1.el8_2.x86_64 << using this one for this graphical boot

3. 4.18.0-193.28.1.el8_2.x86_64

Only #3 will boot without a *Virtual console can not start *error 
message but it hangs up trying to get into graphical mode, although it 
will boot to multi-user.

The first 2 seem to work reaosnably well in either graphical or 
multi-user but I get a *Virtual console can not start *in boot messages 
with both of these.

Does anyone know anything about this?

Having a heck of a time trying to prevent lock ups.

Thanks.


**

Please disregard this message. My additional muckings seem to have more 
or less fixed this including NOT saving journal files and using X to 
start gdm instead of Wayland.

On 11/14/20 1:39 PM, Kay Schenk wrote:
>
> Hello all--
>
> I have 3 CentOs 8 kernels insalled on my new machine --
>
> 1. 4.18.0-193.14.2.el8_2.x86_6
>
> 2. 4.18.0-193.19.1.el8_2.x86_64 << using this one for this graphical
boot
>
> 3. 4.18.0-193.28.1.el8_2.x86_64
>
> Only #3 will boot without a *Virtual console can not start *error 
> message but it hangs up trying to get into graphical mode, although it 
> will boot to multi-user.
>
> The first 2 seem to work reaosnably well in either graphical or 
> multi-user but I get a *Virtual console can not start *in boot 
> messages with both of these.
>
> Does anyone know anything about this?
>
> Having a heck of a time trying to prevent lock ups.
>
> Thanks.
>
>