Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
I was very pleased to read Pat's announcement about the most recent distribution being finally slackware 15! However: I followed the upgrade directions and got a kernel panic when I rebooted. Hmm. Okay, I was able to save some crucial files and did a clean installation which boots, but only from the thumb drive that I made during installation. The real issue(s) that I'm having is about permissions. It looks like root owns everything! I have, by trial and error, changed ownership and group on a bunch of files and I have got the system to a more or less usable condition. The remaining problem is that I can't get sound to work. I think pulse audio is in charge now and I can't get it to work.
I know that this sounds like I'm a newbe but I have used Slackware for a long time and I have never run into anything like this.
Any help would be appreciated.
Jwc
What are the permissions on your home directory? And .config? Pulseaudio writes to .config/pulse and if those directories are owned by root it won't be able to write to them and it will fail. Other programs would fail too though.
Also, try:
Quote:
pulseaudio -v
and see if it says anything about permissions.
You can keep adding '-v's to increase the verbosity
Thanks, I changed a few more permissions and I got at least one on-line program to produce sound. Onward and upward! However I would like to know if anyone else is having permission issues with this software.
At this point you're probably best off wiping it and doing a clean install. IMO, there have been too many "structural" changes between 14.2 and 15.0 to make upgrading a viable option.
After I tried the upgrade process and got a kernel panic on booting I have done a clean install. What I have now is a system that looks like it is meant to be run by 'root'. I'm in the process of making it more usable now.
What I have now is a system that looks like it is meant to be run by 'root'. I'm in the process of making it more usable now.
Please explain what you mean by this?
The Slackware installer doesn't ask you to create users. That's up to you:
Quote:
Originally Posted by The Slackware-HOWTO [on the installation disc]
6.4 User Accounts
You should make a user account for yourself. Using "root" as your
everyday account is dangerous, and is considered bad form (at the very
least) since you can accidentally damage your system if you mistype a
command. If you're logged in as a normal user, the effects of bad
commands will be much more limited. Normally you'll only log in as root
to perform system administration tasks, such as setting or changing the
root password, installing, configuring, or removing system software, and
creating or deleting user accounts.
To make an account for yourself, use the 'adduser' program. To start it,
type 'adduser' at a prompt and follow the instructions. Going with the
default selections for user ID, group ID, and shell should be just fine
for most users. You'll want to add your user to the cdrom, audio, video
plugdev (plugable devices like USB cameras and flash memory), scanner, and
lp groups if you have a computer with multimedia peripherals and want to
be able to access these. Add these group names at the following prompt:
Additional groups (comma separated) []:
To add the user to all the recommended user groups automatically, hit the
up arrow at this prompt to fill them in, and then hit enter.
It's been a loooong time since I posted here, but Slackware 15 is out, and I want to share some of my experiences (and hassles). I had no problems with the installation per se, but I have a heavily modified system, I leave out a lot of packages, and compile a lot of my own. Most of the packages I run on 14.2 will compile on 15.0, but there are a few that will not, and I won't be able to cut over from 14.2 until they are resolved. I at present have 15.0 installed on a Lenovo Thinkpad, Kaby Lake generation. I'm running my own compiled kernel-5.15.19.
The following packages will compile on 15.0, some need a little arm twisting: apulse, avidemux, faad2, file-roller, geany, jack2, jack-rack, kdiff3, ladspa_sdk, lame, libass, libdvdcss, libisofs, liblo, mjpegtools, mplayer, mpv, qjackctl, smplayer, swh-plugins, sylpheed, timemachine, viewnior, xsane, and zvbi.
I have been unable to compile the following: caps_0.9.7 (a ladspa plugin suite for guitar), dvdbackup-0.4.2 (makes backups of dvd's), qpdfview-0.4.18 (pdf viewer), xfburn-0.5.5 (dvd burner from XFCE), and xforms-1.2.4 (a form builder). Mostly errors about .la files not being found in /usr/lib64.
And then wine. I need the multilib version to run Windows 98 era apps. I'm presently running wine-4.0 on my 14.2 system, but it will not compile on 15.0, wine-7.0 will compile, but one of my apps won't run, wine 6.0 will compile and run all my apps, but the startup is very slow due to not finding rpcss. But I can take the wine-4.0 package that I compiled on 14.2, and it runs fine on 15.0, it's quick and everything works, just not a good long-term solution.
The login is a hassle cause I get the long timeout, something not configured right and I haven't figured out what yet. Also, the desktop icon doesn't come up when I mount a USB stick, I can issue the mount command manually but it's a hassle. Polkit/udev/udisks tangle, probably, somewhere.
All in all it works pretty well, but I need to get the remaining issues resolved before I cut over for good.
It's a self-contained binary, which has all of the required libraries built in. You can use this on a Slackware64 system without multi-lib and it will allow you to run 32 bit Windows apps and games with wine. I see no difference in performance running (for example) Warcraft III with this rather than a version of wine I compiled myself... but that's on a 9th Gen i5. If your computer is older, you may not get the same result but it's probably still worth trying. It'll save you from having to use multi-lib and all of the headaches that brings, as well as compiling wine yourself, which can take ages on it's own.
The login is a hassle cause I get the long timeout, something not configured right and I haven't figured out what yet. Also, the desktop icon doesn't come up when I mount a USB stick, I can issue the mount command manually but it's a hassle. Polkit/udev/udisks tangle, probably, somewhere.
Have also had long timeout issue specifically with the 5.15.19 kernel in Slackware64 v15.0 , whereas the same just isn't true with the up-to-date 4.4.301 kernel in v14.2.
Was consistently getting some init random message during timeout when kernel loading on bootup that's apparently tied to the machine's BIOS version
Nope, not updating BIOS since still ZERO hangs on Slackware64 v14.2 or on amd64 distros based on Debian "bullseye" v11.x (kernels < 5.15.19)
.
.
.
Last edited by nycace36; 02-11-2022 at 03:25 PM.
Reason: current Debian stable version
Have also had long timeout issue specifically with the 5.15.19 kernel in Slackware64 v15.0 , whereas the same just isn't true with the up-to-date 4.4.301 kernel in v14.2.
Was consistently getting some init random message during timeout when kernel loading on bootup that's apparently tied to the machine's BIOS version
Nope, not updating BIOS since still ZERO hangs on Slackware64 v14.2 or on amd64 distros based on Debian "bullseye" v11.x (kernels < 5.15.19)
.
.
.
It's not a kernel issue, I'm running 5.15.19 on Slackware 14.2 and no issues there. Something with elogind, maybe? A new thing I'm not familiar with.
I also get the "random: udevd: uninitialized urandom read" message a few times at bootup, doesn't seem to cause any problems.
It's been nearly a year since I first posted about slackware15. I have been using it since then; some things work ok and others not. Like everyone else, I've had trouble getting chrome to work. The Slackbuild crashes and, while others have been able to work it out, I have not. Also some other strange things have happened, e. g., I downloaded slack15 from alien bob's site and installed it. Later, having no fun with firefox at all, I downloaded chromium from his site. It downloaded and is installed but it won't run; no error message, it just doesn't run. I've been using slackware since it's early days but I don't recall having this much trouble in the past. Any ideas?
JWC
What's slack15 ? Do you mean an iso image ?
A link or name of the file would be useful.
Same for Chrome / Chromium / de-googled Chromium.
You'd better post a link. Isn't there a Chrome SlackBuild in extra ? Is that failing ? If yes, where ?
I downloaded and installed the slackware15 iso file from alien bob's web site. As far as I know that is the same iso file as found elsewhere. The chrome slackbuild has a glitch in it. There is a message someplace about how to deal with it but I couldn't find it when I tried to install chrome, so I have reluctantly been using firefox.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.