Solved LMDE 6 Crashed On Startup

[Angelsong7]

I recently installed LMDE 6 on my desktop. Yesterday, I updated the system from the update manager. After the update was finished, the manager said to reboot the system. Upon reboot, it failed and went into the TTYL mode. I cannot get out of this. Attached are photos of what is shown on the screen. I do have Timeshift enabled. How do I fix this, with or without Timeshift?



Code:
System:
Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 5.8.4
tk: GTK v: 3.24.38 wm: muffin dm: LightDM Distro: LMDE 6 Faye base: Debian 12.1 bookworm
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 1202 date: 10/22/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard ERGO K860 serial: <filter>
charge: 50% (should be ignored) status: N/A
Device-2: hidpp_battery_1 model: Logitech ERGO M575 Trackball serial: <filter> charge: 100%
status: discharging
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ rev: 0 cache:
L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 2199 high: 2200 min/max: 2200/4850 boost: enabled cores: 1: 2200 2: 2200
3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2198 11: 2200 12: 2200 13: 2200
14: 2200 15: 2200 16: 2200 bogomips: 121363
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Gigabyte
driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: HDMI-A-2
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 1002:73df
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96
Monitor-1: HDMI-A-2 mapped: HDMI-A-1 model: INSIGNIA-TV res: 3840x2160 dpi: 138
diag: 1079mm (42.5")
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6750 XT (navi22 LLVM 15.0.6 DRM 3.49
6.1.0-13-amd64) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:ab28
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487
API: ALSA v: k6.1.0-13-amd64 status: kernel-api
Server-1: JACK v: 1.9.21 status: off
Server-2: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Broadcom NetXtreme II BCM5709 Gigabit Ethernet driver: bnx2 v: kernel pcie:
speed: 2.5 GT/s lanes: 4 port: N/A bus-ID: 04:00.0 chip-ID: 14e4:1639
IF: enp4s0f0 state: down mac: <filter>
Device-2: Broadcom NetXtreme II BCM5709 Gigabit Ethernet driver: bnx2 v: kernel pcie:
speed: 2.5 GT/s lanes: 4 port: N/A bus-ID: 04:00.1 chip-ID: 14e4:1639
IF: enp4s0f1 state: down mac: <filter>
Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 06:00.0 chip-ID: 8086:2723
IF: wlp6s0 state: up mac: <filter>
Device-4: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s
lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8125
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-5:2 chip-ID: 8087:0029
Report: hciconfig ID: hci0 rfk-id: 12 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 200f
Drives:
Local Storage: total: 4.09 TiB used: 804.29 GiB (19.2%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDBRPG0010BNC-WRSN size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 44.9 C
ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850 1TB size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 40.9 C
ID-3: /dev/sda vendor: Western Digital model: WDBNCE0010PNC size: 931.51 GiB speed: 6.0 Gb/s
serial: <filter>
ID-4: /dev/sdb vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB speed: 6.0 Gb/s
serial: <filter>
ID-5: /dev/sdc vendor: Western Digital model: WDBNCE5000PNC size: 465.76 GiB speed: 6.0 Gb/s
serial: <filter>
Partition:
ID-1: / size: 883.82 GiB used: 27.18 GiB (3.1%) fs: ext4 dev: /dev/dm-0 mapped: lvmlmde-root
ID-2: /boot/efi size: 285.4 MiB used: 5.8 MiB (2.0%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 31.23 GiB used: 1.09 GiB (3.5%) priority: -2 dev: /dev/dm-1
mapped: lvmlmde-swap
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 10 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002
Device-1: 1-5:2 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb rev: 2.0
speed: 12 Mb/s chip-ID: 8087:0029
Device-2: 1-6:3 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid rev: 2.0
speed: 12 Mb/s chip-ID: 0b05:1939
Hub-2: 1-7:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 05e3:0610
Device-1: 1-8:5 info: Prolific LG GE24LU21 type: Mass Storage driver: usb-storage rev: 2.0
speed: 480 Mb/s chip-ID: 067b:2571
Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
Hub-4: 3-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002
Hub-5: 3-3:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 05e3:0610
Device-1: 3-3.1:3 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
driver: logitech-djreceiver,usbhid rev: 2.0 speed: 12 Mb/s chip-ID: 046d:c52b
Hub-6: 3-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 05e3:0610
Device-1: 3-3.3:5 info: STMicro PCPanel Pro 1.0 type: HID driver: N/A rev: 2.0 speed: 12 Mb/s
chip-ID: 0483:a3c5
Device-2: 3-3.4:6 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
driver: logitech-djreceiver,usbhid rev: 2.0 speed: 12 Mb/s chip-ID: 046d:c52b
Hub-7: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
Sensors:
System Temperatures: cpu: 42.1 C mobo: N/A gpu: amdgpu temp: 42.0 C mem: 38.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3116 pm: dpkg pkgs: 3056 pm: flatpak pkgs: 60
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com faye main upstream import backport
2: deb https: //deb.debian.org/debian bookworm main contrib non-free non-free-firmware
3: deb https: //deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
4: deb http: //security.debian.org/ bookworm-security main contrib non-free non-free-firmware
5: deb https: //deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
Info:
Processes: 404 Uptime: 6d 23h 17m Memory: 31.23 GiB used: 4.8 GiB (15.4%) Init: systemd v: 252
target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Client: Unknown
python3.11 client inxi: 3.3.26

 

[Condobloke]

To fix with Timeshift, boot the pc to a usb stick....does not have to have your particular OS on it...just so long as it is a Linux OS which runs Timeshift.
When booted to the 'live' environment, open Timeshift and set the location to the place where you have your Timeshift snapshots stored.
Click on a previous snapshot....one that is prior to the update and reboot....

Click on Restore. Follow the prompts through...you should not have to change any settings.

5 Minutes should see you back in action.

In update manager, an Update will soon show for the kernel that caused this drama. Right click on it and select to ignore updates for that kernel.

 

[arochester]

On the screen that says: login
Can you still login with your name and password?
Try updating again.
It might not work immediately. You might have to wait a day or two

 

[KGIII]

If I'm reading the 'net correctly, at least this site, this may be a bad kernel?

If so, you can tell GRUB to boot to a previous kernel.

Access Recovery Mode On Ubuntu • Linux Tips

Today's article shouldn't be too long, but covers something important, which is how to access recovery mode on Ubuntu.

linux-tips.us

(It will be the same as it is with Ubuntu. Mint is derived from Ubuntu.)

 

[wizardfromoz]

G'day @Angelsong7

How do I fix this, with or without Timeshift?

I can show you 3 methods, but manners dictate your first responding to friends Brian @Condobloke and @arochester .

A couple of bits of additional information you should consider

1. On #2 with Timeshift - if the existing snapshot is just covering your system files that is fine.

If the snapshot is older, maybe a week or more, and you have included /home with it, you might want to make separate arrangements to safeguard Home. Timeshift is not technically a backup solution, it is for System Restore, and it will not prompt you before overwriting existing files and folders.

2. With #4 by David G. @KGIII - the possibility of using an older kernel from Advance Options is sound, but the Recovery Option will not work (without tweaking) because of the Debian influence over LMDE.

It will throw a message

"Unable to access open console, root is locked" or similar.

I can work around that.

See how you go, and if need be, I will assist.

Cheers

Chris Turner
wizardfromoz

 

[Angelsong7]

To fix with Timeshift, boot the pc to a usb stick....does not have to have your particular OS on it...just so long as it is a Linux OS which runs Timeshift.
When booted to the 'live' environment, open Timeshift and set the location to the place where you have your Timeshift snapshots stored.
Click on a previous snapshot....one that is prior to the update and reboot....

Click on Restore. Follow the prompts through...you should not have to change any settings.

5 Minutes should see you back in action.

In update manager, an Update will soon show for the kernel that caused this drama. Right click on it and select to ignore updates for that kernel.

Thank you for the tip. I've got a number of options here. I think I will try yours first. (Sorry for the delayed reply. I'm just now getting back to working on this. Thank you for your patience.)

 

[Angelsong7]

On the screen that says: login
Can you still login with your name and password?
Try updating again.
It might not work immediately. You might have to wait a day or two

(Sorry for the delayed reply. I'm just now getting back to working on this. Thank you for your patience.) I did not set the system up with a totally encrypted system. So I have no access with username/password.

 

[Angelsong7]

If I'm reading the 'net correctly, at least this site, this may be a bad kernel?

If so, you can tell GRUB to boot to a previous kernel.

Access Recovery Mode On Ubuntu • Linux Tips

Today's article shouldn't be too long, but covers something important, which is how to access recovery mode on Ubuntu.

linux-tips.us

(It will be the same as it is with Ubuntu. Mint is derived from Ubuntu.)

(Sorry for the delayed reply. I'm just now getting back to working on this. Thank you for your patience.) LMDE 6 is based on Debian. How would you tell GRUB to boot to a previous kernel?

 

[Angelsong7]

G'day @Angelsong7



I can show you 3 methods, but manners dictate your first responding to friends Brian @Condobloke and @arochester .

A couple of bits of additional information you should consider

1. On #2 with Timeshift - if the existing snapshot is just covering your system files that is fine.

If the snapshot is older, maybe a week or more, and you have included /home with it, you might want to make separate arrangements to safeguard Home. Timeshift is not technically a backup solution, it is for System Restore, and it will not prompt you before overwriting existing files and folders.

2. With #4 by David G. @KGIII - the possibility of using an older kernel from Advance Options is sound, but the Recovery Option will not work (without tweaking) because of the Debian influence over LMDE.

It will throw a message

"Unable to access open console, root is locked" or similar.

I can work around that.

See how you go, and if need be, I will assist.

Cheers

Chris Turner
wizardfromoz

Howdy, wizardfromoz.
Thank you for the etiquette lesson. This is the first that I have been online since my last post yesterday. Also, thank you for your additional tips on the response of the previous responders.
Y'all come back, ya hear?

 

[arochester]

I did not set the system up with a totally encrypted system. So I have no access with username/password.

I do not understand what you are saying. If you set up LMDE the other day you must have set up a username and password.

I thought it was a Kernel problem, although I did not say this. A replacement Kernel will be along.

 

[Angelsong7]

Thank you all for your tips and help. The computer is up and running fine now.

You'll never know until you try.

 

[Condobloke]

So, did timeshift do the job ? or did you use another approach ?

 

[Angelsong7]

So, did timeshift do the job ? or did you use another approach ?

Timeshift did the job. Once back up, I created a snapshot and installed the updates minus the kernel. Rebooted. And then installed the suspected kernel. Everything is just fine.

 

[Condobloke]

And then installed the suspected kernel.

So you have installed the kernel which we thought was the problem.
If that is the case then obviously that kernel was not the problem.......which leaves us to wonder just what the problem was !?

 

[KGIII]

So you have installed the kernel which we thought was the problem.

An alternative theory, unless they paid exact attention, would be that the problem was recognized and a newer kernel released in the interim. There were a number of complaints that seemed to involve the kernel. It happens...