NVIDIA 320M on MB Pro 13" NVIDIA 320M Graphic Card on the new MacBook Pro 13"

Hi all,

I’m going to buy a new MB Pro equipped with the NVIDIA 320M gpu. I wonder to know if is it a CUDA capable device. I didn’t found any official information about that. And if has anybody already tested it for CUDA development.
Thank you for any answers

Ric

I would like to undestand how cuda will interact with the macbook pro switching video cards automatically. Anyone has some idea?

Indeed the 320M card is not on the supported devices list here. But it’s working fine on my Macbook Pro 13" so I’d say that it is supported.

mtk, your question is only concerning the 15 and 17-inch versions, the 13" MBP has just one (onboard) GPU.

So are you currently using CUDA with MBP 13"?

It’s an amazing news!!!

Thanks a lot!

Hi Ric,

I checked this thread before buying the new macbook pro 13

I couldn’t figure out which was the computer capability of 320M back then…

now finally i bought it, installed cuda (straightforward following the get started guide) 3.0 and run devicequery sample

the output:

./deviceQuery Starting…

CUDA Device Query (Runtime API) version (CUDART static linking)

There is 1 device supporting CUDA

Device 0: “GeForce 320M”

CUDA Driver Version: 3.0

CUDA Runtime Version: 3.0

CUDA Capability Major revision number: 1

CUDA Capability Minor revision number: 2

Total amount of global memory: 265027584 bytes

Number of multiprocessors: 6

Number of cores: 48

Total amount of constant memory: 65536 bytes

Total amount of shared memory per block: 16384 bytes

Total number of registers available per block: 16384

Warp size: 32

Maximum number of threads per block: 512

Maximum sizes of each dimension of a block: 512 x 512 x 64

Maximum sizes of each dimension of a grid: 65535 x 65535 x 1

Maximum memory pitch: 2147483647 bytes

Texture alignment: 256 bytes

Clock rate: 0.00 GHz

Concurrent copy and execution: Yes

Run time limit on kernels: Yes

Integrated: Yes

Support host page-locked memory mapping: Yes

Compute mode: Default (multiple

host threads can use this device simultaneously)

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 53931, CUDA

Runtime Version = 3.0, NumDevs = 1, Device = GeForce 320M

PASSED

Press to Quit…


So, YES, it is cuda computing capability 1.2 compatible.

Cheers, happy coding,

ant

Hi Ric,

I checked this thread before buying the new macbook pro 13

I couldn’t figure out which was the computer capability of 320M back then…

now finally i bought it, installed cuda (straightforward following the get started guide) 3.0 and run devicequery sample

the output:

./deviceQuery Starting…

CUDA Device Query (Runtime API) version (CUDART static linking)

There is 1 device supporting CUDA

Device 0: “GeForce 320M”

CUDA Driver Version: 3.0

CUDA Runtime Version: 3.0

CUDA Capability Major revision number: 1

CUDA Capability Minor revision number: 2

Total amount of global memory: 265027584 bytes

Number of multiprocessors: 6

Number of cores: 48

Total amount of constant memory: 65536 bytes

Total amount of shared memory per block: 16384 bytes

Total number of registers available per block: 16384

Warp size: 32

Maximum number of threads per block: 512

Maximum sizes of each dimension of a block: 512 x 512 x 64

Maximum sizes of each dimension of a grid: 65535 x 65535 x 1

Maximum memory pitch: 2147483647 bytes

Texture alignment: 256 bytes

Clock rate: 0.00 GHz

Concurrent copy and execution: Yes

Run time limit on kernels: Yes

Integrated: Yes

Support host page-locked memory mapping: Yes

Compute mode: Default (multiple

host threads can use this device simultaneously)

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 53931, CUDA

Runtime Version = 3.0, NumDevs = 1, Device = GeForce 320M

PASSED

Press to Quit…


So, YES, it is cuda computing capability 1.2 compatible.

Cheers, happy coding,

ant

So, you mean your cudadriver and toolkit are 3.0?~

I try 3.2 on my pro, it doesn’t work, I don’t know why

So, you mean your cudadriver and toolkit are 3.0?~

I try 3.2 on my pro, it doesn’t work, I don’t know why

I change my driver and toolkit from 3.2 to 3.0, now, it’s working !

I change my driver and toolkit from 3.2 to 3.0, now, it’s working !

I had the same problem with 3.2 RC 1 and 2 on my 2010 13" Macbook pro. The 3.1 (and 3.0) versions work fine, as discussed above.

I had the same problem with 3.2 RC 1 and 2 on my 2010 13" Macbook pro. The 3.1 (and 3.0) versions work fine, as discussed above.