Screen suddenly went blank [Solved]

[iridesce]

The title should be kern.log.zip

Edit: The file name should be kern.log.zip

[timkb4cq]

I'm not seeing anything obvious in these logs. But I do see that you are using the 6.1.0-30 kernel. That's a recent automatic upgrade. Have you tried, when in the Grub screen, using the Advanced options for MX-23.5 and selecting the previous kernel? We have occasionally found cases where a kernel upgrade causes issues with one or another device driver, including video drivers.

[Eadwine Rose]

Shouldn't change back to the 29 kernel, that one was one that gave issues with.. I believe it was the snapshot. Maybe that has been fixed now, but.. don't know.

28 is ok.

[j2mcgreg]

Shouldn't change back to the 29 kernel, that one was one that gave issues with.. I believe it was the snapshot. Maybe that has been fixed now, but.. don't know.

28 is ok.

I think that at this point any kernel that gets the OP to the desktop would be preferred.

[iridesce]

Thanks all for your suggestions. Coming to you from 23.5 now

I came up with a work around that I should have seen from the beginning.

Booting into GRUB and selecting Advanced, there is no option for the 29 kernel, only 30 and 28. Tried to boot into 28 and no joy, same result as above.

However when I tried the systemd option for 30 and in 28, I was able to get to the user login and to my desktop

Of note: When selecting Shut Down from both the user login screen and from the desktop after booting from the systemd option above, the process hangs after the animated MXlinux logo. The only way to shutdown is to hold the power button down for 5 seconds ( I don't know/remember what the term for this type of shutdown is, hard shutdown? )

Once again, I am in awe and have huge respect for you folks. That developers would take time to help a long time noob is hugely appreciated and humbling.

Thanks again for leading me back to functionality once again

[iridesce]

Also, fyi, though you probably already know this ...

After getting to the desktop using the above systemd approach, when I tried to access my vpn, Nordvpn though the command line

Code: Select all

nordvpn connect

I received the below error

Code: Select all

 /run/nordvpn/nordvpnd.sock not found.
The NordVPN background service isn't running. Execute the "systemctl enable --now nordvpnd" command with root privileges to start the background service. If you're using NordVPN in an environment without systemd (a container, for example), use the "/etc/init.d/nordvpn start" command.

Executing

Code: Select all

sudo systemctl enable --now nordvpnd

did the trick and I am running through the vpn now.

[iridesce]

So ... when I booted with the systemd 30 option, I found that I lost sound. The mixer levels showed activity and there was no sound coming from the speakers ... all the audio setting were correct

Updates - Discover showed updates and so did that process. What I remember were ffmpeg updates. I Shut Down and it hung at the MXLinux logo again.

The next morning I turned the laptop on and then got distracted with making breakfast. When I came back I saw the login screen and logged in. Then realized I hadn't selected the Advanced option to boot the systemd 30 option ....

At that point I checked an audio file and heard sound from the speaker ... when I Shut Down, it shut down as it normally does.

I rebooted without playing in GRUB and it booted fine into the login screen and then into the desktop.

Gremlins and angels at work evidently. Just thought I'd add this

Thanks again for all your ideas and support - you folks rock