Quote:
|
Originally Posted by broom
another quick thing.
the error message is:
Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened (No such device)
The sound server will continue, using the null output device.
|
This should get you started:
1) @ console or in a terminal as root run `lspci`
This will list the majority of the devices on your system, and one of them should be your soundcard. There'll be a lot of output that isn't entirely relevant for your particular problem, but surely at least one of them will be a soundcard device.
2) note the chipset for your soundcard from the `lspci` command
This one is entirely up to you
There are a ton of different chipsets on the market, and I'm not familiar with the Optiplex line, so you're going to have to figure out which item is indeed your soundcard. It should list a chip or soundcard type.
3) check
http://google.com/linux and search for your soundcard.
You won't need the entire line that is your soundcard, just the chip/chipset is usually enough, and perhaps the brandname to narrow down results. Try to find what module is the driver for your soundcard. Also check
http://www.alsa-project.org soundcard matrix, which should help you narrow down which driver is for your card, if it is supported, etc etc.
4) @ console or in a terminal as root run `lsmod`.
This will list the modules your kernel currently has loaded, you're looking for the module for your soundcard. Chances are it isn't listed, in which case `modprobe <modulename>`. Ideally this will be successful and you'll now have a /dev/dsp. Refer to the ALSA documentation as noted in step 3 for more info. If for some reason you have a sound module loaded that is NOT your card, `modprobe -r <modulename>` should unload it, and then you can modprobe the proper module.
5) @ console or in a terminal as root run `alsamixer` adjust volume levels, namely Master and PCM if they exist. If the slider has a "MM" at the bottom the channel is muted, and "M" key will unmute it. If it helps you can run `aplay < /dev/urandom` in another term or console while you adjust mixer levels... That command should generate static through your speakers. Use `Ctrl C` or `Ctrl \` to stop it. Once you get mixer levels where you like press [Esc] to exit alsamixer, and do as root `alsactl store` to store mixer levels.
If for some reason you can't find/load the module you need, check kernel config to make sure it exists/is compiled... I personally had to carefully do my own build of kernel 2.6.18 to get all the hardware on my laptop working, but the default Slack kernel should be able to handle your Optiplex fine.
If steps 1-5 above work for you, read up on how slackware module loading works, as it applies to loading modules at boot, module blacklisting, etc.
______
Edit:
Alien_Bob posted while I was typing this, and I consistently forget about `alsaconf`.
Try that first
