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.
Could you please wrap all future output in CODE tags, please? It will be easier to read for everyone. You can actually edit your previous posts as well to help people who come to this thread in the future.
Do you have any aliases set up by alsaconf? They would be under /etc/modprobe.d/. I think it will be called sound. Let us know what files are in the directory, and cat any that are relevant.
Edit /etc/rc.d/rc.modules-$(uname -r)
Under ### Network device support ###
add
Code:
/sbin/modprobe forcedeth
Under ### ALSA (Advanced Linux Sound Architecture) support:
add
Code:
/sbin/modprobe snd_hda_intel
When you boot the next time look carefully for any error messages that fly by while these modules are being loaded.
There are no files in /etc/modprobe.d/ It is empty.
...that's not good. There should at least be a /etc/modprobe.d/blacklist file (and usually a /etc/modprobe.d/isapnp file as well). In 12.1, there should also be a /etc/modprobe.d/psmouse file too. You may wish to reinstall the udev-118-i486-3.tgz package to see if that will help -- but I'm not sure if it will. I'm assuming you did a fresh install based on your posts. Did you check the md5sum of your install media before installing? In the simplest case, you could do the following as root in the console (ie OUTSIDE of X):
Code:
# cd
# wget http://slackware.osuosl.org/slackware-12.1/slackware/a/udev-118-i486-3.tgz
# telinit 1
You could also have mounted the install media instead of downloading the package (it is located in the a/ series). Then login as root and perform the following:
Then reboot your computer and check to make sure that there are some files in /etc/modprobe.d. If upgradepkg complains that udev is not installed (that would be strange if you did a full install of 12.1), then you could use `upgradepkg --installnew /path/to/udev-118-i486-3.tgz` instead.
I just realised that you have to put sound or blacklist etc at the end of the command /etc/modprobe.d/
Stupid me. No wonder the command didn't return anything.
This is the output of /etc/modprobe.d/sound
Code:
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
Sounds to me like your /etc/modprobe.d/ directory is fine. Just a quick check while on the subject, though...
What is your output from
Code:
ls -l /etc/modprobe.d/
Go ahead and keep the two commands I showed you earlier in rc.local for now. It won't hurt to reload your network and sound if it is already loaded.
Also, in your /etc/rc.d/rc.modules-2.6.24.5-smp (does that match the kernel you are using?) try adding a couple of echo statements to help you see when your modules are loaded.
right before you load the sound module and something similar for the network card module. This should help you spot it as the messages go by. If you want add other echo lines so you know when they are done being loaded.
Also keep in mind that you can freeze the messages that scroll by by using your 'Scroll Lock' button. Shift+'Page Up' and Shift+'Page Down' lets you scroll manually up and down, respectively.
I want to make sure everything that should be executed is actually getting executed.
Please show the output of
Code:
ls -l /etc/rc.d/rc.*
Code:
cat /etc/rc.d/rc.alsa
Code:
cat /etc/rc.d/rc.local
Let us know what you see when your modules are being loaded.
Let us know what you see when your rc.local is being run (sound and network being re-loaded.
# cat /etc/rc.d/rc.alsa
#!/bin/sh
# Load the mixer settings and OSS compatibility for ALSA.
# (the Advanced Linux Sound Architecture)
# A function to load the ALSA mixer settings:
load_alsa_mixer() {
if [ -r /etc/asound.state ]; then
echo "Loading ALSA mixer settings: /usr/sbin/alsactl restore"
/usr/sbin/alsactl restore
else
# It's possible a user might not want to set a default sound state.
# In that case, do this: touch /etc/no.asound.state
if [ ! -r /etc/no.asound.state ]; then
echo "Setting default ALSA mixer settings."
# set default mixer volumes for ALSA
# Taken from the alsaconfig script.
amixer -s -q <<EOF
set Master 75% unmute
set Master -12dB
set 'Master Mono' 75% unmute
set 'Master Mono' -12dB
set Front 75% unmute
set Front -12dB
set PCM 90% unmute
set PCM 0dB
mixer Synth 90% unmute
mixer Synth 0dB
mixer CD 90% unmute
mixer CD 0dB
# mute mic
set Mic 0% mute
# ESS 1969 chipset has 2 PCM channels
set PCM,1 90% unmute
set PCM,1 0dB
# Trident/YMFPCI/emu10k1
set Wave 100% unmute
set Music 100% unmute
set AC97 100% unmute
# CS4237B chipset:
set 'Master Digital' 75% unmute
# Envy24 chips with analog outs
set DAC 90% unmute
set DAC -12dB
set DAC,0 90% unmute
set DAC,0 -12dB
set DAC,1 90% unmute
set DAC,1 -12dB
# some notebooks use headphone instead of master
set Headphone 75% unmute
set Headphone -12dB
set Playback 100% unmute
# turn off digital switches
set "SB Live Analog/Digital Output Jack" off
set "Audigy Analog/Digital Output Jack" off
EOF
echo "Storing default ALSA mixer settings: /usr/sbin/alsactl store"
/usr/sbin/alsactl store
fi
fi
}
# A function to load the ALSA OSS compat modules:
load_alsa_oss_modules() {
if ! cat /proc/modules | tr _ - | grep -wq snd-pcm-oss ; then
echo "Loading OSS compatibility modules for ALSA."
modprobe snd-pcm-oss
modprobe snd-seq-oss
modprobe snd-mixer-oss
fi
}
# If hotplug or something else has loaded the ALSA modules, then
# simply load the mixer settings and make sure the OSS compat
# modules are loaded:
if [ -d /proc/asound ]; then
load_alsa_oss_modules
load_alsa_mixer
else
# If there are ALSA modules defined in /etc/modules.conf, but
# ALSA is not yet loaded, then load the modules now:
DRIVERS=$(modprobe -c | grep -E "^[[:space:]]*alias[[:space:]]+snd-card-[[:digit:]]" | tr -s "[[:space:]]" " " | cut -d " " -f 3)
if [ ! "$DRIVERS" = "" ]; then
echo "Loading ALSA kernel modules."
for module in $DRIVERS; do
modprobe $module
done
fi
# If ALSA is now up, then load the mixer settings and OSS modules:
if [ -d /proc/asound ]; then
load_alsa_oss_modules
load_alsa_mixer
fi
fi
root@slackbox1:
Code:
# cat /etc/rc.d/rc.local
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
/etc/rc.d/rc.inet1 restart
/etc/rc.d/rc.alsa
root@slackbox1:
Thankyou guys for being so patient with your expert help.
I'd had enough so I reinstalled 12.1 and have none of those problems now.
It runs beautifully.
It must have been a problem with the installation in the first place.
I think it got a seed stuck between it's teeth or something.It couldn't have been my fault
I learned a lot from the exercise but I'm sure I'll be back for more advice from this friendly forum in the future.
I've been running Arch for a couple of years and now I can play around with Slackware as well.
It's fun.
Regards
drum
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.