Gents:
Things have more or less been "OK" in Siduction since my last post, but now a couple of problems have cropped up in "Bulls eye" . . . one doesn't seem to be problematic beyond taking time, but this morning I tried to log into Siduction and the GUI failed to load . . . it stops at the TTY prompt.
I logged into the tty and I ran "apt update && apt upgrade" and it installed a few packages, 27? and a new kernel; I rebooted and selected Siduction from Grub and we scrolled through the dmesg, which first shows an error of "mdadm: no arrays found in config or ?? automatically??" which then it announces that it is "tired" of running that error and drops into the regular dmesg list.
A couple weeks ago I ran some code that I found in a Debian forum showing how to repair this "mdadm" error, but it didn't seem to fix it. Today on the second boot attempt for Siduction it showed two "Failed" errors for "Failed to start Load Kernel Modules" and then a bit down it showed another one, "Failed to start Nvidia Persistent xxxxx" . . . and then a bit later it showed a "Dependency" error . . . of course all of these things are moving fast up until it loads the log in prompt for the tty.
The system has the Nvidia repos and in running the update/upgrade no errors showed up . . . any thoughts or prayers on this one?? It does seema bit "labor intensive" to keep Siduction in tidy order; I have a rolling Gecko install that tells me the "gpg keys are very wrong" for the install as I believe I didn't update it for a month a few weeks back, but it still boots up and gets me into a GUI . . . . Siduction seems to be "blocking" me from doing that, can't log into the GUI environment, only command line.
e.e.p.PS: 3 "return" key strokes were provided between each paragraph, for those who care about spacing & formatting of posts, etc.