Mx-23.2 boot failure

[DukeComposed]

someone else here may be better at explaining how chroot works. generally i believe it is usually used from a live environment.

chroot means "change root". It was developed by Bill Joy to help him install UNIX more easily. It simply tricks the shell into believing the designated directory is / and nothing exists above it. There are security benefits to chrooting some software, and it can, as was used in this thread, be used to configure a system inside of another system. The reason it's so useful in live sessions is because mounting a fixed drive under /media and then running "sudo chroot /media/something" allows you to add software, change passwords, add and remove users, and set up GRUB on it with the normal, everyday commands you'd normally use on a normal, everyday running machine, without any of it affecting your ephemeral session or the USB/DVD media.

The alternative would be manually editing /media/something/etc/passwd, /media/something/etc/group, temporarily redirecting apt-get default locations by setting a new RootDir in apt.conf, and so forth.

[xaol]

... the display manager can start before nvidia drivers are loaded. i have seen a few instances where adding the nvidia modules to ...

Yep, that's why we added them to /etc/modules on post #53

thank you for the clarification. i didn't know if those were the same.

[Charlie Brown]

... have to use the failsafe option for it to boot...

Ok. Normally one can use that (or nomodeset alone) and boot (just to be able to boot, till the job is done) then install and be able to use (boot) the installed system without that..

[Charlie Brown]

... didn't know if those were the same...

Though not exactly (and though we could add one more command for that) this one solves such issues. (This either makes sure / forces them to be loaded and also be loaded a bit earlier).

[james]

Charlie Brown: I just brought up Mx Service Manager - I do not see Plymouth.

[james]

DukeComposed: thank you for that explanation. You can be sure I am not going to be doing any of the stuff you described in that second paragraph. ;-)

[Charlie Brown]

Ok, we can even purge it, but this is less radical :) :

Code: Select all

sudo update-rc.d plymouth disable ; sudo update-rc.d plymouth-log disable

Reboot.

[james]

Charlie Brown: output of your suggested command. Rebooting now..

Code: Select all

$ sudo update-rc.d plymouth disable ; sudo update-rc.d plymouth-log disable
[sudo] password for james:            
insserv: warning: current start runlevel(s) (empty) of script `plymouth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 2 3 4 5 6) of script `plymouth' overrides LSB defaults (0 6).
insserv: warning: current start runlevel(s) (empty) of script `plymouth-log' overrides LSB defaults (S).
insserv: warning: current stop runlevel(s) (S) of script `plymouth-log' overrides LSB defaults (empty).
[~]

[Charlie Brown]

Ok, that's normal (just gives info) ... reboot :)

[james]

Rebooted. No change.