liquourix 6.6.8 kernel, virtual consoles [Solved]

[Charlie Brown]

Yep, I was talking about the "tty" issue :)

[dolphin_oracle]

Though it says "do not manually edit", does it change if you comment out that line (then reboot) ?

I believe those are compile time options.

[Charlie Brown]

Oh la la :D

Thank you .

[AVLinux]

Hi,

To clarify in case I've muddied the water... It's entirely possible X not loading was simply a boot glitch but removing 'quiet' from my boot switches allowed X to start normally on a rebuilt ISO... I suppose we will hear more about this if more issues pop up with people remastering on these newer kernels..

The removal of 'quiet' seemed to only mean an extra couple of milliseconds of code blurting across the screen so not really a vital option anyway, Although boot splashes look very professional I have never minded watching the console output..

[Charlie Brown]

What if you just: threadirqs splash ?

At least out of curiosity :)

[siamhie]

This issue of the virtual consoles DOES happen as I explained in post #9 mx21 and 6.6.7 liquorix ( UEFI ) , as well as 6.6.8 as I am on now.

Thanks for pointing out the post @CharlesV . I should go through the thread and make notes as to what does work and what doesn't.

So I think we can now rule out plymouth as there are two versions between MX-21 and MX-23.

MX-21 uses plymouth-0.9.5 version released 2020-07-08 (0.9.5-3)
MX-23 uses plymouth-22.02.122 version released 2022-01-11 (22.02.122-3)

[siamhie]

Though it says "do not manually edit", does it change if you comment out that line (then reboot) ?

Not entirely sure. I find it easier to just open MX Boot Options and make the changes right there on the kernel parameters line.

[siamhie]

Hi,

To clarify in case I've muddied the water... It's entirely possible X not loading was simply a boot glitch but removing 'quiet' from my boot switches allowed X to start normally on a rebuilt ISO... I suppose we will hear more about this if more issues pop up with people remastering on these newer kernels..

The removal of 'quiet' seemed to only mean an extra couple of milliseconds of code blurting across the screen so not really a vital option anyway, Although boot splashes look very professional I have never minded watching the console output..

From my limited understanding of those two kernel options from this trial and error.

The quiet option just suppresses more of the log messages you'll see on the screen.
The splash/nosplash option just enables or disables the plymouth boot animation.

[fehlix]

Liquorix:

Code: Select all

CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y
# end of Console display driver support

Seems Debian comments out "CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER" and Liquorix doesn't.

Good findings.
Maybe try this kernel boot parameter:

Code: Select all

fbcon=nodefer

to disabled "deferred takeover" of the framebuffer,
which may help to show the virtual console.

[dolphin_oracle]

that does the trick.