You are not logged in.

#1 2020-06-20 18:49:46

regid
Member
Registered: 2016-06-06
Posts: 171

Switching between X and VTs is problematic

  1. Xorg was started manually from VT1.

  2. While in Xorg, pressing leftctrl+leftalt+F2 to switch to VT2: Mouse cursor disappears. There is a noticeable delay before switching to VT2. Now VT2 is the active VT.

  3. At VT2, pressing the leftwindows key returnes to Xorg.

  4. Trying again to switch to VT2 by pressing leftctrl+leftalt+F2 to switch to VT2 makes the mouse cursor disappears. The mouse and keyboard seems to hang. Pressing some keys doesn’t echos them to the screen. Attempting to switch to another VT, for example VT3 with leftctrl+leftalt+F3, is successful. At this point the active VT is VT3.

  5. At the current VT, VT3 in this description, pressing the leftwindows key makes it switch to the previous active VT. VT2 in this description. It also echos to the screen the keys that were not echoed to the screen previously. Pressing the leftwindows key once again makes it returns to Xorg.

  6. At this point, switching back and forth between Xorg and VT2 might be smooth. However, switching between Xorg and VT3 is problematic. Keys that were not echoed to the screen previously might now be echoed.

The issue is not windows manager specific. It does behaves similarly, but not exactly as described above, when running an xterm with no windows manager present.
I think the issue started sometimes at the last couple of weeks.


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#2 2020-06-22 14:12:49

bbonetc
Member
Registered: 2013-07-16
Posts: 1

Re: Switching between X and VTs is problematic

Very similar recent behavior on all my Arch Linux machines (5 running various combinations of hardware). I startx from a console, run XFCE or Openbox desktop sometimes. Switching from Xorg to a onsole is blank, then if ctl-alt-Fx to another console it works and  then switching between console VTs is normal until I go back to X. Just new and annoying for now.

I run no special software and tend toward minimal installs. Been only linux since 1999, mostly Arch Linux.

Offline

#3 2020-06-23 09:09:33

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

It looks to be X, or some under layers, issue.
Those starting X manually from a VT, with xinit, might be able to verify the problem as follows:

  1. mv -v .xinitrc .xinitrc.bak

  2. echo ' #!/bin/bash \n exec xterm ' > .xinitrc .
    For that, the xterm package is required to be installed. Some other X client, say xorg-xeyes, will do.

This assumes the working directory is wassumes the working directory is where the .xinitrc file is located.here the .xinitrc file is located.
A black screen with only an xterm will be presented after X is started by means of the xinit command. If X was already started when running the previous commands, it must be terminated first.
Now start X and try to switch to a VT. Possibly by ctrl+alt+F2. after some experiments you will succeed. Possibly with ctrl+alt+F3. At that point, restore your usual environment with

  1. pkill xinit

  2. mv -v .xinitrc.bak .xinitrc

Again, assuming the working directory is where the .xinitrc file is located.


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#4 2020-06-23 11:31:02

seth
Member
Registered: 2012-09-03
Posts: 15,372

Re: Switching between X and VTs is problematic

When you return to X11 "unexpectedly", can you perform normal I/O there (ie. click w/ the mouse on something and see the expected reaction or just type into the xterm etc)
If not: if you type into the xterm and seek to return to the VT that you were drawn from: does the input end up there?

If none of the above: can you reliably change the VT w/ "chvt"?

(This could be framebuffer related, if you can ssh into the system, check the status of "fgconsole" on the various VT conditions)

Offline

#5 2020-06-23 19:00:17

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

There is definitely a problem. It happens more often then not. But I can not find a definite sequence of events to always reproduce it. Perhaps after the 1st activation of xinit from VT1 it always requires more then one combination of ctrl+alt+F2 to switch from the xterm to VT2. But I am not sure if that is always the case.

seth wrote:

When you return to X11 "unexpectedly", can you perform normal I/O there (ie. click w/ the mouse on something and see the expected reaction or just type into the xterm etc)

Sometimes I can, and sometimes it freezes. No mouse cursor to be seen. Or no echoed characters to the xterm. Or Both. Or neither of the two, it just works as expected. By freezing I mean it will eventually succeed to switch from the xterm to some of the VTs. After repeatedly issuing the ctrl+alt+F(some digit)  itself. I assume this was not what you looking for. Is it?t from within an xtermsequence.

seth wrote:

If not: if you type into the xterm and seek to return to the VT that you were drawn from: does the input end up there?

When typed characters not echoed to the xterm, it does seem to end up in the VT after I manage to get back there. As if they were redirected to the VT, but the screen kept displaying the xterm. But I am confused if that is always the case, or just only sometimes. I am also confused if the characters ended up in one VT, and I had to switch to another VT, and then switch to the VT where the characters ended in.

seth wrote:

If none of the above: can you reliably change the VT w/ "chvt"?

It does looks like I can reliably chvt from another VT. I assume it is expected not to be able to chvt from within the xterm:

$ chvt 4
Couldn't get a file descriptor referring to the console
seth wrote:

(This could be framebuffer related, if you can ssh into the system, check the status of "fgconsole" on the various VT conditions)

I can not ssh to the machine at all.


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#6 2020-06-23 21:19:26

seth
Member
Registered: 2012-09-03
Posts: 15,372

Re: Switching between X and VTs is problematic

You're absolutely supposed to be able to switch the VT from xterm, you might require root permissions.

ls -l /dev/tty*

Offline

#7 2020-06-24 15:13:02

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

seth wrote:

You're absolutely supposed to be able to switch the VT from xterm, you might require root permissions.

ls -l /dev/tty*
/dev/tty* permissions

/dev/tty is 0666 root.tty
/dev/tty1, from which xinit was run, is 0640 myUsername.tty
Edit: I am confused about /dev/tty1 permissions. It is now 0600 myUsername.tty. I think I have to be told when exactly to check it.
/dev/tty2, 0600 myUsername.tty, but only after I logged in to VT2.
All the other ttys are 0640 root.tty

After running xinit from VT1:

Trying to use ctrl+alt+F2 to switch from xterm to VT2
Using ctrl+alt+F2 in order to switch from xterm to VT2 works only once. After returning to xterm, issuing another ctrl+alt+F2 mostly hangs the xterm. I had to ctrl+alt+F3 to get from the xterm to VT3. From VT3 I could switch to VT2. Yet it does looks like that after the xterm hanged, keyboard keystrokes ends in VT2.

Trying to use chvt to switch from xterm to VT2
Issuing chvt in the xterm by my UID always returns

Couldn't get a file descriptor referring to the console

Issuing chvt in the xterm as root hangs, in the same manner that ctrl+alt+F2 hangs.

Last edited by regid (2020-06-24 15:20:03)


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#8 2020-06-24 18:34:44

seth
Member
Registered: 2012-09-03
Posts: 15,372

Re: Switching between X and VTs is problematic

Yeah, I was actually more interested in whether tty4 exists (and on which permissions)

Anyway, chvt ultimately shows the same behavior.

Yet it does looks like that after the xterm hanged, keyboard keystrokes ends in VT2.

Framebuffer issue. Switching among the non-X11 VTEs generally works fine (eg. when there's no X11 at all)?

Please post your xorg log, wild guess: drop xf86-video-intel

Offline

#9 2020-06-25 07:47:30

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

seth wrote:

Framebuffer issue. Switching among the non-X11 VTEs generally works fine (eg. when there's no X11 at all)?

Yes. Switching among the non-X11 VTs generally works fine.

seth wrote:

Please post your xorg log, wild guess: drop xf86-video-intel

It is an Intel board. xf86-video-intel was not installed. But i915, and related, kernel modules are installed. And probably used.

[   307.000] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[   307.003] 
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
[   307.011] Build Operating System: Linux Arch Linux
[   307.015] Current Operating System: Linux m43 5.7.4-arch1-1 #1 SMP PREEMPT Thu, 18 Jun 2020 16:01:07 +0000 x86_64
[   307.015] Kernel command line: initrd=\efi\archlinux\intel-ucode.img initrd=\efi\archlinux\initramfs-linux.img root=UUID=c43f0b41-d306-471b-a012-8e4614d99009 ro
[   307.017] Build Date: 05 May 2020  05:08:17AM
[   307.017]  
[   307.018] Current version of pixman: 0.40.0
[   307.020] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   307.020] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   307.024] (==) Log file: "/home/u52/.local/share/xorg/Xorg.0.log", Time: Thu Jun 25 07:19:46 2020
[   307.065] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   307.087] (==) No Layout section.  Using the first Screen section.
[   307.087] (==) No screen section available. Using defaults.
[   307.087] (**) |-->Screen "Default Screen Section" (0)
[   307.087] (**) |   |-->Monitor "<default monitor>"
[   307.096] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   307.096] (==) Automatically adding devices
[   307.096] (==) Automatically enabling devices
[   307.096] (==) Automatically adding GPU devices
[   307.096] (==) Automatically binding GPU devices
[   307.096] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   307.103] (WW) The directory "/usr/share/fonts/misc" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[   307.103] 	Entry deleted from font path.
[   307.103] (==) FontPath set to:
	
[   307.103] (==) ModulePath set to "/usr/lib/xorg/modules"
[   307.103] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   307.103] (II) Module ABI versions:
[   307.103] 	X.Org ANSI C Emulation: 0.4
[   307.103] 	X.Org Video Driver: 24.1
[   307.103] 	X.Org XInput driver : 24.1
[   307.103] 	X.Org Server Extension : 10.0
[   307.104] (++) using VT number 1

[   307.104] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   307.106] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   307.107] (II) xfree86: Adding drm device (/dev/dri/card0)
[   307.107] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 9 paused 0
[   307.110] (--) PCI:*(0@0:2:0) 8086:041e:8086:2052 rev 6, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[   307.110] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   307.110] (II) LoadModule: "glx"
[   307.142] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   307.216] (II) Module glx: vendor="X.Org Foundation"
[   307.216] 	compiled for 1.20.8, module version = 1.0.0
[   307.216] 	ABI class: X.Org Server Extension, version 10.0
[   307.216] (==) Matched intel as autoconfigured driver 0
[   307.216] (==) Matched modesetting as autoconfigured driver 1
[   307.216] (==) Matched fbdev as autoconfigured driver 2
[   307.216] (==) Matched vesa as autoconfigured driver 3
[   307.216] (==) Assigned the driver to the xf86ConfigLayout
[   307.216] (II) LoadModule: "intel"
[   307.222] (WW) Warning, couldn't open module intel
[   307.222] (EE) Failed to load module "intel" (module does not exist, 0)
[   307.222] (II) LoadModule: "modesetting"
[   307.222] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   307.239] (II) Module modesetting: vendor="X.Org Foundation"
[   307.239] 	compiled for 1.20.8, module version = 1.20.8
[   307.239] 	Module class: X.Org Video Driver
[   307.239] 	ABI class: X.Org Video Driver, version 24.1
[   307.239] (II) LoadModule: "fbdev"
[   307.240] (WW) Warning, couldn't open module fbdev
[   307.240] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   307.240] (II) LoadModule: "vesa"
[   307.240] (WW) Warning, couldn't open module vesa
[   307.240] (EE) Failed to load module "vesa" (module does not exist, 0)
[   307.240] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   307.240] (II) modeset(0): using drv /dev/dri/card0
[   307.240] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   307.240] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[   307.240] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   307.240] (==) modeset(0): RGB weight 888
[   307.240] (==) modeset(0): Default visual is TrueColor
[   307.240] (II) Loading sub module "glamoregl"
[   307.240] (II) LoadModule: "glamoregl"
[   307.241] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   307.282] (II) Module glamoregl: vendor="X.Org Foundation"
[   307.282] 	compiled for 1.20.8, module version = 1.0.1
[   307.282] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   307.986] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2)
[   307.986] (II) modeset(0): glamor initialized
[   307.987] (II) modeset(0): Output VGA-1 has no monitor section
[   307.989] (II) modeset(0): Output HDMI-1 has no monitor section
[   307.990] (II) modeset(0): Output HDMI-2 has no monitor section
[   307.999] (II) modeset(0): EDID for output VGA-1
[   307.999] (II) modeset(0): Printing probed modes for output VGA-1
[   307.999] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   307.999] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   307.999] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   307.999] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[   307.999] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   308.001] (II) modeset(0): EDID for output HDMI-1
[   308.002] (II) modeset(0): EDID for output HDMI-2
[   308.002] (II) modeset(0): Output VGA-1 connected
[   308.002] (II) modeset(0): Output HDMI-1 disconnected
[   308.002] (II) modeset(0): Output HDMI-2 disconnected
[   308.002] (II) modeset(0): Using exact sizes for initial modes
[   308.002] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0
[   308.002] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[   308.002] (==) modeset(0): DPI set to (96, 96)
[   308.002] (II) Loading sub module "fb"
[   308.002] (II) LoadModule: "fb"
[   308.002] (II) Loading /usr/lib/xorg/modules/libfb.so
[   308.010] (II) Module fb: vendor="X.Org Foundation"
[   308.010] 	compiled for 1.20.8, module version = 1.0.0
[   308.010] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   308.968] (==) modeset(0): Backing store enabled
[   308.968] (==) modeset(0): Silken mouse disabled
[   308.973] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[   308.973] (==) modeset(0): DPMS enabled
[   308.973] (II) modeset(0): [DRI2] Setup complete
[   308.973] (II) modeset(0): [DRI2]   DRI driver: i965
[   308.973] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[   308.973] (II) Initializing extension Generic Event Extension
[   308.973] (II) Initializing extension SHAPE
[   308.973] (II) Initializing extension MIT-SHM
[   308.973] (II) Initializing extension XInputExtension
[   308.973] (II) Initializing extension XTEST
[   308.973] (II) Initializing extension BIG-REQUESTS
[   308.973] (II) Initializing extension SYNC
[   308.973] (II) Initializing extension XKEYBOARD
[   308.973] (II) Initializing extension XC-MISC
[   308.973] (II) Initializing extension SECURITY
[   308.973] (II) Initializing extension XFIXES
[   308.973] (II) Initializing extension RENDER
[   308.973] (II) Initializing extension RANDR
[   308.973] (II) Initializing extension COMPOSITE
[   308.973] (II) Initializing extension DAMAGE
[   308.973] (II) Initializing extension MIT-SCREEN-SAVER
[   308.974] (II) Initializing extension DOUBLE-BUFFER
[   308.974] (II) Initializing extension RECORD
[   308.974] (II) Initializing extension DPMS
[   308.974] (II) Initializing extension Present
[   308.974] (II) Initializing extension DRI3
[   308.974] (II) Initializing extension X-Resource
[   308.974] (II) Initializing extension XVideo
[   308.974] (II) Initializing extension XVideo-MotionCompensation
[   308.974] (II) Initializing extension GLX
[   308.982] (II) AIGLX: Loaded and initialized i965
[   308.982] (II) GLX: Initialized DRI2 GL provider for screen 0
[   308.982] (II) Initializing extension XFree86-VidModeExtension
[   308.982] (II) Initializing extension XFree86-DGA
[   308.982] (II) Initializing extension XFree86-DRI
[   308.982] (II) Initializing extension DRI2
[   309.067] (II) modeset(0): Damage tracking initialized
[   309.067] (II) modeset(0): Setting screen physical size to 270 x 203
[   309.630] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   309.630] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   309.630] (II) LoadModule: "libinput"
[   309.630] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[   309.669] (II) Module libinput: vendor="X.Org Foundation"
[   309.669] 	compiled for 1.20.8, module version = 0.30.0
[   309.669] 	Module class: X.Org XInput Driver
[   309.669] 	ABI class: X.Org XInput driver, version 24.1
[   309.669] (II) Using input driver 'libinput' for 'Power Button'
[   309.670] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 14 paused 0
[   309.670] (**) Power Button: always reports core events
[   309.670] (**) Option "Device" "/dev/input/event1"
[   309.670] (**) Option "_source" "server/udev"
[   309.753] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   309.753] (II) event1  - Power Button: device is a keyboard
[   309.754] (II) event1  - Power Button: device removed
[   309.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[   309.754] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   309.756] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   309.756] (II) event1  - Power Button: device is a keyboard
[   309.757] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[   309.757] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[   309.757] (II) Using input driver 'libinput' for 'Video Bus'
[   309.759] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 17 paused 0
[   309.759] (**) Video Bus: always reports core events
[   309.759] (**) Option "Device" "/dev/input/event2"
[   309.759] (**) Option "_source" "server/udev"
[   309.762] (II) event2  - Video Bus: is tagged by udev as: Keyboard
[   309.762] (II) event2  - Video Bus: device is a keyboard
[   309.762] (II) event2  - Video Bus: device removed
[   309.762] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2/event2"
[   309.762] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[   309.764] (II) event2  - Video Bus: is tagged by udev as: Keyboard
[   309.765] (II) event2  - Video Bus: device is a keyboard
[   309.766] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[   309.766] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   309.766] (II) Using input driver 'libinput' for 'Power Button'
[   309.767] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 18 paused 0
[   309.767] (**) Power Button: always reports core events
[   309.767] (**) Option "Device" "/dev/input/event0"
[   309.767] (**) Option "_source" "server/udev"
[   309.767] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   309.767] (II) event0  - Power Button: device is a keyboard
[   309.767] (II) event0  - Power Button: device removed
[   309.767] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[   309.767] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[   309.768] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   309.768] (II) event0  - Power Button: device is a keyboard
[   309.768] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event6)
[   309.768] (II) No input driver specified, ignoring this device.
[   309.768] (II) This device may have been added with another device file.
[   309.769] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event7)
[   309.769] (II) No input driver specified, ignoring this device.
[   309.769] (II) This device may have been added with another device file.
[   309.769] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event8)
[   309.769] (II) No input driver specified, ignoring this device.
[   309.769] (II) This device may have been added with another device file.
[   309.769] (II) config/udev: Adding input device Dell Dell QuietKey Keyboard (/dev/input/event3)
[   309.769] (**) Dell Dell QuietKey Keyboard: Applying InputClass "libinput keyboard catchall"
[   309.769] (II) Using input driver 'libinput' for 'Dell Dell QuietKey Keyboard'
[   309.770] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 19 paused 0
[   309.770] (**) Dell Dell QuietKey Keyboard: always reports core events
[   309.770] (**) Option "Device" "/dev/input/event3"
[   309.770] (**) Option "_source" "server/udev"
[   309.771] (II) event3  - Dell Dell QuietKey Keyboard: is tagged by udev as: Keyboard
[   309.771] (II) event3  - Dell Dell QuietKey Keyboard: device is a keyboard
[   309.771] (II) event3  - Dell Dell QuietKey Keyboard: device removed
[   309.771] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0/0003:413C:2106.0001/input/input3/event3"
[   309.771] (II) XINPUT: Adding extended input device "Dell Dell QuietKey Keyboard" (type: KEYBOARD, id 9)
[   309.772] (II) event3  - Dell Dell QuietKey Keyboard: is tagged by udev as: Keyboard
[   309.772] (II) event3  - Dell Dell QuietKey Keyboard: device is a keyboard
[   309.773] (II) config/udev: Adding input device PixArt HP USB Optical Mouse (/dev/input/event4)
[   309.773] (**) PixArt HP USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[   309.773] (II) Using input driver 'libinput' for 'PixArt HP USB Optical Mouse'
[   309.773] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 20 paused 0
[   309.773] (**) PixArt HP USB Optical Mouse: always reports core events
[   309.773] (**) Option "Device" "/dev/input/event4"
[   309.773] (**) Option "_source" "server/udev"
[   309.774] (II) event4  - PixArt HP USB Optical Mouse: is tagged by udev as: Mouse
[   309.774] (II) event4  - PixArt HP USB Optical Mouse: device is a pointer
[   309.775] (II) event4  - PixArt HP USB Optical Mouse: device removed
[   309.775] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-8/2-8:1.0/0003:03F0:134A.0002/input/input4/event4"
[   309.775] (II) XINPUT: Adding extended input device "PixArt HP USB Optical Mouse" (type: MOUSE, id 10)
[   309.775] (**) Option "AccelerationScheme" "none"
[   309.775] (**) PixArt HP USB Optical Mouse: (accel) selected scheme none/0
[   309.775] (**) PixArt HP USB Optical Mouse: (accel) acceleration factor: 2.000
[   309.775] (**) PixArt HP USB Optical Mouse: (accel) acceleration threshold: 4
[   309.776] (II) event4  - PixArt HP USB Optical Mouse: is tagged by udev as: Mouse
[   309.776] (II) event4  - PixArt HP USB Optical Mouse: device is a pointer
[   309.776] (II) config/udev: Adding input device PixArt HP USB Optical Mouse (/dev/input/mouse0)
[   309.776] (II) No input driver specified, ignoring this device.
[   309.776] (II) This device may have been added with another device file.
[   309.777] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[   309.777] (II) No input driver specified, ignoring this device.
[   309.777] (II) This device may have been added with another device file.
[   309.777] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event11)
[   309.777] (II) No input driver specified, ignoring this device.
[   309.777] (II) This device may have been added with another device file.
[   309.777] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[   309.777] (II) No input driver specified, ignoring this device.
[   309.777] (II) This device may have been added with another device file.
[   309.777] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event9)
[   309.777] (II) No input driver specified, ignoring this device.
[   309.777] (II) This device may have been added with another device file.
[   309.778] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[   309.778] (II) No input driver specified, ignoring this device.
[   309.778] (II) This device may have been added with another device file.

pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#10 2020-06-25 10:35:06

seth
Member
Registered: 2012-09-03
Posts: 15,372

Re: Switching between X and VTs is problematic

[   307.999] (II) modeset(0): Printing probed modes for output VGA-1
[   307.999] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   307.999] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   307.999] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   307.999] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[   307.999] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)

What kind of an output is this? Really a 13" 4:3 XGA monitor?

xf86-video-intel was not installed.

In this case I'll just reverse the random blame-game: try to install it ;-)

Offline

#11 2020-06-25 16:32:50

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

seth wrote:

What kind of an output is this? Really a 13" 4:3 XGA monitor?

It is an old 19" (diagonal) 5:4. Possibly SXGA.
User's manual recommends VESA 1280 x 1024 @60 Hz. It also states information is subject to change without notice. MS Windows also seem to use 1024x768@60 by default. Though it offers 1280x1024, and possibly 1280x1152, with Intel tools.

seth wrote:

xf86-video-intel was not installed.

In this case I'll just reverse the random blame-game: try to install it ;-)

Before playing blame-game I tried to downgrade the kernel. Current arch's xorg-server was built at 05-May-2020. linux-5.6.15.arch1-1, built at 27-May-2020, doesn't demonstrate the switching problem. In contrast, I can see it with linux-5.7.2.arch1-1. Though there was a smiley, I am offended by your suggestion to install xf86-video-intel. Shouldn't I got offended?


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

#12 2020-06-25 18:27:25

seth
Member
Registered: 2012-09-03
Posts: 15,372

Re: Switching between X and VTs is problematic

Shouldn't I got offended?

For me randomly blaming the intel and then the modesetting driver? Why?
(In case that wasn't clear enough: *I* blatantly reversed *my* blame direction, not saying you were blaming anything - because you weren't)

You may however still want to test whether the intel driver plays better w/ the i915 module, though since this is a kernel regression, I doubt it.
There're several posts about issues w/ i915 and the 5.7 kernels, this probably just falls into that category as well then, see eg. https://bbs.archlinux.org/viewtopic.php?id=256520

Offline

#13 2020-06-26 17:01:59

regid
Member
Registered: 2016-06-06
Posts: 171

Re: Switching between X and VTs is problematic

I wonder what hardware is used by bbonetc, who posted the 2nd message in this thread. In particular, does his hardware i915 related? What are his kernels version?


pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver (AUR): PPDs, drivers, for Pantum P1000, P2000, P3000, M5100, M5200 printers.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.

Offline

Board footer

Powered by FluxBB