Every X server (GUI) loads input devices upon startup of that server. It also dynamically loads the NVIDIA GPU driver (if it can’t, then you can’t use GPU acceleration, including CUDA and display). The drivers are binary, which means that the server has to (A) be configured to load the particular drivers for that release ABI, and (B) actually be ABI compatible. An example problem is that an Xorg server upgrade to a completely new release will fail to load the GUI since it can’t load the old NVIDIA driver’s ABI.
A server normally is an API to interact with a buffer. It just happens that by default the buffer is available to the GPU (if the driver is present), and that the buffer has an HDMI or DP socket which a monitor can use to view that buffer.
A virtual server tends to have a buffer too, but instead of an HDMI cable it will also have the ability to network the buffer content. The server just wants a buffer accessible by some specific API, and is completely unaware of whether or not there is a monitor attached. Perhaps the buffer is simultaneously visible to both a local monitor and a network remote client. The software won’t care.
If you’ve replaced the GPU-driver-compatible server with a virtual server which is also compatible with this, then there is no problem. As soon as the server is incompatible with the GPU driver which NVIDIA provides you will probably lose video. This is just the most common problem people see when working with X server changes. The same is also true for input devices: Mice, keyboards, and microphones have dynamic plugin to the X server just like the GUI driver does. Should they break, or simply not be configured, then those components will fail.
What I suggest is to first make sure which X server designation is involved so you can look at the correct log. While you are logged in to that GUI (not remotely…I assume the mic is connected to the Jetson itself and that you are working from the Jetson), in a console, what do you see from:
Most likely it is “
:0”. However, maybe it is “
:1” or “
:10”. Take that number, and use it to get this file (I’m assuming it is “
:0”, but adjust for your case):
(so if it is “
:1”, then “
Attach that to the forum. There will be a note in the log regarding input devices which might say what is happening.
If you are actually using the remote desktop and a microphone on the remote PC, then a lot changes.
Most likely it is “