I have a dell desktop pc which has an integrated gpu.
If I add one more gpu over PCIe will I be able to run cuda? Probably yes.
The integrated gpu has its own driver (i915) and I am not sure what will happen with nvidia driver (for the second gpu) alongside.
Is there a special procedure, something to take into account?
edit: forgot to mention that OS is Ubuntu 11.10. sorry
Thanks in advance
UPDATE:
finally there is a problem. I just put the video card gtx 460. I want to have the display on integrated card so as to use the "good" card dedicated to computing. but if i dont plug the monitor cable to gtx I get the following message
System halted! Attention: Unsupported Video Configuration Detected
Action is Required
This computer has an add-in graphics card, but the monitor is plugged
into the integrated video connector. To attach the monitor cable to
the add-in graphics card:
Shut down the computer
Plug the monitor cable into the add-in graphics card connector. This may require a video adapter or video adapter cable. (provided
with the system)
Turn on the computer.
This message should not appear after completing these steps. For more
information or help, please refer to the system documentation.
Please help.
CUDA only supports NVidia GPUs so it won't even see the embedded intel one.
The CUDA startup functions also return the type and capabilities of all the CUDA devices found so you can pick which device to run a task on.
ps. You might want to manually set the app to 'use enhanced/performance graphics' in windows explorer->properties - we have had issues in laptops with Intel+Nvidia optima systems where the app doesn't see the Nvidia GPU by default for some reason
Related
I have a Dell PowerEdge T430 running Fedora 25. It comes per default only with onboard graphics (which allows only a resolution of 1024x768 (at least I was not able to get any drivers running) and is insufficient for some applications that produce graphical output).
I bought a Geforce210 graphics card and plugged it in but how do I tell Fedora to use it instead of the onboard graphics?
Pretty sure you need to do this in the system's own System Setup ("BIOS configuration") — go to the Integrated Devices section and switch Embedded Video Controller to Disabled. I don't think there is any support for multiple video controllers to be active at the same time.
I have a USB audio device (Scarlett Focusrite 18i6) which does not require a driver, so I assume it uses the USB HID Audio Class standard.
It works on everything from Windows and Mac to Linux and iOS.
But on Mac and Windows, it has a control application which can for instance enable and disable direct monitoring.
How would I go about reverse-engineering how this is done, so that I can reproduce it on platforms where the control application does not exist?
I'm thinking of booting up Windows in a VMWare session and then logging the USB communication (somehow?) while using the control application, but it does sound tedious considering the amount of data and my very limited understanding of USB.
Any other suggestions?
You could try running the control application using Wine instead of reverse engineering it. However, if it's accessing USB devices then there is a good chance it might be using an API not supported by Wine.
To reverse engineer it, you should find a way to look at the USB traffic between the computer and the device. Total Phase has some hardware USB protocol analyzers, but you might be able to find a good software solution for free.
Apologies for asking a time dependant question, but does anyone know when Microsoft are going to sort out there drivers for the Raspberry Pi 3's on-board Bluetooth chip?
Currently the console Device Settings just display the following exception error code relating to a fault with the OS files:
The device is not ready for use. (Excep_FromHResult 0x800710DF)
Or does anyone know of a workaround to this problem?... Short of developing your own drivers and creating a custom OS image for the board.
Many thanks for your help.
Raspberry Pi 3 onboard Bluetooth support is in a future release of Windows IoT Core Insider Preview, per the page it should come soon, so please be patient.
The workaround is to use a compatible USB Bluetooth dongle, check out here to find the list.
If you want to develop your own driver and create a custom image for hobby or fun, you can find very good code samples in https://github.com/ms-iot/bsp/tree/master/drivers, and follow https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/iot/iot-core-manufacturing-guide
to create custom windows IoT core image.
Update!!!
Onboard Bluetooth driver seems to be included in the latest preview build version 14376. I did not test it thoroughly but per the snapshots below, it looks very promising.
I am trying to connect my POS Terminal(WinCE Secure Multi-Application Operating System,200 MHz ARM 920T 32 bit CPU) to my windows 7 PC. The issue is i am getting a device driver software issue and the device is not been recognized. I didn't got any installation CD or software with the product.I couldn't find a suitable driver for the same in the web and would need to install the CAB files through WMDC into the device so that i can automate the product testing. Can someone please advice in fixing this driver issue and direct me on how to establish the connection. Any help is highly appreciated.
Thanks,
John
This can be a complex task. First, the connection type (serial, USB, Ethernet, other) is important. I'm going to assume USB, as that feels like what you're probably talking about (you should edit and clarify though).
For USB to work, you need drivers on both ends - the device and the PC - and they need to cooperate. For Windows CE devices and USB, the common way (though not only option) is to use ActiveSync. There is an out-of-the-box client application driver for Windows CE (repllog.exe) - though it requires the OEM actually plumbs it through to the transport driver. For the desktop (Vista and later) you would use Windows Mobile Device Center (WMDC).
You might simply be able to install WMDC and you're off and running, but it's always possible that the OEM disabled that, since you might not want someone to connect a PC to a POS system and subvert the normal operation. Have you asked the device OEM?
I've been involved with a project where I have to install and use a USB GPRS modem on an ARM board (RSC-W910) with Windows CE 6.0 installed.
The modem is the Sierra Wireless product GL6110 (GL61x0) and I need to use it only for data, making HttpWebRequests (TCP) send/receive XML data. Prefered development tool is C# and .Net Framework 3.5.
When the modem is connected via USB to the board, the error message that appears is saying "Unidentified USB Device" which I believe its normal.
Siera Wireless(SW) provides a driver for ARM920, but it failed to install using 'wceload.exe'. The error was "Setup Failed" that I could see on the small LCD screen attached to the board. To install the driver I connect to the board via Telenet and CAB file is stored on SD card.
Am I right to think that the failure to install the driver could be related to the fact that the Win CE image has RAM-based Registry?
If SW does not provide a driver for the modem, could this mean that I have to develop my own driver? or is there a generic driver that I can use instead?
Will I have to create a new Win CE image for the board to support the modem, or is it possible to use code within the C# application to access it?
Any help will be very much appreciated!
Thanks,
Nick
There's no generic driver, no. Sierra modems generally have CE support (I'm not checked this model, but it's likely to work). What you need is:
A Driver DLL, build for ARM and for CE 6.0 or 7.0 (the CE 5.0 driver model differs, so a CE 5.0 driver probably won't work)
The registry entries the device.exe looks for when the device is enumerated
These sometime come in a CAB, sometimes not. Generally I prefer it when they don't but either will work.
If the CAB file fails to install, it's probably because it's marked for some other platform. I'd use something like WinZip or WinRAR to pull it apart, rename the DLL and extract the necessary reg entries (depends on the CAB format how easy/hard this will be).
Generally, though, you need to copy the driver DLL to the \Windows Folder, then apply the registry entries. Then when the device is plugged in, it will read the registry, which will point it to the DLL, which is then loaded. "Unidentified USB device" typically means the registry entries were not found.
This can all be done without rolling a new OS image, though sometimes a new image is simpler than doing the necessary copying at startup, especially if the device is plugged in at boot.