On Sun, 9 Apr 2017 16:50:44 -0500 Ian Pilcher <arequipeno@xxxxxxxxx> wrote: > I'm not sure when this started, but I am unable to switch away from my > X VT (usually VT 1) to a text VT. > > Actually, blind-typing shows that I am actually able to switch to the > text VT, but nothing shows up; I'm left looking at a "frozen" version > of the X VT contents. > > I am using an AMD/ATI FirePro V4900 with the open source drivers. > > Anyone else seeing anything like this? No. On F25, using X, not Wayland or Xwayland, switching to virtual term works fine (on LXDE). Also using radeon driver. I think it is fbdev(2?) (frame buffer device) that is used for the VTs, and it should be compiled into the kernel. Look in your boot logs for tty, to see if the VTs are being started. journalctl -b 00:08: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A console [tty0] enabled I think they are started on demand by systemd for all but tty0. I explicitly start them at boot, so my experience might not be the same as yours. It could be that systemd, or getty, isn't starting them correctly when you switch to them. systemd[1]: Started Getty on tty1. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res= _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
