• henfredemars
    link
    fedilink
    English
    arrow-up
    37
    ·
    9 months ago

    Are you running a proprietary video driver? It might be worthwhile to disable it in case it became incompatible perhaps after a kernel upgrade.

    Did you perform a graphical login prior?

      • henfredemars
        link
        fedilink
        English
        arrow-up
        14
        ·
        9 months ago

        First, you might try booting an older kernel to see if that runs for you. Your bootloader such as grub might help you pick an old one.

        The older kernels are actually combinations of kernel + initial ramdisk that contains the version of your graphics drivers that were being used at that time. It could be a way to test the hypothesis.

          • henfredemars
            link
            fedilink
            English
            arrow-up
            12
            ·
            9 months ago

            Hmm, interesting. That tells us that it’s not actually a problem with your graphics driver or kernel version, and given that it was working on this version before, I would think some aspect of Xorg configuration, your graphics hardware has an issue, or your installation in general has been corrupted when it tried to upgrade.

            You might try to detect corruption by using a tool like debsums to check for any obviously corrupted files.

            What’s the state of your debian packages I wonder… does something like apt-get update or apt-get check highlight any problems with the state of installed packages that could point to a failed upgrade?

            • mariah@feddit.rocksOP
              link
              fedilink
              arrow-up
              6
              arrow-down
              1
              ·
              9 months ago

              I think its because / is full. Some packages cant update. Is there a way to combine them without gui as i am disabled and cant use a mouse? I know u cant edit partitions booted

              • Successful_Try543@feddit.de
                link
                fedilink
                arrow-up
                13
                ·
                edit-2
                9 months ago

                If you can boot into terminal session, e.g. by pressing Ctrl + Alt + F2, you can try:

                sudo apt clean
                sudo apt -f install
                sudo apt clean
                sudo apt dist-upgrade
                sudo apt clean
                

                If sudo apt -f install doesn’t work properly, you can create an apt-cache folder on, e.g. your home partition, assuming this is the one with sufficient amounts of free storage.

                sudo apt clean
                sudo mkdir /home/apt-cache
                sudo nano /etc/fstab
                

                In the fstab you specify where this directory shall be mounted:

                /home/apt-cache    /var/cache/apt/archives    none    bind    0    0
                

                Now you copy the files in place and mount the partition:

                sudo cp -r /var/cache/apt/archives/* /home/apt-cache
                sudo mount -a
                

                Nou you should be able to run the fix-installation and update commands without the errors:

                sudo apt -f install
                sudo apt dist-upgrade
                
              • henfredemars
                link
                fedilink
                English
                arrow-up
                5
                ·
                9 months ago

                This may seem like an obvious question, but are there files you can remove or perhaps move to another drive or USB stick temporarily to make enough space to get through your updates? You should be able to do those while rootfs is full.

                We can certainly delete or copy files using the terminal.

                Are you sure the root is full and not readonly due to other errors? Why do you believe root is full?