Its useful to know that your PC’s hardware audio codec might be an ALC883, but it would be more useful to confirm that as best possible. Please, could you provide some more information, such that a good recommendation can be provided?
Specifically to provide more information, then with your PC connected to the internet, please copy and paste the following into a gnome-terminal / konsole:
wget http://home.cfl.rr.com/infofiles/tsalsa && su -c 'bash ./tsalsa'
when prompted for a password please enter your root password. Please try to accurately answer the question on the number of plugs/jacks on your PC (for example my PC has 3 i/o plugs/jacks). When the script completes it will pass you a URL. Please post that URL here.
Also, please copy and paste the following, one line at a time, into a gnome-terminal or konsole and post the output here.
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/soundAlso, are you using Gnome? KDE4? or KDE3?
//////////////////////////////////////////////////
./tsalsa: line 169: lsof: command not found
cat: /proc/asound/card0/pcm0p/info: No such file or directory
aplay: device_list:215: no soundcards found…
arecord: device_list:215: no soundcards found…
uploading /tmp/tsalsa.txt to nopaste.com
Uploading /tmp/tsalsa.txt: #-------------------------------------------------] 0.2 Seconds
tsalsa completed in 221 seconds
paste this url in #alsa:tsalsa.txt - nopaste.com (beta)
which: no lsof in (/home/standard/bin:/usr/local/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin)
This is strange, … given alsa is not detecting your PC’s sound device, I am surprised to see this in /proc/asound/pcm. Plus that directory suggests both an ALC268 and an ALC883 (they are not the same).
Next time you restart your PC, can you run: dmesg > dmesg.txt && curl -F file=@dmesg.txt nopaste.com/a
and post the URL it gives here. I am looking for an error message in the dmesg file for “snd” or “hda” or “alsa” or “sound” …
Is your “medion m2280” a laptop?
Also, what is the output of: su -c lspci (enter root password when prompted for a password)
There are boot codes for the ALC883 for the medion. For example, looking at the ALSA-Configuration.txt file for the ALC883/888 (here is an extract):
which suggests the following edit to your /etc/modprobe.d/sound file might work:
options snd slots=snd-hda-intel
# u1Nb.1DH0SjRJ4FC:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
options snd-hda-intel model=medion
followed by a reboot, or by restarting alsa with su -c ‘rcalsasound restart’ but given your sound device is not working at all, I am not convinced that will help.
Doing a search for medion on the alsa web site I obtain this: Search results for medion - AlsaProject
… which suggests you may need to update your alsa to 1.0.17 or newer.
There is guidance here on how to update your alsa: Alsa-update guide - openSUSE
note there are six zypper commands to send if updating via zypper. One need to update their various alsa apps (that are already installed) and also install the alsa-driver-kmp-their-kernel that is applicable to one’s kernel.
I re-installed the system, I think I messed up with the Realtek drivers.
Sound was/is open on the bios. After the fresh install, sound worked like a charm for a while, but suddenly, it stopped to work properly.
Now when I start the computer while headphones are plugged, there is no sound from speakers when I unplug the headphones.
When I start the computer while headphones are unplugged, sound comes from both speaker and headphones if I plug the headphones. I don’t know what thing I did wrong, it was working good.
BTW, if I restart the sound driver it works fine again. So I think I can go like this. I prepared a shortcut to restart sound driver. If anything goes wrong, a doble-click will solve it.
I actually don’t boot my computer often. Once in three days or so. Sound now works without a problem. It doesn’t need to restart driver on every boot.
And yes, I use that command. I didn’t need to use it since last time (just before I posted my last message). I think it happens when I don’t shut down the OS properly.