I just ran an update, as one does with apt update and upgrade. Afterwards all my monitors, bedies that one ancient 4 by 3 monitor stopped working. That 4 by 3 displays gnome at a lower resolution then usual. So I assumed that this has something to do with the nvidia drivers (has happened many times before). So I run nvidia-detect and get a really interesting output: marty@MartyPC:~$ nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1060 6GB] [10de:1b83] (rev a1)

Checking card: NVIDIA Corporation GP104 [GeForce GTX 1060 6GB] (rev a1) Uh oh. Failed to identify your Debian suite.

“Failed to identify your Debian suite” Uh oh, that sounds bad. This is Debian 12, so I assumed this was apparent… neofetch still says it’s Debian 12!

I also made a post today trying to fix my desktop icons, so maybe the things which happened there kinda give away some hints?

Does anyone have an idea on what might be going on here?

  • MadMaurice@discuss.tchncs.de
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    10 months ago

    First of all: Did you do apt dist-upgrade as well? If I remember correctly that is a new required step when upgrading to a new Debian release.

    If that doesn’t help, you could check if your nvidia-detect package version is the expected version, that comes with Debian 12.

    If neither of these steps help you could disregard nvidia-detect and try the steps listed in the following link. It seems the firmware was moved to a separate repository compared to Debian 11. You might need to add that by hand. https://wiki.debian.org/NvidiaGraphicsDrivers#bookworm-525

    • Smorty [she/her]@lemmy.blahaj.zoneOP
      link
      fedilink
      arrow-up
      7
      ·
      10 months ago

      Thank you very much for your answer. I was not aware of the dist-upgrade being required now, so I did that, but unfortunately it did not change anything after a reboot. I reinstalled nvidia-detect to see if that caused any issues, but that did not seem to be the case. Your last step I actually already did some time ago, and I tried to do the same no. Unfortunately that also did not seem to have fixed the problem. The nvidia graphics settings software is still installed, but it only shows some very limited control options compared to how it used to be. This is what that program looks like now:

      So this really seems to be more of an nvidia issue, rather than a gnome one.

      • Secret300
        link
        fedilink
        arrow-up
        5
        arrow-down
        2
        ·
        10 months ago

        I had a 1650 until recently. I thought Wayland was just buggy as hell but as soon as I put in an AMD card it was smooth as butter. I know it’s not always an option but in my area cards sell locally for $80 specifically the Rx 5500 and RX 580

        • Smorty [she/her]@lemmy.blahaj.zoneOP
          link
          fedilink
          arrow-up
          3
          ·
          10 months ago

          Yeah. Actually wanted to put an -nvidia hate- comment at the bottom, buzt thought it’d be too much. I do actually have some money lying around, so if I switch, it’ll be an amd. I currently have the classic: GTX 1060 in my machine, how did you feel your performance change, if at all?

          • Secret300
            link
            fedilink
            arrow-up
            1
            ·
            10 months ago

            I found an Rx 5500 for $75 at a pawn shop and so far it’s performing the same but my CPU is a huge bottleneck so not sure yet til I upgrade

          • 0x0@social.rocketsfall.net
            link
            fedilink
            arrow-up
            1
            ·
            10 months ago

            I recommend an RX 580. Older card, but better than the 1060 and 8GB instead of 6GB. Good for 1080p gaming at 60fps and can be workable up to 1440 if you lower settings. Used price is around $60 - $90 USD (down from $110 when I bought it earlier this year used on eBay.) Only thing to look out for is the bios switch, which downclocks memory if in the wrong position. I drive 3 displays with it and used to do 4 with no issue on Wayland. Highly recommended for a budget card.

            • Smorty [she/her]@lemmy.blahaj.zoneOP
              link
              fedilink
              arrow-up
              1
              ·
              10 months ago

              I’m not really a game player and more of a game maker and modelling person, so as long as it’s better then my 1060, I’m perfectly fine with that.

        • yianiris@kafeneio.social
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          10 months ago

          I’ve hated the idea of wayland and still dislike many things about it, but 1st wayland is just a protocol, wlroots is the common base for everything. After trying labwc the current seemed to turn around quite a bit. Still missing some basic utilities that seem to only exist for sway and be based on sway.
          Both sway and waybox are a disappointment.

          So keep trying different projects to find what fits, because eventually we will be there.

          @Secret300 @Smorty

          • Secret300
            link
            fedilink
            arrow-up
            4
            ·
            10 months ago

            Nvidia just sucks with Wayland is what I was saying. I got an AMD card and it’s noice now on gnome and kde

    • Smorty [she/her]@lemmy.blahaj.zoneOP
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      I’m back from trying that reinstall with aptitude, and it keeps getting file sizes wrong. It says, that reinstalling all software will take 0 Bytes. After not finding some sources, it tells me that the unpacked packages will combine to 0 Bytes again:

      E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python2-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python2:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »libpython2.7-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »python2.7-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »7.0-5« von »libreadline7:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.2.0-travis995~0f91801+bionic« von »appimagelauncher:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »4.9.2-427« von »blockbench:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »0.0.39« von »discord:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »3.2.1-9« von »libffi6:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »libpython2-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »libpython-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »libpython2.7-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »1.1.1n-0+deb10u6« von »libssl1.1:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »python2.7:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2023.1« von »trenchbroom:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »0.11.4« von »weylus:amd64« herunterzuladen. Nach dem Entpacken werden 0 B zusätzlich belegt sein. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python2-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python2:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »python:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »libpython2.7-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »python2.7-minimal:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »7.0-5« von »libreadline7:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.2.0-travis995~0f91801+bionic« von »appimagelauncher:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »4.9.2-427« von »blockbench:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »0.0.39« von »discord:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »3.2.1-9« von »libffi6:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »libpython2-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-1« von »libpython-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »libpython2.7-stdlib:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »1.1.1n-0+deb10u6« von »libssl1.1:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2.7.16-2+deb10u3« von »python2.7:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »2023.1« von »trenchbroom:amd64« herunterzuladen. E: Es konnte keine Quelle gefunden werden, um Version »0.11.4« von »weylus:amd64« herunterzuladen. E: Interner Fehler: Liste der herunterzuladenden Pakete konnte nicht erzeugt werden. E: Perhaps the package lists are out of date, please try 'aptitude update' (or equivalent); otherwise some packages or versions are not available from the current repository sources

      “Es konnten keine Quellen gefunden werden” meaning, that it couldn’t find the sources for a specific program. I already ran sudo aptitude update so that is not the issue. Soo maybe I really do need to reinstall the entire system?

    • Smorty [she/her]@lemmy.blahaj.zoneOP
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      I don’t have any sources files in my /etc directory. My Debian install in general is really weird, since the default apt sources came only with some CD ROM source, which did not work with the Internet. So I had to manually add all sources myself (probably caused some of my troubles…) These are my sources right now

      deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free non-free-firmware deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware

      I’m assuming these are correct, as they all got that bookworm in them.

      I will try the other options though, thanks!

  • danielfgom@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    10 months ago

    Backup your data. Download the correct Debian and burn to usb. Do a fresh install. Make sure to format the disk first.

    Unless you’re dual booting in which case only format the Linux partition