Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 did what you said, and it worked, but next time i booted the machine, it gave me an error message which i ignored (saying something about sound) and i clicked don't show again. and now the sound doesn't work. alsamixer returns the mixer and everything looks good, but no sound. Any ideas? How can I view that error message again?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
My apologies mate, I misspelled the directory. I have edited that post. Have a look at dmesg, and post any relevant info. Make sure the module isn't loading, have a look at lsmod, and the blacklist file.
good luck.
take a look at your modules and stuff like that in your menuconfig (xconfig in the grafical interface)
have you ever recompiled the kernel? maybe you've changed some important option..
once,, I had to recompile my kernel and I inconsciently made some little bad changes.. It affected exactly my ALSA drivers.. and I was simply configuring the video modules
#
# Listing a module here prevents the hotplug scripts from loading it.
# Usually that'd be so that some other driver will bind it instead,
# no matter which driver happens to get probed first. Sometimes user
# mode tools can also control driver binding.
#
# Syntax: driver name alone (without any spaces) on a line. Other
# lines are ignored.
#
# To get the sound to work (blocks modem part of Audio Card)
snd-intel8x0m
# uhci ... usb-uhci handles the same pci class, so one of the two
# needs to be listed below.
usb-uhci
# usbcore ... module is loaded implicitly, ignore it otherwise
usbcore
# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
de4x5
# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
dmfe
#evbug is a debug tool and should be loaded explicitly
evbug
# Alternate Intel EtherExpress Pro/100 support driver. List it
# here so it won't conflict with an already-loaded eepro100 module.
e100
# Alternate 8139 driver. Some 8139 cards need this specific driver,
# though...
8139cp
# This module causes many Intel motherboards to crash and reboot.
i810-tco
# The kernel lists this as "experimental", but for now it's "broken"
via-ircc
# OSS (Open Sound System) modules. This is the old and deprecated Linux
# sound system, though we still ship modules for it (for now). If you
# want to use OSS, remove the alsa-driver package and cut out (or comment
# out) this list. With these modules blacklisted ALSA will load by default.
ac97
ac97_codec
aci
ad1816
ad1848
ad1889
adlib_card
aedsp16
ali5455
awe_wave
btaudio
cmpci
cs4232
cs4281
cs46xx
emu10k1
es1370
es1371
esssolo1
forte
gus
i810_audio
kahlua
mad16
maestro
maestro3
maui
mpu401
msnd
msnd_classic
msnd_pinnacle
nm256_audio
opl3
opl3sa
opl3sa2
pas2
pss
rme96xx
sb
sb_lib
sgalaxy
sonicvibes
sound
sscape
trident
trix
uart401
uart6850
v_midi
via82cxxx_audio
wavefront
ymfpci
# Hardware specific video framebuffer modules. If the user wants
# these, they can load them manually or de-blacklist them. Having
# them load automatically may lead to funny side effects with
# certain revisions of video hardware.
atyfb
sisfb
radeonfb
cyber2000fb
rivafb
tdfxfb
vga16fb
aty128fb
hgafb
clgenfb
pm2fb
sstfb
fbgen
matroxfb_DAC1064
i2c-matroxfb
matroxfb_accel
matroxfb_g450
matroxfb_Ti3026
matroxfb_misc
matroxfb_base
matroxfb_crtc2
matroxfb_maven
fbcon-cfb2
fbcon-cfb4
tridentfb
fbcon-mfb
fbcon-hga
pm3fb
fbcon-vga-planes
neofb
# SCSI and SATA controller modules. Typically these are either
# built into the kernel or loaded with an initrd already.
3w-xxxx
53c7,8xx
AM53C974
BusLogic
NCR53c406a
a100u2w
advansys
aha152x
aha1542
aha1740
aic79xx
aic7xxx
aic7xxx_old
ata_piix
atp870u
cpqfc
dc395x
dmx3191d
dpt_i2o
dtc
eata
eata_dma
eata_pio
fdomain
g_NCR5380
g_NCR5380_mmio
gdth
ide-scsi
imm
in2000
initio
ipr
ips
libata
megaraid
ncr53c8xx
nsp32
osst
pas16
pci2000
pci2220i
ppa
psi240i
qla1280
qla2100
qla2200
qla2300
qla2322
qla2xxx
qla6312
qla6322
qlogicfas
qlogicfas408
qlogicfc
qlogicisp
seagate
sim710
sata_promise
sata_sil
sata_sis
sata_svw
sata_sx4
sata_via
sata_vsc
scsi_debug
scsi_transport_fc
scsi_transport_spi
sym53c416
sym53c8xx
sym53c8xx
t128
tmscsim
u14-34f
what's interesting everything seems to work in gnome. I think i'm going to abandon kde and stick with gnome, at least till the new version of kde comes out.
Thanks for your help
Well actually it's weird sometimes the sound works and sometimes it doesn't. As if sometimes the modules don't load right. One time the mixer will work, but i get not sound. Next time there is sound, and sometimes the mixer won't even work. Is this an issue with Slackware or hardware?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.