LM 20.3 shutdown hangs

eastexas · Post by **eastexas** » Fri Feb 11, 2022 5:38 pm

I fresh installed LM20.3 coming form LM18 and everything works great except I cant turn the computer off. I have read all the forum post and nothing seems to help.
system core I 5 6600k
amd 390
16gb ram

Tried amd driver
fresh install with fresh iso. multiple tries with each
cant see any issue in bios
all the latest drivers and kernel as its the latest ISO

I really like my linux mint computer and only tried to upgrade because of end of support for LM18. This one issue is a real problem for me.

Like I said, except for shutdown and restart hangs it works perfectly. Hangs everytime. Terminal shutdown works.

Could really use some help from the Linux Mint Gods out there. Willing to try anything. All data backed up.

Thanks for your time and support

eastexas · Post by **eastexas** » Fri Feb 11, 2022 6:00 pm

Additional info after telling it to shut down it goes through the motions and ends on a green screen but computer is still running.

eastexas · Post by **eastexas** » Fri Feb 11, 2022 7:34 pm

Terminal shutdown works only some times

eastexas · Post by **eastexas** » Fri Feb 11, 2022 8:01 pm

tried installing mate edition but same shutdown issue. any help would be appreciated

AZgl1800 · Post by **AZgl1800** » Fri Feb 11, 2022 8:03 pm

eastexas wrote: ⤴Fri Feb 11, 2022 5:38 pm
Tried amd driver
fresh install with fresh iso. multiple tries with each
cant see any issue in bios
all the latest drivers and kernel as its the latest ISO

You "seem to" think that the ISOs are updated after the initial release.

Sorry, but they are not.
that is what Update Manager is for;
once you do a Fresh Install, IF, you do NOT ever let Update Manager run, it will be the same exact version that was released on Day 1.

Did you check the Box for "allow Media files to be installed?"
if you did not, then your install is crippled.

.

eastexas · Post by **eastexas** » Fri Feb 11, 2022 8:32 pm

Thanks for replying AZ.

I did check the media box and i also ran the update manager first thing. Each time I tried the install I did both and the results were always the same.

Any other ideas would be greatly appreciated.

Thanks for taking the time to help

eastexas · Post by **eastexas** » Sat Feb 12, 2022 11:10 am

do you think trying an older kernel might help?

I am running the latest bios

eastexas · Post by **eastexas** » Tue Feb 15, 2022 10:57 pm

I can not seem to get any assistance with my shutdown hanging. Tried recent bios,fresh install with updates, amd proprietary drivers and now I am at the end of my knowledge. Shutdown via terminal works sometimes and normal shutdown has worked twice for some reason. Linux Mint shuts down and flickers at LM logo and then hangs on a full green screen. Have noticed it does it when trying to just fresh install as well. The 2 times it shut down normal the LM logo did not flicker. Not sure if that's related. I had no hardware problems running LM18 before I fresh installed LM 20.3. with all recommended software updated with no change. Media box checked on install.

I have read similar threads that most end without a solution.

My system works flawlessly except for the shutdown hangs. Without a solution and the knowledge to troubleshoot this problem I will be needing to find a new distro. I have run Linux Mint for over 10 years and would very much like to continue but I will need to solve this shutdown hang issue. Having to hold the power button every time I shutdown is not a feasible solution for a long term commitment to an OS.

I am making one last plea to the Linux Gods with the knowledge to help me troubleshoot this issue.

If it helps I am coming from Linux Mint 18 since its launch and I believe it was LM 14 before that. Would like to be on LM 20 till 2025. Please help

Thank you for your time and hope I can continue to be a Linux Mint user.

pdc_2 · Post by **pdc_2** » Tue Feb 15, 2022 11:50 pm

the new release of Mint 22: based on Ubuntu 22.04 I understand; may be available by July this year? one possibility; if keen to stay with Mint; would be to try the live USB for Mint 19; if it allows you to shut the computer down, you could install and run Mint 19 till the Mint 22 comes available; (perhaps it will be called Mint 21 ..... don't know)

BeyondLies_MintForum · Wed Feb 16, 2022 12:11 am

Let's see whether I can help.

Four questions.

1) When the Mint logo is showing, upon shutting down (or trying to), press a key. Do you see any messages?

2) When trying unsuccessfully to shut down via terminal: do you see any messages?

3) Is there anything relevant in logs? Look in all the logs that the Mint 'Log's program (or e.g. the program 'ksyslog') provides.

4) Can you provide fuller system specifications? Do that via inxi -Fxxxrz. (Also, but never mind this now, but the 'Installation and Boot' section of the forum does not quite seem the right one for this problem.)

eastexas · Post by **eastexas** » Wed Feb 16, 2022 1:09 am

Thanks for trying to help. It really means a lot to me.
questions answered

1- no message

2- no message

3- in logs under system there are several lines that end with "tainted kernel". Could this be the problem?

4-Have not done this yet as I want to see what you say about tainted kernel. But I will be happy to do this . Just not sure how to copy and post the info.

Thank you so much for trying to help BEYOND and PDC. I know there is a way to copy your names to give you credit but its been so long since I needed help I have forgotten.

Also I really did not know where to post this thread. Sorry

eastexas · Post by **eastexas** » Wed Feb 16, 2022 1:16 am

Code: Select all

inxi -Fxxxrz
System:
  Kernel: 5.4.0-99-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170-DELUXE v: Rev 1.xx 
  serial: <filter> UEFI: American Megatrends v: 3801 date: 03/14/2018 
Battery:
  Device-1: hidpp_battery_0 model: Logitech G700s serial: <filter> 
  charge: 5% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core i5-6600K bits: 64 type: MCP 
  arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 27999 
  Speed: 900 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2750 2: 3209 
  3: 3828 4: 2900 
Graphics:
  Device-1: AMD Tonga PRO [Radeon R9 285/380] vendor: Tul driver: amdgpu 
  v: kernel bus ID: 01:00.0 chip ID: 1002:6939 
  Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 3840x2160~30Hz 
  OpenGL: renderer: AMD Radeon R9 380 Series (TONGA DRM 3.35.0 
  5.4.0-99-generic LLVM 12.0.0) 
  v: 4.6 Mesa 21.2.6 direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 
  Device-2: AMD Tonga HDMI Audio [Radeon R9 285/380] vendor: Tul 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aad8 
  Sound Server: ALSA v: k5.4.0-99-generic 
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k 
  port: f000 bus ID: 00:1f.6 chip ID: 8086:15b8 
  IF: enp0s31f6 state: down mac: <filter> 
  Device-2: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network 
  Adapter 
  vendor: ASUSTeK driver: wl v: kernel port: e000 bus ID: 07:00.0 
  chip ID: 14e4:43a0 
  IF: wlp7s0 state: dormant mac: <filter> 
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb 
  v: 5.6.0-k port: b000 bus ID: 0b:00.0 chip ID: 8086:1539 
  IF: enp11s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 462.05 GiB used: 32.16 GiB (7.0%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 256GB 
  size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 1B0QBXX7 
  scheme: GPT 
  ID-2: /dev/sda vendor: Patriot model: Ignite size: 223.57 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 01.5 scheme: MBR 
Partition:
  ID-1: / size: 233.24 GiB used: 32.15 GiB (13.8%) fs: ext4 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A gpu: amdgpu temp: 63 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 949 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 226 Uptime: 4h 32m Memory: 15.57 GiB used: 1.41 GiB (9.0%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

eastexas · Post by **eastexas** » Wed Feb 16, 2022 1:17 am

Beyond --- That above post was question #4 output from terminal command

Must go to bed now but will check back tomorrow after work. Look forward to your reply

eastexas · Post by **eastexas** » Wed Feb 16, 2022 1:28 am

Also saw something in application logs that said Warning screensaver detected on the bus. But this problem has been there from the start and I disable all screensaver to never. Not sure this is relevant but I wanted to share all info

BeyondLies_MintForum · Wed Feb 16, 2022 1:50 am

Hello again @eastexas

Kernel 'tainting' is a technical business that does not indicate a problem for the end user. The screensaver message is a known problem with Mint and fairy harmless (and I think due to be fixed with a soon-to-appear update to Mint).

I think the problem has to do with Linux not liking your graphics card, so to speak. For, see here and here. One of those threads suggests a kernel upgrade fixed the problem. Newer Linux kernels bring support for new hardware and bugfixes for drivers. Mint 20 supports, officially, kernels up to 5.13 - so I suggest you install the version of the 5.13 kernel that Mint offers. One can install that kernel via Mint's Update Manager: View -> Linux Kernels.

If the kernel upgrade does not do the the trick, then something else that might help is a firmware update for your graphics card. If such an update is available - check with the manufacturer of the card (e.g. Asus or whomever) - then you might have to use Windows (if you can) to install it, but perhaps Linux's Firmware Update Manager can do it. To that latter end, try:

Code: Select all

sudo fwupdmgr get-devices && sudo fwupdmgr refresh && sudo fwupdmgr get-updates && sudo fwupdmgr update

eastexas · Post by **eastexas** » Wed Feb 16, 2022 10:28 am

BeyondLies_MintForum wrote: ⤴Wed Feb 16, 2022 1:50 am Hello again @eastexas

Kernel 'tainting' is a technical business that does not indicate a problem for the end user. The screensaver message is a known problem with Mint and fairy harmless (and I think due to be fixed with a soon-to-appear update to Mint).

I think the problem has to do with Linux not liking your graphics card, so to speak. For, see here and here. One of those threads suggests a kernel upgrade fixed the problem. Newer Linux kernels bring support for new hardware and bugfixes for drivers. Mint 20 supports, officially, kernels up to 5.13 - so I suggest you install the version of the 5.13 kernel that Mint offers. One can install that kernel via Mint's Update Manager: View -> Linux Kernels.

If the kernel upgrade does not do the the trick, then something else that might help is a firmware update for your graphics card. If such an update is available - check with the manufacturer of the card (e.g. Asus or whomever) - then you might have to use Windows (if you can) to install it, but perhaps Linux's Firmware Update Manager can do it. To that latter end, try:
Code: Select all
sudo fwupdmgr get-devices && sudo fwupdmgr refresh && sudo fwupdmgr get-updates && sudo fwupdmgr update

Thanks for trying to help.

I loaded kernel 5.13 and booted into it. Made it active but no change. Ran the code you listed in terminal and this is what it said but not sure how to read the output.i

Code: Select all

:        
System Product Name
│
├─BCM20702A0:
│     Device ID:          8968a3bef0b7bbcda914f444d4c5ebcda641032f
│     Current version:    1.12
│     Vendor:             Broadcom Corp (USB:0x0B05)
│     Serial Number:      80A589A058F3
│     GUIDs:              ff3f3a18-1b33-5339-87fa-0d586aca4644 ← USB\VID_0B05&PID_180A&REV_0112
│                         8e441291-f2bd-5d5b-b0d8-6479e3abd2a2 ← USB\VID_0B05&PID_180A
│     Device Flags:       • Updatable
│   
├─Patriot Ignite:
│     Device ID:          948241a24320627284597ec95079cc1341c90518
│     Summary:            ATA Drive
│     Current version:    SAFM01.5
│     Vendor:             Phison (ATA:0x1987)
│     Serial Number:      DCA9075605EE01850115
│     GUIDs:              d87caf66-5320-5c62-9512-9b900a9fc6ab ← IDE\Patriot_Ignite__________________________SAFM01.5
│                         7594d2af-dbbd-5d70-b1c8-ff0d8db0896b ← IDE\0Patriot_Ignite__________________________
│                         96b199e0-5e02-5a53-b2f4-08e9a4ed6d74 ← Patriot Ignite
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│   
├─Samsung SSD 950 PRO 256GB:
│     Device ID:          3e02fa93f5a23507599b43d9363b0f6759cc4979
│     Summary:            NVM Express Solid State Drive
│     Current version:    1B0QBXX7
│     Vendor:             Samsung Electronics Co Ltd (NVME:0x144D)
│     Serial Number:      S2GLNXAH300611Y
│     GUIDs:              b586caf2-ac7e-5a07-8630-dd289d8fd3f4 ← NVME\VEN_144D&DEV_A802&SUBSYS_144DA801&REV_01
│                         484eb66f-4175-5499-8dc9-a8cc651e8450 ← NVME\VEN_144D&DEV_A802&SUBSYS_144DA801
│                         cce2386f-6d68-5f85-9f3f-ebead9288696 ← NVME\VEN_144D&DEV_A802&REV_01
│                         77bb4022-9503-586c-99b7-c8a64502da30 ← NVME\VEN_144D&DEV_A802
│                         70abbc51-af10-52e7-b2fd-20059eb95663 ← Samsung SSD 950 PRO 256GB
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│   
└─System Firmware:
  │   Device ID:          ed374603adf8124f3deb34491e286a4b467b4250
  │   Current version:    14337
  │   Minimum Version:    14337
  │   Vendor:             System manufacturer (DMI:American Megatrends Inc.)
  │   GUIDs:              3f0997ae-b4c6-583b-9af0-929bfe45f890
  │                       230c8b18-8d9b-53ec-838b-6cfc0383493a ← main-system-firmware
  │                       9371e0f5-7f8a-5b2f-8507-a4f87d5289f3 ← UEFI\RES_{3F0997AE-B4C6-583B-9AF0-929BFE45F890}
  │   Device Flags:       • Internal device
  │                       • Updatable
  │                       • System requires external power source
  │                       • Needs a reboot after installation
  │                       • Cryptographic hash verification is available
  │                       • Device is usable for the duration of the update
  │ 
  └─UEFI dbx:
        Device ID:        362301da643102b9f38477387e2193e57abaa590
        Summary:          UEFI Revocation Database
        Current version:  77
        Minimum Version:  77
        Vendor:           UEFI:Linux Foundation
        Install Duration: 1 second
        GUIDs:            fda6234b-adcb-5105-8515-9af647d29775 ← UEFI\CRT_D7F66BE77CEF858C174BF4338A99263C8795B74E02026411F5F532F716AE3263
                          f8ff0d50-c757-5dc3-951a-39d86e16f419 ← UEFI\CRT_D7F66BE77CEF858C174BF4338A99263C8795B74E02026411F5F532F716AE3263&ARCH_X64
                          c6682ade-b5ec-57c4-b687-676351208742 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503
                          f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
                          7d5759e5-9aa0-5f0c-abd6-7439bb11b9f6 ← UEFI\CRT_ED1FE72CB9CA31C9AF5B757AFCD733323D675825032E6CED7FE1AE9EB767998C
                          0c7691e1-b6f2-5d71-bc9c-aabee364c916 ← UEFI\CRT_ED1FE72CB9CA31C9AF5B757AFCD733323D675825032E6CED7FE1AE9EB767998C&ARCH_X64
        Device Flags:     • Internal device
                          • Updatable
                          • Needs a reboot after installation
      
Firmware metadata last refresh: 8 hours ago. Use --force to refresh again.

I am with you in believing it may be a graphics card issue and maybe I will try to load the proprietary amd drivers again. Look for a graphics card firmware update but could not find one

FYI- I went back to the latest 5.4.0.99 kernel

BeyondLies_MintForum · Wed Feb 16, 2022 10:45 am

Ah: 'proprietary amd drivers' - it could be these that 'taint' the kernel and perhaps are causing the problem. (I had managed to overlook the, 'Tried amd driver' in your first post.) What it is for a kernel to be tainted (I think) is simply for a driver to be running that is not within the kernel itself. External/tainting graphics drivers are known to cause problems on Linux or at least Nvidia ones are. Perhaps the external AMD driver is somehow installed already but not functioning properly.

Good luck.

AZgl1800 · Post by **AZgl1800** » Wed Feb 16, 2022 11:33 am

eastexas wrote: ⤴Wed Feb 16, 2022 10:28 am
When Posting Code, Please do the forum Readers a Favor, and always click on the "Code Brackets" just above the Editor. they look like this </>

That will keep the code inside a scrollable box, and is it MUCH more readable for us.

Code: Select all

inxi -Fxxxrz
System:
Kernel: 5.4.0-99-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0
Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: ASUSTeK model: Z170-DELUXE v: Rev 1.xx
serial: <filter> UEFI: American Megatrends v: 3801 date: 03/14/2018
Battery:
Device-1: hidpp_battery_0 model: Logitech G700s serial: <filter>
charge: 5% (should be ignored) rechargeable: yes status: Discharging
CPU:
Topology: Quad Core model: Intel Core i5-6600K bits: 64 type: MCP
arch: Skylake-S rev: 3 L2 cache: 6144 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 27999
Speed: 900 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2750 2: 3209
3: 3828 4: 2900
Graphics:
Device-1: AMD Tonga PRO [Radeon R9 285/380] vendor: Tul driver: amdgpu
v: kernel bus ID: 01:00.0 chip ID: 1002:6939
Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa resolution: 3840x2160~30Hz
OpenGL: renderer: AMD Radeon R9 380 Series (TONGA DRM 3.35.0
5.4.0-99-generic LLVM 12.0.0)
v: 4.6 Mesa 21.2.6 direct render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170
Device-2: AMD Tonga HDMI Audio [Radeon R9 285/380] vendor: Tul
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aad8
Sound Server: ALSA v: k5.4.0-99-generic
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k
port: f000 bus ID: 00:1f.6 chip ID: 8086:15b8
IF: enp0s31f6 state: down mac: <filter>
Device-2: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network
Adapter
vendor: ASUSTeK driver: wl v: kernel port: e000 bus ID: 07:00.0
chip ID: 14e4:43a0
IF: wlp7s0 state: dormant mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: 5.6.0-k port: b000 bus ID: 0b:00.0 chip ID: 8086:1539
IF: enp11s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 462.05 GiB used: 32.16 GiB (7.0%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 256GB
size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 1B0QBXX7
scheme: GPT
ID-2: /dev/sda vendor: Patriot model: Ignite size: 223.57 GiB
speed: 6.0 Gb/s serial: <filter> rev: 01.5 scheme: MBR
Partition:
ID-1: / size: 233.24 GiB used: 32.15 GiB (13.8%) fs: ext4
dev: /dev/nvme0n1p2
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A gpu: amdgpu temp: 63 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 949
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
Processes: 226 Uptime: 4h 32m Memory: 15.57 GiB used: 1.41 GiB (9.0%)
Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash
v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

eastexas · Post by **eastexas** » Wed Feb 16, 2022 4:45 pm

@beyond I had tried the AMD proprietary drivers but have since reinstalled the OS several times trying to ensure a clean install. So I am running LM 20.3 clean with all the updates from LM update manager. The problem has been there since installation and through updates. Maybe I need the proprietary drivers and when I tried to load them the last time I may have never implemented them properly. I will research that.

I want to believe this has something to do with the graphics card or that screensaver bug. Because the system is almost acting like the green screen might be a screensaver not loading or something. As the system is still running. But I could be way off base as I do not know anything when it comes to this stuff.

Thanks again for trying to help me. I'm going to keep on trying as I am happy about everything except not shutting down.

P.S. I will try to upload code properly from now on. Thanks for educating me

I

BeyondLies_MintForum · Wed Feb 16, 2022 5:04 pm

eastexas:

I am confident that the problem does indeed owe to the graphics card. For, the reports that I mentioned suggest that and also because of how, as you mention, the problem manifests itself.

I think it is indeed wise to start by trying to make sure the drivers are in order.

If that gets you nowhere, you could use the program 'Ukuu' (which, at least in its recent versions, is paid software) in order to install a newer kernel than Mint itself will let you install. (Or to save money there is a manual method of installation but I suspect that you should not go there, so to speak.)

A yet further option is to try a different Linux distribution but, since one of the aforementioned reports was for OpenSuse, so doing might not help.

And as a last resort you might change the graphics card - for one that is of a different series. (One could also go Nvidia but I do not recommend so doing.)

Also, some deep Internet searches, with multiple search engines, for '<your graphics card> Linux shutdown' might disclose something that I missed when I did some searches.

Linux Mint Forums

LM 20.3 shutdown hangs

LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs

Re: LM 20.3 shutdown hangs