SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When the current kernel was installed on 14.2 the intel_xhci_usb_role_switch and cqhci wasn't included in the mkinitrd command therefore the failure. They don't show up in the 14.2 installer, and didn't know about them until trying to figure out why current was also producing a kernel panic. Now that you know what modules are needed in the initrd.gz for a current kernel to boot, you have a good chance of getting 14.2 booting with a current kernel.
And there is no sound! How could I begin to solve this problem? Perhaps this should go in a new thread?
Again, as you didn't do a full Slackware installation, you are missing important packages. Don't waste people's time helping you to find out which ones. And please keep your questions in this thread as all your various issues have the same root causes:
Running a partial installation but not knowing how to handle it.
(Soon to come) running -current not knowing how to properly maintain it.
Last edited by Didier Spaier; 07-08-2020 at 10:50 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,152
Rep:
Quote:
Originally Posted by Didier Spaier
Again, as you didn't do a full Slackware installation, you are missing important packages. Don't waste people's time helping you to find out which ones. And please keep your questions in this thread as all your various issues have the same root causes:
Running a partial installation but not knowing how too handle it.
(Soon to come) running -current not knowing how to properly maintain it.
Hear, hear!
Well said!
As I said a month or so ago,
Quote:
Originally Posted by cwizardone
Over the years what I've seen, repeatedly, is someone asking a question about this or that problem, and it is only after several board members have made an attempt to help, that we eventually find out the person with the problem didn't do a full installation........
On the one hand, the problem has been solved. I entered youtube and there was the audio. Then I ran mplayer and there was sound too. Somehow the problem was magically solved.
On the other hand: I installed series a,ap,l,n,x,xap,xfce and y complete each of them. Do you want me to install the international series?
I am in a GUI terminal as regular user. I do 'su -' and type the password and I get the prompt followed by the password I just typed and this password executed as if it were a command. Followed by a certain amount of errors, as is natural.
Code:
root@darkstar:~# xh7tj&dji
[1] 4262
-su: xh7tj: command not found
-su: dji: command not found
[1]+ Exit 127 xh7tj
root@darkstar:~#
On the other hand: I installed series a,ap,l,n,x,xap,xfce and y complete each of them. Do you want me to install the international series?
The "international" series, kdei, is just for KDE applications. But you are missing the d/ series which will mean that you can't compile any software and are likely missing perl and python, both of which are used throughout the distro. And I don't think it is as easy as just installing the perl and python packages
Quote:
Originally Posted by stf92
I am in a GUI terminal as regular user. I do 'su -' and type the password and I get the prompt followed by the password I just typed and this password executed as if it were a command. Followed by a certain amount of errors, as is natural. How can this be explained?
There shouldn't be any errors when doing that. Without having the errors, it's impossible to know what's happening. Can you copy/paste the output?
I am in a GUI terminal as regular user. I do 'su -' and type the password and I get the prompt followed by the password I just typed and this password executed as if it were a command. Followed by a certain amount of errors, as is natural.
Code:
root@darkstar:~# xh7tj&dji
[1] 4262
-su: xh7tj: command not found
-su: dji: command not found
[1]+ Exit 127 xh7tj
root@darkstar:~#
How can this be explained?
Maybe you were already root? I've never not had su - prompt me for root's password unless I was already root (or I ran it using sudo).
Quote:
Originally Posted by stf92
@bassmadrigal: that about the international series was ironical.
You never mentioned on any other posts that you had installed the rest of the series (at least not that I noticed), so we were still under the impression you still on a very partial installation of Slackware.
It's simple. I was a regular user and did 'su -'. Then, as natural, su asked for root's password. I typed it, pressed Enter and got that weird output. And the system tried to execute the password! It was the system who output the password and then output <Enter> and "executed" it!
The op had mentioned that x was going to be used, hid amongst all the other post in this thread.
Stf92 slackware doesn’t auto create a user account, you have to do that after the install. The # in the console indicates your logged in as root, a user will have the $. I believe there is a sticky in Slackware forums on what needs to be done after installing Slackware
Last edited by colorpurple21859; 07-08-2020 at 12:13 PM.
I haven't been clear enough. The password you see after '#' was not typed by me. It was put there by the OS. When I typed the password I was a regular user. Of course I use useradd to create it.
My apologies. It was me who typed the password, not the system. What happens is that entering 'su -' gives me a root prompt without having to type the password. I was used to enter the password always after su - so I automatically typed the password and pressed enter. Still why does su - not asks me for the password?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
