CTRL+ALT+F2 black console

[Fitap]

Hi,
sorry if this topic not in right place.

Like I said, I get black console when doing CTRL+ALT+F2 to into a non graphic console, however I can return to graphic session with CTRL+ALT+F7 fine.

Where I must to check?

Regards.

[nick_gentoo]

Hi, Fitap

Here is a possibly similar problem: https://forums.gentoo.org/viewtopic-t-1083076.html
It could be an incorrect kernel configuration related to the console framebuffer. Could you post a link to your dmesg log and kernel configuration?
Also, at boot, do you see text scrolling on the screen before the graphic session starts?

[nvaert1986]

Are you using openrc or systemd? If you are using systemd, you might need to manually enable and start the getty@tty1 service, before seeing a console pop-up. I've seen this issue occurring in the past.

[Fitap]

Hi, Fitap

Here is a possibly similar problem: https://forums.gentoo.org/viewtopic-t-1083076.html
It could be an incorrect kernel configuration related to the console framebuffer. Could you post a link to your dmesg log and kernel configuration?
Also, at boot, do you see text scrolling on the screen before the graphic session starts?

Thanks for response nick_gentoo

I don't use GRUB, and yes, I see text scrolling on the screen before GUI starts.

dmesg
kernel config

Are you using openrc or systemd? If you are using systemd, you might need to manually enable and start the getty@tty1 service, before seeing a console pop-up. I've seen this issue occurring in the past.

Thanks for response nvaert1986

I use openrc.

[nick_gentoo]

Code: Select all

[    0.896850] uvesafb: failed to execute /sbin/v86d
[    0.896852] uvesafb: make sure that the v86d helper is installed and executable

This is from having "Userspace VESA VGA graphics support" (FB_UVESA) enabled in the kernel, that's probably not needed.
In my case, I have the following options set in that kernel configuration menu:

• VESA VGA graphics support
• EFI-based Framebuffer Support
• Simple framebuffer support

You could try that and see if it works.
I did this config once based on advice found here in the forum, but I did not spend the time to fully understand all the details. Maybe not all 3 settings are needed.

[Fitap]

Code: Select all

# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set

Still not working, I have black screen with an underscore blinking.

Forgot to mention what I use sddm like DM, I have 3 boxes with the same DM, and only in this box, not working ctrl+alt+f2

[apiaio]

Hi.

I had the same problem with CTRL+ALT+Fx, Return to graphic session via CTRL+ALT+F7 worked. Problem was with my graphic card
Radeon R7 240/340.

Soved after

Code: Select all

emerge -a sys-kernel/linux-firmware

[Fitap]

Hi.

I had the same problem with CTRL+ALT+Fx, Return to graphic session via CTRL+ALT+F7 worked. Problem was with my graphic card
Radeon R7 240/340.

Soved after

Code: Select all

emerge -a sys-kernel/linux-firmware

Thanks for reply apiaio

The 3 boxes what I have, run intel driver and sys-kernel/linux-firmware is up today.

[nick_gentoo]

Code: Select all

# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set

Still not working, I have black screen with an underscore blinking.

Forgot to mention what I use sddm like DM, I have 3 boxes with the same DM, and only in this box, not working ctrl+alt+f2

Hi, what I meant was to try to have all of the following enabled:

• CONFIG_FB_VESA
• CONFIG_FB_EFI
• CONFIG_FB_SIMPLE

This works in my case (not with Intel though), maybe somebody else will reply if this is not a good advice.

Are there any significant differences between the kernel configs of those 3 boxes?

[Fitap]

enabled:

• CONFIG_FB_VESA
• CONFIG_FB_EFI
• CONFIG_FB_SIMPLE

This works in my case (not with Intel though), maybe somebody else will reply if this is not a good advice.

Are there any significant differences between the kernel configs of those 3 boxes?

I just enable like you, no luck yet.

The other boxes have the same kernel config in it's video's card.

[nick_gentoo]

Well, I don't have another good idea for now...
Just 2 things:

• could you please post again the dmesg log with the last kernel config?
• the console does not appear for any of the CTRL+ALT+F1, F2, ... virtual terminals? (maybe not all of them are started, this is done through /etc/inittab)

[Fitap]

Well, I don't have another good idea for now...
Just 2 things:

• could you please post again the dmesg log with the last kernel config?
• the console does not appear for any of the CTRL+ALT+F1, F2, ... virtual terminals? (maybe not all of them are started, this is done through /etc/inittab)

I appreciate your help, let's see if someone will make me a tip.

Here you are:
dmesg

Code: Select all

#
# /etc/inittab:  This file describes how the INIT process should set up
#                the system in a certain run-level.
#
# Author:  Miquel van Smoorenburg, <miquels@cistron.nl>
# Modified by:  Patrick J. Volkerding, <volkerdi@ftp.cdrom.com>
# Modified by:  Daniel Robbins, <drobbins@gentoo.org>
# Modified by:  Martin Schlemmer, <azarah@gentoo.org>
# Modified by:  Mike Frysinger, <vapier@gentoo.org>
# Modified by:  Robin H. Johnson, <robbat2@gentoo.org>
# Modified by:  William Hubbs, <williamh@gentoo.org>
#

# Default runlevel.
id:3:initdefault:

# System initialization, mount local filesystems, etc.
si::sysinit:/sbin/openrc sysinit

# Further system initialization, brings up the boot runlevel.
rc::bootwait:/sbin/openrc boot

l0u:0:wait:/sbin/telinit u
l0:0:wait:/sbin/openrc shutdown
l0s:0:wait:/sbin/halt.sh
l1:1:wait:/sbin/openrc single
l2:2:wait:/sbin/openrc nonetwork
l3:3:wait:/sbin/openrc default
l4:4:wait:/sbin/openrc default
l5:5:wait:/sbin/openrc default
l6u:6:wait:/sbin/telinit u
l6:6:wait:/sbin/openrc reboot
l6r:6:wait:/sbin/reboot -dkn
#z6:6:respawn:/sbin/sulogin

# new-style single-user
su0:S:wait:/sbin/openrc single
su1:S:wait:/sbin/sulogin

# TERMINALS
#x1:12345:respawn:/sbin/agetty 38400 console linux
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux

# SERIAL CONSOLES
#s0:12345:respawn:/sbin/agetty -L 115200 ttyS0 vt100
#s1:12345:respawn:/sbin/agetty -L 115200 ttyS1 vt100

# What to do at the "Three Finger Salute".
ca:12345:ctrlaltdel:/sbin/shutdown -r now

# Used by /etc/init.d/xdm to control DM startup.
# Read the comments in /etc/init.d/xdm for more
# info. Do NOT remove, as this will start nothing
# extra at boot if /etc/init.d/xdm is not added
# to the "default" runlevel.
x:a:once:/etc/X11/startDM.sh

[Hu]

If you get a blinking cursor on the F2 console, that suggests to me that your graphics stack is working properly. The kernel is able to draw on your screen, but it has almost nothing to show you. That inittab looks reasonable to me. When you are on the F2 terminal, if you type printable characters or press enter, does the system react?

Does Ctrl+Alt+F1 behave differently than Ctrl+Alt+F2?

[Fitap]

When you are on the F2 terminal, if you type printable characters or press enter, does the system react?

None, doesn't system react.

Does Ctrl+Alt+F1 behave differently than Ctrl+Alt+F2?

None