*New to Linux* Can’t evaluate _crs 12311

[kc1di]

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?

Good Luck.

 

[Crpt112]

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?

Good Luck.

Nomodeset is working only if i change grub conf.. if i go back to “quiet splash” the error appears again.. please check screenshots below.

This is how it looks with nomodeset everytime i start/restart/shutdown PC (can’t evaluate…) does not appear

 

[kc1di]

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

inxi -G

 

[Crpt112]

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

inxi -G

Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
    driver: N/A
  Device-2: NVIDIA GF106GL [Quadro 2000] driver: nvidia v: 390.147
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1680x1050~60Hz
  OpenGL: renderer: Quadro 2000/PCIe/SSE2 v: 4.6.0 NVIDIA 390.147

 

[kc1di]

Ok it's a dual graphics card does it work with the intel side?

 

[wizardfromoz]

@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.

Thanks

Wizard

 

[Crpt112]

@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.

Thanks

Wizard

There is no /timeshift folder in /sys nor /tmp

 

[Brickwizard]

The FAILED Casper is a bug in Ubuntu that has transgressed to mint
see

Ubuntu boot systemd[1]: Failed to start casper-md5check Verify Live ISO checksums

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.

askubuntu.com

 

[Crpt112]

The FAILED Casper is a bug in Ubuntu that has transgressed to mint
see

Ubuntu boot systemd[1]: Failed to start casper-md5check Verify Live ISO checksums

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.

askubuntu.com

Just checked.. seems like it's safe to completely remove casper.. but is this something related to my issue?

 

[kc1di]

Just checked.. seems like it's safe to completely remove casper.. but is this something related to my issue?

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

sudo systemctl disable casper-md5check.service

 

[wizardfromoz]

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.

df

My first few lines in this older Mint look as follows

[email protected]:~$ df
df: /run/user/1000/doc: Operation not permitted
Filesystem     1K-blocks      Used Available Use% Mounted on
udev             8096912         0   8096912   0% /dev
tmpfs            1628780      2204   1626576   1% /run
/dev/sdb7       20466388  12362520   7038908  64% /
tmpfs            8143884         0   8143884   0% /dev/shm
tmpfs               5120         4      5116   1% /run/lock
tmpfs            8143884         0   8143884   0% /sys/fs/cgroup
/dev/sdb1         523244    338248    184996  65% /boot/efi

So in my case, for my Linux Mint 20.3 Cinnamon, the root partition is /dev/sdb7 and I have the EFI System Partition at /dev/sdb1.

2. The second command tells me exactly when the system was installed.

sudo dumpe2fs $(mount | grep 'on \/ ' | awk '{print $1}') | grep 'Filesystem created:'

For clarity, with grep 'on \/ '
that is a backslash followed by a forward slash, NOT a capital V, so best to copy and paste my command.

Mine shows

[email protected]:~$ sudo dumpe2fs $(mount | grep 'on \/ ' | awk '{print $1}') | grep 'Filesystem created:'
[sudo] password for chris:         
dumpe2fs 1.45.5 (07-Jan-2020)
Filesystem created:       Wed Jun 22 15:44:20 2022

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

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

[email protected]:~$ 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.

Spoiler: Wizard's Timeshift Logs Mint 20.3

[email protected]:~$ ls /var/log/timeshift/
2022-06-23_09-56-33_gui.log 2022-07-07_17-41-25_gui.log
2022-06-24_08-33-00_gui.log 2022-07-08_08-18-10_gui.log
2022-06-24_09-56-58_gui.log 2022-07-08_11-32-35_gui.log
2022-06-24_10-00-08_gui.log 2022-07-08_14-50-49_gui.log
2022-06-26_09-15-44_gui.log 2022-07-09_10-56-33_gui.log
2022-06-26_13-27-09_gui.log 2022-07-10_09-03-04_gui.log
2022-06-26_16-38-36_gui.log 2022-07-10_12-31-31_gui.log
2022-06-27_11-41-26_gui.log 2022-07-10_14-08-28_gui.log
2022-06-27_12-31-18_gui.log 2022-07-11_07-25-45_gui.log
2022-06-27_15-20-50_gui.log 2022-07-11_12-44-36_gui.log
2022-06-28_17-41-18_gui.log 2022-07-11_14-26-40_gui.log
2022-06-29_08-06-10_gui.log 2022-07-11_16-52-03_gui.log
2022-07-01_14-14-14_gui.log 2022-07-12_10-09-44_gui.log
2022-07-01_17-21-57_gui.log 2022-07-12_12-55-50_gui.log
2022-07-02_13-03-20_gui.log 2022-07-13_11-55-16_gui.log
2022-07-02_14-10-30_gui.log 2022-07-13_15-03-57_gui.log
2022-07-02_14-47-50_gui.log 2022-07-13_17-01-48_gui.log
2022-07-03_08-35-10_gui.log 2022-07-14_16-57-23_gui.log
2022-07-03_13-10-19_gui.log 2022-07-15_09-53-22_gui.log
2022-07-05_09-05-49_gui.log 2022-07-15_09-56-39_gui.log
2022-07-05_12-34-53_gui.log 2022-07-22_10-01-44_gui.log
2022-07-05_13-24-36_gui.log 2022-07-24_12-05-07_gui.log
2022-07-05_13-26-47_gui.log 2022-07-25_12-28-59_gui.log
2022-07-05_13-55-41_gui.log 2022-07-25_12-29-38_gui.log
2022-07-06_09-32-48_gui.log 2022-07-26_13-46-06_gui.log
2022-07-06_13-12-28_gui.log 2022-07-30_14-52-51_gui.log
2022-07-06_15-03-38_gui.log 2022-08-05_15-42-01_gui.log
2022-07-06_15-44-54_gui.log 2022-08-06_14-48-06_gui.log
2022-07-06_17-10-00_gui.log 2022-08-20_16-24-31_gui.log
2022-07-07_09-12-30_gui.log 2022-08-21_17-03-59_gui.log
2022-07-07_11-59-22_gui.log 2022-09-28_16-11-50_gui.log
2022-07-07_16-19-54_gui.log 2022-10-23_09-52-51_gui.log
2022-07-07_16-21-55_gui.log 2022-11-26_07-06-22_gui.log
2022-07-07_17-40-50_gui.log

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

sudo grub-install /dev/sdx

sudo update-grub

reboot

... where /dev/sdx is the device/drive identified as being where his root partition is.

Later.

Wizard

 

[Lord Boltar]

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

 

[wizardfromoz]

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.

Cheers

Wizard

 

[Lord Boltar]

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?

Most likely they are working intermittently just not effectively which is why I believe it is a kernel/driver compatibility issue

 

[wizardfromoz]

... 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.

Make sense?

Wiz

 

[wizardfromoz]

BTW, the OP said 3 days ago

I switched from Windows to Linux Mint 2 days ago.

... so unless he finds that snapshot and adds comments in the Comments field, that will be lost.

The clock is ticking.

Wiz

 

[Lord Boltar]

so unless he finds that snapshot and adds comments in the Comments field, that will be lost

My guess - if their is a snapshot , it will most likely just have the Nouveau drivers

 

[wizardfromoz]

... 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.