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.
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?
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
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.
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?
Did you solve it? Recently there was a problem with graphics thing and downgrading mess from 1.24 to 1.23 helped me. It was in arch with AMD graphics, but some people said Nvidia ones also had the problem.
I would be looking for ways to revert that update. Either using a pre-existing timeshift shapshot or maybe apt's built in reversion capability. (Which I'm not familiar with, sorry.) Hopefully someone with real skills will chime in, good luck.
You may want to go back to driver 525... im not running debian at the moment, nor do i use mvidia graphics, but this page seems to say that 525 is the newest supported version as of feb 2
Yeah. Why would anyone expect one of the most popular video cards in the world to work in Linux. Those idiots.
Just to be clear. I understand why a proprietary card may not work. It isn't Linux's responsibility to make it work. However, what isn't acceptable is for the automated update system of an OS to break a working system. Proprietary driver or not. The update system should have thrown up some very strong warnings that proceeding would break the system.
This would implies the package management system to know the inner working of nvidia drivers so it can warn users when updates would break it. How one's implement it?
The distro should be testing the driver within their update system before including it in their repo. The package should include metadata about system settings that could potentially break the system.
Distro makers have test machines to test their packages before pushing them out, but they can only cover popular and common hardware. Expecting them to test it on all graphic card permutations is too much considering most distros are released for free and maintained by volunteers, especially since nvidia cards aren't cheap anymore.
As long as you keep relying on this cliche excuse, Linux is never going to be treated as a serious desktop operating system.
Distros are trying to create usable, friendly systems. They failed at that if their distros are this fragile. That's what "unacceptable" means in this context. You can't just throw your middle finger up in the air at the user when their system fails by saying "you didn't pay for it" and scurry off giggling. Yet Linux advocates keep pushing Linux on inexperienced users, saying that it's the solution to everything; that it's so easy their grandma uses it.
I don't use Linux as anything more than a toy for this very reason. I'll start taking it seriously when its advocates do.
72 Comments
henfredemars@infosec.pub · 35 pts · 2y
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?
mariah@feddit.rocks · 9 pts · 2y
Yes to both. What should i do
henfredemars@infosec.pub · 11 pts · 2y
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.
mariah@feddit.rocks · 5 pts · 2y
Same error on older kernel
henfredemars@infosec.pub · 11 pts · 2y
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
debsumsto check for any obviously corrupted files.What's the state of your debian packages I wonder... does something like
apt-get updateorapt-get checkhighlight any problems with the state of installed packages that could point to a failed upgrade?mariah@feddit.rocks · 5 pts · 2y
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 · 12 pts · 2y
If you can boot into terminal session, e.g. by pressing Ctrl + Alt + F2, you can try:
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.
In the fstab you specify where this directory shall be mounted:
Now you copy the files in place and mount the partition:
Nou you should be able to run the fix-installation and update commands without the errors:
mariah@feddit.rocks · 12 pts · 2y
I booted into i3!
AnUnusualRelic@lemmy.world · 6 pts · 2y
A full root will absolutely kill your system.
You have unlocked a new achievement: the software hoarder!
mariah@feddit.rocks · 1 pts · 2y
Yay. What did i win
henfredemars@infosec.pub · 5 pts · 2y
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?
mariah@feddit.rocks · 2 pts · 2y
duf / lists 0gb as available. Idk what i should move
XTL@sopuli.xyz · 3 pts · 2y
Avoid Nvidia like the plague.
mariah@feddit.rocks · 3 pts · 2y
Wait months to buy a amd gpu as im on disablity? Got it
redcalcium@lemmy.institute · 28 pts · 2y
* zoom in on the error message
Yep, of course it's Nvidia.
cevn@lemmy.world · 7 pts · 2y
Every time I have seen a funky black screen with text against my will Nvidia was involved.
skullgiver@popplesburger.hilciferous.nl · 22 pts · 2y
Naz@sh.itjust.works · 21 pts · 2y
It's good to see that the same problems from Knoppix in 1998 still persist into 2024.
It's become my standard procedure to do a full backup before a major version upgrade of Linux nowadays as a result
Xserver has failed to start.
mariah@feddit.rocks · 9 pts · 2y
Gotta love xorg
mojofrododojo@lemmy.world · 8 pts · 2y
now there's a name I haven't heard in ages...
db2@lemmy.world · 13 pts · 2y
Looks like it wants to remove the cause but not the symptom.
EveryMuffinIsNowEncrypted@lemmy.blahaj.zone · 12 pts · 2y
I'm gonna be honest: I don't know what you're trying to say.
db2@lemmy.world · 2 pts · 2y
Rocky Horror
EveryMuffinIsNowEncrypted@lemmy.blahaj.zone · 2 pts · 2y
Ohhhhhhh
Good movie. Thanks!
VerseAndVermin@lemmy.world · 10 pts · 2y
I'm not knocking it, but I feel like you really wanted to use this image somewhere. 😁👍
db2@lemmy.world · 2 pts · 2y
Look on top of op's monitor
VerseAndVermin@lemmy.world · 2 pts · 2y
Oh snap!
Haha
luves2spooge@lemmy.world · 3 pts · 2y
Looks like Eddie Izzard
tsonfeir@lemm.ee · 2 pts · 2y
Looks like Tim Curry.
mariah@feddit.rocks · 1 pts · 2y
Yes thats a toy
ryannathans@aussie.zone · 12 pts · 2y
That's the novideo graphics card for you
ipsirc@lemmy.ml · 11 pts · 2y
It's a known and fixed problem. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
ulu_mulu@lemm.ee · 4 pts · 2y
That was on the kernel 6.1.0-18, I had it too, fixed several days ago, but in OP picture the kernel is 6.1.0-17, that one wasn't affected.
skullgiver@popplesburger.hilciferous.nl · 3 pts · 2y
unexposedhazard@discuss.tchncs.de · 7 pts · 2y
MommysBabygiwl ?? On the third line. Is this canon to debian lore or did OP change it to that?
backhdlp@iusearchlinux.fyi · 2 pts · 2y
that's the hostname
unexposedhazard@discuss.tchncs.de · 1 pts · 2y
Ah i see ty
baggins@lemmy.ca · 7 pts · 2y
Nice! That looks like a fun one.
mariah@feddit.rocks · 1 pts · 2y
Ikr. So fun
thevoidzero@lemmy.world · 5 pts · 2y
Did you solve it? Recently there was a problem with graphics thing and downgrading mess from 1.24 to 1.23 helped me. It was in arch with AMD graphics, but some people said Nvidia ones also had the problem.
Edit: mesa not mess
mariah@feddit.rocks · 5 pts · 2y
Yes. Apt-cache is mounted on /home which allowed me to update fully
PrettyFlyForAFatGuy@lemmy.ml · 4 pts · 2y
if your updates included a new kernel try installing the kernel headers for the new kernel.
then if it's still not working reinstall the nvidia driver.
i used to daily drive debian with proprietary nvidia drivers and it would break with every kernel upgrade
from memory, so almost certainly incorrect, the fix was simply something like
BabyVi@lemmy.world · 4 pts · 2y
I would be looking for ways to revert that update. Either using a pre-existing timeshift shapshot or maybe apt's built in reversion capability. (Which I'm not familiar with, sorry.) Hopefully someone with real skills will chime in, good luck.
cetvrti_magi@lemmy.world · 4 pts · 2y
I had same problem on Arch based distros, it's Nvidia problem. Try booting with LTS kernel.
mvirts@lemmy.world · 3 pts · 2y
You may want to go back to driver 525... im not running debian at the moment, nor do i use mvidia graphics, but this page seems to say that 525 is the newest supported version as of feb 2
https://wiki.debian.org/NvidiaGraphicsDrivers#sid-525
allywilson@sopuli.xyz · 1 pts · 2y
Give this a try: https://unix.stackexchange.com/questions/543021/broken-bumblebee-on-debian-testing-crashes-with-ee-unw-get-proc-name-failed-n
riodoro1@lemmy.world · 1 pts · 2y
Oh no! It was only supposed to happen to Arch.
wintermute_oregon@lemm.ee · 0 pts · 2y
mariah@feddit.rocks · 4 pts · 2y
Yup
wintermute_oregon@lemm.ee · 5 pts · 2y
possiblylinux127@lemmy.zip · 4 pts · 2y
That explains it
tdawg@lemmy.world · 4 pts · 2y
Good luck
rah@feddit.uk · -3 pts · 2y
You bought an Nvidia graphics card.
BradleyUffner@lemmy.world · 6 pts · 2y
Yeah. Why would anyone expect one of the most popular video cards in the world to work in Linux. Those idiots.
Just to be clear. I understand why a proprietary card may not work. It isn't Linux's responsibility to make it work. However, what isn't acceptable is for the automated update system of an OS to break a working system. Proprietary driver or not. The update system should have thrown up some very strong warnings that proceeding would break the system.
redcalcium@lemmy.institute · 2 pts · 2y
This would implies the package management system to know the inner working of nvidia drivers so it can warn users when updates would break it. How one's implement it?
BradleyUffner@lemmy.world · 1 pts · 2y
The distro should be testing the driver within their update system before including it in their repo. The package should include metadata about system settings that could potentially break the system.
redcalcium@lemmy.institute · 3 pts · 2y
Distro makers have test machines to test their packages before pushing them out, but they can only cover popular and common hardware. Expecting them to test it on all graphic card permutations is too much considering most distros are released for free and maintained by volunteers, especially since nvidia cards aren't cheap anymore.
rah@feddit.uk · 0 pts · 2y
Have you contacted whoever you pay for your support contract?
BradleyUffner@lemmy.world · 0 pts · 2y
As long as you keep relying on this cliche excuse, Linux is never going to be treated as a serious desktop operating system.
Distros are trying to create usable, friendly systems. They failed at that if their distros are this fragile. That's what "unacceptable" means in this context. You can't just throw your middle finger up in the air at the user when their system fails by saying "you didn't pay for it" and scurry off giggling. Yet Linux advocates keep pushing Linux on inexperienced users, saying that it's the solution to everything; that it's so easy their grandma uses it.
I don't use Linux as anything more than a toy for this very reason. I'll start taking it seriously when its advocates do.
rah@feddit.uk · 1 pts · 2y
Oh noes!
I disagree.
LOL
BradleyUffner@lemmy.world · 0 pts · 2y
... And your reply shows exactly why no one should take anything you say seriously. You're just trolling.
rah@feddit.uk · 1 pts · 2y
Don't confuse laughing at you for trolling, they're not the same thing.
mariah@feddit.rocks · 2 pts · 2y
I know, shame on me. Its like i wasnt on linux when i bought this computer
mariusafa@lemmy.sdf.org · 1 pts · 2y
Pretty much sums up every thing