Hey guys, Ive been running PoP OS for more than a year without any big issues until today. I did a reboot (with checkmark to do updates) and after that PC got stuck at MBO logo. After reading a bit I rebooted again and was holding space button -> chose old kernel and PC started. One screen was just black while the other one was using super low resolution. I went to pop_shop and downgraded video drivers from 555 to 470 and eddited /boot/efi/loader/loader.conf to default Pop_OS-oldkern rebooted and viola its booting fine. Then I noticed my app PrusaSlicer (flatpak) doesnt show the Platter (main tab) and it crashes if I try to slice. I read it could be graphic driver related. Then I was struggling to update drivers to 555 again and eventually succeeded using sudo apt remove ~nnvidia and sudo apt install pop-desktop system76-driver-nvidia. I believe Im using old kernel and new gpu drivers, but still have an issue with PrusaSlicer. Anyone know a solution?

When I had only one screen working (at low resolution) PrusaSlicer was working fine…reinstall doesnt help at all

Thx in advance

  • riquisimo@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    3
    ·
    4 months ago

    Idk, but this last nvidia update broke things for me. Changing my display with ARandR wouldn’t work, I’d get a black screen with a mouse cursor and it would never recover, and the display driver would crash when waking the computer from sleep. I ended up reverting to the 470 drivers and that fixed it for me.

    • rambos@lemm.eeOP
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      When you say last nvidia update, when was that? I had some updates few days ago and everything went smooth, but today things went south. Is there any way I can confirm Im having gpu driver issue or kernel issue or both?

      • riquisimo@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        I don’t knowwww. I just for back from an out of town trip that lasted a week and a half and I remember updating everything when I got back.

        So I’m really just assuming it was a graphics driver update, especially since rolling back my drivers fixed the issue.