Hi all,
Second attempt at explaining this as first seemed to get reponses that suggested people had misunderstood my problem 
I have a KVM switch (HDMI ond USB) that has 4 ports, currently I have connected :
PC 1 Suse Leap.
PC 2 Windows 10
PC 3 Spare
PC 4 Suse Tumbleweed.
Now if I select PC1 on the KVM, and either turn it on and re-boot it leaving it selected, it will boot correctly and I can login on the console / through X and everything works correctly. I can once booted use the KVM to switch to PC 2 or 4 without problems and switching back works correctly. The monitor type and resolution IS detected correctly so I am fairly certain that the KVM is passing through the monito ID without problems.
However If I say have the Windows PC selected on the KVM, and then ssh into PC1 and tell it to reboot, it will do so. Once booted I can continue to connect to it over the network (via ssh), but if I switch the KVM to it it does not seem to detect the screen, keyboard and mouse, hitting keys or wiggling the mouse gets no reponse and after a few seconds the monitor goes to sleep after detecting no input.
The other Linux PC also behaves the same way. However the Windows PC seems to default to a low resolution and then once you have logged in ajust itself to the detected monitor.
What I need is a way to force PC 1 to always have a screen keyboard and mouse even if it doesn’t detect them at boot time. Is there a way of doing this ?
Cheers.
Phill.
@phillhs if you switch to Wayland on Tumbleweed, does the problem go away?
Can you give me some pointers please, my experience in the past, and the results of a google serach suggest a wayland session is selected from the login screen, I’m not even getting that far no screen is displayed.
As a test I did try setting PC3 to multi-user.target, so that it wouldn’t start the GUI, and that worked, at least in as far as I could remotely reboot and then switch and get the text mode console, which does suggest something about the GUI isn’t working correctly.
Cheers.
Phill.
@phillhs So with the Tumbleweed system switched to the monitor etc on the KVM and booted, you get to a desktop? Which Desktop environment in use?
It switched fine without starting into the GUI, so just booting to text mode desktop. From there I could login and startx to get the gui, though It seemed not to want to close x and go back to the console when I logged out (from the menu). But could CTRL-ALT-F2 to get a second console ok.
Desktop environment is XFCE looking in Yast…
Default desplay manager is /usr/lib/X11/displaymanagers/lightdm
Default xsession.desktop is /usr/share/xsessions/xfce.desktop
I think I set lightdm to be the default so that I could use xvnc to connect to it.
Cheers.
Phill.
Additional, I’ve just rebooted remotely PC3, then switched to it, no screen as expected, however I could CTRL-ALT-F1 to get a text console, login as root
then issue init 3 followed by init 5 and the GUI started without problems. So it deffo looks like a problem with X. At least I have a temporary work around…
Cheers.
Phill.
@phillhs Ahh ok, don’t think Wayland support is there yet for XFCE?
You should be able to get the the desktop as root via systemctl isolate graphical.target && exit if want to drop to a multi-user session, systemctl isolate multi-user.target instead of starx as your user…
So on the linux machines you have a defined xorg.conf file for your setups?
I suspect for the linux machines the udev rules may not be triggered when switching to detect that your usb devices are present, for the screen not sure.
I would inspect the ~/.local/share/xorg/Xorg.0.log or maybe Xorg.1.log to see what happens when you switch and it doesn’t work.
This KVM switch is a powered device, USB powered or passive?
Looking at /var/log/Xorg.0.log I took a copy, switched, wiggled the mouse, tapped the keyboard and then switched back difference between before and after was :
193.082] (--) modeset(0): HDMI max TMDS frequency 300000KHz
[ 193.490] (II) config/udev: Adding input device CHESEN PS2 to USB Converter Mouse (/dev/input/mouse0)
[ 193.490] (II) No input driver specified, ignoring this device.
[ 193.490] (II) This device may have been added with another device file.
[ 193.492] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/mouse1)
[ 193.492] (II) No input driver specified, ignoring this device.
[ 193.492] (II) This device may have been added with another device file.
[ 193.510] (II) config/udev: Adding input device CHESEN PS2 to USB Converter (/dev/input/event13)
[ 193.510] (**) CHESEN PS2 to USB Converter: Applying InputClass "evdev keyboard catchall"
[ 193.510] (**) CHESEN PS2 to USB Converter: Applying InputClass "libinput keyboard catchall"
[ 193.510] (**) CHESEN PS2 to USB Converter: Applying InputClass "system-keyboard"
[ 193.510] (II) Using input driver 'libinput' for 'CHESEN PS2 to USB Converter'
[ 193.510] (**) CHESEN PS2 to USB Converter: always reports core events
[ 193.510] (**) Option "Device" "/dev/input/event13"
[ 193.511] (II) event13 - CHESEN PS2 to USB Converter: is tagged by udev as: Keyboard
[ 193.511] (II) event13 - CHESEN PS2 to USB Converter: device is a keyboard
[ 193.511] (II) event13 - CHESEN PS2 to USB Converter: device removed
[ 193.539] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3.2/1-3.2:1.0/0003:0A81:0205.0004/input/input20/event13"
[ 193.539] (II) XINPUT: Adding extended input device "CHESEN PS2 to USB Converter" (type: KEYBOARD, id 9)
[ 193.539] (**) Option "xkb_model" "microsoftpro"
[ 193.539] (**) Option "xkb_layout" "gb"
[ 193.539] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 193.540] (II) event13 - CHESEN PS2 to USB Converter: is tagged by udev as: Keyboard
[ 193.540] (II) event13 - CHESEN PS2 to USB Converter: device is a keyboard
[ 193.541] (II) config/udev: Adding input device CHESEN PS2 to USB Converter System Control (/dev/input/event15)
[ 193.541] (**) CHESEN PS2 to USB Converter System Control: Applying InputClass "evdev keyboard catchall"
[ 193.541] (**) CHESEN PS2 to USB Converter System Control: Applying InputClass "libinput keyboard catchall"
[ 193.541] (**) CHESEN PS2 to USB Converter System Control: Applying InputClass "system-keyboard"
[ 193.541] (II) Using input driver 'libinput' for 'CHESEN PS2 to USB Converter System Control'
[ 193.541] (**) CHESEN PS2 to USB Converter System Control: always reports core events
[ 193.541] (**) Option "Device" "/dev/input/event15"
[ 193.542] (II) event15 - CHESEN PS2 to USB Converter System Control: is tagged by udev as: Keyboard
[ 193.542] (II) event15 - CHESEN PS2 to USB Converter System Control: device is a keyboard
[ 193.542] (II) event15 - CHESEN PS2 to USB Converter System Control: device removed
[ 193.560] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3.2/1-3.2:1.1/0003:0A81:0205.0005/input/input22/event15"
[ 193.560] (II) XINPUT: Adding extended input device "CHESEN PS2 to USB Converter System Control" (type: KEYBOARD, id 10)
[ 193.560] (**) Option "xkb_model" "microsoftpro"
[ 193.560] (**) Option "xkb_layout" "gb"
[ 193.560] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 193.561] (II) event15 - CHESEN PS2 to USB Converter System Control: is tagged by udev as: Keyboard
[ 193.561] (II) event15 - CHESEN PS2 to USB Converter System Control: device is a keyboard
[ 193.562] (II) config/udev: Adding input device CHESEN PS2 to USB Converter Consumer Control (/dev/input/event16)
[ 193.562] (**) CHESEN PS2 to USB Converter Consumer Control: Applying InputClass "evdev keyboard catchall"
[ 193.562] (**) CHESEN PS2 to USB Converter Consumer Control: Applying InputClass "libinput keyboard catchall"
[ 193.562] (**) CHESEN PS2 to USB Converter Consumer Control: Applying InputClass "system-keyboard"
[ 193.562] (II) Using input driver 'libinput' for 'CHESEN PS2 to USB Converter Consumer Control'
[ 193.562] (**) CHESEN PS2 to USB Converter Consumer Control: always reports core events
[ 193.562] (**) Option "Device" "/dev/input/event16"
[ 193.563] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: is tagged by udev as: Keyboard
[ 193.563] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: device is a keyboard
[ 193.563] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: device removed
[ 193.572] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3.2/1-3.2:1.1/0003:0A81:0205.0005/input/input23/event16"
[ 193.572] (II) XINPUT: Adding extended input device "CHESEN PS2 to USB Converter Consumer Control" (type: KEYBOARD, id 11)
[ 193.572] (**) Option "xkb_model" "microsoftpro"
[ 193.572] (**) Option "xkb_layout" "gb"
[ 193.572] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 193.573] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: is tagged by udev as: Keyboard
[ 193.573] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: device is a keyboard
[ 193.574] (II) config/udev: Adding input device CHESEN PS2 to USB Converter Mouse (/dev/input/event14)
[ 193.574] (**) CHESEN PS2 to USB Converter Mouse: Applying InputClass "evdev pointer catchall"
[ 193.574] (**) CHESEN PS2 to USB Converter Mouse: Applying InputClass "libinput pointer catchall"
[ 193.574] (II) Using input driver 'libinput' for 'CHESEN PS2 to USB Converter Mouse'
[ 193.574] (**) CHESEN PS2 to USB Converter Mouse: always reports core events
[ 193.574] (**) Option "Device" "/dev/input/event14"
[ 193.575] (II) event14 - CHESEN PS2 to USB Converter Mouse: is tagged by udev as: Mouse
[ 193.575] (II) event14 - CHESEN PS2 to USB Converter Mouse: device is a pointer
[ 193.575] (II) event14 - CHESEN PS2 to USB Converter Mouse: device removed
[ 193.596] (II) libinput: CHESEN PS2 to USB Converter Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.596] (II) libinput: CHESEN PS2 to USB Converter Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.596] (II) libinput: CHESEN PS2 to USB Converter Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.596] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3.2/1-3.2:1.1/0003:0A81:0205.0005/input/input21/event14"
[ 193.596] (II) XINPUT: Adding extended input device "CHESEN PS2 to USB Converter Mouse" (type: MOUSE, id 12)
[ 193.596] (**) Option "AccelerationScheme" "none"
[ 193.596] (**) CHESEN PS2 to USB Converter Mouse: (accel) selected scheme none/0
[ 193.596] (**) CHESEN PS2 to USB Converter Mouse: (accel) acceleration factor: 2.000
[ 193.596] (**) CHESEN PS2 to USB Converter Mouse: (accel) acceleration threshold: 4
[ 193.597] (II) event14 - CHESEN PS2 to USB Converter Mouse: is tagged by udev as: Mouse
[ 193.597] (II) event14 - CHESEN PS2 to USB Converter Mouse: device is a pointer
[ 193.598] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/event17)
[ 193.598] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[ 193.598] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "libinput pointer catchall"
[ 193.598] (II) Using input driver 'libinput' for 'Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)'
[ 193.598] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): always reports core events
[ 193.598] (**) Option "Device" "/dev/input/event17"
[ 193.631] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): is tagged by udev as: Mouse
[ 193.631] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): device is a pointer
[ 193.631] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): device removed
[ 193.639] (II) libinput: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.639] (II) libinput: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.639] (II) libinput: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Step value 0 was provided, libinput Fallback acceleration function is used.
[ 193.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3.3/1-3.3:1.0/0003:045E:0039.0006/input/input24/event17"
[ 193.639] (II) XINPUT: Adding extended input device "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)" (type: MOUSE, id 13)
[ 193.639] (**) Option "AccelerationScheme" "none"
[ 193.639] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) selected scheme none/0
[ 193.639] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[ 193.639] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[ 193.641] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): is tagged by udev as: Mouse
[ 193.641] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): device is a pointer
[ 208.892] (II) event13 - CHESEN PS2 to USB Converter: device removed
[ 208.902] (II) config/udev: removing device CHESEN PS2 to USB Converter
[ 208.902] (II) UnloadModule: "libinput"
[ 208.914] (II) event14 - CHESEN PS2 to USB Converter Mouse: device removed
[ 208.922] (II) config/udev: removing device CHESEN PS2 to USB Converter Mouse
[ 208.922] (II) UnloadModule: "libinput"
[ 208.935] (II) event15 - CHESEN PS2 to USB Converter System Control: device removed
[ 208.951] (II) config/udev: removing device CHESEN PS2 to USB Converter System Control
[ 208.951] (II) UnloadModule: "libinput"
[ 208.968] (II) event16 - CHESEN PS2 to USB Converter Consumer Control: device removed
[ 208.977] (II) config/udev: removing device CHESEN PS2 to USB Converter Consumer Control
[ 208.977] (II) UnloadModule: "libinput"
[ 209.019] (II) event17 - Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): device removed
[ 209.035] (II) config/udev: removing device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)
[ 209.035] (II) UnloadModule: "libinput"
Looking at that, it looks like it sees the mouse / keyboard ok just not the screen.
I don’t seem to have an xorg.conf in /etc/X11 or /usr/etc/X11
Cheers.
Phill.
@phillhs The have a read of man 5 xorg.conf and have a read of the “DISPLAY SUBSECTION”. Are there files in /etc/X11/xorg.conf.d/ directory? If not your likely going to have to configure something up…