Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33644 - [nvidia] cuda programs do not see second GPU unless run as root
Attached to Project:
Arch Linux
Opened by Nick Henderson (nwhsvc) - Wednesday, 30 January 2013, 19:14 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 11 February 2014, 04:41 GMT
Opened by Nick Henderson (nwhsvc) - Wednesday, 30 January 2013, 19:14 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 11 February 2014, 04:41 GMT
|
DetailsDescription:
After updating to the new driver, my cuda programs started to fail. However, they would work properly if run as root. With user permissions the cuda driver only reports seeing the GPU attached to the display. With sudo, it can see both gpus. The attached code will demonstrate this on a system with multiple GPUs. Run with and without sudo. Additional info: * package versions: 313.18-2 and 313.18-1 * config and/or log files etc. Steps to reproduce: - install the new driver - have the current cuda package installed - compile the attached program - run on a multi-gpu system with and without sudo Output: $ ./sd device count: 1 current device: 0 device name: Quadro FX 1700 device version: 1.1 ok, done. last cuda error: no error $ sudo ./sd [sudo] password for user: device count: 2 current device: 0 device name: Tesla C2070 device version: 2.0 ok, done. last cuda error: no error |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Tuesday, 11 February 2014, 04:41 GMT
Reason for closing: Upstream
Additional comments about closing: No responses since one year.
Tuesday, 11 February 2014, 04:41 GMT
Reason for closing: Upstream
Additional comments about closing: No responses since one year.
Comment by Gerardo Exequiel Pozzi (djgera) -
Thursday, 31 January 2013, 03:00 GMT
- Field changed: Status (Unconfirmed → Assigned)
- Field changed: Category (Packages: Extra → Upstream Bugs)
- Task assigned to Ionut Biru (wonder)
do you report this to upstream? I guess is not a packaging issue.
Comment by Nick Henderson (nwhsvc) -
Monday, 18 February 2013, 22:49 GMT
I will report upstream. CUDA programs work fine with the nvidia-304xx driver. I will also put a note in the CUDA wiki. Sorry for taking so long to respond. One of the issues is that nvidia distributes driver version 304.54 with the CUDA toolkit.
sd.cu