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.
The selected soundcard gives out nothing. There's one sound setup in this elderly laptop. I can go into alsamixer, select the second option, unmute & set volumes (again), & restart all sound and it often works until the next startup.
Can I get around it by correcting some currently unknown config file, or putting something like
/etc/rc.d/rc.alsa and /etc/rc.d/rc.pulseaudio should not be executable.
Forget alsa utilities. Run pavucontrol. On the top menu, click "Output Devices'. There is "Built-in Audio Analog Stereo" or similar and a speaker icon. Is the speaker icon on a grey background (muted)? Click to unmute and you get a blue volume slider below. Do you get any sound now? Is the "Port" correct?
The pulseaudio settings are saved in $HOME/.config/pulse.
Pulseaudio wasn't executable, fixed rc.alsa, went through pavucontrol. Things looked slightly better. Chromium-ungoogled worked with brave 'bravely chickening out' to quote Sir Robin's Minstrel (referencing "Monty Python & the Holy Grail")
Just ignore that if you're not into Monty Python.
So you fixed chromium-ungoogled for me, and I'm thanking you for the solution & marking this solved.
No output devices - like I've no sound card fitted. 15.0 is OK, this is just on Current. But it's a 10 year old laptop, with a cheap intel cpu & chipset, so what can one hope for? At least it's faster than it was new, because I upgraded the spinning rust to an ssd.
I thought turning off rc.pulseaudio would turn off audio, but it didn't... what's the reason to actually have rc.pulseaudio disabled? I think I also have some old programs that use ALSA and maybe even OSS like someone explained above is needed for soundcard configuration/volume.
what's the reason to actually have rc.pulseaudio disabled?
From /etc/rc.d/rc.pulseaudio:
Code:
# Please note: this is not generally the best way to use PulseAudio!
# Normally pulseaudio will start automatically as-needed with an instance
# per audio user. Unless you really need to use system mode you should leave
# this script non-executable.
Quote:
Originally Posted by dchmelik
I think I also have some old programs that use ALSA and maybe even OSS like someone explained above is needed for soundcard configuration/volume.
By default, in Slackware /etc/asound.conf redirects ALSA to PulseAudio. alsamixer only sees 'Card: PulseAudio'. If your old program only uses OSS, you might want to try aoss which redirects OSS to ALSA (which gets redirected to PulseAudio). You should not enable /etc/rc.d/rc.alsa-oss because the real OSS blocks the sound device from other sound users. From that file:
Code:
# Load the ALSA OSS kernel modules to support OSS applications.
# To use this, set this script as executable (chmod 755 rc.alsa-oss)
# and it will be run from the main rc.alsa script. Unless you know
# that something requires OSS support, it is better to leave this
# script disabled. Some applications will try OSS first even though
# they also support ALSA, and will block other applications from
# using audio I/O.
#
# Many programs that use OSS can be run using the aoss wrapper and
# will then use ALSA in a non-blocking way (and will not require
# loading these kernel modules). Consider trying that before enabling
# these modules. (See "man aoss")
My soundcard is seen 1½ times in alsamixer. The ½ is selected bu default, and the '1' is muted. I have to deselect the '½' and select the (muted) '1' and unmute it. When I finish, neither pulse nor alsa is running.
After I turned off the rc scripts, seems I no longer can get input for my Creative Labs Sound Blaster Audigy 2 ZS platinum front panel microphone socket.
After I turned off the rc scripts, seems I no longer can get input for my Creative Labs Sound Blaster Audigy 2 ZS platinum front panel microphone socket.
If you run 'pavucontrol', do you see it under the menu item 'Input Devices' after you insert the microfone plug in the socket? Try to click 'Port:' to see what ports are available.
Last edited by Petri Kaukasoina; 01-20-2024 at 03:38 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.