[SOLVED] MX Often Hanging at Boot on SysV...

[Huckleberry Finn]

disable the login screen from boot up, and only use it during logouts ?

I guess no. But you can try these just to see what happens, out of curiosity- maybe helps others in case one works-

First, you don't have to use the splash screen. You can uninstall Plymouth (as I did on mine :) ), or when it's booting, during splash, can hit Home (or Esc) and see the init actually, what's going on...

You'd tried Ctrl Alt F1 but this time:

Ctrl Alt F4 (or Alt F4) and enter command line.. login (user won't be permitted to use sudo, so when required only, root) type command there as you always do, update etc if internet is connected.. then exit with Ctrl Alt F7 or simply type logout and hit Enter..

or, During grub, say when 5.11 is selected, hit e and edit the Grub temporarily and change the line ... quiet splash to ... quiet nomodeset (splash may/may not stay).. and go on

or remove the /etc/X11/xorg.conf file (just to see what happens, or move to somewhere to put back later) and start ...

or, using the modprob command, reinstall the graphics firmware .. (just a rough idea)

Since it appears you'll go on using 4.9 (not old, but the best), nothing to lose and maybe finding the solution may help many people..

[Snake420]

I guess no. But you can try these just to see what happens, out of curiosity- maybe helps others in case one works-

First, you don't have to use the splash screen. You can uninstall Plymouth (as I did on mine :) ), or when it's booting, during splash, can hit Home (or Esc) and see the init actually, what's going on...

You'd tried Ctrl Alt F1 but this time:

Ctrl Alt F4 (or Alt F4) and enter command line.. login (user won't be permitted to use sudo, so when required only, root) type command there as you always do, update etc if internet is connected.. then exit with Ctrl Alt F7 or simply type logout and hit Enter..

or, During grub, say when 5.11 is selected, hit e and edit the Grub temporarily and change the line ... quiet splash to ... quiet nomodeset (splash may/may not stay).. and go on

or remove the /etc/X11/xorg.conf file (just to see what happens, or move to somewhere to put back later) and start ...

or, using the modprob command, reinstall the graphics firmware .. (just a rough idea)

Since it appears you'll go on using 4.9 (not old, but the best), nothing to lose and maybe finding the solution may help many people..

To remove the boot splash, I just went to /etc/default/grub and adjusted...

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to say...

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT=""

then did a sudo update-grub in terminal, and rebooted.

I rebooted a few times just to see if there would be any hangups at boot, but there were none, but there aren't any with the boot splash either, so far, with kernel 4.9.182 on my Dell laptop, which is a relief. I figured that it just had to be something simple...go figure.

I'll continue testing for a couple days and see what happens.

As far as the boot splash, preferably I would rather keep it, since I custom made it, as I'm just one of those guys that like things aesthetically pleasing. I know, I know...what are ya gonna do ? Plus, My Wife wouldn't like the text going by on boot up, making her all nervous that something's wrong. Just better to hide it, for our household. haha

Thanks for all your help Huckleberry !

I'll swing back by here in a couple days, if I can keep myself away, and post an update.
If all is well, at that point, I'll likely dive into splitting up my current MX partition, clean it up real nice, and install another copy of MX on the new partition and copy my home folder to it...play around a bit, and if all goes well at least I'll have a backup if anything in the future goes wrong. As a bonus, I can also use that partition to upgrade to MX19, once it rolls out this Fall.

TTYS...Snake.

[Huckleberry Finn]

Ok. I mean, the problem is not the splash, go on with it.. just i.e. whenever you'd like to see the text under the curtain, hit Home or esc .

And, the options to try, I mean "whenever you face that blank screen with a blinking cursor on top left.." (tty4)

Also the one with "nomodeset".. I mean just to add/insert the word nomodeset among them (could be "... ro quiet nomodeset splash ...." , as well)

Shortly: the culprit is not the splash or Plymouth :)

By the way; as you might already know, 19.0 will require a fresh install since it will be based on Debian 10 Buster, (now 9 Stretch; different bases...)

You can also remove unnecessary kernels and save many space. Say, only the original 4.19.0.5 (just to try things) and 4.9 . After you finish the experiment, can leave only 4.9 (to boot directly...)

As the last two things: Should a problem occurs again, you can also install the other 4.9 ones named "Debian" - you'll see in the Package Installer- ( 4.9 is an LTS one which is trusted most and used by Debian, too). In addition, newest kernels are not a "must" for many computers which are not very new..

And, after shrinking sda5 with Gparted and creating new small partitions, remember that they'll have new names as sd6 etc... So, before dd zero, just be sure which is which.. (Can also right-click and "Label" them all to recognize later easily).. ( no need to say "all, on live-session") .. and anytime before such an operation:

Code: Select all

sudo lsblk -f

See you :)

[Snake420]

And, the options to try, I mean "whenever you face that blank screen with a blinking cursor on top left.." (tty4)

Thank you. That's a good tip to know. I caught that earlier in one of your responses and good advice.

Also the one with "nomodeset".. I mean just to add/insert the word nomodeset among them (could be "... ro quiet nomodeset splash ...." , as well)

I tried the "nomodest" at grub earlier, and it did remove the splash, using text instead, but when it loaded up my desktop after the boot up, the resolution of the desktop had changed and it was all stretched out, including the panel and dock, etc., so I nixed that idea for my computer. I appreciate the idea though. It just didn't work in my case, at least in whole.

The rest I understand and know how to do as far as using GParted, selecting correct partitions, uninstalling kernels, etc., and now I know, thanks to you, how too dd zero my chosen partition, when I need to.

Thanks Huckleberry !
It's good to have a great forum to go to to get fantastic, helpful and very fast advice and responses.
I greatly appreciate all of you here.

[Snake420]

So it seems my problem with this has been SOLVED !

Getting rid of the 4.19.0-5 kernel, and replacing it with the 4.9.182 kernel has removed the issue, as I no longer see it or am experiencing this problem I had before I came here.
Whatever the issue may have been, whether it was partly a compatibility issue with Dell computers to the kernel, or just certain kernel bugs for some cases, the problem seems to be no more.

Hopefully, this fix will help a lot of unanswered questions that we have seen in many other forums, so that whoever still has this issue can resolve it.

Thank you to everyone that has helped out here, especially to Huckleberry. Great forum !

[Huckleberry Finn]

You're welcome

(Now I'll go to that unanswered topic, though it's asked last year and link here for reference)