Installed xrdp with xfce in Ubuntu 14.
I am trying to take remote from Windows 10.First I was not able to see anything except dotted grey and black dot.
Then added "xfce4-session" to /etc/xrdp/startwm.sh file.
Now I am able to view my desktop but when I launch any application it is launched in the physical machine when it is not locked.
Related
As I and most of us WFH nowadays I am curious to know if there is way we can debug android app using remote AS and device connected to local machine.
I am using my laptop to connect my work machine which is super fast compare to my laptop so I want that device connected to my laptop is accessible by AS running in my work machine(Remote desktop).
I tried enabling usb port sharing while connecting to work system with remote desktop but no luck.
Yes in fact there is, I had the same problem as you, I was WFH but my Remote machine was unable to detect devices plugged into my laptop at home through Windows Remote Desktop (both machines Windows 10).
After searching for a long time I found the following the guide here: https://workspot.zendesk.com/hc/en-us/articles/214248563-Configuring-USB-Redirection-with-RemoteFX-in-Workspot
It requires you to Edit the Group Policy on both machines to allow USB Redirection with RemoteFX.
After following the instructions, I was able to detect the devices on my Remote Machine and all worked perfectly through Android Studio on the Remote Machine.
After rebooting both machines and connecting the RDP, make sure to enable the device to be shared on the RDP session using the bar at the top with a Printer icon, there you can tick to enable the device.
As a beginner with Virtual Machines and Linux I have my trouble understanding how to properly upgrade Linux on the Tegra - Board. I found some good explanations but they all were too advanced for a beginner - a student - and not a professional in the field.
Therefore, I would like to know how to properly upgrade the Linux Version on the Tegra X1 Board with a Windows machine
Step1:
Make sure you have the following items:
The Tegra Board
Admin priviliges on the Windows machine (needed once)
Micro USB-B to USB Cable
HDMI Cable and Monitor
These are all the things needed before.
Step 2
Download Linux 14.04 - it is the only distribution compatible with the Tegra Board at the moment.
http://releases.ubuntu.com/14.04/ubuntu-14.04.4-desktop-amd64.iso
Step 3
Download and install Oracle Virtual Machine. You will need admin privilages for install.
http://download.virtualbox.org/virtualbox/5.1.8/VirtualBox-5.1.8-111374-Win.exe
Step 4
Set up an NVIDIA Developer Account
https://developer.nvidia.com/group/node/873376/subscribe/og_user_node?downloadable_file=874988
Step 5
Set up the virtual machine. To do so start the installed Oracle VM Virtual Box (see Step 3). On the upper left you find the button "new". After clicking on it a window will pop up. At the bottom you can change to "Expert-Mode".
In the field "Name" you can give it a fitting phrase like "Ubuntu for Tegra" etc.. The next field Typ should be obiously Linux, and the Version 64 bit.
Set the memory size to a good fitting size, depending on how much RAM you got on your machine. It works fine with 6 GB, anything smaller could lead to some lagging, but will still run.
Put the radio button in the middle so it will create a hard drive.
Go to the next step by hitting "Create"
Step 6
In this window two inputs are interesting. Firstly, it needs a path where to create the virtual environment. So choose a path to a disk that has enough space. Secondly, how many space you give to the environment - 50 gb will work fine.
Step 7
Launch it by selecting the newly created environemt and then hitting "Start". You will be asked to choose a medium to be booted. Here select the downloaded .iso file from step 2.
Step 8
You will be greeted with the Linux-Install environemnt. You can choose between "Try" and "Install". You must choose "Install".
Step 9
After you instaleld Linux you must restart the Virtual Machine. To do so, you can either do it by "normaly" shutting down Linux via the GUI or the command Line tool or from the VM-Software directly by right-clicking on the running virtual machine - close - power down.
Step 10
You may encounter the problem that you do not see the full screen of the Linux environment. To fix this you need to restart the virtual machine. On the virtual machine display at the top bar you can see the entry "devices". If you click on it a drop down menu will open, the last point is "guest additions", click on it and install them. After that reboot the virtual machine.
Step 11
On the virtual machine log in on your NVIDIA Account and download the latest Jetpack Version.
https://developer.nvidia.com/embedded/downloads?#?dn=jetpack-for-l4t-2-3
https://developer.nvidia.com/embedded/jetpack
Step 12
After downloading a file with the extension .run should be in your Downloads-Folder. This is the installation file needed, but it is not executable yet. To make it executable open a shell (right click on the upper left ubuntu symbol, search for terminal and open it).
Go to the Downloads folder with:
cd ~/Downloads
and make the run file executable:
sudo chmod u+x *.run
Step 12
Run the .run file with
sudo *./run
Step 12
In the installer choose the board and the software you want to be installed, also agree the software license agreements. After some downloading time the installer will open a terminal.
If the prompt asks you about Network Layout. If it does, choose eth0 if you have you board connected via ethernet cable, if it is connected via Wi-fi choose wlan0.
Step 13
You need to put the Tegra Board in recovery mode. Make sure that all your data is saved, since it will wipe everything clean.
Follow the instructions on the terminal to put the Tegra Board in recovery mode. If directions unclear follow this youtube video (which also includes some followign steps):
https://youtu.be/4JUWS9i_FCQ
Step 14
When you think the Tegra is in recovery mode check by doing the following: At the virtual machine, on the top bar go the "devices" and then to USB. Select the NVIDIA entry. If it is not there, the board is not in recovery mode. Make sure that this was really selected. (It is highlighted blue when selected)
Step 15
Back in the Linux virtual machine enter lsusb on a second terminal. If there is an entry with NVIDIA Corp the tegra board was successfully put into recovery mode. Press enter, now the flashing starts - this will take some time
Step 16
After flashing finishes, the jetson board will auomatically boot. Connect it to an HDMI Cable and Monitor. If a login is asked, the username and password are ubuntu.
Step 17
Connect to the Internet
Either connect it to the ethernet or a Wifi - depending on what you have chosen at step 12. You may need to disable Wifi to connect via ethernet cable.
Step 18
If you use static IPs you can skip this part since you already now the IP-Adress you gave to the tegra board. If not you have to run
ifconfig
in a terminal. It will show you your adapters and what IP-Adresses they have, note the one that you chose.
Step 19
The Post Installation in the virtual machine either has given up and was unable to determine the IP adress of the Jetson Developer Kit or has found it. If it has not found it give it manually the ip adress you found out by entering "2". After this a GUI is shown where you can enter the Ip-Adress and the username password combo, which is ubuntu.
Step 20
After hitting Next the installation will continue.
Hello I have installed qemu manager virtualization program on my gateway amd e2-3800 windows 10 laptop, in order to install ubuntbu 16.04.
i have created a virtual machine, using the default definitions (beside giving the maximum ram of 2gb).
i have downloaded the ubunbu 16.04 imag file, pinted the "CD-ROM" drive of the virtual machine to the image fileand and run the virtual machine.
It didn't worked as expectd - the console and the monitor are empty and at the botom of the windows is written "QEMU console not connected",
there is nothing in "google" for this problem, and i have watched several youtube videos on using QEMU to see wether i have made some error in dfining the virtual machine, i have also read the manual... but came up with, well... nothing.
Does anybody have any idia or recomendations?
thank you in adanced.
chen.
I had the same problem and after decreasing the VM's RAM to 1 GB it worked okay.
Hardware -> Video Card, select other options.
In my case, running OVMF, I select "None", then it works.
I have a laptop, and I want to force the native screen to display 1080p. I know the display driver is capable of that because I have connected it to a 1080p screen before and it worked.
I am doing this because I want to establish a remote connection from my Raspberry Pi to the laptop. The Pi (an ARM linux machine) is connected to the 1080p screen. At the moment, the remote connection only covers part of the screen, as the laptop is only displaying 1366x768 (or something).
I want a software solution, if possible. Also, I want a server-side solution (that is, on the windows machine) as finding and using Linux software that works on the pi is a bit of a nightmare!
I am using TightVNC, though am prepared to try any package is free and which works well, as a server for Windows and client for ARM Linux.
Solutions I have tried that don't work:
'show all modes' on control panel (still didn't show the mode 1920x1080, which I know the graphics adapter can do)
ZoneScreen OS (wouldn't let me create a higher resolution)
Demoforge Mirage (um... didn't do anything. Maybe I didn't get how you're supposed to use it)
To force the raspberry pi to have a certain display. Go on boot folder cd /boot/
After that, open the config file with your editor (I use geany sudo apt-get install geany)
sudo geany config.txt
In this file, it should have two line that you have to uncomment it:
framebuffer_width=800
framebuffer_height=600
Just change the values of those variables and save the file.
You may have to reboot your raspberry pi
The problem:
I have a scrambled keyboard while using VMware Player on Linux from NX Client on a MacBook Pro. Letters are numbers, numbers are letters, delete is comma, e is delete; it's pure madness. I asked Google but it seems just as confused as me.
Note:
I am using an old-school mac keyboard with number pad plugged into my MBP and an additional monitor.
Things I've tried:
Altering my Linux keyboard settings (Layout: USA, USA Macintosh. Model: Apple, MBP, Apple Aluminum)
Altering my MBP keyboard settings (actually didn't see any settings that would affect this)
Unplugging my old-school keyboard with number pad and only using my MBP keyboard
Have the same issue, but with virt-manager (NX client runs on my Mac 10.6.8, connects to an Ubuntu 10.10 server and all is well, but if I run virt-manager and open a virtual machine, the keystrokes sent to the VM are all messed up).
I guess it has something to do with the Mac NX client and the VNC client (built into virt-manager) on the linux server. I tested the same setup in a Windowx XP virtual machine and it worked flawlessly. So it's got to be the Mac NX Client somehow.
As a workaround I've found that if I create an SSH with a port-forward from the remote linux-server (where I used to run virt-manager to access a VM running on another server) to the server with the VM and I forward a local port to the VM's vnc-server, then I can start up a VNC client (on the linux-server that I connect to via NX) and connect to the VM via the SSH tunnel and keys work just fine. So in my case the problem is somehow with the Mac NX Client + virt-manager's embedded VNC client.
I'm just guessing here, but VMware Player might use an embedded VNC server+client as well to show you the VM's screen. And both the reason for the problem and the workaround might be the same. Ie. try to use a separate VNC client to connect to the VM.
Update: I've got the solution to my problem, it's a KVM bug. The KVM machine starts the VNC server for the VM without specifying the correct keymap to use. See: http://blog.loftninjas.org/2010/11/17/virt-manager-keymaps-on-os-x/
The solution for VMware Player might be just as simple. A little googling revealed that VMware supports connections to a VM via VNC. Here's how to specify a keyboard layout for a VM's VNC server: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004815
Probably you just have to:
shut down the VM
open the VMX file in an editor
add the proper keyboard layout to the file as described on the page linked above (I guess you should specify the layout that your Linux server uses, eg. en-us)
start the VM and test with a VNC client
Of course it'd be better if you could tweak the Player's console to handle keycodes properly, but I did not find a fix for that.