LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-26-2021, 12:12 PM   #1
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 282

Rep: Reputation: 60
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.
 
Old 01-26-2021, 12:23 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
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.
 
Old 01-26-2021, 12:52 PM   #3
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 282

Original Poster
Rep: Reputation: 60
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.
 
Old 01-26-2021, 06:41 PM   #4
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,787

Rep: Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435Reputation: 4435
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?

Last edited by enorbet; 01-26-2021 at 06:44 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
flickering of screen while returning back to GUI mode from Text mode using Ctl+Alt+F7 varun_shrivastava Linux - Newbie 1 03-30-2007 10:12 AM
Does Ctl-Alt-F1 kill X, or just put in background? TreeDragon60 Linux - General 18 03-31-2004 02:17 AM
ctl-alt-del equivalent in linux? pekuekfir Linux - General 14 09-20-2003 12:14 PM
ctl-alt-f8 thru f10 give nothing desolat Mandriva 2 09-17-2003 07:28 PM
CTL+ALT+DEL logoff screen gone ScreeminChikin Linux - General 2 09-19-2002 04:16 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration