At least as recently as Linux Mint 20, a behavior existed where Win+Ctrl would be the be sent to a web-based virtual console as Ctrl and Win+Alt would be sent as Alt, which would prevent browser shortcuts from interfering with console shortcuts. I have tried the Mint virtual keyboard, two different browsers (Firefox and Brave), and two different ISPs (Vultr and Frantech), and Win+Ctrl+\ is only sent to the virtual console as \. Note that using another computer with Mint 21.3 the behavior is the same. Is there a way to make Win+Ctrl be sent to the console as Ctrl and Win+Alt be sent to the console as Alt?

I am now running Ubuntu 20.04, and using server: Wayland. I have no idea how to disable virtual console switch under Wayland. Under the X.org server adding this: Option "DontVTSwitch" "True" to /etc/X11/xorg.conf prevents virtual console switch.

As I type this, in my Netrunner Debian 12 KDE system, if I hit for example Ctrl-Alt-F3, it gives a terminal login prompt. * I can't get past that prompt. If I type the username and password correctly, it just clears the screen and shows the terminal login prompt again. * I can still go back to the GUI using Ctrl-Alt-F7 to keep typing this question. Any suggestions where to look? * /var/log/syslog contains this after doing that:

2024-11-27T18:59:14.388452-08:00 RzT470Netrunner systemd: Started session-1623.scope - Session 1623 of User rinzin.
    2024-11-27T18:59:14.394477-08:00 RzT470Netrunner wireplumber: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed?
    2024-11-27T18:59:14.394688-08:00 RzT470Netrunner wireplumber: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.
    2024-11-27T18:59:14.396358-08:00 RzT470Netrunner systemd: getty@tty3.service: Deactivated successfully.
    2024-11-27T18:59:14.410998-08:00 RzT470Netrunner systemd: session-1623.scope: Deactivated successfully.
    2024-11-27T18:59:14.411962-08:00 RzT470Netrunner systemd: getty@tty3.service: Scheduled restart job, restart counter is at 3.
    2024-11-27T18:59:14.412850-08:00 RzT470Netrunner systemd: Stopped getty@tty3.service - Getty on tty3.
    2024-11-27T18:59:14.436539-08:00 RzT470Netrunner systemd: Started getty@tty3.service - Getty on tty3.
    2024-11-27T18:59:16.025507-08:00 RzT470Netrunner rtkit-daemon: Supervising 0 threads of 0 processes of 0 users.
    2024-11-27T18:59:16.034408-08:00 RzT470Netrunner rtkit-daemon: Supervising 0 threads of 0 processes of 0 users.
    2024-11-27T18:59:20.238554-08:00 RzT470Netrunner wireplumber: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed?
    2024-11-27T18:59:20.239586-08:00 RzT470Netrunner wireplumber: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.
    2024-11-27T18:59:21.834857-08:00 RzT470Netrunner kded5: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
    2024-11-27T18:59:21.872833-08:00 RzT470Netrunner kded5: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
    2024-11-27T18:59:21.872895-08:00 RzT470Netrunner kded5: kcm_touchpad: Using X11 backend
    2024-11-27T18:59:21.874708-08:00 RzT470Netrunner kded5: Width:  3794  height:  3036
    2024-11-27T18:59:21.874761-08:00 RzT470Netrunner kded5: Approx. resX:  42  resY:  60
    2024-11-27T18:59:21.874822-08:00 RzT470Netrunner kded5: Touchpad resolution: x:  45  y:  54
    2024-11-27T18:59:21.874863-08:00 RzT470Netrunner kded5: Final resolution x: 45  y: 54
    2024-11-27T18:59:21.881830-08:00 RzT470Netrunner kwin_x11: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43603, resource id: 153092101, major code: 18 (ChangeProperty), minor code: 0

* And with journalctl -r I find this:

Nov 27 19:22:21 RzT470Netrunner login: Permission denied
    Nov 27 19:22:21 RzT470Netrunner login: gkr-pam: couldn't unlock the login keyring.

I run Fedora 24 and sometimes use a virtual console.
(I use Ctrl+Alt+F3 to switch to the virtual console, so it's not a terminal in X).
In the past I could use Shift+PgUp or Shift+PgDown to scroll but today it stopped. In the manpages and in vim the PgUp and PgDown work fine; furthermore the same shortcuts work fine in Xterm. Does anybody know why I lost the shortcuts to scroll the screen in the virtual consoles?

I am using a dell XPS 13 laptop with 4k screen and the text on the virtual console is very small. I would like to increase the font size. With the command sudo dpkg-reconfigure console-setup I took: 1. UTF-8 2. Guess optimal character set 3. TerminusBold 4. 16x32 (framebuffer only) This seems to be the largest font available. Does anyone know if it is possible to obtain larger font sizes somewhere? Can you download them for example? The 16x32 size seems to be the largest available on my system. For a 13 inch 4k screen it is still small. Any help is highly appreciated, I am new to using ubuntu. Another option would be to change the resolution of the tty console. Is it possible to have different resolutions for the tty2-tty6 consoles compared to the tty1 where you use the GUI?

Where can I get/download additional *Console* / Virtual-Terminal (on F1 through F6) fonts - especially larger ones? I'm here talking about the font that can be set with the setfont command. Also, are there any tools letting me convert other font-formats (like TrueType) to the format used by the console/setfont (I guess assuming it's a fixed-width font)?

I have a server in production which was booted with a 1080p widescreen monitor attached and it used that when it automatically selected that resolution for the console on boot. Currently, it is attached with a standard 1280x1024-capable monitor, but it did not change the resolution to match so long lines go off the edges of the screen. How do I have it redetect the monitor or manually switch the resolution without requiring a reboot of this production server? The console is only needed for certain maintenance and other core operations and we have been able to get by without seeing everything we are typing, but I would like to see if I can fix this sooner than the next, scheduled reboot of the server. Most answers seem to discuss using the obsolete fbset command, but their package was dropped from Fedora about 5 years ago and their official website is defunct now. Also, it looks like CONFIG_FB_DEVICE was not defined in the standard Fedora kernel so there's no /dev/fb* interface to even talk to. What is the current method to change the resolution used by the Linux framebuffer console? I did see some mentions of KMS (Kernel Mode Setting), but no way to use that from the command-line. Also, I did confirm that running startx loads the correct resolution while inside X11, but I would prefer not to keep that running for the time being.

I have an application that binds CTRL+ALT+F7, but my linux machine seems to catch the keystroke. Is there a way to rebind/disable this key? A recompile of the kernel is an acceptable answer. The distributions in question are Fedora 16 and Ubuntu 11.10.

In the early days of computing, the setup is usually like this: and we call the VT-100 "physical terminal". But in Linux, we call virtual terminals "virtual" (the ones accessed by pressing Ctrl + Alt + F*). What I don't understand is why do we call them "virtual". When you use virtual terminal, you are also sitting in front of a screen and you see texts as you type on a keyboard, just like when you are using a VT-100 terminal. How is this "virtual"? How is it different from using a "physical terminal" such as a VT-100? The only difference I can see is that when using a physical terminal you are using a serial cable to connect to the computer. Is using a serial cable what sets apart between physical terminal and virtual terminal?

I am trying to boot a Linux system (Debian 11) with an NVIDIA GPU; I need to avoid loading the nouveau driver, which I can do if I include some options on the linux command line (in grub.cfg):

terminal_input console
terminal_output console
set gfxmode=text
set timeout=5

menuentry 'Debian 11' {
  linux /debian11/boot/vmlinuz-5.10.0-22-amd64 console=tty0 ip=dhcp root=/dev/nfs ro nfsroot=192.168.50.111:/image/debian11,vers=3,nolock panic=60 ipv6.disable=1 rootwait vga=normal nofb nomodeset video=vesafb:off
  initrd /debian11/boot/initrd.img-5.10.0-22-amd64
}

The reason for doing this is that I need to load NVIDIA's proprietary modules, and it works OK, as far as it goes. The unfortunate consequence of this is that I no longer have the VTYs available - not a huge problem, since this is for a server that is mostly accessed via ssh, but sometimes it is necessary to look at the text console, so I'd like to have it back - but without loading the nouveau module. This used to be perfectly easy in the past, but it seems the kernel insists on loading a framebuffer device instead of just printing text. Is there a way to fix this?

Please, correct me if the wording of the title is wrong, as I do want to understand the correct terminology too. The think is, I can swtich using Ctrl+Alt+F _N_ between different window managers each launched on a different virtual console. I've always used one, but these days I'm experimenting with a new window manager (XMonad) while still mainly using the one I've used for years (i3), so I'm frequently switching from one to another and viceversa. In practical terms, I have this config in place:

[[ "$XDG_VTNR" -eq 1 ]] && exec i3
[[ "$XDG_VTNR" -eq 2 ]] && exec xmonad

One thing I've noticed is that if I open Chromium, the first time it will open in the current session, e.g. i3, but if open another Chromium process, it will open in i3 even if in the meanwhile I switched to xmonad. Same thing the other way around. Do I have control on this behavior? How?

I noticed that in Debian 12 (amd64, but I guess that's independent of the platform actually), when a user logs into the graphical UI (Xorg based with nvidia), the GDM3 server no longer is active on :0 and switching users is not available as prominently as it used to be in older Debian distributions. Also, when going to the text virtual console with Ctrl-Alt-F[1-7] not getty process seems to be activated by default nowadays. This causes problems when I start an X server for remote rendering with TurboVNC and VirtualGL because startx then places the newly created X server port on :0 and prevents GDM3 from relaunching. Also, I can't simply enter a text console when the graphics is hosed. I did not find any mention of those changes in the bookworm release notes, so I wondered if I could get the old behaviour back? And on another note, if not, if there is some command-line tool to query the next available X server slot above a certain threshold? SSH X11 forwarding seems to be using to not interfere with X servers launched by GDM3, which I would like to emulate here.

I remember some time ago I couldn't start X in two consoles at the same time. What I mean, if I had i3 running on tty7, I could do Ctrl+Alt+F6 to go to tty6, I could log in, but I couldn't start another, say i3 session. Recently I've noticed it's possible. When did this change occur?

In the past you could trivially replace NVIDIA proprietary drivers on the fly after switching to the text console, killing X.org and unloading (rmmod) the appropriate NVIDIA modules, and installing new drivers. However nowadays NVIDIA recommends to run the driver with KMS support, options nvidia-drm modeset=1 and that makes it impossible to unload kernel modules ("The device is busy"). The Linux kernel allows to unbind the graphical driver from the text console by running this command:

echo 0 > /sys/class/vtconsole/vtcon1/bind

However this command results in all the text consoles being completely dead. They just freeze, the system keeps running. Looks like after this command, one needs to run another command to make the kernel re-enable built-in drivers which drove text consoles prior to NVIDIA drivers, only the Internet has no information on that. This question is **not** limited to NVIDIA drivers. Would be nice to know how to unload an open source KMS driver, be it Intel, AMD or Nouveau. Here's what I see on boot:

Console: colour dummy device 80x25
printk: console [tty0] enabled
fbcon: Deferring console take-over
fbcon: Taking over console
Console: switching to colour frame buffer device 128x48

Here's what I have in my .config:

CONFIG_SYSFB=y
CONFIG_SYSFB_SIMPLEFB=y
CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=200
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
CONFIG_FB_SIMPLE=y

Here's what I have in /sys:

$ find /sys -iname '*fb*'
/sys/class/graphics/fb0
/sys/class/graphics/fbcon
/sys/devices/platform/simple-framebuffer.0/graphics/fb0
/sys/devices/virtual/graphics/fbcon
/sys/module/drm_kms_helper/parameters/drm_fbdev_overalloc
/sys/module/drm_kms_helper/parameters/fbdev_emulation
/sys/module/fb
/sys/module/fb/parameters/lockless_register_fb

So after 3 times of trying to install arch Linux, I finally succeeded. I've noticed that when I was booting from my USB drive, the text size in the terminal was a lot smaller than it is when using the actual installed operating system. I was able to see a lot of text on one line, but now it takes up two or three lines. It's just annoying trying to read "locale" and have the "loc" on the right side of the screen and have "ale" on the left side on the next line. I don't have a desktop environment yet. I am talking about the text size seen on the virtual terminals, logging in at a TUI login:prompt. Is there any way that I can make the text size smaller?

Firstly, I switched to some virtual console with Ctrl+Alt+F2-6 even right after installing Debian 11 with KDE and, secondly, I tried to type something in that console. No letters appear, but it works with numerals. As you know, a login prompt appears first. So I can't login in the system via those consoles. Initially, logged in through the GUI.

I recently switched from DE-ISO to US-ANSI layout and have an issue across my Archlinux machines that I cannot resolve which is a bit painful as the encryption key expects German layout but my keyboard is US. Here is what I have tried so far: 1. Checked that the US keymap is available on my system:

~
    ❯ localectl list-keymaps | grep -iI "us"
    
    amiga-us
    atari-us
    br-latin1-us
    cz-us-qwertz
    is-latin1-us
    mac-us
    sunt5-cz-us
    sunt5-us-cz
    us
    us-acentos
    us1

1. Changed KEYMAP for the vconsole:

~
    ❯ cat /etc/vconsole.conf
    KEYMAP=us
    FONT=lat9w-16

2. Ensured that the keymap hook comes before the encrypt one in mkinitcpio:

~
    ❯ grep -iI "hooks" /etc/mkinitcpio.conf
    # The following modules are loaded before any boot hooks are
    # HOOKS
    # This is the most important setting in this file.  The HOOKS control the
    # order in which HOOKS are added.  Run 'mkinitcpio -H ' for
    #    HOOKS=(base)
    #    HOOKS=(base udev autodetect block filesystems)
    #    HOOKS=(base udev block filesystems)
    #    HOOKS=(base udev block mdadm encrypt filesystems)
    #    HOOKS=(base udev block lvm2 filesystems)
    #    usr, fsck and shutdown hooks.
    HOOKS=(base udev autodetect modconf block keyboard keymap consolefont encrypt filesystems fsck shutdown)

3. Rebuilt mkinitcpio for the current Linux kernel:

~
    ❯ sudo mkinitcpio -p linux
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 6.0.8-arch1-1
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: xhci_pci
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [consolefont]
      -> Running build hook: [encrypt]
    ==> WARNING: Possibly missing firmware for module: qat_4xxx
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
      -> Running build hook: [shutdown]
    ==> Generating module dependencies
    ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 6.0.8-arch1-1
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: qed
    ==> WARNING: Possibly missing firmware for module: qla1280
    ==> WARNING: Possibly missing firmware for module: wd719x
    ==> WARNING: Possibly missing firmware for module: qla2xxx
    ==> WARNING: Possibly missing firmware for module: bfa
    ==> WARNING: Possibly missing firmware for module: aic94xx
    ==> WARNING: Possibly missing firmware for module: xhci_pci
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [consolefont]
      -> Running build hook: [encrypt]
    ==> WARNING: Possibly missing firmware for module: qat_4xxx
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
      -> Running build hook: [shutdown]
    ==> Generating module dependencies
    ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
    ==> Image generation successful

However, when I boot the system, it fails to decrypt my device and between two encryption attempts I keep hitting random keys to see which keymap is active and it turns out it's still the German ISO layout.

~
❯ uname -a
Linux bunda 6.0.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Nov 2022 21:14:24 +0000 x86_64 GNU/Linux

Is there any other location I could have defined that? What else could I check?

I have a wireless Logitech mouse and keyboard combo and I want to remap capslock to leftctrl and vice versa for the Linux console as well as the X terminal so I want to use the instructions [here](https://wiki.archlinux.org/title/Map_scancodes_to_keycodes) . The steps I have taken so far are: 1. I have identified the scancodes that I am interested in by going to a virtual console with Ctrl+Alt+F1 and running: showkey -s to reveal the scancodes that I am interested in. These are in decimal so I convert them to hex to get the information I am interested in. 2. I found the keycode as suggested from the wiki (leftctrl, capslock in lowercase) 3. To find which /dev/input/eventX corresponds to the wireless devices I run: sudo evtest|less This will output a list with options which match the Logitech keyboard and mouse. You select the desired option and on the top you can find some nice information. 4. To determine the whole evdev:input:b*v*p*e*-modalias string that must go into the .hwdb file I run cat /sys/class/input/eventX/device/modalias where X is found in the previous step 5. I create a new 61-keyboard.hwdb in /etc/udev/hwdb.d (not in (/usr)/lib/udev/hwdb.d I found that this doesn't update hwdb.bin) and run: sudo systemd-hwdb update; sudo udevadm trigger and run udevadm info /dev/input/by-path/*-*-*-kbd to verify that my KEYBOARD_KEY_=` has been updated correctly aaaaaand nothing happens. I have tried rebooting as well but the change never happens. I have tried globbing the evdev:input: line to make it more general but this has failed to work as well. One thing that I have noticed is that VC keymap: n/a but I don't know if it helps at all. [move]I'm moving![/move] Also I don't know if this is important but I am trying to do this in a Raspberry Pi 4. I am at my wit's end with this can someone help?

1. Why are there so many ttys? Are multiple tty necessary? 2. Why are multiple things spread in different ttys? For eg i have the runit logs on tty1, wm on tty7, and a blinking white cursor on the corner of screen on tty8. Why not everything in one tty? 3. Why doesn't linux place these in order - tty1: runit logs, tty2: wm, etc. 4. What does the binking cursor mean?

As far as I've understood, a terminal emulator is a GUI-based program which gives me a terminal-like viewport and allows me to interact with it just like I'd do with a terminal, except that it has all the support from the X system, so I suspect that ssh user@ip will not give me access to a terminal emulator running on the remote machine. If I want to use that, I need to connect to that machine via VNC, and then open a terminal emulator window in _that_ desktop. But do I get access to a virtual console (one that, physially on the remote machine I'd get via Ctrl+Alt+F2, for instance)? I can ssh -X ..., which gives me access to the clipboard, which comes with X, so it kind of feels I'm not in a virtual console either... --- As regards the proposed duplicate, since my question is specifically about SSH, the information I can gather is the following: - > [Ssh](http://en.wikipedia.org/wiki/Secure_shell) (which connects a terminal on one machine with programs on another machine) [from the accepted answer](https://unix.stackexchange.com/a/4132/164309) , - > pseudoterminals [use PTY “devices” to arrange communication between console applications and the terminal-making program that runs in userspace](https://unix.stackexchange.com/questions/117981/what-are-the-responsibilities-of-each-pseudo-terminal-pty-component-software) . Examples are X-based terminal emulators and sshd, that allocates a pseudotty for each login session. [from another answer](https://unix.stackexchange.com/a/228052/164309) , - > There may be some application that "emulates" terminal accepting keystrokes from user and sending them somewhere (xterm and ssh are good examples). There is an API in Kernel called **pseudo terminal** for that. So your **tty** may really be connected to some application instead of real terminal. Xterm uses X11 to display text and ssh uses network connection for it. [from yet another answer](https://unix.stackexchange.com/a/376058/164309) ; so the answer to my question seems to be "it gives access to a pseudo terminal".