I have one machine with GeForce GTX 480 but I can't debug or run analysis activity on it.
This error appears when I debug or run analysis activity:
The remote system is logged in through Remote Desktop. CUDA debugging
does not support Remote Desktop unless a TCC adapter is installed.
My Nsight version is 2.2. Whats wrong?
You would need a TCC capable card (Quadro or Tesla series) if you want to use the GPU from inside a RPD session.
When you do not have a TCC capable GPU, you can for example install VNC Server as a service and use that to access the machine.
Alternatively you can configure windows autologin to log you in automatically and have have the Nsight Monitor in the startup group (but to access the desktop remotely you would still need some kind of remote access software like VNC).
after some test and try ,I found that this problem is because of RDC and if you connect to the target machine from one computer with remote desktop connection even if you disconnect all remote desktop and try to debug with Nsight remotely or locally you get this error .
I were connected to the target machine with remote desktop and configure and run Nsight monitor and then close the RDC . and then I tried to debug the project remotely from host on the target and because of it I get this error
I found that one solution will be restart the target machine and configure the Monitor physically at front of the target machine and then DO NOT remote to the target from anywhere, now I can debug my project from host machine on the target machine .
Related
My Setup:
Windows 10 VM running in VirtualBox on Windows 7 Pro
Raspberry Pi 3 running Windows 10 IoT Core - 10.0.16299.19
The VM can see the RaspberryPi/Wionows IoT
I know this because:
On the VMI I can Install and Debug from Visual Studio 2017 to the Pi.
On the VM the IoT Dashboard detects the PI and allows me to change
settings
On the VM I can access the Pi's Device Portal
On the VM I can use Powershell to log in to the Pi.
What I can't do is use Windows IoT Remote Client. Which I want so I can see changes produced by my code.
When I start the client I get the spinning buffer animation followed by a blank, white screen.
I have tried the following as recommended in web articles:
Reset the Pi resolution to 800x600 - This killed the Pi's ability to
display at all; including on the attached HDMI.
Checked Enable Windows IoT Remote Server in Device Portal. - This is
set to On
Disconnected the HDMI from the Pi - Made no difference.
Typed the following into an Admin level PowerShell:
net start WinRM
Set-Item WSMan:\localhost\Client\TrustedHosts -Value
PiName
This allowed Powershell access but no change to Remote Desktop
What should I try next?
On version 16299,the Windows IoT Remote client does not work for Raspberry Pi. Please reference the know issue of release notes for Windows 10 IoT 16299.Currently you can attach a monitor for local display.
Try starting the NanoRDP server manually (not through the web interface) and see if that helps. That has solved a few issues for me.
I believe the executable is in c:\windows\ and is called nanordpserver.exe. just SSH or Powershell into the device, run nanordpserver.exe and try again.
The lightweight RDP protocol that IoT Core uses is not as robust as the version installed on the full Windows 10 OS.
I am running visual studio 2013 with windows 8.1 pro , I have enabled hyper-v from bios and enable it from program and features also. Firstly when I run my project it gives message like this
after that when I clicked retry it gives this deployment error
Need help in solving this.
Try running visual studio 2013 as an administrator this sometimes helps fix the permission issue running the emulator the first time.
After checking in that textbox where you have to add your lap to the Hyper-V Administrators, just try restarting the machine.
Have a look over here
You should try out these too
1.Run VS 2012 as administrator.
2.Open Hyper-V Manager and check the Windows Phone Emulator Internal Switch from Virtual Switch Manager. Remove the emulator switch and start a new instance of the emulator.
3.If your host computer has a WLAN connection, you should check whether it is running fine or not.
4.If your host computer is in a dedicated network, you can do a wired tethering and create a peer to peer network with another computer. Enable unrestricted internet in one of the systems, share the connection with the other computer, the emulator running in that, will also get the shared internet.
Disclaimer: I know that this question has been asked numerous times, but before Nsight 5.5 the answer simply was "You can't."
I'm trying to debug a CUDA program with Nsight 5.5 on Ubuntu. The remote machine is also an Ubuntu with CUDA Toolkit 5.5.
I setup debugging in NSight using the "Debug an application on a remote system".
Whenever I try to run the application I get a "Could not start gdbserver on the remote host" error.
This is what I get on the console:
Last login: Thu Aug 1 16:09:26 2013 from host.whatever.edu
echo $PWD'>'
:2345 /tmp/nsight-debug/flow;exit
someuser#remotehost:~$ echo $PWD'>'
/home/someuser>
someuser#remotehost:~$ :2345 /tmp/nsight-debug/flow;exit
:2345: command not found
logout
Both gdbserver and cuda-gdbserver are installed on both machines.
If I ssh to the remote host, I can run /tmp/nsight-debug/flow manually.
What might be the problem here? Is there anything missing from the setup?
This looks like a bug in Nsight, we will take a look into this matter.
Please make sure that you have remote toolkit configured for your connection.
From the main menu, select Run -> Debug Configurations...
In the left-hand tree, select you debug configuration under C/C++ Remote Application
Make sure that Remote toolkit combo has proper toolkit selected. If you don't have any toolkit configured, click Manage... and setup the toolkit.
Usually you will only have to setup the toolkit once per your connection - e.g. you will not have to setup it if you want to debug another application on the same remote system.
I would like to start a remote debugging session from my development pc on our soon-to-be production server. On the server I start NSight using the remote desktop, and then I try to Start CUDA Debugging on my local machine (given the server as target before). The result is, that the debug session disconnects saying "The remote system is logged in through remote desktop. WDDM adapters will not be debuggable".
Is this intended behaviour, a bug, wrong configuration? And if there is no solution involveing remote desktop, how could I start the NSight monitor, so that I can start a debugging session?
On the target server I have two Tesla K10 and a Quadro FX (for Display). All Tesla devices (which are actually four), show TCC turned on.
I am using NSight 3.0, CUDA 5.0 and Visual Studio 2008 (the latter two only on the development workstation).
One last thing: Copying the application to the server and executing through remote desktop works fine.
The message you refer to is a warning to let users know that Nsight has detected that you have a RDP session running on the target side and that it won't be able to do Nsight debugging on any WDDM cards in it, if there is one (or more) - which looks like you do, with that Quadro FX that you mentioned).
This message is a Warning, and it should continue to let you run or debug the application under Nsight and debug the application assuming GPU code runs on the TCC devices. Are you sure the application ran successfully on the target machine? Can you double check that you have set a GPU breakpoint and see if you hit those breakpoint(s)?
Are there any other messages shown? - you can check the VS Output window.
Which driver version are you using?
Can you try running (double clicking) the application on the server but from the directory that Nsight synced the application to? It should be under %appdata\NVIDIA Corporation\Nsight\Monitor\Mirror\<hostdev_machine_name>\<path_to_the_sync_app>
I know you mentioned you tried copying it, but I'd like to see if everything that Nsight sync is what's required by the application and that maybe there's not something missing that you need to specify to sync (more info on syncing is here: http://http.developer.nvidia.com/NsightVisualStudio/3.0/Documentation/UserGuide/HTML/Content/Synchronization.htm)
Thank you
Has anyone had any experience debugging CUDA code on a server while coding on a workstation?
My laptop (Thinkpad T400) doesn't support CUDA, but I have access to a server with pair of NVIDIA GTX 295 cards that runs Linux.
Can I use NVidia's Visual Studio tools to debug remotely on the server?
Failing that, I also have an Ubuntu VM running on my laptop. Is there a debugger that I can use under Linux to debug on the server?
I really don't want to have to buy another laptop with dual NVidia cards.
Developing in c on a remote linux machine (like your server) is quite common. You can ssh onto the server from any client (like your laptop) to compile and run the code just as you would if you were sitting at the machine, and you can use gdb to debug your code in a terminal. You can also use ddd as a graphical front end to gdb or a linux IDE such as eclipse by forwarding X11 over ssh.
You can use cuda-gdb to debug your CUDA code in a terminal in exactly the same way. Unfortunately, there is not a visual cuda debugger for linux yet. However, it appears you can use ddd with cuda-gdb [source], as you have two gpus. I'm not sure about using cuda-gdb in eclipse.
Yes you can but you need to buy the Parallel Nsight Studio from Nvidia
After installing on the remote machine the NsightDebugServer you can upload and debug programs from
your cuda-less laptop.
Update
Turns out This solution requires a WINDOWS server in order to run the NsightDebugServer.
To connect to the linux machine from your laptop, use a remote connection.
install putty and a Xserver for windows and just login with
ssh -X username#cudaserver.
The environment would not be fancy as Visual Studio but you can do the basic steps of debugging.
Eclipse "might" have some support for remote gdb servers. Never experimented that (Emacs + gdb is sufficient for me)