# Fresh Install Cuda Issues Ubuntu 22.04

**URL:** <https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283>\
**Category:** Technical Help\
**Created:** [July 9, 2024, 5:27am UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283 "2024-07-09T05:27:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aris-T](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@Aris-T](https://deeptalk.lambda.ai/u/Aris-T)\
**Post date:** [July 9, 2024, 5:27am UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283/1 "2024-07-09T05:27:34Z")

</div>

So this is on a lambda desktop hardware. I just reinstalled the os and put on lambda stack to be able to get torch running again. No joy. Before I go and start messing with drivers again I was hoping someone might be able to help tell me why a fresh install is having issues.

The CUDA version seems to be ahead of that used by the latest pytorch.  
This is a fresh OS and lambda stack. I thought this should work out of the box.

 ![stacked_image](https://us1.discourse-cdn.com/flex019/uploads/deeptalk/original/1X/21d9cbbf6c1ac432dfe52d3b7084a87ff8789f7d.jpeg)

---

<div class="post-metadata">

**Author:** ![cody\_b](https://avatars.discourse-cdn.com/v4/letter/c/67e7ee/32.png) [@cody\_b](https://deeptalk.lambda.ai/u/cody_b)\
**Post date:** [July 10, 2024, 12:41am UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283/2 "2024-07-10T00:41:37Z")

</div>

Did you reinstall using a [recovery image](https://docs.lambdalabs.com/software/lambda-stack-and-recovery-images#workstations)?

---

<div class="post-metadata">

**Author:** ![Aris-T](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@Aris-T](https://deeptalk.lambda.ai/u/Aris-T)\
**Post date:** [July 10, 2024, 5:02pm UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283/3 "2024-07-10T17:02:32Z")

</div>

No I did not. I’ll give that a go. What is different about these recovery images from a standard Ubuntu image?

---

<div class="post-metadata">

**Author:** ![Aris-T](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@Aris-T](https://deeptalk.lambda.ai/u/Aris-T)\
**Post date:** [July 10, 2024, 8:36pm UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283/4 "2024-07-10T20:36:01Z")

</div>

Just finished rebuilding from a recovery image. Same issue.  
Installed the recovery image, put on lambda stack. Cant get PyTorch to see the GPUs.

---

<div class="post-metadata">

**Author:** ![Aris-T](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@Aris-T](https://deeptalk.lambda.ai/u/Aris-T)\
**Post date:** [July 11, 2024, 1:24am UTC](https://deeptalk.lambda.ai/t/fresh-install-cuda-issues-ubuntu-22-04/4283/5 "2024-07-11T01:24:32Z")

</div>

Solution:  
Ok I figured it out. I was looking over the additional drivers section and I saw it had thought it installed the drivers for a P5000 instead of RTX6000. WTF! I also had been wondering why my standard setup worked on another system with near identical specs.

Turns out this box had been used by the deployment folks to test different graphics cards for deployment. So I took a look at the hardware and sure enough, tucked beneath the two RTX 6000s was a P5000 in slot 3.

I pulled that and it worked. I think it comes down to the RTX and Pxx series having different internal architectures and so can’t share a driver.

Final verdict. Dont mix GPUs. Thanks for the help.