Hello Again @Crpt112,
did you try the nomodeset as outlined in the release notes. That usually fixes Nvidia problems. At least temporarily.
Also did the live boot work?
Hello Again @Crpt112,
did you try the nomodeset as outlined in the release notes. That usually fixes Nvidia problems. At least temporarily.
Also did the live boot work?
If it's working with nomodeset then try the Nvidia drivers listed on the driver tool. See if one will work.
Also go to a terminal and type this command and post the output here
If it's working with nomodeset then try the Nvidia drivers listed on the driver tool. See if one will work.
Also go to a terminal and type this command and post the output here
@Crpt112 - important question - can you open your File Manager, click on left to show File System, and see if there is a folder called /timeshift , if there, it will be between /sys and /tmp ?
If it is there, open it and let us know what it contains.
@Crpt112 - important question - can you open your File Manager, click on left to show File System, and see if there is a folder called /timeshift , if there, it will be between /sys and /tmp ?
If it is there, open it and let us know what it contains.
When booting the laptop a message like this systemd[1]: Failed to start casper-md5check Verify Live ISO checksums. shows up (this is taken from journalctl -p err) and systemctl status casper-md5check.
When booting the laptop a message like this systemd[1]: Failed to start casper-md5check Verify Live ISO checksums. shows up (this is taken from journalctl -p err) and systemctl status casper-md5check.
Don't think it is because even with that bug system should eventually boot.
How ever you can try booting without it by issuing the command in a terminal
Heads up, Helpers and take a look at the first screenshot the OP supplied in #42 above. I reproduce it below.
This shows the OP in a working session of Mint, using Nano the console-based text editor to edit /etc/default/grub.
I would suggest, therefore that if the OP (@Crpt112 ) can get into Terminal (don't go as far as opening Nano) he provide us with output from the following commands:
1.
Code:
df
My first few lines in this older Mint look as follows
and that is correct, as I was moving Distros from the computer in the garage to the computer in the Study, and that would be the day I installed it on the new computer.
3. Two commands here
Code:
ls /etc/timeshift
and
ls /var/log/timeshift/
If there is no output for these, that will tell us that Timeshift has not ever run.
Mine for the first shows as
Code:
chris@UnaCinnamon-SSD:~$ ls /etc/timeshift
default.json restore-hooks.d timeshift.json
and for the second I have put it in a spoiler, if the OP has output it will be much less - click to open the Spoiler and click to close.
So if the OP could provide that output from 4 commands, it will assist.
To the helpers, I am thinking that if we need to we could have the OP either run the following from within an active session of Mint, or via a chroot session from Live USB
I think his problem is he is running NVIDIA Drivers 390 on kernel 5.15 that does not support those old drivers anymore - I believe kernel 5.4 was the last kernel that could use those legacy drivers - so I believe you have a couple of options 1) remove the NVIDIA drivers and let Nouveau handle your GPU or 2) Retrograde back to Mint 20 which came with kernel 5.4 and then install the NVIDIA Legacy drivers
I certainly defer to you in regard to driver problems, but if that is so, how was he able to have visual to the point of providing the screenshot of a Nano session?
I may be being obtuse, or the Aspie (Asperger's) is kicking in, but I am inclined to believe there is an automatic Timeshift snapshot there somewhere, and it may be not where we expect it to be. If that is the case, and we can establish the time it was generated, compared to the time he installed the system, he may be able to restore functionality and work from there.
Regrets, @Crpt112 , on referring to you in the third person.
I certainly defer to you in regard to driver problems, but if that is so, how was he able to have visual to the point of providing the screenshot of a Nano session?
... sounds good to me. BUT (and you know what they say about Wizard's butt), see as follows.
The OP's distro is Mint, and Timeshift is installed.
Timeshift by default is set up to take a first snapshot on the first day of use, that is, the day the OP installed it (or other, if he did not use it right away).
It will take a Daily snapshot first, and keep it for 5 days before culling, unless you add comments. It will take the snapshot on the hour (as it changes) from when the session commences.
To illustrate that - yesterday I purged my Timeshift on my Linux Mint 21.0 'Vanessa' Cinnamon, and its dependencies, and also the default and created files in /etc/timeshift/ , thus eliminating previous settings. I had logged into Vanessa at 8:17AM before doing this.
I then reinstalled a clean version of Timeshift, and went about my chores.
When I returned, Timeshift had taken a snapshot at 9:00:03 , size 8 GB or so.
So there is a strong chance this may have happened with the OP, and if that is before he started experimenting with drivers, we can roll him back to before then, and work from there with the correct drivers.
... and that is fine, because then he can add comments to the snapshot which will keep it, and then he can work through the steps you suggest.
Cheers
Wizard
BTW @Crpt112 , if you can provide us with a screenshot of your drive, taken from GParted (or several if there is more than one drive involved), I can likely tell you where to check for a Timeshift snapshot better.