LinuxQuestions.org - In plasma from -current ALT + CTL + F2 gives a blank screen. This is -current-live related.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - In plasma from -current ALT + CTL + F2 gives a blank screen. This is -current-live related. (https://www.linuxquestions.org/questions/slackware-14/in-plasma-from-current-alt-ctl-f2-gives-a-blank-screen-this-is-current-live-related-4175689301/)

jkh2cpu

01-26-2021 12:12 PM

In plasma from -current ALT + CTL + F2 gives a blank screen. This is -current-live related.

I had to use slackware64-current-live to restore a kernel to my bricked machine, and -current-live seemed to change my /etc/inittab run-level to 4. I fixed that, but I have a new problem. When I boot I get the same screen that I've seen for over 20 years. It takes my login and puts my in my home directory. Startx starts Plasma.

When KDE/Plasma is running, and I want to switch to a terminal using ALT + CTL + F2, I now get a blank screen. I get back to Plasma with ALT+CTL+F1.

When I exit Plasma and return to a terminal, I get the same blank screen as noted above. I can start Plasma by typing startx.

Where might I look to try to sort this out.

John.

Alien Bob

01-26-2021 12:23 PM

You seem to have installed the actual Slackware Live instead of merely fixing your kernel. Nothing you do to install a kernel or use any of the Slackware package tools touches /etc/inittab except when you upgrade/reinstall Slackware's 'sysvinit-scripts' package.
And Slackware's default runlevel is 3.

On the other hand if you used the 'setup2hd' tool of Slackware Live, then that actually sets the default runlevel to 4. Which it dies after installing the full content of the Live ISO to your hard disk.

jkh2cpu

01-26-2021 12:52 PM

I tried numerous things before I could boot into UEIF. Who knows what might have happened.

My problems stem from the age of the slackware64 installer and the newness of some new equipment. It will be sorted with the new slackware64-15.

John.

enorbet

01-26-2021 06:41 PM

Slackware Live can be used as a repair disk but the best way I've found is download whatever package you need and then to "Ctrl-Alt-F1" from the login screen and do a chroot to the system you wish to fix, where you can "upgradepkg --install-new".

In Slackware Live I just

Code:

 

mkdir /mnt/LOOP

mount /dev/sdfoo /mnt/LOOP



and if needed



mount /dev/sdfoo2 /mnt/LOOP/boot

mount /dev/sdfoo3 /mnt/LOOP/boot/efi



then 



mount -o bind /dev /mnt/LOOP/dev

mount -o bind /proc /mnt/LOOP/proc

mount -o bind /sys /mnt/LOOP/sys



and



chroot /mnt/LOOP /bin/bash

and you're in!

I don't find any problems with the "age" of the installer. It's excellent and customizable. My newest gear isn't the very newest as of today but just a few weeks ago a Z490 system with an i5-10600K was bleeding edge. It runs just fine with both 14.2 and Current.

As for your specific question to sort out what's going on with plasma login/logout, exactly what did you do from Slackware Live to "fix" your hard install?

All times are GMT -5. The time now is 10:51 AM.