Page 1 of 1
Screen suddenly went blank
Posted: Sun Feb 02, 2025 3:48 pm
by iridesce
Hi all,
Thanks for taking time to puzzle this out.
Normally I'm running MX-23.5_KDE_x64 on the below laptop
This afternoon after a Zoom session and then picking up the laptop, my screen went blank. No amount of playing with the touchpad, power button, etc would bring the screen back.
Rebooted, saw the Lenovo boot screen, GRUB menu, the MX animated logo then nothing. So, fantastically relieved my hardware wasn't borked.
Tried booting into the MX-23.5 Advanced option in GRUB menu, got the same results.
Very fortunately I had MX-21.3_KDE_x64 on another partition and booted into that, display was fine without any problems and so I'm able to send this query.
I would appreciate any ideas about how to bring the display back on the 23.5 partition as I'm out of the country and need to remote into my main work desktop from the 23.5 partition.
Appreciate any suggestions
Code: Select all
System: Kernel: 5.10.0-30-amd64 [5.10.218-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-30-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.3_KDE_x64 Wildflower September 18 2022
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: LENOVO product: 20HES26N00 v: ThinkPad T470 serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20HES26N00 v: SDK0J40697 WIN serial: <filter> UEFI-[Legacy]: LENOVO
v: N1QET71W (1.46 ) date: 01/24/2018
Battery: ID-1: BAT0 charge: 5.2 Wh (26.7%) condition: 19.5/24.0 Wh (81.4%) volts: 10.6 min: 11.5
model: SMP 01AV421 type: Li-poly serial: <filter> status: Discharging cycles: 131
ID-2: BAT1 charge: 19.1 Wh (100.0%) condition: 19.1/24.1 Wh (79.6%) volts: 12.7
min: 11.4 model: Celxpert 01AV424 type: Li-poly serial: <filter> status: Full
cycles: 118
CPU: Info: Dual Core model: Intel Core i7-7600U bits: 64 type: MT MCP arch: Amber/Kaby Lake
note: check family: 6 model-id: 8E (142) stepping: 9 microcode: F4 cache: L2: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23199
Speed: 806 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 806 2: 803 3: 801 4: 813
Vulnerabilities: Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics: Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:5916 class-ID: 0300
Device-2: Acer Integrated IR Camera type: USB driver: uvcvideo bus-ID: 1-5:2
chip-ID: 5986:111d class-ID: 0e02 serial: <filter>
Device-3: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:4
chip-ID: 5986:111c class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3")
s-diag: 484mm (19.1")
Monitor-1: eDP-1 res: 1600x900 dpi: 132 size: 309x173mm (12.2x6.8") diag: 354mm (13.9")
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.0.5
direct render: Yes
Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-30-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: efa0
bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl port: efa0
bus-ID: 04:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
bus-ID: 1-7:3 chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: slave accept service-classes: rendering, capturing, object transfer, audio
Drives: Local Storage: total: 238.47 GiB used: 34.98 GiB (14.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN530 SDBPNPZ-256G-1006 size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: HPS2
temp: 31.9 C scheme: MBR
Partition: ID-1: / raw-size: 40.04 GiB size: 39.11 GiB (97.69%) used: 34.98 GiB (89.4%) fs: ext4
dev: /dev/nvme0n1p5 maj-min: 259:4
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.79 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p7 maj-min: 259:6
Sensors: System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos: Packages: note: see --pkg apt: 2479 lib: 1336 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye main non-free
2: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com//deb/nordvpn/debian stable main
Info: Processes: 208 Uptime: 17m wakeups: 3 Memory: 15.15 GiB used: 2 GiB (13.2%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 4:58 pm
by j2mcgreg
If you get a cursor in the otherwise blank screen run:
and post the result here encased in code tags.
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 5:09 pm
by j2mcgreg
A possibility that can cause a black screen is that your / or /home is >= 90% full. If you used the same size for your MX 23.5 partition as you did MX 21, it doesn't take a lot to fill that space quickly.
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 6:43 pm
by iridesce
Thanks for your reply
Code: Select all
System:
Kernel: 5.10.0-30-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-30-amd64
root=UUID=89e1eeff-6a0d-4233-bf00-7b2c44b88c01 ro quiet splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.3_KDE_x64 Wildflower September 18 2022
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Laptop System: LENOVO product: 20HES26N00 v: ThinkPad T470
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20HES26N00 v: SDK0J40697 WIN serial: <filter>
UEFI-[Legacy]: LENOVO v: N1QET71W (1.46 ) date: 01/24/2018
Battery:
ID-1: BAT0 charge: 19.4 Wh (98.0%) condition: 19.8/24.0 Wh (82.6%)
volts: 12.1 min: 11.5 model: SMP 01AV421 type: Li-poly
serial: <filter> status: Discharging cycles: 132
ID-2: BAT1 charge: 19.1 Wh (100.0%) condition: 19.1/24.1 Wh (79.4%)
volts: 12.7 min: 11.4 model: Celxpert 01AV424 type: Li-poly
serial: <filter> status: Full cycles: 118
CPU:
Info: Dual Core model: Intel Core i7-7600U bits: 64 type: MT MCP
arch: Amber/Kaby Lake note: check family: 6 model-id: 8E (142)
stepping: 9 microcode: F4 cache: L2: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 23199
Speed: 2554 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 2554
2: 1965 3: 1783 4: 1708
Vulnerabilities: Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes,
SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP:
conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
Device-2: Acer Integrated IR Camera type: USB driver: uvcvideo
bus-ID: 1-5:2 chip-ID: 5986:111d class-ID: 0e02 serial: <filter>
Device-3: Acer Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-8:4 chip-ID: 5986:111c class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver:
loaded: modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3")
s-diag: 484mm (19.1")
Monitor-1: eDP-1 res: 1600x900 dpi: 132 size: 309x173mm (12.2x6.8")
diag: 354mm (13.9")
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2)
v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
chip-ID: 8086:9d71 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-30-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network:
Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e
v: kernel port: efa0 bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
modules: wl port: efa0 bus-ID: 04:00.0 chip-ID: 8086:24fd
class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
v: 0.8 bus-ID: 1-7:3 chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
bt-v: 2.1 lmp-v: 4.2 sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: slave accept
service-classes: rendering, capturing, object transfer, audio
Drives:
Local Storage: total: 238.47 GiB used: 175.94 GiB (73.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN530 SDBPNPZ-256G-1006 size: 238.47 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: HPS2 temp: 29.9 C scheme: MBR
Partition:
ID-1: / raw-size: 40.04 GiB size: 39.11 GiB (97.69%)
used: 35.14 GiB (89.8%) fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.79 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p7 maj-min: 259:6
Sensors:
System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos:
Packages: note: see --pkg apt: 2479 lib: 1336 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye main non-free
2: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com//deb/nordvpn/debian stable main
Info:
Processes: 220 Uptime: 3h 59m wakeups: 3 Memory: 15.15 GiB
used: 2.18 GiB (14.4%) Init: SysVinit v: 2.96 runlevel: 5 default: 5
tool: systemctl Compilers: gcc: N/A alt: 10 Shell: Bash v: 5.1.4
running-in: konsole inxi: 3.3.06
Edit: To reiterate, I am currently using the MX-21.3_KDE_x64 partition to write this
Currently 17.8GiB free of 95.6GiB ( 81% used ) on the MX-23.5_KDE_x64 partition
Thanks for your assistance
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 7:10 pm
by j2mcgreg
That's all well and good but it doesn't do anything to help us diagnose your problem MX 23.5 partition. Did you try running the command I gave you in post #2?
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 9:05 pm
by iridesce
j2mcgreg wrote: Sun Feb 02, 2025 4:58 pm
If you get a cursor in the otherwise blank screen run:
and post the result here encased in code tags.
Thank you for your reply. I apologize if I was not clear in my original post
Attempting to boot the MX-23.5 partition from GRUB, after the animated MXLinux logo that typically precedes the user login, all I get is a blank screen.
No cursor, nothing but a blank screen.
I supplied the inxi -Fxxrza code in the MX-21.3_KDE_x64 as that is the only partition that would boot into a desktop. Again apologies if I didn't make that clear.
After having booted successfully into the MX-21.3 partition and looking at the MX-23.5 device in Dolphin, right clicking on a folder Properties, it shows 17.8GiB free of 95.6GiB ( 81% used )
I do appreciate your assistance.
If I am still not able to supply information that makes sense to you, please advise.
p.s. your avatar looks like my cat
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 9:46 pm
by timkb4cq
Use the file manager to look at your MX-23.5 partition. Navigate to /var/log/boot.log
Right click -> Edit as root. Paste that text into a reply, and using Full Editor & Preview highlight it and apply the code tags ( the </> icon ). That may tell us what's not working. If that doesn't have enough info, the next two files from /var/log that might are dmesg & kern.log
Those are large enough that if they are needed they may need to be zipped up & attached instead of pasted.
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 9:56 pm
by iridesce
Thanks Tim
Code: Select all
------------ Sun Feb 02 13:33:52 CST 2025 ------------
rootMX23: recovering journal
rootMX23: clean, 495694/6406144 files, 19640483/25599744 blocks
INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Sun Feb 02 13:35:23 CST 2025 ------------
rootMX23: clean, 495681/6406144 files, 19640548/25599744 blocks
INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Sun Feb 02 18:46:20 CST 2025 ------------
rootMX23: clean, 495683/6406144 files, 19640627/25599744 blocks
INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 10:06 pm
by timkb4cq
Well, that's a perfectly normal boot.log
Time to try var/log/dmesg
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 10:18 pm
by iridesce
Apologies about how long it took to compress the files, here they are
Thanks for your help
Re: Screen suddenly went blank
Posted: Sun Feb 02, 2025 10:19 pm
by iridesce
The title should be kern.log.zip
Edit: The file name should be kern.log.zip
Re: Screen suddenly went blank [Solved]
Posted: Sun Feb 02, 2025 10:38 pm
by 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.
Re: Screen suddenly went blank
Posted: Mon Feb 03, 2025 4:00 am
by 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.
Re: Screen suddenly went blank
Posted: Mon Feb 03, 2025 6:53 am
by j2mcgreg
Eadwine Rose wrote: Mon Feb 03, 2025 4:00 am
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.
Re: Screen suddenly went blank
Posted: Mon Feb 03, 2025 7:50 pm
by 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
Re: Screen suddenly went blank
Posted: Mon Feb 03, 2025 8:00 pm
by 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
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.
Re: Screen suddenly went blank
Posted: Tue Feb 04, 2025 10:35 pm
by 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
