PDA

View Full Version : Comprehensive Sound Problem Solutions Guide



Pages : [1] 2 3 4 5 6 7 8 9

LordRaiden
June 28th, 2006, 06:03 PM
This thread, dating back to 2006, has now served its purpose. A lot of what is written here is obsolete, and the thread is now closed.

A new sticky thread is available at
http://ubuntuforums.org/showthread.php?t=1885240

Enjoy!
/Mörgćs





Comprehensive Sound Problem Solutions Guide v0.5e




Version History (DD-MM-YY)



28-06-06 - version 0.1 - initial creation
28-06-06 - version 0.2 - alsa-source guide added
28-06-06 - version 0.3 - alsa-drivers from alsa-project guide added
29-06-06 - version 0.4 - multiple sounds and multiple cards support added
02-07-06 - version 0.4 - fixed mistake spotted by Jvaldezjr (http://www.ubuntuforums.org/member.php?u=16088)
04-07-06 - version 0.5a - layout changes - starting on MIDI guide - Read *EXPERIMENTAL*
04-07-06 - version 0.5a - added part on saving sound settings so they are restored after reboot.
11-07-06 - version 0.5b - added guide for doing a *fresh* kernel installation
13-07-06 - version 0.5c - minor layout edit - moved *fresh* kernel above compilation to see if it is more help and if it solves more problems.
15-07-06 - version 0.5d - usage update
17-07-06 - version 0.5e - added Advanced Guides by other Ubuntuers
21-08-06 - Initial phase of moving page to UDSF
23-08-06 - Added a Further Reading section - first link thanks to segalion.
12-11-06 - version 0.6 - finally added "Adding the current user to the audio group" - and a few formatting fixes




Background / Notes / Warnings


I can't guarantee if these instructions will work for everybody, and this is definitely a work in progress. But if these instructions can at least help one person out, I'll be happy.


If anyone has any suggestions or tips in making this post better, feel free to PM me or post below. Credits will be given regardless of how small the improvement.


If you find that you have followed the instructions on this post that something did not and you don't know why, it will be better if you start a new post and cite the fact that you used the instructions on this guide to solve your problem. Your post might get lost in all the other posts and you might not get help.


If you however find a solution to your problem, and you fee that the solution should be here, don't hesistate to post. However, please be specific.

If you cannot use hear anything, and you have just installed Ubuntu, then it could very possibly be a bug. It could be something as simple as not detecting your hardware the first time or evidence of a deeper problem. As fun as it is to find workarounds and fixes on your own or with help, Ubuntu developers need your feedback to see what is not working for you. That's right ladies and gentlemen, they would really really like it if you would file bug reports on http://launchpad.net (http://launchpad.net/)under the Ubuntu distribution.

Note: To make it absolutely clear, when I say 'Ubuntu', I mean Ubuntu AND Kubuntu AND Xubuntu (for people who find this confusing - just accept it and don't feel bad - I and probably a whole lot others got confused when we started out).


Important syntax note: ALSA modules are denoted by the prefix 'snd' followed by the dash ' - ', followed by the module name (i.e. 'via82xx'). So the full name might be something like snd-via82xx. However, in some cases you will see an underscore ' _ ' instead of the dash. This is OK, do not let it confuse you. For all intensive purposes (installing modules or posting on forums) only use the dash ' - '.

General Help - Start here if you have no idea why sound is not playing


(1) Go to a shell and type:
aplay -l


Success - You will get a list of the all the soundcards installed on your system. Your sound just might be muted. See alsamixer section.

Failure - You will get a message like
aplay: device_list:221: no soundcard found... Move on to step 2.

(2) Type this into the shell:
lspci -v


Success - At this point, you should see your sound card listed. This is a positive sign because it means that Ubuntu is detecting the presence of your soundcard, but the drivers are not installed/running. Leave your shell running since you will need it.


Failure - If it is not listed, then there are a few things that you can do.


If your soundcard is an onboard sound card, then it might be disabled in the system's BIOS. You will have to reboot and hit the key that lets you enter into the BIOS (usually Delete, F2, or F8).

If your soundcard is not onboard, make sure that it is properly seated in the PCI slot. If your card is working under Windows then this is not a problem.
(3) Check to see if the ALSA driver for your sound card exists. Go to http://www.alsa-project.org/alsa-doc/ (http://www.alsa-project.org/alsa-doc/) and search for your sound card (chipset) manufacturer in the dropdown box. You'll be given a matrix of the sound cards made by the manufacturer. Try to match the chipset you found in step 2 with the driver(green hyperlink text).
Success - You will have found the driver for your soundcard's chipset.

Failure - You will have not found the driver for your soundcard chipset. (at the moment I cannot help you, but stay tuned!)

(4) Now go back to the shell and type
sudo modprobe snd- Now, press the TAB key BEFORE pressing the ENTER key to see a list of modules. Try to find the module that matches the driver you found in step 3.



For example, my driver is a via82xx so I would type, sudo modprobe snd-via82xx.

Success


A success here means that your soundcard was installed, but it was not being loaded. Now you have loaded it for the current session.


To load it for all sessions (you will probably want to do this) you will have to edit /etc/modules (I think this is the file, I'll check once I get to my Dapper PC).


Type this into the shell
sudo nano /etc/modules


Add only the name of the module to be loaded at the end of the file. In my case, the via82xx module gave me sound so I added "snd-via82xx" to the end of the file.(iii) Make sure that you have all channels unmuted in alsamixer


See the alsamixer section


Play media using your favorite media player. Set your audio engine to alsa. In some cases, you have to configure your audio engine within another (media engine) like in Kaffiene in Kubuntu. If you hear sound, hurray!

One final step. Go onto Saving Sound Settings

Failure -You have two options

Move on to Getting the ALSA drivers from a *fresh* kernel. This step is easier and is recommended to users who might have been tinkering with their sound settings and want to revert back to the way it was just after installing Ubuntu (without reinstalling Ubuntu of course ;) )

Move on to ALSA driver Compilation, if you have not done so already. If you have, please post a new thread with your problem.


Getting the ALSA drivers from a *fresh* kernel

Sometimes, sound might be configured correctly, but for some reason or another (tinkering) it stops working. One way to go back to the old setup is to reinstall Ubuntu. However, this step is actually quite unnecessary since you are reinstalling everything because of one thing.

A faster way, is to just remove the problematic packages and reinstall them cleanly.

(1) Remove these packages
sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
(2) Reinstall those same packages

sudo apt-get install linux-sound-base alsa-base alsa-utils



VERY IMPORTANT NOTE: Ubuntu (GNOME) users have reported that packages 'gdm' and 'ubuntu-desktop' are removed after removing the linux-sound-base packages. If this happens, then do the following

sudo apt-get install gdm ubuntu-desktop
(3) Reboot



VERY IMPORTANT NOTE: Xubuntu (XFCE) users have reported that packages 'gdm' and 'xubuntu-desktop' are removed after removing the linux-sound-base packages. If this happens, then do the following

sudo apt-get install gdm xubuntu-desktop
(3) Reboot
Now you may ask "I already had the packages, so why did I go through the trouble of removing them, then installing them". The answer lies in the --purge option which removes all the extra information that accumulated from tinkering and upgrading. After doing a purge then install, the packages are unpackaged as if it they are brand new.
(4) At this point, try using
aplay -l you should get your soundcard listed.[LIST]
Success - Your soundcard is detected. Go onto the Using alsamixer section, then try playing something on your music or media player.
Failure - Your card was not detected. You should try compiling your driver, so go onto ALSA drive Compilation.
ALSA driver Compilation


If you are here, then either your soundcard driver could not be loaded with modprobe, or you want to compile the drivers yourself from scratch. Good luck to you!

There are two main ways the sources of alsa-drivers are made available to you. One is though the apt-get system. Using this system would be the recommended system since most of the heavy lifting is done for you.

The other way, is getting the latest drivers from alsa-project.org. This page has the latest drivers available, which you might want to fix problems with. However, these have not been tested with Ubuntu and therefore should be used with caution.

Using alsa-source


Type the following to shell: (note: module-assistant is optional, it will compile the package for you)
sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant alsa-source


sudo dpkg-reconfigure alsa-source

You now have a big blue dialog box (left and right keys to choose 'Yes' and 'No', Enter key proceed). Answer yes (for ISA-PNP - recommended by package maintainers), then yes again (for debugging - recommended by package maintainers).

Now you must pick which driver you want to install. Use space to select and deselect modules, and up and down to navigate.

From General Help step 3, you should know the name of your driver. Deselect 'all' (the * will go away), and select your driver. In my case, I deselected 'all' then selected 'via82xx'. Hit Enter. Almost home free!


If you chose module-assistant
sudo module-assistant a-i alsa-source If the progress bar reaches 100% with no errors, you will have installed the drivers successfully. Resume this guide from General Help step 4.

If you did not choose module-assistant - Remember the name of your soundcard driver and use it place of the blue text below.


cd /usr/src sudo tar xjvf alsa-driver.tar.bz2 cd modules/alsa-driver
sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=<enter driver name here e.g. via82xx> --with-oss=yes
sudo make
sudo make install








If you get no error messages, you will have installed the drivers successfully.
Success - Resume this guide from General Help step 4.

Failure - Start a new thread in this thread of the forum. Paste the error message that you get and state that you were following instructions on this page.

Using drivers from alsa-project - update I now recommend using the stable version 1.0.12


The alsa-project route is very similar to the alsa-source route without the module-assistant.

First you would have to get the alsa-driver tar from alsa-project then pretty much do configure, make and make install again.

However, I do recommend that you make a specific directory when you compile something from source. Remember the name of your soundcard driver and use it place of the blue text below.



mkdir src
cd src


mkdir alsa


cd alsa


sudo apt-get install build-essential linux-headers-$(uname -r)
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.12rc2.tar.bz2

tar xvjf alsa-driver-1.0.12rc2.tar.bz2
cd alsa-driver-1.0.12rc1
sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=<enter driver name here e.g. via82xx> --with-oss=yes
sudo make
sudo make install

If you get no errors from doing the above then you have successfully compiled alsa-drivers from source. Resume this guide from General Help step 4.



Using alsamixer

Type this into a shell
alsamixerYou will now see what appears to be a graphical equalizer. It is more like ten different volume controls in the sample place.
To navigate around:
Left and Right Arrow Keys - Move left and right (if you move long enough in one direction you will get back to where you started - you will not fall off the screen :lol:)
[LEFT]Up and Down Arrow Keys - Increase and decrease volume respectively.

Letter M Key - Mutes/unmutes. If a channel is unmuted, then there is a green box underneath the volume slider. If the channel is muted, the box is grey.
Saving Sound Settings
Do this step to ensure that your alsamixer settings are reloaded with each boot. First make sure you have your settings just the way you like them in alsamixer. Then do
sudo alsactl store 0 or if this is your nth sound card (where n is the number of soundcards in your computer) replace 0 with n-1. Many thanks to xpix for trying this out.-


Getting more than one application to use the soundcard at the same time


You might want to play a game and listen to music on your favorite music player at the same time. To do this successfully, you will have to use ALSA since it supports this feature the best. On all the music players I know of, you can configure the sound engine, to any module that is available.


The setting is usually found under something like Tools >>> Configure >>> Player Engines.


For games, it is a bit more tricky since there is not always a way to configure the player engine directly. Most games, however, do support the OSS. ALSA has an OSS module that allows OSS applications to use the ALSA driver.


To do this you will need the alsa-oss package
sudo apt-get install alsa-oss

After doing this step, it is very easy to use alsa-oss. In the shell, you can type 'aoss' then the name of the program name you want to use with alsa-oss.

Configuring default soundcards / stopping multiple soundcards from switching


Note: This section assumes that you have installed each soundcard properly.


In a shell, type
cat /proc/asound/modules


This will give the the name and index of each soundcard you have currently. Make a note of the names, and decide which one you want to be the default card.


Now type
sudo nano /etc/modprobe.d/alsa-base


At the very end of the file, add the following (assuming you have 3 cards with module names A, B and C and you want to have them in the order CAB)



options snd-C index=0
options snd-A index=1
options snd-B index=2


Adding the current user to the audio group


A very common cause for a user to not have sound is not having his/her username in the /etc/group.

Thanks to rustybutt for this simple check.


grep 'audio' /etc/group

You should see a line similar to
audio:x:29: followed by a username i.e. if the username is "ubuntu" then you should see
audio:x:29:ubuntu. If you see something else i.e.
audio:x:29:root you should add your username to the file by doing
sudo nano /etc/group. Now find the line that looks like
audio:x:29:root and change it to
audio:x:29:root:moocow only replacing moocow with your real username.

Hit CTRL + 0 to save, then CTRL + X to exit. That's the end of that :-D




Getting MIDI To Work - *EXPERIMENTAL*

This section assumes you can successfully hear sound from your soundcard.

First of all, make sure that you actually have a MIDI port on your soundcard. Most onboard soundcards do not have a MIDI port.


Next, open up this file:



sudo nano /etc/modprobe.d/alsa-base


Then add this options line



options <snd module name here i.e. snd-via82xx> mpu_port=0x330
OR if you already have a options line for this soundcard add
mpu_port=0x330 to the line.


The default MIDI port is 330. You should verify this number in your BIOS if you are not sure. If the number is not listed, it is most likely that the number is 330 (add the 0x for the file).


If you get no errors, you have successfully installed your MIDI port. At the moment, I do not know if any further configuration is necessary.


Miscellaneous Tips and Tricks


Here are a few things that other people have dug up over the course of this guide. Not all tips are meant to work for all hardware (believe me hda-intel will probably have like a mini guide of it's own one day).

shaviro found the following from this post http://www.ubuntuforums.org/showthread.php?t=153752 (http://www.ubuntuforums.org/showthread.php?t=153752&highlight=touchpad+sony)
I wasn't getting any sound out of my Sony Vaio PCG-4B1L ...
The crucial thing is to enable everything in alsamixer EXCEPT "external amplifier." (I had to turn off microphone too, to stop feedback).
Useff had a very annoying problem where he could get sound through alsa from one user, but not through is main account. http://www.ubuntuforums.org/showthread.php?p=1221754 (http://www.ubuntuforums.org/showthread.php?p=1221754). Him and I managed to fix the problem by making sure the main account was in the audio group in /etc/groups (which he was) and deleting the .asoundrc file in the main account's /home directory.

Bo Rosén solved his ISA problem the following way. Thanks to FarEast for his help in the matter.

Thanks to http://ubuntuforums.org/showthread.php?t=127402 (http://ubuntuforums.org/showthread.php?t=127402) this post I got soundblaster 16 isa working. In short add
snd-sb16 to /etc/modules then create a new file:
gedit /etc/modprobe.d/sound and enter this line:
options snd-sb16 isapnp=0 port=0x220 irq=5 dma8=1 dma16=5
sudo update-modules reboot
webbca01 figured out how to get AC'97 work with the help of the second last post here (http://www.linuxforum.com/forums/index.php/topic,178761.new/topicseen.html) and this post (http://www.ubuntuforums.org/showthread.php?t=14989&highlight=ac97_quirk). Basically, if you have an intel8x0 module, you can get AC'97 working by
sudo nano /etc/modprobe.d/alsa-base and adding this as the last line:
"options snd-intel8x0 ac97_quirk=3"Advanced Guides by other Ubuntuers
Soundblaster Audigy 2 AC3 Passthrough - Howto (http://www.ubuntuforums.org/showthread.php?p=1269056#post1269056) by dave_euser
Further Reading

http://www.sabi.co.uk/Notes/linuxSoundALSA.html - Some advanced reading on ALSA - thanks segalion

To Do:


Important - no particular order


Getting MIDI to work

Compiling alsa entirely (drivers, utils, oss, etc)

Getting line input to work if it does not already - for microphones, etc.

Getting SPDIF output to work if it does not already - for amplifiers, speakers with digital in.
On the backburner

Scripts for getting configuration that needs to be done in this post to be done automatically

Related


Getting keyboard multimedia keys to work - http://doc.gwos.org/index.php/MultimediaKeys (http://doc.gwos.org/index.php/MultimediaKeys)


(I personally like the non-keytouch route - configuring xmodmap and then using gnome-keybindings or for KDE (System Settings >> Regional and Language Settings >> Keyboard Shortcuts). The xmodmap route also works for XFCE, but I do not how to configure XFCE application keybindings.



Posts / References /Credits


Hoary Sound Broke (http://www.ubuntuforums.org/showthread.php?t=21211)


Problem with Azalia audio (http://ubuntuforums.org/showthread.php?t=181186)


MultipleCards (http://alsa.opensrc.org/index.php?page=MultipleCards) from alsa.opensrc.org


Volume Control does not save my settings after reboot (http://ubuntuforums.org/showthread.php?t=207107)


Every single sound problem error post I have read :-\"


The Ubuntu community for being energetic, dynamic, and polite :smile: providers of help with Ubuntu Linux in all its flavours.

LordRaiden
June 29th, 2006, 02:37 AM
Bumping this post since I think it is ready to be used by people having trouble with sound. I'll do my best to field questions and make changes to this guide as needed. If you are an experienced Ubuntu user, please help out with testing, verifying, and helping people who use this guide.

Thanks in advance

estevez
June 30th, 2006, 11:24 PM
Excellent. Thank you.
I had a problem with multiple card switching and reported it as a bug. Are options in alsa-base (also suggested to me on launchpad) workaround or solution? :-)
Im definitely interested in midi (new yamaha dx-305 sitting just next to pc).

LordRaiden
July 1st, 2006, 09:11 PM
Options in alsa-base would be a solution. alsa-base is a part of the official Ubuntu Repositories, so they would be considered a solution. The alsa-drivers from alsa-project would be considered a workaround until Ubuntu incorporates the official 1.0.11 stable into alsa-base.

linish
July 2nd, 2006, 08:38 AM
it just helped ma mute computer to speak up..is there sum comprehensive graphx driver problem solutions guide too...:oops:

ubuntu_demon
July 2nd, 2006, 05:44 PM
great guide! I'm sure this will help a lot of users!

Jvaldezjr
July 2nd, 2006, 08:52 PM
Excellent guide- I've just reinstalled Dapper, so I'll retry my sound issues with this guide, and see what happens.

**Update***
I went through the steps like you mentioned, and I believe it is working like it is supposed to. I'll post if I have more problems in another thread, but as of right now I'm getting 5.1 sound. The only problem I had was when I rebuilding the alsa drivers with alsa-source. The command "dpkg-reconfigure alsa-base" didn't produce anything- there was a pause at the prompt, then that was it. Something ran, but I got no feedback as to what it did. So I went through the steps with the module-assistant method, and so far so good.

Also, I never was able to get any output when I did "sudo modprobe snd-" and hit tab. So I went through with the loading the module anyway (my case it was snd-intel8x0). When I added that module to my /etc/modules file and rebooted, I believe that fixed it. However, when I checked to see if the module was loaded (lsmod | grep snd) the only thing I saw that was close to snd-intel8x0 was snd_intel8x0. Is there a different between using the - and the _ , or is it still the same module, and should I have added snd_intel8x0 to /etc/modules?

Thanks

acorn22
July 3rd, 2006, 01:15 AM
Wonderful!

If only all howto type things where broken down into the nice "tree" you made. (I'm refering to the succes/failure thing)

It was very easy to understand, even for a noob like me :)

Starmartyr
July 3rd, 2006, 02:47 AM
Tried it, and have yet to have success. I am using a Gigabyte nVidia nForce 4 motherboard, and the alsa-project has nothing set for it, or what I can make of it.

:confused:

LordRaiden
July 3rd, 2006, 03:55 AM
Jvaldezjr (http://www.ubuntuforums.org/member.php?u=16088) - Thanks for the comments - you found an error in my instructions - it was supposed to read
sudo apt-get dpkg-reconfigure alsa-source not alsa-base. In the alsa-project wiki, using a - and a _ are the same thing. They just appear in different areas.

ubuntu_demon - thanks for the comments and the sticky!!!

linish - glad I could help. Video gets a bit tricky and most of the work has been done. I might make a guide that links to all the relevant guides for ATI/NVIDIA/free drivers.

acorn22 - thanks for the comments. I tried to make it as new-user friendly as possible and I assume that the new-user has no previous knowledge whatsoever. This characteristic, IMO, makes the guide longer, but more thorough and less ambiguous.

starmartyr - I think your sound card driver is th intel8x0.

pinguinus
July 3rd, 2006, 07:23 AM
A nice guide, thank you.

By the way, what is the difference between, say, snd-ymfpci and snd_ymfpci or do they mean and work the same? (Sometimes those modules are written with "_" sometimes with "-" after snd). Does it matter if I do
sudo modprobe snd-
(or)
sudo modprobe snd_

pinguinus
July 3rd, 2006, 07:34 AM
I wonder what's my problem with my Hoontech YMF-754 soundcard? The soundcard worked without a problem in Ubuntu Breezy (etc.) but I've not managed to get it working in Dapper yet. Somewhere I read that there might be some small bug in Dapper sound?

Some information:
#lspci -v

0000:00:08.0 Multimedia audio controller: Yamaha Corporation YMF-754 [DS-1E Audio Controller]
Subsystem: Yamaha Corporation DS-XG PCI Audio Codec
Flags: bus master, medium devsel, latency 64, IRQ 193
Memory at dfff0000 (32-bit, non-prefetchable) [size=32K]
I/O ports at e800 [size=64]
I/O ports at e400 [size=4]
Capabilities: <available only to root>

#cat /proc/asound/modules
0 snd_ymfpci

#aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: YMF754 [Yamaha DS-XG (YMF754)], device 0: YMFPCI [YMFPCI]
Subdevices: 31/32
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Subdevice #8: subdevice #8
Subdevice #9: subdevice #9
Subdevice #10: subdevice #10
Subdevice #11: subdevice #11
Subdevice #12: subdevice #12
Subdevice #13: subdevice #13
Subdevice #14: subdevice #14
Subdevice #15: subdevice #15
Subdevice #16: subdevice #16
Subdevice #17: subdevice #17
Subdevice #18: subdevice #18
Subdevice #19: subdevice #19
Subdevice #20: subdevice #20
Subdevice #21: subdevice #21
Subdevice #22: subdevice #22
Subdevice #23: subdevice #23
Subdevice #24: subdevice #24
Subdevice #25: subdevice #25
Subdevice #26: subdevice #26
Subdevice #27: subdevice #27
Subdevice #28: subdevice #28
Subdevice #29: subdevice #29
Subdevice #30: subdevice #30
Subdevice #31: subdevice #31
card 0: YMF754 [Yamaha DS-XG (YMF754)], device 1: YMFPCI - IEC958 [YMFPCI - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: YMF754 [Yamaha DS-XG (YMF754)], device 2: YMFPCI - Rear [YMFPCI - Rear PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

I've unmuted all the channels in alsamixer (sudo alsamixer) and that was usually all I needed to do (in Breezy etc.) to get my sound working, including the digital output - but no joy yet. :(

I also added (both or the other):
snd-ymfpci
snd_ymfpci
at the end of my /etc/modules file but that doesn't seem to help either.:confused:

What's the problem Dapper is having with my soundcard? Everything works flawlessly in Breezy or in Debian Sarge, or in MS Windows too.

ubuntu_demon
July 3rd, 2006, 10:25 AM
I've linked to this guide on my blog :
http://ubuntudemon.wordpress.com

LordRaiden
July 3rd, 2006, 08:34 PM
pinguinus - the dash/underscore thing is sort of weird to understand, but this is what I have been seeing. When loading the modules using modprobe, the dash is used. When displaying, the underscore is used. So for all intensive purposes, use the dash since it matters for input.

Regarding your soundcard, it seems installed so that does not seem like an issue.
Paste in the results of
dmesg in a code box, and I'll see if anything is there.



ubuntu_demon - thank for the link in your blog, this page is really starting to get a lot of views.

pinguinus
July 3rd, 2006, 10:13 PM
Thanks LordRaiden. By the way, I haven't yet tried the alsa-source method of your guide - because previously that was not needed. I just recently installed Ubuntu Dapper to this machine. I suppose I could try alsa-source too if nothing else helps.

Here's the output from dmesg (there was quite much ethernet related stuff that I removed from the output) :


[17179569.184000] Linux version 2.6.15-25-k7 (buildd@terranova) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Wed Jun 14 11:43:20 UTC 2006
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[17179569.184000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[17179569.184000] BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
[17179569.184000] BIOS-e820: 000000002fff0000 - 000000002fff8000 (ACPI data)
[17179569.184000] BIOS-e820: 000000002fff8000 - 0000000030000000 (ACPI NVS)
[17179569.184000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[17179569.184000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[17179569.184000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[17179569.184000] 0MB HIGHMEM available.
[17179569.184000] 767MB LOWMEM available.
[17179569.184000] found SMP MP-table at 000fb880
[17179569.184000] On node 0 totalpages: 196592
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] DMA32 zone: 0 pages, LIFO batch:0
[17179569.184000] Normal zone: 192496 pages, LIFO batch:31
[17179569.184000] HighMem zone: 0 pages, LIFO batch:0
[17179569.184000] DMI 2.3 present.
[17179569.184000] ACPI: RSDP (v000 AMI ) @ 0x000fa710
[17179569.184000] ACPI: RSDT (v001 AMIINT VIA_K7 0x00000010 MSFT 0x00000097) @ 0x2fff0000
[17179569.184000] ACPI: FADT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x2fff0030
[17179569.184000] ACPI: MADT (v001 AMIINT VIA_K7 0x00000009 MSFT 0x00000097) @ 0x2fff00c0
[17179569.184000] ACPI: DSDT (v001 VIA VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
[17179569.184000] ACPI: PM-Timer IO Port: 0x808
[17179569.184000] ACPI: Local APIC address 0xfee00000
[17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[17179569.184000] Processor #0 6:6 APIC version 16
[17179569.184000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[17179569.184000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[17179569.184000] ACPI: IRQ0 used by override.
[17179569.184000] ACPI: IRQ2 used by override.
[17179569.184000] ACPI: IRQ9 used by override.
[17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs
[17179569.184000] Using ACPI (MADT) for SMP configuration information
[17179569.184000] Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
[17179569.184000] Built 1 zonelists
[17179569.184000] Kernel command line: root=/dev/hda2 ro quiet splash
[17179569.184000] mapped APIC to ffffd000 (fee00000)
[17179569.184000] mapped IOAPIC to ffffc000 (fec00000)
[17179569.184000] Initializing CPU#0
[17179569.184000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[17179569.184000] Detected 1100.247 MHz processor.
[17179569.184000] Using pmtmr for high-res timesource
[17179569.184000] Console: colour VGA+ 80x25
[17179572.048000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[17179572.048000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179572.088000] Memory: 767476k/786368k available (2094k kernel code, 18256k reserved, 597k data, 332k init, 0k highmem)
[17179572.088000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[17179572.168000] Calibrating delay using timer specific routine.. 2202.73 BogoMIPS (lpj=4405474)
[17179572.168000] Security Framework v1.0.0 initialized
[17179572.168000] SELinux: Disabled at boot.
[17179572.168000] Mount-cache hash table entries: 512
[17179572.168000] CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
[17179572.168000] CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
[17179572.168000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[17179572.168000] CPU: L2 Cache: 256K (64 bytes/line)
[17179572.168000] CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000
[17179572.168000] mtrr: v2.0 (20020519)
[17179572.168000] Enabling fast FPU save and restore... done.
[17179572.168000] Enabling unmasked SIMD FPU exception support... done.
[17179572.168000] Checking 'hlt' instruction... OK.
[17179572.184000] SMP alternatives: switching to UP code
[17179572.184000] checking if image is initramfs... it is
[17179573.144000] Freeing initrd memory: 6760k freed
[17179573.164000] ACPI: Looking for DSDT ... not found!
[17179573.164000] CPU0: AMD Athlon(tm) Processor stepping 02
[17179573.164000] Total of 1 processors activated (2202.73 BogoMIPS).
[17179573.164000] ENABLING IO-APIC IRQs
[17179573.168000] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[17179573.308000] Brought up 1 CPUs
[17179573.308000] NET: Registered protocol family 16
[17179573.308000] EISA bus registered
[17179573.308000] ACPI: bus type pci registered
[17179573.308000] PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
[17179573.308000] PCI: Using configuration type 1
[17179573.308000] ACPI: Subsystem revision 20051216
[17179573.316000] ACPI: Interpreter enabled
[17179573.316000] ACPI: Using IOAPIC for interrupt routing
[17179573.316000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[17179573.316000] PCI: Probing PCI hardware (bus 00)
[17179573.320000] Boot video device is 0000:01:00.0
[17179573.320000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[17179573.348000] ACPI: Power Resource [URP1] (off)
[17179573.348000] ACPI: Power Resource [URP2] (off)
[17179573.352000] ACPI: Power Resource [FDDP] (off)
[17179573.352000] ACPI: Power Resource [LPTP] (off)
[17179573.352000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[17179573.352000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[17179573.352000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[17179573.352000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[17179573.352000] Linux Plug and Play Support v0.97 (c) Adam Belay
[17179573.352000] pnp: PnP ACPI init
[17179573.360000] pnp: PnP ACPI: found 11 devices
[17179573.360000] PnPBIOS: Disabled by ACPI PNP
[17179573.360000] PCI: Using ACPI for IRQ routing
[17179573.360000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[17179573.364000] PCI: Bridge: 0000:00:01.0
[17179573.364000] IO window: disabled.
[17179573.364000] MEM window: dfe00000-dfefffff
[17179573.364000] PREFETCH window: d7c00000-dfcfffff
[17179573.364000] PCI: Setting latency timer of device 0000:00:01.0 to 64
[17179573.364000] audit: initializing netlink socket (disabled)
[17179573.364000] audit(1151960590.360:1): initialized
[17179573.364000] VFS: Disk quotas dquot_6.5.1
[17179573.364000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[17179573.364000] Initializing Cryptographic API
[17179573.364000] io scheduler noop registered
[17179573.364000] io scheduler anticipatory registered
[17179573.364000] io scheduler deadline registered
[17179573.364000] io scheduler cfq registered
[17179573.364000] isapnp: Scanning for PnP cards...
[17179573.716000] isapnp: No Plug & Play device found
[17179573.744000] Real Time Clock Driver v1.12
[17179573.744000] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[17179573.744000] serio: i8042 AUX port at 0x60,0x64 irq 12
[17179573.744000] serio: i8042 KBD port at 0x60,0x64 irq 1
[17179573.744000] Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
[17179573.744000] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179573.744000] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[17179573.748000] 00:01: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179573.748000] 00:02: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[17179573.748000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[17179573.748000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179573.748000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179573.748000] mice: PS/2 mouse device common for all mice
[17179573.748000] EISA: Probing bus 0 at eisa.0
[17179573.748000] EISA: Detected 0 cards.
[17179573.748000] NET: Registered protocol family 2
[17179573.776000] input: AT Translated Set 2 keyboard as /class/input/input0
[17179573.784000] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[17179573.784000] TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
[17179573.788000] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[17179573.788000] TCP: Hash tables configured (established 131072 bind 65536)
[17179573.788000] TCP reno registered
[17179573.788000] TCP bic registered
[17179573.788000] NET: Registered protocol family 1
[17179573.788000] NET: Registered protocol family 8
[17179573.788000] NET: Registered protocol family 20
[17179573.788000] Using IPI No-Shortcut mode
[17179573.788000] ACPI wakeup devices:
[17179573.788000] PCI0 UAR1 USB USB1 USB2 AC9 MC9 ILAN SLPB
[17179573.792000] ACPI: (supports S0 S1 S4 S5)
[17179573.792000] Freeing unused kernel memory: 332k freed
[17179573.872000] vga16fb: initializing
[17179573.872000] vga16fb: mapped to 0xc00a0000
[17179573.932000] Console: switching to colour frame buffer device 80x25
[17179573.932000] fb0: VGA16 VGA frame buffer device
[17179575.012000] Capability LSM initialized
[17179575.148000] ACPI: Processor [CPU1] (supports 16 throttling states)
[17179576.040000] VP_IDE: IDE controller at PCI slot 0000:00:11.1
[17179576.040000] PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 0
[17179576.040000] VP_IDE: chipset revision 6
[17179576.040000] VP_IDE: not 100% native mode: will probe irqs later
[17179576.040000] VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
[17179576.040000] ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
[17179576.040000] ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
[17179576.044000] Probing IDE interface ide0...
[17179576.460000] hda: ST340016A, ATA DISK drive
[17179576.740000] hdb: ST380021A, ATA DISK drive
[17179576.800000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179576.804000] Probing IDE interface ide1...
[17179577.668000] hdc: HL-DT-ST RW/DVD GCC-4120B, ATAPI CD/DVD-ROM drive
[17179578.452000] hdd: HL-DT-ST DVDRAM GSA-4167B, ATAPI CD/DVD-ROM drive
[17179578.512000] ide1 at 0x170-0x177,0x376 on irq 15
[17179578.528000] hda: max request size: 128KiB
[17179578.560000] hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
[17179578.560000] hda: cache flushes not supported
[17179578.560000] hda: hda1 hda2 hda3 < hda5 hda6 hda7 > hda4
[17179578.604000] hdb: max request size: 128KiB
[17179578.604000] hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
[17179578.604000] hdb: cache flushes not supported
[17179578.604000] hdb:<6>hdc: ATAPI 32X DVD-ROM CD-R/RW drive, 2048kB Cache, DMA
[17179578.604000] Uniform CD-ROM driver Revision: 3.20
[17179578.612000] hdd: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179578.620000] hdb3 < hdb5 hdb6 hdb7 hdb8 hdb9 >
[17179579.424000] usbcore: registered new driver usbfs
[17179579.424000] usbcore: registered new driver hub
[17179579.428000] ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
[17179579.428000] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 169
[17179579.428000] ohci_hcd 0000:00:0b.0: OHCI Host Controller
[17179579.428000] ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 1
[17179579.428000] ohci_hcd 0000:00:0b.0: irq 169, io mem 0xdfffd000
[17179579.496000] USB Universal Host Controller Interface driver v2.3
[17179580.004000] hub 1-0:1.0: USB hub found
[17179580.004000] hub 1-0:1.0: 3 ports detected
[17179580.520000] ACPI: PCI Interrupt 0000:00:0b.1[b] -> GSI 17 (level, low) -> IRQ 177
[17179580.520000] ohci_hcd 0000:00:0b.1: OHCI Host Controller
[17179580.524000] ohci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 2
[17179580.524000] ohci_hcd 0000:00:0b.1: irq 177, io mem 0xdfffe000
[17179581.088000] hub 2-0:1.0: USB hub found
[17179581.088000] hub 2-0:1.0: 2 ports detected
[17179581.608000] ACPI: PCI Interrupt 0000:00:0b.2[C] -> GSI 18 (level, low) -> IRQ 185
[17179581.608000] ehci_hcd 0000:00:0b.2: EHCI Host Controller
[17179581.632000] ehci_hcd 0000:00:0b.2: new USB bus registered, assigned bus number 3
[17179581.632000] ehci_hcd 0000:00:0b.2: irq 185, io mem 0xdffffb00
[17179581.632000] ehci_hcd 0000:00:0b.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
[17179581.636000] hub 3-0:1.0: USB hub found
[17179581.636000] hub 3-0:1.0: 5 ports detected
[17179581.744000] ACPI: PCI Interrupt 0000:00:11.2[D] -> GSI 5 (level, low) -> IRQ 5
[17179581.744000] uhci_hcd 0000:00:11.2: UHCI Host Controller
[17179581.744000] uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 4
[17179581.744000] uhci_hcd 0000:00:11.2: irq 5, io base 0x0000d800
[17179581.744000] hub 4-0:1.0: USB hub found
[17179581.744000] hub 4-0:1.0: 2 ports detected
[17179581.848000] ACPI: PCI Interrupt 0000:00:11.3[D] -> GSI 5 (level, low) -> IRQ 5
[17179581.848000] uhci_hcd 0000:00:11.3: UHCI Host Controller
[17179581.848000] uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 5
[17179581.848000] uhci_hcd 0000:00:11.3: irq 5, io base 0x0000dc00
[17179581.852000] hub 5-0:1.0: USB hub found
[17179581.852000] hub 5-0:1.0: 2 ports detected
[17179581.956000] ACPI: PCI Interrupt 0000:00:11.4[D] -> GSI 5 (level, low) -> IRQ 5
[17179581.956000] uhci_hcd 0000:00:11.4: UHCI Host Controller
[17179581.956000] uhci_hcd 0000:00:11.4: new USB bus registered, assigned bus number 6
[17179581.956000] uhci_hcd 0000:00:11.4: irq 5, io base 0x0000e000
[17179581.960000] hub 6-0:1.0: USB hub found
[17179581.960000] hub 6-0:1.0: 2 ports detected
[17179582.368000] Attempting manual resume
[17179582.396000] ReiserFS: hda2: found reiserfs format "3.6" with standard journal
[17179582.436000] ReiserFS: hda2: using ordered data mode
[17179582.448000] ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[17179582.452000] ReiserFS: hda2: checking transaction log (hda2)
[17179582.468000] ReiserFS: hda2: Using r5 hash to sort names
[17179583.020000] usb 2-2: new full speed USB device using ohci_hcd and address 2
[17179591.556000] Linux agpgart interface v0.101 (c) Dave Jones
[17179591.588000] Floppy drive(s): fd0 is 1.44M
[17179591.612000] FDC 0 is a post-1991 82077
[17179591.648000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179591.656000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179591.680000] input: PC Speaker as /class/input/input1
[17179591.712000] agpgart: Detected VIA KT266/KY266x/KT333 chipset
[17179591.716000] agpgart: AGP aperture is 64M @ 0xe0000000
[17179591.740000] irda_init()
[17179591.740000] NET: Registered protocol family 23
[17179592.032000] Linux Tulip driver version 1.1.13 (December 15, 2004)
[17179592.032000] ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 18 (level, low) -> IRQ 185
[17179592.032000] tulip0: MII transceiver #1 config 1000 status 786d advertising 05e1.
[17179592.032000] tulip0: MII transceiver #2 config 1000 status 7849 advertising 05e1.
[17179592.032000] tulip0: MII transceiver #3 config 1000 status 7849 advertising 05e1.
[17179592.036000] tulip0: MII transceiver #4 config 1000 status 7849 advertising 05e1.
[17179592.036000] eth0: ADMtek Comet rev 17 at 0001ec00, 00:04:E2:3D:97:05, IRQ 185.
[17179592.092000] parport: PnPBIOS parport detected.
[17179592.092000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
[17179592.280000] ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 193
[17179592.312000] input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
[17179592.924000] ts: Compaq touchscreen protocol output
[17179593.680000] lp0: using parport0 (interrupt-driven).
[17179593.808000] Adding 746980k swap on /dev/hda5. Priority:-1 extents:1 across:746980k
[17179593.820000] Adding 746920k swap on /dev/hdb6. Priority:-2 extents:1 across:746920k
[17179594.184000] NET: Registered protocol family 17
[17179594.264000] md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179594.264000] md: bitmap version 4.39
[17179595.072000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[17179595.280000] cdrom: open failed.
[17179595.784000] cdrom: open failed.
[17179595.792000] cdrom: open failed.
[17179596.124000] 0000:00:07.0: tulip_stop_rxtx() failed (CSR5 0xfc664010 CSR6 0xff972113)
[17179596.124000] eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
[17179640.400000] ReiserFS: hda4: found reiserfs format "3.6" with standard journal
[17179642.136000] ReiserFS: hda4: using ordered data mode
[17179642.156000] ReiserFS: hda4: journal params: device hda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[17179642.160000] ReiserFS: hda4: checking transaction log (hda4)
[17179642.196000] ReiserFS: hda4: Using r5 hash to sort names
[17179642.284000] NTFS driver 2.1.25 [Flags: R/O MODULE].
[17179642.356000] NTFS volume version 3.0.
[17179642.580000] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
[17179642.580000] SGI XFS Quota Management subsystem
[17179642.604000] XFS mounting filesystem hdb9
[17179642.692000] Ending clean XFS mount for filesystem: hdb9
[17179642.716000] XFS mounting filesystem hda6
[17179642.792000] Ending clean XFS mount for filesystem: hda6
[17179642.828000] XFS mounting filesystem hdb8
[17179642.936000] Ending clean XFS mount for filesystem: hdb8
[17179642.984000] XFS mounting filesystem hda7
[17179643.100000] Ending clean XFS mount for filesystem: hda7
[17179643.112000] XFS mounting filesystem hdb7
[17179643.212000] Ending clean XFS mount for filesystem: hdb7
[17179644.024000] ip_tables: (C) 2000-2002 Netfilter core team
[17179644.060000] Netfilter messages via NETLINK v0.30.
[17179644.064000] ip_conntrack version 2.4 (6143 buckets, 49144 max) - 232 bytes per conntrack
[17179648.964000] pcc_acpi: loading...
[17179648.988000] ACPI: Power Button (FF) [PWRF]
[17179648.988000] ACPI: Power Button (CM) [PWRB]
[17179648.988000] ACPI: Sleep Button (CM) [SLPB]
[17179649.080000] ibm_acpi: ec object not found
[17179654.252000] ppdev: user-space parallel port driver
[17179654.600000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[17179654.600000] apm: overridden by ACPI.
[17179658.892000] mtx: module license 'Copyright (c) 2002, 2004, Matrox Graphics Inc.' taints kernel.
[17179658.900000] [mtx] MTX driver v1.4.3
[17179658.900000] [mtx] Allocated a MTX agp driver strucure
[17179658.900000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
[17179658.900000] [mtx] 0x2537(sub:0xffffffff) board found at 01:00.0
[17179659.260000] [mtx] Registers at 0xdfefe000, size: 8K, flags: 512, knl_addr: 0xf0dd4000
[17179659.260000] [mtx] Framebuffer at 0xd8000000, size: 64M, flags: 4616, knl_addr: 0x00000000, write-combining: YES
[17179659.260000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[17179659.260000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
[17179659.260000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[17179659.260000] [mtx] AGP aperture at 0xe0000000, size: 65536K, rate: 1X, write-combining: YES
[17179659.260000] [mtx] Busmastering flags:
[17179659.260000] [mtx] Board type detected: AGP
[17179659.260000] [mtx] Chipset 0x2537:0x102b was detected
[17179659.264000] [mtx] AGP chipset was detected
[17179659.264000] [mtx] PCI transfers available for read write
[17179659.264000] [mtx] AGP transfers available
[17179659.264000] [mtx] AGP serialize is used
[17179659.264000] [mtx] Parhelia patches applied: PowerM Cap66Mhz CompBypass
[17179659.264000] [mtx] Registers at 0xdfefe000, size: 8K, flags: 512, knl_addr: 0xf0dd4000
[17179659.264000] [mtx] Framebuffer at 0xd8000000, size: 64M, flags: 4616, knl_addr: 0x00000000, write-combining: YES
[17179659.264000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[17179659.264000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
[17179659.264000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[17179659.264000] [mtx] AGP aperture at 0xe0000000, size: 65536K, rate: 1X, write-combining: YES
[17179659.264000] [mtx] Busmastering flags:
[17179659.264000] [mtx] Board type detected: AGP
[17179659.264000] [mtx] Chipset 0x2537:0x102b was detected
[17179659.264000] [mtx] AGP chipset was detected
[17179659.264000] [mtx] PCI transfers available for read write
[17179659.264000] [mtx] AGP transfers available
[17179659.264000] [mtx] AGP serialize is used
[17179659.264000] [mtx] Parhelia patches applied: PowerM Cap66Mhz CompBypass
[17179662.996000] Bluetooth: Core ver 2.8
[17179662.996000] NET: Registered protocol family 31
[17179662.996000] Bluetooth: HCI device and connection manager initialized
[17179662.996000] Bluetooth: HCI socket layer initialized
[17179663.056000] Bluetooth: L2CAP ver 2.8
[17179663.056000] Bluetooth: L2CAP socket layer initialized
[17179663.060000] Bluetooth: RFCOMM socket layer initialized
[17179663.060000] Bluetooth: RFCOMM TTY layer initialized
[17179663.060000] Bluetooth: RFCOMM ver 1.7

LordRaiden
July 3rd, 2006, 10:29 PM
Seems ok. No sound errors as far as I can see. Yes, you could try the alsa-source method as well.

Jvaldezjr
July 4th, 2006, 09:20 AM
Just wanted to update you and tell you that your method has worked for me. I only have one more problem, but it has to do with input jacks on my onboard sound, so I'll ask in another thread since my hardware is detected, and the modules are loading correctly and working as it is supposed to.

Thanks for the guide, this rocks.

LordRaiden
July 4th, 2006, 02:25 PM
Jvaldezjr - Thanks for the comments, and I'm glad it worked for you. I'll put input down as an Important To-do item. Skype and Teamspeak are getting popular especially with Linux clients, so I should try to cover it. However, if you find something first, I'd like to include in the guide eventually giving the appropriate credit to all involved.


UPDATE - added a MIDI guide. Try it if you are interested. I have no idea of how to actually configure the MIDI device itself though (i.e. keyboard, joystick)

pinguinus
July 4th, 2006, 07:52 PM
Ok, I got my sound card problem, described above, solved. I did try alsa-source too (and learned new things in the process), but actually the solution was much simpler: heh.., I just needed to mute one certain channel in alsamixer... :oops: I could have sweared that I knew which alsamixer settings I had used before and that worked... But maybe I remembered wrong, or maybe that was some new setting there I hadn't sen before..??:o :oops: Anyway, I tried several alsamixer settings and found the one that worked for me, and now everything works perfectly again, also the digital output... \\:D/

LordRaiden
July 4th, 2006, 07:57 PM
Ok, I got my sound card problem, described above, solved. I did try alsa-source too (and learned new things in the process), but actually the solution was much simpler: heh.., I just needed to mute one certain channel in alsamixer... :oops: I could have sweared that I knew which alsamixer settings I had used before and that worked... But maybe I remembered wrong, or maybe that was some new setting there I hadn't sen before..??:o :oops: Anyway, I tried several alsamixer settings and found the one that worked for me, and now everything works perfectly again, also the digital output... \\:D/

Yeah, lol alsamixer is a mystery of it's own at time. BTW your card was a snd-ymfpci - [Yamaha DS-XG (YMF754)], what setting did you use to get it to work. I'll add it to the guide in case someone with similar problems experiences what you did.

pinguinus
July 4th, 2006, 09:52 PM
Yamaha DS-XG (YMF754)], what setting did you use to get it to work.
From alsamixer I switched off / muted "IEC958 Loop" which did the trick Also "Mic Boost (+20dB)" needed to be muted / switched off in order to avoid noise. Other alsamixer settings could be kept unmuted. (Somehow I thought and remembered that it should have been some other settings muted / switched off - but maybe I had just forgotten...??)

pinballkid
July 5th, 2006, 12:05 AM
Thanks for the wonderful howto. I got successes all the way through - except the part where sound is supposed to come out of the speakers.

I'm trying to use the hda-intel driver, as aplay -l gave "card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]" as my sound card. I've even tried using the drivers from the alsa project with no luck.

I'm a bit stumped on where to go from here. Perhaps I've got the sound card wrong?

EDIT:
I've just noticed that there is quite a bit of discussion about this card on alsa-devel and it doesnt seem to have been resolved yet, so this is probably something that I'm going to have to wait for :P As a side note I'm using a Toshiba Satellite P100 and here is the bug report in alsa: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2106

LordRaiden
July 5th, 2006, 01:35 PM
I did a quick read of the notes section on the link you gave me.

Try this

open up /etc/modprobe.conf with a text editor (nano/gedit/kate)

paste in the following


alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0 model=basic
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel

then save.

do a reboot. Then see what happens.

shaviro
July 6th, 2006, 03:03 AM
I wasn't getting any sound out of my Sony Vaio PCG-4B1L

I followed the instructions in this guide; I got as far as successfully installing/compiling the correct alsa-driver for my machine; I then as instructed went back to step 4, and in the terminal I typed "sudo modprobe snd-" followed by tab and enter.... And I still got the message back:
FATAL: Module snd_ not found.
just like I did before I did the compilation.

Finally, I found the answer here:

http://www.ubuntuforums.org/showthread.php?t=153752&highlight=touchpad+sony.

The crucial thing is to enable everything in alsamixer EXCEPT "external amplifier." (I had to turn off microphone too, to stop feedback).

LordRaiden
July 6th, 2006, 05:41 AM
It's really more like pressing TAB a few times. This way, you see the full list of modules beginning with prefix "snd-". You would problem get an error for just "snd-" because there is no module by that name.

However, it is very interesting that just having "External Amplifier" disabled worked for you. I'll add that to my guide and give you credit for it.

Slurm
July 7th, 2006, 06:20 AM
Lord Raiden,

Excellent post, but I have an odd problem. I am running amd64 on an ASUS a8n motherboard with a built in soundcard.

lspci -v is the following:
0000:00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 225
I/O ports at dc00 [size=256]
I/O ports at e000 [size=256]
Memory at d5003000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

OK, I have surround sound speakers and only three of the six speakers work. (Left, Right,
Subwoofer). The other speakers don't work (Left rear, Right rear, Center speaker). They are not muted and I ran:

speaker-test -c6 -Dplug:surround51

and got white noise out of four of my speakers (Left, Right, Left Rear, Right Rear) and two didn't work (Subwoofer, and Center speaker).

The three speakers playback fine for both audio, video, mp3 anything. I guess I am a little greedy on wanting the others to work.

Any suggestions?

Slurm

Number6
July 7th, 2006, 08:07 AM
Thanks for this Lord Raiden, guys like you take alot of frustration out of setting up things like this in Linux

My problem is the sharing of the soundcard! Why is it that some programs can share the card and others can't? for example if I'm playing an mp3 on xmms, Gaim's sounds still come through OK but if i run say xmame, no sound! and vice versa also (sound xmame,no sound xmms!!) Is there no way aound this other than alsa-oss? I always thought ALSA was supposed to address this issue..

Im on amd64-64bit Ubuntu BTW

LordRaiden
July 7th, 2006, 05:26 PM
Slurm - Not greedy at all. Hmm.. you have checked alsamixer for the channel settings I suppose. Maybe a 5.1 setting? Also, remember to get any music player application to actually use 5.1. For example, I use amarok, and I can select my speaker set up from a dropdown box. I'll have to look into 5.1 or my guide (natural progression lol - getting soundcard to work --> getting 5.1 to work)


Number6 - make sure xmame is using alsa (if it can). ALSA lets applications share the soundcard whereas OSS does not. alsa-oss does address the issue the alsa way since alsa-oss is an alsa project. It is fine to use alsa-oss to get xmame to work (very little overhead if any).

tlaloczint
July 8th, 2006, 02:13 AM
ok I have sound working so far but it came some how its garble out

I am a newbie but I got this I hope that this help a little

tlaloc@aztlan:~$ lspci -v 0000:00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: <available only to root>

0000:00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
Subsystem: ASUSTeK Computer Inc.: Unknown device 815a
Flags: bus master, 66MHz, fast devsel, latency 0

0000:00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: 66MHz, fast devsel, IRQ 3
I/O ports at dc00 [size=32]
I/O ports at 4c00 [size=64]
I/O ports at 4c40 [size=64]
Capabilities: <available only to root>

0000:00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 233
Memory at d3103000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 50
Memory at feb00000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at f000 [size=16]
Capabilities: <available only to root>

0000:00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc.: Unknown device 815a
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
I/O ports at 09f0 [size=8]
I/O ports at 0bf0 [size=4]
I/O ports at 0970 [size=8]
I/O ports at 0b70 [size=4]
I/O ports at d800 [size=16]
Memory at d3102000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 225
I/O ports at 09e0 [size=8]
I/O ports at 0be0 [size=4]
I/O ports at 0960 [size=8]
I/O ports at 0b60 [size=4]
I/O ports at c400 [size=16]
Memory at d3101000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=128
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: d3000000-d30fffff

0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
Memory at d3100000 (32-bit, non-prefetchable) [size=4K]
I/O ports at b000 [size=8]
Capabilities: <available only to root>

0000:00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Capabilities: <available only to root>

0000:00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Capabilities: <available only to root>

0000:00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: <available only to root>

0000:00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00009000-00009fff
Memory behind bridge: d0000000-d2ffffff
Prefetchable memory behind bridge: 00000000c0000000-00000000cff00000
Capabilities: <available only to root>

0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: <available only to root>

0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel

0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0092 (rev a1) (prog-if 00 [VGA])
Subsystem: XFX Pine Group Inc.: Unknown device 2182
Flags: bus master, fast devsel, latency 0, IRQ 66
Memory at d0000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d1000000 (64-bit, non-prefetchable) [size=16M]
I/O ports at 9000 [size=128]
Expansion ROM at d2000000 [disabled] [size=128K]
Capabilities: <available only to root>

0000:05:06.0 Multimedia audio controller: Creative Labs SB Audigy LS
Subsystem: Creative Labs SB0410 SBLive! 24-bit
Flags: bus master, medium devsel, latency 32, IRQ 58
I/O ports at a000 [size=32]
Capabilities: <available only to root>

0000:05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, medium devsel, latency 32, IRQ 58
Memory at d3004000 (32-bit, non-prefetchable) [size=2K]
Memory at d3000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>

tlaloc@aztlan:~$

pinballkid
July 8th, 2006, 12:53 PM
I did a quick read of the notes section on the link you gave me.

Try this

open up /etc/modprobe.conf with a text editor (nano/gedit/kate)

paste in the following


alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0 model=basic
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel

then save.

do a reboot. Then see what happens.

Thanks for taking the time to look over that. Unfortunately I still dont hear any sound. It might be woth mentioning that under the playback section in alsamixer I now only see a PCM bar and nothing else, whereas I used to have a master bar as well.

(I may have that name wrong, but there was definitely another one)

Is there any more diagnosis that I can do to nail down the problem?

LordRaiden
July 9th, 2006, 07:09 AM
tlaloczint - I would not know why it would be garbled out? Did you follow my guide? If you did, I would suggest filing a bug in alsa-project (https://bugtrack.alsa-project.org) since they would better understand and are better able to to deal with that sort of problem.

pinballkid - check in your home directory whether or not you have a .asoundrc file (it's hidden). Assuming that aplay -l works your card is installed. But I am sure that other hda-intel users would at least get the Master volume and not just PCM. Did you get any warnings or errors at all?

pinballkid
July 9th, 2006, 04:22 PM
pinballkid - check in your home directory whether or not you have a .asoundrc file (it's hidden). Assuming that aplay -l works your card is installed. But I am sure that other hda-intel users would at least get the Master volume and not just PCM. Did you get any warnings or errors at all?

Just a few notes while I'm going through this:
aplay -l works and returns this:

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0

.asoundrc exists and contains the following:

Names of available sound cards:
Intel
stephen@stephen:~/pystarburst$ cat /home/stephen/.asoundrc
pcm.hda-intel {
type hw
card 0
}

ctl.hda-intel {
type hw
card 0
}

however, "asoundconf list" shows that there is an "Intel" card, but asoundconf is-active returns nothing.

Unfortunately I havn't noticed any warnings along the way in your tutorial, but I'm considering starting again to see if I catch any the second time round. Once again thanks for all the effort reading through other people's problems!

tailsfan
July 9th, 2006, 07:52 PM
Prob on that, alsa-project.org is loading up on my end, if anyone can help me I have a ESS 1869 Audiodrive.

Slurm
July 10th, 2006, 03:37 AM
Thank you again your Lordship for this help. I am using XMMS for playbac of files and I cannot find anywhere on their screen whether it supports surround5.1. Do you know if XMMS supports it and where I can make sure that it is optimized for surround?

But I also now have a newbie question for your. I went back to alsamixer and unmuted the button labelled 'duplicate' and lo and behold 5 out of six speakers are now working. Obviously the left rear and right rear are now duplicated what is coming out of the left and right speaker. (Newbie question warning) Is this duplicate the same as SurroundSound? I feel dumb asking this because is should not be. Then the next question is should I mute this and try to solve it in some other way.

At least I know that all speakers (except the center one) CAN work with the built in sound card.

Thanks again.
Slurm

LordRaiden
July 10th, 2006, 04:52 AM
pinballkid - delete the .asoundrc file, then reboot and try again.

Slurm - I wouldn't know if duplicate means Surround Sound, but like you say it should not. Try using the suggestion here http://www.linuxforums.org/forum/suse-linux-help/31275-5-1-surround-sound.html

post back if it works and i'll add it to my guide.

seethermtx
July 10th, 2006, 11:10 AM
Hi everyone.. just wanted to let you all know how I got my SPDIF sound working w/ my VIA8237 chipset in Kubuntu Dapper:

First, I brought the 'IEC958 Playback AC97-SP5A' fader in KMix (or alsamixser) all the way down to 0. I read in another thread that if it wasn't like this, it wouldn't work.

Next, I performed 'speaker-test -c6 -Dplug:surround51' .. when I looked at my Sony receiver it displayed the 'OPT' indicator.

Then, I control-c'd speaker-test and attempted to play 50 Cent's 'In Da Club' (not that that has anything to do with getting sound working.. just thought you would like to know :)) in Kaffeine.

It was very low (had to turn the receiver up to MAX to hear it), but that was fixed when I adjusted the 'VIA DXS' fader in KMix.


This was all done using a fresh install of Kubuntu. I'm using an Asus KV8 mobo w/ AMD64. I haven't actually rebooted since doing these things, so this might just be a temporary fix. Hope this helps.

Edit:
I rebooted and everything seems to be as it was. THe sound is working from Kaffeine, systems sounds, even from firefox's flash plugin (thanks Russian Girls, on Google VIdeo!)

pinballkid
July 11th, 2006, 12:04 AM
I've removed .asoundrc as you suggested and I am seeing one difference: when I start gnome-sound-properties now HDA-Intel appears under 'default sound card'. Unfortunately alsa-mixer still only shows PCM and there is still no sound, but I feel like I'm getting somewhere ;)

ivuntu
July 11th, 2006, 05:32 PM
Hi!

I followed your guide, it's very easy to follow for a newbie like me. In Breezy the sound worked perfectly, but when I upgraded to Dapper I got several problems, and the sound is one of them. I get stuck afte I installed the sound module and have to go to point 4 again sudo modprobe snd- gives nothing with TAB, if I fill in the used driver like this (sudo modprobe snd-intel8x0) it gives no output at all.

It does seem to load the sound driver into memory ( cat /proc/asound/modules gives the following output:
0 snd_intel8x0
1 snd_mpu401)

But it cannot find my soundcard. aplay -l gives:
aplay: device_list:221: no soundcards found...

I don't know what to make of this. Any suggestions are greatly appreciated!


here are a few outputs that might give a clue:


lspci -v
0000:00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0
Memory at e0000000 (32-bit, prefetchable) [size=256M]
Capabilities: <available only to root>

0000:00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0

0000:00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: 66MHz, fast devsel
I/O ports at 5080 [size=32]
I/O ports at 5000 [size=64]
I/O ports at 5040 [size=64]
Capabilities: <available only to root>

0000:00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 3
Memory at febfd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 9
Memory at febfe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
Memory at febffc00 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80a7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
Memory at febfc000 (32-bit, non-prefetchable) [size=4K]
I/O ports at ec00 [size=8]
Capabilities: <available only to root>

0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
Subsystem: ASUSTeK Computer Inc.: Unknown device 819d
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11
I/O ports at e800 [size=256]
I/O ports at e400 [size=128]
Memory at febfb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc.: Unknown device 813f
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at ffa0 [size=16]
Capabilities: <available only to root>

0000:00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=10
Memory behind bridge: faa00000-feafffff
Prefetchable memory behind bridge: ba900000-da8fffff

0000:00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=128

0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: <available only to root>

0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel

0000:01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2) (prog-if 00 [VGA])
Subsystem: XFX Pine Group Inc.: Unknown device 2119
Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 11
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: <available only to root>

I think the soundcard is recognized, but I am not sure!
I post here the output of dmesg also, it might help.
As you can see, there is more on my system that is not working (especially my usb Lexmark printer). But that is probably off-topic here (except if it is related, somehow)


dmesg
[17179569.184000] Linux version 2.6.15-26-386 (buildd@terranova) (gcc version 4. 0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Fri Jul 7 19:27:00 UTC 2006
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[17179569.184000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[17179569.184000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[17179569.184000] BIOS-e820: 0000000000100000 - 000000001ffc0000 (usable)
[17179569.184000] BIOS-e820: 000000001ffc0000 - 000000001ffd0000 (ACPI data)
[17179569.184000] BIOS-e820: 000000001ffd0000 - 0000000020000000 (ACPI NVS)
[17179569.184000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[17179569.184000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[17179569.184000] BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
[17179569.184000] 0MB HIGHMEM available.
[17179569.184000] 511MB LOWMEM available.
[17179569.184000] found SMP MP-table at 000ff780
[17179569.184000] On node 0 totalpages: 131008
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] DMA32 zone: 0 pages, LIFO batch:0
[17179569.184000] Normal zone: 126912 pages, LIFO batch:31
[17179569.184000] HighMem zone: 0 pages, LIFO batch:0
[17179569.184000] DMI 2.3 present.
[17179569.184000] ACPI: RSDP (v000 ACPIAM ) @ 0x0 00f9ed0
[17179569.184000] ACPI: RSDT (v001 A M I OEMRSDT 0x06000527 MSFT 0x00000097) @ 0x1ffc0000
[17179569.184000] ACPI: FADT (v002 A M I OEMFACP 0x06000527 MSFT 0x00000097) @ 0x1ffc0200
[17179569.184000] ACPI: OEMB (v001 A M I OEMBIOS 0x06000527 MSFT 0x00000097) @ 0x1ffd0040
[17179569.184000] ACPI: DSDT (v001 A0342 A0342003 0x00000003 INTL 0x02002026) @ 0x00000000
[17179569.184000] ACPI: PM-Timer IO Port: 0x4008
[17179569.184000] Intel MultiProcessor Specification v1.1
[17179569.184000] Virtual Wire compatibility mode.
[17179569.184000] OEM ID: TEMPLATE Product ID: APIC at: 0xFEE00000
[17179569.184000] Processor #0 15:12 APIC version 16
[17179569.184000] I/O APIC #1 Version 17 at 0xFEC00000.
[17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs
[17179569.184000] Processors: 1
[17179569.184000] Allocating PCI resources starting at 30000000 (gap: 20000000:d ec00000)
[17179569.184000] Built 1 zonelists
[17179569.184000] Kernel command line: root=/dev/hda1 ro noapic quiet splash
[17179569.184000] mapped APIC to ffffd000 (fee00000)
[17179569.184000] mapped IOAPIC to ffffc000 (fec00000)
[17179569.184000] Initializing CPU#0
[17179569.184000] PID hash table entries: 2048 (order: 11, 32768 bytes)
[17179569.184000] Detected 1607.974 MHz processor.
[17179569.184000] Using pmtmr for high-res timesource
[17179569.184000] Console: colour VGA+ 80x25
[17179571.916000] Dentry cache hash table entries: 131072 (order: 7, 524288 byte s)
[17179571.916000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179571.928000] Memory: 508596k/524032k available (1976k kernel code, 14800k r eserved, 606k data, 288k init, 0k highmem)
[17179571.928000] Checking if this processor honours the WP bit even in supervis or mode... Ok.
[17179572.008000] Calibrating delay using timer specific routine.. 3219.27 BogoM IPS (lpj=6438554)
[17179572.008000] Security Framework v1.0.0 initialized
[17179572.008000] SELinux: Disabled at boot.
[17179572.008000] Mount-cache hash table entries: 512
[17179572.008000] CPU: After generic identify, caps: 078bfbff e3d3fbff 00000000 00000000 00000001 00000000 00000001
[17179572.008000] CPU: After vendor identify, caps: 078bfbff e3d3fbff 00000000 0 0000000 00000001 00000000 00000001
[17179572.008000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/li ne)
[17179572.008000] CPU: L2 Cache: 256K (64 bytes/line)
[17179572.008000] CPU: After all inits, caps: 078bfbff e3d3fbff 00000000 0000041 0 00000001 00000000 00000001
[17179572.008000] mtrr: v2.0 (20020519)
[17179572.008000] CPU: AMD Sempron(tm) Processor 2800+ stepping 02
[17179572.008000] Enabling fast FPU save and restore... done.
[17179572.008000] Enabling unmasked SIMD FPU exception support... done.
[17179572.008000] Checking 'hlt' instruction... OK.
[17179572.024000] checking if image is initramfs... it is
[17179572.632000] Freeing initrd memory: 6616k freed
[17179572.640000] ACPI: Looking for DSDT ... not found!
[17179572.644000] ACPI: setting ELCR to 0200 (from 0e08)
[17179572.748000] NET: Registered protocol family 16
[17179572.748000] EISA bus registered
[17179572.748000] ACPI: bus type pci registered
[17179572.748000] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
[17179572.748000] PCI: Using configuration type 1
[17179572.748000] ACPI: Subsystem revision 20051216
[17179572.752000] ACPI: Interpreter enabled
[17179572.752000] ACPI: Using PIC for interrupt routing
[17179572.752000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[17179572.752000] PCI: Probing PCI hardware (bus 00)
[17179572.756000] Boot video device is 0000:01:00.0
[17179572.756000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[17179572.768000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[17179572.768000] ACPI: Power Resource [ISAV] (on)
[17179572.772000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 11 12 14 15 ) *0, disabled.
[17179572.772000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 11 12 14 15 ) *0, disabled.
[17179572.772000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 11 12 14 15) * 0, disabled.
[17179572.772000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 11 12 14 15 ) *0, disabled.
[17179572.772000] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12 14 1 5)
[17179572.772000] ACPI: PCI Interrupt Link [LUS0] (IRQs *3 4 5 7 9 10 11 12 14 1 5)
[17179572.772000] ACPI: PCI Interrupt Link [LUS1] (IRQs 3 4 5 7 *9 10 11 12 14 1 5)
[17179572.772000] ACPI: PCI Interrupt Link [LUS2] (IRQs 3 4 5 7 9 *10 11 12 14 1 5)
[17179572.772000] ACPI: PCI Interrupt Link [LKLN] (IRQs 3 4 5 7 9 *10 11 12 14 1 5)
[17179572.772000] ACPI: PCI Interrupt Link [LAUI] (IRQs 3 4 5 7 9 10 *11 12 14 1 5)
[17179572.776000] ACPI: PCI Interrupt Link [LKMO] (IRQs 3 4 5 7 9 10 11 12 14 15 ) *0, disabled.
[17179572.776000] ACPI: PCI Interrupt Link [LKSM] (IRQs 3 4 5 7 9 10 11 12 14 15 ) *0, disabled.
[17179572.776000] ACPI: PCI Interrupt Link [LTID] (IRQs 10) *0, disabled.
[17179572.776000] ACPI: PCI Interrupt Link [LTIE] (IRQs 10) *0, disabled.
[17179572.776000] ACPI: PCI Interrupt Link [LATA] (IRQs 3 4 6 7 10 11 12 *14 15)
[17179572.776000] Linux Plug and Play Support v0.97 (c) Adam Belay
[17179572.776000] pnp: PnP ACPI init
[17179572.784000] pnp: PnP ACPI: found 15 devices
[17179572.784000] PnPBIOS: Disabled by ACPI PNP
[17179572.784000] PCI: Using ACPI for IRQ routing
[17179572.784000] PCI: If a device doesn't work, try "pci=routeirq". If it help s, post a report
[17179572.788000] pnp: 00:0b: ioport range 0x480-0x487 has been reserved
[17179572.788000] pnp: 00:0b: ioport range 0xd00-0xd07 has been reserved
[17179572.788000] PCI: Bridge: 0000:00:0b.0
[17179572.788000] IO window: disabled.
[17179572.788000] MEM window: faa00000-feafffff
[17179572.788000] PREFETCH window: ba900000-da8fffff
[17179572.788000] PCI: Bridge: 0000:00:0e.0
[17179572.788000] IO window: disabled.
[17179572.788000] MEM window: disabled.
[17179572.788000] PREFETCH window: disabled.
[17179572.788000] PCI: Setting latency timer of device 0000:00:0e.0 to 64
[17179572.788000] audit: initializing netlink socket (disabled)
[17179572.788000] audit(1152634115.788:1): initialized
[17179572.788000] VFS: Disk quotas dquot_6.5.1
[17179572.788000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[17179572.788000] Initializing Cryptographic API
[17179572.788000] io scheduler noop registered
[17179572.788000] io scheduler anticipatory registered
[17179572.788000] io scheduler deadline registered
[17179572.788000] io scheduler cfq registered
[17179572.788000] isapnp: Scanning for PnP cards...
[17179573.144000] isapnp: No Plug & Play device found
[17179573.156000] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[17179573.156000] PNP: PS/2 controller doesn't have AUX irq; using default 12
[17179573.156000] serio: i8042 AUX port at 0x60,0x64 irq 12
[17179573.156000] serio: i8042 KBD port at 0x60,0x64 irq 1
[17179573.156000] Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ shar ing enabled
[17179573.156000] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179573.160000] 00:0d: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179573.160000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 b locksize
[17179573.160000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179573.160000] ide: Assuming 33MHz system bus speed for PIO modes; override w ith idebus=xx
[17179573.160000] mice: PS/2 mouse device common for all mice
[17179573.160000] EISA: Probing bus 0 at eisa.0
[17179573.160000] Cannot allocate resource for EISA slot 4
[17179573.160000] Cannot allocate resource for EISA slot 5
[17179573.160000] EISA: Detected 0 cards.
[17179573.160000] NET: Registered protocol family 2
[17179573.196000] IP route cache hash table entries: 8192 (order: 3, 32768 bytes )
[17179573.196000] TCP established hash table entries: 32768 (order: 5, 131072 by tes)
[17179573.196000] TCP bind hash table entries: 32768 (order: 5, 131072 bytes)
[17179573.196000] TCP: Hash tables configured (established 32768 bind 32768)
[17179573.196000] TCP reno registered
[17179573.196000] TCP bic registered
[17179573.196000] NET: Registered protocol family 1
[17179573.196000] NET: Registered protocol family 8
[17179573.196000] NET: Registered protocol family 20
[17179573.196000] Using IPI Shortcut mode
[17179573.196000] ACPI wakeup devices:
[17179573.196000] PS2K UAR1 USB0 MAC USB1 USB2 P0P1
[17179573.196000] ACPI: (supports S0 S1 S3 S4 S5)
[17179573.196000] Freeing unused kernel memory: 288k freed
[17179573.240000] vga16fb: initializing
[17179573.240000] vga16fb: mapped to 0xc00a0000
[17179573.348000] input: AT Translated Set 2 keyboard as /class/input/input0
[17179573.656000] Console: switching to colour frame buffer device 80x25
[17179573.656000] fb0: VGA16 VGA frame buffer device
[17179574.976000] Capability LSM initialized
[17179575.736000] SCSI subsystem initialized
[17179575.736000] ACPI: bus type scsi registered
[17179575.736000] libata version 1.20 loaded.
[17179575.740000] NFORCE3-250: IDE controller at PCI slot 0000:00:08.0
[17179575.740000] NFORCE3-250: chipset revision 162
[17179575.740000] NFORCE3-250: not 100% native mode: will probe irqs later
[17179575.740000] NFORCE3-250: BIOS didn't set cable bits correctly. Enabling wo rkaround.
[17179575.740000] NFORCE3-250: 0000:00:08.0 (rev a2) UDMA133 controller
[17179575.740000] ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb :DMA
[17179575.740000] ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd :DMA
[17179575.740000] Probing IDE interface ide0...
[17179576.028000] hda: MAXTOR 6L040J2, ATA DISK drive
[17179576.308000] hdb: Maxtor 5T020H2, ATA DISK drive
[17179576.364000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179576.364000] Probing IDE interface ide1...
[17179577.100000] hdc: HL-DT-ST DVDRAM GSA-4167B, ATAPI CD/DVD-ROM drive
[17179577.884000] hdd: LITE-ON LTR-32123S, ATAPI CD/DVD-ROM drive
[17179577.940000] ide1 at 0x170-0x177,0x376 on irq 15
[17179577.948000] hda: max request size: 128KiB
[17179577.964000] hda: 78177792 sectors (40027 MB) w/1818KiB Cache, CHS=65535/16 /63, UDMA(133)
[17179577.964000] hda: cache flushes supported
[17179577.964000] hda: hda1 hda2 < hda5 hda6 > hda3 hda4
[17179577.992000] hdb: max request size: 128KiB
[17179577.992000] hdb: 40021632 sectors (20491 MB) w/2048KiB Cache, CHS=39704/16 /63, UDMA(100)
[17179577.992000] hdb: cache flushes not supported
[17179577.992000] hdb: hdb1
[17179578.000000] hdc: ATAPI 79X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179578.000000] Uniform CD-ROM driver Revision: 3.20
[17179578.008000] hdd: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179578.504000] usbcore: registered new driver usbfs
[17179578.504000] usbcore: registered new driver hub
[17179578.504000] ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
[17179578.504000] **** SET: Misaligned resource pointer: de8aa9c2 Type 07 Len 0
[17179578.504000] ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 3
[17179578.504000] PCI: setting IRQ 3 as level-triggered
[17179578.504000] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 3 (l evel, low) -> IRQ 3
[17179578.504000] PCI: Setting latency timer of device 0000:00:02.0 to 64
[17179578.504000] ohci_hcd 0000:00:02.0: OHCI Host Controller
[17179578.936000] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus nu mber 1
[17179578.936000] ohci_hcd 0000:00:02.0: irq 3, io mem 0xfebfd000
[17179578.968000] forcedeth.c: Reverse Engineered nForce ethernet driver. Versio n 0.54.
[17179578.992000] hub 1-0:1.0: USB hub found
[17179578.992000] hub 1-0:1.0: 4 ports detected
[17179579.096000] **** SET: Misaligned resource pointer: de8aa6c2 Type 07 Len 0
[17179579.096000] ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 9
[17179579.096000] PCI: setting IRQ 9 as level-triggered
[17179579.096000] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS1] -> GSI 9 (l evel, low) -> IRQ 9
[17179579.096000] PCI: Setting latency timer of device 0000:00:02.1 to 64
[17179579.096000] ohci_hcd 0000:00:02.1: OHCI Host Controller
[17179579.112000] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus nu mber 2
[17179579.112000] ohci_hcd 0000:00:02.1: irq 9, io mem 0xfebfe000
[17179579.168000] hub 2-0:1.0: USB hub found
[17179579.168000] hub 2-0:1.0: 4 ports detected
[17179579.272000] **** SET: Misaligned resource pointer: de8aa3c2 Type 07 Len 0
[17179579.272000] ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 10
[17179579.272000] PCI: setting IRQ 10 as level-triggered
[17179579.272000] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUS2] -> GSI 10 ( level, low) -> IRQ 10
[17179579.272000] PCI: Setting latency timer of device 0000:00:02.2 to 64
[17179579.272000] ehci_hcd 0000:00:02.2: EHCI Host Controller
[17179579.272000] ehci_hcd 0000:00:02.2: debug port 1
[17179579.272000] PCI: cache line size of 64 is not supported by device 0000:00: 02.2
[17179579.272000] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus nu mber 3
[17179579.272000] ehci_hcd 0000:00:02.2: irq 10, io mem 0xfebffc00
[17179579.272000] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 D ec 2004
[17179579.272000] hub 3-0:1.0: USB hub found
[17179579.272000] hub 3-0:1.0: 8 ports detected
[17179579.376000] **** SET: Misaligned resource pointer: de8aa0c2 Type 07 Len 0
[17179579.376000] ACPI: PCI Interrupt Link [LKLN] enabled at IRQ 10
[17179579.376000] ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LKLN] -> GSI 10 ( level, low) -> IRQ 10
[17179579.376000] PCI: Setting latency timer of device 0000:00:05.0 to 64
[17179579.896000] eth0: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:05.0
[17179579.968000] ohci_hcd 0000:00:02.1: wakeup
[17179580.024000] Attempting manual resume
[17179580.052000] kjournald starting. Commit interval 5 seconds
[17179580.052000] EXT3-fs: mounted filesystem with ordered data mode.
[17179580.352000] usb 2-2: new low speed USB device using ohci_hcd and address 2
[17179580.572000] ohci_hcd 0000:00:02.0: wakeup
[17179580.956000] usb 1-3: new low speed USB device using ohci_hcd and address 3
[17179581.140000] usb 1-3: device descriptor read/64, error -110
[17179581.424000] usb 1-3: device descriptor read/64, error -110
[17179581.704000] usb 1-3: new low speed USB device using ohci_hcd and address 4
[17179581.884000] usb 1-3: device descriptor read/64, error -110
[17179582.168000] usb 1-3: device descriptor read/64, error -110
[17179582.448000] usb 1-3: new low speed USB device using ohci_hcd and address 5
[17179582.856000] usb 1-3: device not accepting address 5, error -110
[17179583.032000] usb 1-3: new low speed USB device using ohci_hcd and address 6
[17179583.440000] usb 1-3: device not accepting address 6, error -110
[17179590.368000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179590.368000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179590.412000] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000
[17179590.412000] i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5040
[17179590.700000] usbcore: registered new driver hiddev
[17179590.708000] input: USB Scroll Mouse as /class/input/input1
[17179590.708000] input: USB HID v1.00 Mouse [USB Scroll Mouse] on usb-0000:00:0 2.1-2
[17179590.708000] usbcore: registered new driver usbhid
[17179590.708000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179590.716000] **** SET: Misaligned resource pointer: dd4609c2 Type 07 Len 0
[17179590.716000] ACPI: PCI Interrupt Link [LAUI] enabled at IRQ 11
[17179590.716000] PCI: setting IRQ 11 as level-triggered
[17179590.716000] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LAUI] -> GSI 11 ( level, low) -> IRQ 11
[17179590.716000] PCI: Setting latency timer of device 0000:00:06.0 to 64
[17179590.732000] Linux agpgart interface v0.101 (c) Dave Jones
[17179590.736000] agpgart: Detected AGP bridge 0
[17179590.736000] agpgart: Setting up Nforce3 AGP.
[17179590.784000] Real Time Clock Driver v1.12
[17179590.816000] input: PC Speaker as /class/input/input2
[17179590.948000] NET: Registered protocol family 17
[17179591.020000] parport: PnPBIOS parport detected.
[17179591.020000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRIST ATE,COMPAT,ECP,DMA]
[17179591.036000] intel8x0_measure_ac97_clock: measured 54614 usecs
[17179591.036000] intel8x0: clocking to 46952
[17179591.176000] FDC 0 is a post-1991 82077
[17179591.288000] ts: Compaq touchscreen protocol output
[17179592.732000] Intel ISA PCIC probe: not found.
[17179593.244000] lp0: using parport0 (interrupt-driven).
[17179593.892000] it87: Found IT8712F chip at 0xd00, revision 7
[17179593.940000] Adding 1951856k swap on /dev/hda5. Priority:-1 extents:1 acro ss:1951856k
[17179594.268000] EXT3 FS on hda1, internal journal
[17179594.420000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@ redhat.com
[17179594.792000] md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179594.792000] md: bitmap version 4.39
[17179599.540000] NET: Registered protocol family 10
[17179599.540000] lo: Disabled Privacy Extensions
[17179599.544000] IPv6 over IPv4 tunneling driver
[17179602.264000] kjournald starting. Commit interval 5 seconds
[17179602.264000] EXT3 FS on hda6, internal journal
[17179602.264000] EXT3-fs: mounted filesystem with ordered data mode.
[17179602.304000] NTFS driver 2.1.25 [Flags: R/O MODULE].
[17179602.348000] NTFS volume version 3.1.
[17179604.276000] ACPI: Power Button (FF) [PWRF]
[17179604.276000] ACPI: Power Button (CM) [PWRB]
[17179604.376000] ibm_acpi: ec object not found
[17179604.408000] pcc_acpi: loading...
[17179605.100000] powernow-k8: Power state transitions not supported
[17179608.740000] cdrom: This disc doesn't have any tracks I recognize!
[17179609.924000] eth0: no IPv6 routers present
[17179610.804000] ppdev: user-space parallel port driver
[17179614.244000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[17179614.244000] apm: overridden by ACPI.
[17179614.404000] ip_tables: (C) 2000-2002 Netfilter core team
[17179614.488000] Netfilter messages via NETLINK v0.30.
[17179614.500000] ip_conntrack version 2.4 (4094 buckets, 32752 max) - 232 bytes per conntrack
[17179620.792000] Bluetooth: Core ver 2.8
[17179620.792000] NET: Registered protocol family 31
[17179620.792000] Bluetooth: HCI device and connection manager initialized
[17179620.792000] Bluetooth: HCI socket layer initialized
[17179620.804000] Bluetooth: L2CAP ver 2.8
[17179620.804000] Bluetooth: L2CAP socket layer initialized
[17179620.808000] Bluetooth: RFCOMM socket layer initialized
[17179620.808000] Bluetooth: RFCOMM TTY layer initialized
[17179620.808000] Bluetooth: RFCOMM ver 1.7

LordRaiden
July 11th, 2006, 06:12 PM
pinballkid - keep at it. I think you are close.
ivuntu - paste results of the command
lsmod | grep snd here.

I will add a section to my guide about how to reinstall and the kernel modules using apt-get from scratch soon.

I also would like some feedback about the MIDI guide. Is it working for anyone of you? Any things you think I should add?

ivuntu
July 11th, 2006, 08:29 PM
lsmod | grep snd [/CODE] here.



Lordraiden,

thanks for replying,
here is the output of the command above:


snd_mpu401 6728 0
snd_mpu401_uart 7808 1 snd_mpu401
snd_rawmidi 25504 1 snd_mpu401_uart
snd_seq_device 8716 1 snd_rawmidi
snd_intel8x0 33692 0
snd_ac97_codec 93088 1 snd_intel8x0
snd_ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25220 1 snd_pcm
snd 55268 10 snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_dev ice,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mi xer_oss,snd_pcm,snd_timer
soundcore 10208 1 snd
snd_page_alloc 10632 2 snd_intel8x0,snd_pcm


hmmm:-k

tlaloczint
July 12th, 2006, 02:16 AM
[QUOTE=LordRaiden;1231407]tlaloczint - I would not know why it would be garbled out? Did you follow my guide? If you did, I would suggest filing a bug in alsa-project (https://bugtrack.alsa-project.org) since they would better understand and are better able to to deal with that sort of problem.

yep I did fowollow your guide and after a few reboots (my wife use xp for gaming) all started to sound better and now its good really good I really don`t know what was it but thanks this is the first time I make a soundblaster work that good ( with your guide of curse)
thanks keep the good job

Juan Orozco
July 12th, 2006, 05:51 AM
Great guide! i'm a newbie and am having probs with my soud card, went up to step 2 but ubuntu seems not to recognize the card (integrated) i went to the bios and everything seems ok, it works on XP (which i have in a totaly separate hdrive) also, tried researching what my sound card was and i think its a Crystal 4237b (found at dells by searching for my system Presicion 410 Pentium 3), any idea on what should i do next? -thanks for your time>


-better look stupid once than stay stupid forever

Bmbshl
July 12th, 2006, 06:41 AM
Whew.....my sound works....thanks sooooo much....nice tutorial. I'm starting to think I might really be able to do this whole Linux thing. My husband has stopped laughing at me and my kids don't call it "broken" anymore...lol. I think I'm getting somewhere.

KillrBuckeye
July 12th, 2006, 12:03 PM
Could somebody explain how I would go about applying a patch to ALSA? I have a problem with low sound capture levels, and somebody posted a patch on the bugtracking site, but I have no idea what to do with it. Is this process too difficult for a Linux newb?

ivuntu
July 12th, 2006, 03:28 PM
Lordraiden,

thanks for replying,
here is the output of the command above:


snd_mpu401 6728 0
snd_mpu401_uart 7808 1 snd_mpu401
snd_rawmidi 25504 1 snd_mpu401_uart
snd_seq_device 8716 1 snd_rawmidi
snd_intel8x0 33692 0
snd_ac97_codec 93088 1 snd_intel8x0
snd_ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25220 1 snd_pcm
snd 55268 10 snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_dev ice,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mi xer_oss,snd_pcm,snd_timer
soundcore 10208 1 snd
snd_page_alloc 10632 2 snd_intel8x0,snd_pcm


hmmm:-k

Hi again, I just rebooted my pc a couple of times, and now suddenly the soundcard is recognized and the sound works. I don't think I changed anything else, so it's a little mysterious. Thanks anyway very much for your help!

foxhound_oki
July 12th, 2006, 05:09 PM
hi there.... im am having a fustrated time getting ubuntu to work with my sound card. i dj and i perfer to use ubuntu over windows to do my job. i installed the cd about two months ago and found that the sound wasn't working. it gave me the error that i don't have the sound card installed or drivers inplace when you click the sound icon on the desktop. i have gone throught the steps of this guide and still not working. here is my output from the first few step. could someone help me please.

sean@foxubuntu1:~$ aplay -l
aplay: device_list:218: no soundcards found...
sean@foxubuntu1:~$ lspci -v
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
Flags: bus master, medium devsel, latency 64
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro13 3x AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fca00000-feafffff
Prefetchable memory behind bridge: e4800000-e48fffff

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 06)
Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0

0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT82 3x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at ffa0 [size=16]

0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Contr oller (rev 02) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at e800 [size=32]

0000:00:07.3 Bridge: VIA Technologies, Inc. VT82C596 Power Management
Flags: medium devsel

0000:00:12.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Ra deon 7500] (prog-if 00 [VGA])
Subsystem: C.P. Technology Co. Ltd RV200 QW [Radeon 7500 PCI Dual Displa y]
Flags: bus master, stepping, medium devsel, latency 64, IRQ 11
Memory at f0000000 (32-bit, prefetchable) [size=128M]
I/O ports at ee00 [size=256]
Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at febc0000 [disabled] [size=128K]
Capabilities: <available only to root>

0000:00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C /8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at ea00 [size=256]
Memory at febeff00 (32-bit, non-prefetchable) [size=256]
Expansion ROM at febb0000 [disabled] [size=64K]

0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (re v 7a) (prog-if 00 [VGA])
Flags: bus master, stepping, medium devsel, latency 0
Memory at fd000000 (32-bit, non-prefetchable) [disabled] [size=16M]
I/O ports at <ignored> [disabled]
Memory at fca00000 (32-bit, non-prefetchable) [disabled] [size=4K]
Expansion ROM at fffe0000 [disabled] [size=128K]
Capabilities: <available only to root>

sean@foxubuntu1:~$ sudo modprobe snd-via82xx
WARNING: Error inserting snd_ac97_bus (/lib/modules/2.6.12-10-386/kernel/sound/p ci/ac97/snd-ac97-bus.ko): Invalid module format

please, someone help me.:confused:

Zacrifyer
July 12th, 2006, 07:16 PM
Great guide! i'm a newbie and am having probs with my soud card, went up to step 2 but ubuntu seems not to recognize the card (integrated) i went to the bios and everything seems ok, it works on XP (which i have in a totaly separate hdrive) also, tried researching what my sound card was and i think its a Crystal 4237b (found at dells by searching for my system Presicion 410 Pentium 3), any idea on what should i do next? -thanks for your time>


-better look stupid once than stay stupid forever

Ohh, i have exactly the same problem :/ hope someone can help.

gratefultux
July 12th, 2006, 08:40 PM
After I upgraded to Dapper, my soundcard just stopped working. After doing lots of research I was really excited to find this guide. The compile went smoothly, but no sound. So I spent a couple of weeks trying things, without much success. I decided to start from the beginning. I uninstalled linux-sound-base, alsa-base, and alsa-utils.
Reinstalled them and did:
modprobe snd-[TAB], that didn't yield anything, so i did,
modprobe snd-pcm-oss
modprobe snd-mixer-oss
modprobe snd-seq-oss
modprobe snd-DRIVER (in my case it's snd-ens1371)
then i unmuted the main channel in alsamixer and it worked.

The problem i have now is that i have to repeat all the modprobe stuff after reboot. I wrote a script so that it's just one command, but i would still like to have them load at boot. Is that possible, or do i have to stick with the script?

pinballkid
July 12th, 2006, 10:34 PM
hda-intel seems to be pretty notorious on ubuntu. Anyone know if the ubuntu team plans to provide a fix for it? (still no luck here)

nobodysdarling
July 13th, 2006, 02:07 AM
My sound is working just fine , but I cannot get the multimedia keys on my Sony Vaio VGN-FE550G to control all app's . I have to control volume via the app , or ALSA . I would like to have the multimedia volume key's as the master volume which I am accustomed to .

ro314
July 13th, 2006, 08:26 AM
I followed your instructions in section "stopping multiple soundcards from switching" - and it did exactly what is was supposed to do :)
(My soundcard and my usb-headset were switching)
Tanks a million for your guide!

ro314

PS: Maybe you could mention the "dash/underscore-thing" in this section of the guide?

deathseeker25
July 13th, 2006, 12:41 PM
I've been following the guide until now, but when i try the command sudo alsamixer, an error appears in the console:


ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback Volume',0,0,0) appears twice or more

alsamixer: function snd_mixer_load failed: Invalid argument


I'm a newbie in Ubuntu, so I don't know how to solve this problem. Can you give me a hand?;)

LordRaiden
July 13th, 2006, 03:04 PM
Bmbshl, ivuntu, & tlaloczint - Congratulations on getting it to work!

Juan Orozco & Zacrifyer - Your driver is snd-cs4236 driver. I recommend you try compiling that from source using my guide.

foxhound_oki - Your soundcard seems to use the snd-via82xx . I recommend you try compiling that from source using my guide.

gratefultux - Do
sudo nano /etc/modules Add the line 'snd-ens1371' to after the last line in the file (you will only need this one line). Save the file, then do a reboot. The module should get loaded on boot. So it worked without touching the kernel? Great! I'll remove the part about it now.

pinballkid - the Ubuntu team does not work on alsa directly (maybe committing a patches). You should report your issue as a bug and they will be able to give you a solution. (The people who support the hda-intel driver get a bit busy so don't be worried if you don't get a response right away).

nobodysdarling - I have a link to the multimediakeys guide in the USDF at the bottom of my guide. Have a look, I successfully managed to configure my multimedia keyboard with using it.

ro314 - Congratulations and I'll add the dash-underscore thing in my guide.

deathseeker25 - I suggest you try the *fresh* install section near the end of my guide. (It's not really a reinstall so no worries).

gratefultux
July 13th, 2006, 03:16 PM
Sweet, my sound works now.
~Thanks a bunch~

Zacrifyer
July 13th, 2006, 04:06 PM
Thanks a lot, it works perfectly now :)

Bo Rosén
July 13th, 2006, 07:28 PM
Thanks to http://ubuntuforums.org/showthread.php?t=127402 this post I got soundblaster 16 isa working.
In short add


snd-sb16
to /etc/modules

then create a new file:


gedit /etc/modprobe.d/sound
and enter this line:


options snd-sb16 isapnp=0 port=0x220 irq=5 dma8=1 dma16=5

EDIT: Then
sudo update-modules reboot

LordRaiden
July 13th, 2006, 07:44 PM
gratefultux & Zacrifyer - Congrats on getting it to work.

Bo Rosén - I'll add your instructions to the Miscellaneous section in my guide and give you credit it for it.

Bo Rosén
July 13th, 2006, 08:09 PM
Credit should probably go to FarEast whose instructions I stole from the thread I mentioned

JayBachatero
July 13th, 2006, 08:55 PM
This is great. I tried this and when I hit reboot guess what. My whole damn desktop is GONE. Now I'm going to have to try and fix it. >_<

Bo Rosén
July 13th, 2006, 09:42 PM
This is great. I tried this and when I hit reboot guess what. My whole damn desktop is GONE. Now I'm going to have to try and fix it. >_<

:-( Sorry to hear that. All I can say is that it worked for me.
Hm, looking at the instructions again from FarEast I see I forgot to add that you should


sudo update-modules
before rebooting.:oops:

I'm really sorry if this caused your problems, though it seems a bit strange if it could make the whole desktop go awol. Strangers things have happened though. Hope you manage to fix it.

JayBachatero
July 14th, 2006, 06:57 AM
It's ok. I had to reinstall gdm, gnome, nautilus an a mess of other things. I think I'll try to fix my sound when I get a new sound card cause it's been giving me problems ever since i upgraded to Dapper.

Nexusx6
July 14th, 2006, 08:57 AM
I'm having trouble with my sound card in that its not coming out as loud as it should. What I mean is that when I twirl the dial to max sound comes out as just "average' instead of "omg my ears are going to blow!' (lol) know what I mean?

When I tried to use this guide to see if I could find the problem, I ran into another one; after typing in "aplay -" terminal doesn't respond with aything. Just sits there with the blinking cursor on the next line down and won't respond to any other commands save for ctrl+c.

I set all the volume bars in Linux to full (the options brought up by clicking the speaker in the corner and the volume bars within the music players) so I know its not that. Thanks in advance for the help :)

gratefultux
July 14th, 2006, 06:18 PM
Well, as long as your sound works, i guess aplay doesn't like you ;) .
Try turning up the master volume in alsamixer to get more sound.

jonjpeterson
July 14th, 2006, 09:13 PM
I've got no sound and I'm trying to use this Guide to get it back

~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: V8235 [VIA 8235], device 0: VIA 8235 [VIA 8235]
Subdevices: 3/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: V8235 [VIA 8235], device 1: VIA 8235 [VIA 8235]
Subdevices: 1/1
Subdevice #0: subdevice #0



So I figure everything should work - right, but nothing gives me sound. When I type in alsamixer everything is turned on (except ext amp, aux, and the mic). Can anyone help me get my sound working. I'm really new so I don't know if there is a conf problem that I need to fix or what. I'd love an auto fix, but easyubuntu or automatix hasn't helped any at all. Please help.

LordRaiden
July 15th, 2006, 04:12 AM
jonjpeterson - use the *fresh* kernel method in my guide. It worked best for me.

DataInfusions
July 15th, 2006, 04:38 AM
Don't know if this will help anyone, but I had problems getting sound to play through MPD. it would always come back saying it couldn't open the sound driver (or equivalent..)
So i went through this post and everything looked ok. my card seemed to be recognised and set up. (aplay -l came out positive)
But as soon as I told MPD to play. the card wouldn't be loaded anymore (aplay -l would say no devices found).
I didn't try to run anyother music programs to try to see if it was only MPD (the machine I was doing this on is literally a box siting next to the stereo , no keyboard or monitor, everything done via SSH...).

So here I was tearing my dreadlocks out, when I read a little sentence in someone's blog... "make sure your audio program (that uses alsa) is part of the audio users group.."
light bulb went up, and after a judicious :
sudo adduser mpd audio

it all worked perfectly. :-D

This post is probably no quite in the right place (not a hardware issue) but I thought I'd share this incase someone out there is having similar problems...

-D.I.F-

PS - This is only good because MPD was runing as its own user (mpd). if you are just trying to run progs through your normal user, check if your user is in the audio group... (nice GUI for it in GNome somewhere)...

Renko
July 15th, 2006, 09:51 AM
This is great. I tried this and when I hit reboot guess what. My whole damn desktop is GONE. Now I'm going to have to try and fix it. >_<

Yes. This happened here too. I was ablo to fix it by running this commands:

sudo apt-get install gdm
sudo apt-get install ubuntu-desktop

A warning has to be added in the first post of this topic, not everyone will be able to restore their Ubuntu desktop.

apocalypso
July 15th, 2006, 08:37 PM
Thanks for the help provided by this thread, I used the "fresh kernel" method, though I must add that I also second the notion that you must include the warning about having to reinstall the whole gdm and Gnome stuff. In my case I had to run:

sudo apt-get install gdm gnome-applets gnome-control-center gnome-panel
gnome-session gnome-terminal nautilus ubuntu-base ubuntu-desktop
ubuntu-minimal linux-sound-base alsa-base alsa-utils
as all of that was uninstalled by purging/removing linux-sound-base, alsa-base and alsa-utils. :-k
On a side note I want to add that I had a previous working installation of Dapper running on a dedicated 20Gb ATA drive, which run as slave of DVD-R drive, with Windoze running on a Master ATA drive - all of this based on a PIII-933 machine with an Intel 815 mobo. Installation was a breeze then and everything ran out of the box.
Now this time around I built a whole new machine, PD-805 (2,66) with an Intel 945Gtp mobo and a SATA drive with two partitions, one for Windowz and the other one for Ubuntu and, unfortunately, things haven't been that smooth now - I've had trouble with Grub, with the video and now with the sound... ](*,)

Anyway, what really matters is that, in the end, everything gets fixed, with a lot of help from the mates here at Ubuntu Forums, so thanks a lot to all of you!!! :D

bkbaker
July 15th, 2006, 11:00 PM
It worked!:KS :KS :KS

gratefultux
July 15th, 2006, 11:09 PM
That's odd. I did the clean kernel thing as well, and nothing was uninstalled. I'm using Kubuntu, but that shouldn't make a difference. Did it tell any of you that it was uninstalling any other packages?

jonjpeterson
July 16th, 2006, 01:15 AM
Okay I did the new kernal. Like others I lost gdm and the desktop (thanks Renko for getting that up and running again). I still have no sound though, so what's the next step if I put in a whole new kernal. Should I continue to follow the steps in this guide even though I have success right from ~$ aplay -

Xizorbg
July 16th, 2006, 01:22 AM
Hi there-

I am running Dapper Drake on an AMD64 CPU. Sound works okay...BUT.....I have an M-Audio Revolution 7.1. I can get the sound to play out of my SPDIF connection, and Skype will use the regular audio out. Does ANYONE know how I can get the sound to come out of BOTH the Analog AND Digital OUTS???

Thanks everyone,
X

jonjpeterson
July 16th, 2006, 01:46 AM
I'm trying to follow the guide step by step and after I do the dpkg-reconfigure alsa-source I type in the following and get

:~$ sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=via82xx --with-oss=yes
sudo: ./configure: command not found

I don't know if I changed the command wrong or wheather I was supposed to make other changes as well.

LordRaiden
July 16th, 2006, 02:41 AM
Renko - I'm running Kubuntu so I did not get gdm or ubuntu-desktop removed. I'll put in the warnning but I think this a gdm and ubuntu-desktop should not depend on any of the packages I ask to remove (they really are not related).

jonjpeterson - if you have success from aplay then there is no need to do anything after the *fresh* install.

smbrow14
July 16th, 2006, 04:39 PM
I'm not having any success getting sound to work with Dapper.

Output from aplay -l



**** List of PLAYBACK Hardware Devices ****
card 0: V8237 [VIA 8237], device 0: VIA 8237 [VIA 8237]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: V8237 [VIA 8237], device 1: VIA 8237 [VIA 8237]
Subdevices: 1/1
Subdevice #0: subdevice #0


Full output from lspci -v


0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
Subsystem: ASUSTeK Computer Inc.: Unknown device 8118
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e8000000-e9ffffff
Prefetchable memory behind bridge: e4000000-e7ffffff
Capabilities: <available only to root>

0000:00:0a.0 Communication controller: Agere Systems V.92 56K WinModem (rev 03)
Subsystem: Agere Systems: Unknown device 044c
Flags: bus master, medium devsel, latency 32, IRQ 255
Memory at ea000000 (32-bit, non-prefetchable) [size=256]
I/O ports at a000 [size=8]
I/O ports at a400 [size=256]
Capabilities: <available only to root>

0000:00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc.: Unknown device 808a
Flags: bus master, medium devsel, latency 32, IRQ 177
Memory at ea001000 (32-bit, non-prefetchable) [size=2K]
I/O ports at a800 [size=128]
Capabilities: <available only to root>

0000:00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V Deluxe/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 169
I/O ports at ac00 [size=8]
I/O ports at b000 [size=4]
I/O ports at b400 [size=8]
I/O ports at b800 [size=4]
I/O ports at bc00 [size=16]
I/O ports at c000 [size=256]
Capabilities: <available only to root>

0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 169
I/O ports at c400 [size=16]
Capabilities: <available only to root>

0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 185
I/O ports at c800 [size=32]
Capabilities: <available only to root>

0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 185
I/O ports at cc00 [size=32]
Capabilities: <available only to root>

0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 185
I/O ports at d000 [size=32]
Capabilities: <available only to root>

0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 185
I/O ports at d400 [size=32]
Capabilities: <available only to root>

0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 185
Memory at ea002000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X motherboard
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <available only to root>

0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: ASUSTeK Computer Inc.: Unknown device 810a
Flags: medium devsel, IRQ 201
I/O ports at d800 [size=256]
Capabilities: <available only to root>

0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ff
Flags: bus master, medium devsel, latency 32, IRQ 193
I/O ports at e000 [size=256]
Memory at ea003000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc.: Unknown device 8118
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 209
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Memory at e8000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at e9000000 [disabled] [size=64K]
Capabilities: <available only to root>



When I try sudo modprobe snd-via82xx it doesn't seem to do anything:



stephen@chook-n-coop:~$ sudo modprobe snd-via82xx
Password:
stephen@chook-n-coop:~$


I've opened alsamixer and made sure the that the volume was turned up and the output was not muted. Still nothing.

I followed the steps in the Getting the ALSA drivers from a *fresh* kernel section. I used to following commands:



sudo apt-get --purge remove linux-sound-base alsa-base alsa-uti
sudo apt-get install linux-sound-base alsa-base alsa-utils
sudo apt-get install gdm ubuntu-desktop


I then reboot (multiple times) and checked alsamixer again. Still no sound. I have also followed the steps in the section ALSA driver Compilation.

What else can I do?

gbenga
July 17th, 2006, 04:39 AM
Comprehensive Sound Problem Solutions Guide v0.5c


Version History (DD-MM-YY)


28-06-06 - version 0.1 - initial creation
28-06-06 - version 0.2 - alsa-source guide added
28-06-06 - version 0.3 - alsa-drivers from alsa-project guide added
29-06-06 - version 0.4 - multiple sounds and multiple cards support added
02-07-06 - version 0.4 - fixed mistake spotted by Jvaldezjr (http://www.ubuntuforums.org/member.php?u=16088)
04-07-06 - version 0.5a - layout changes - starting on MIDI guide - Read *EXPERIMENTAL*
04-07-06 - version 0.5a - added part on saving sound settings so they are restored after reboot.
11-07-06 - version 0.5b - added guide for doing a *fresh* kernel installation
13-07-06 - version 0.5c - minor layout edit - moved *fresh* kernel above compilation to see if it is more help and if it solves more problems.
15-07-06 - version 0.5d - usage update



Background / Notes / Warnings


I can't guarantee if these instructions will work for everybody, and this is definitely a work in progress. But if these instructions can at least help one person out, I'll be happy.


If anyone has any suggestions or tips in making this post better, feel free to PM me or post below. Credits will be given regardless of how small the improvement.


If you find that you have followed the instructions on this post that something did not and you don't know why, it will be better if you start a new post and cite the fact that you used the instructions on this guide to solve your problem. Your post might get lost in all the other posts and you might not get help.


If you however find a solution to your problem, and you fee that the solution should be here, don't hesistate to post. However, please be specific.


Note: To make it absolutely clear, when I say 'Ubuntu', I mean Ubuntu AND Kubuntu AND Xubuntu (for people who find this confusing - just accept it and don't feel bad - I and probably a whole lot others got confused when we started out).


Important syntax note: ALSA modules are denoted by the prefix 'snd' followed by the dash ' - ', followed by the module name (i.e. 'via82xx'). So the full name might be something like snd-via82xx. However, in some cases you will see an underscore ' _ ' instead of the dash. This is OK, do not let it confuse you. For all intensive purposes (installing modules or posting on forums) only use the dash ' - '.

General Help - Start here if you have no idea why sound is not playing


(1) Go to a shell and type:
aplay -l


Success - You will get a list of the all the soundcards installed on your system. Your sound just might be muted. See alsamixer section.

Failure - You will get a message like
aplay: device_list:221: no soundcard found... Move on to step 2.

(2) Type this into the shell:
lspci -v


Success - At this point, you should see your sound card listed. This is a positive sign because it means that Ubuntu is detecting the presence of your soundcard, but the drivers are not installed/running. Leave your shell running since you will need it.


Failure - If it is not listed, then there are a few things that you can do.


If your soundcard is an onboard sound card, then it might be disabled in the system's BIOS. You will have to reboot and hit the key that lets you enter into the BIOS (usually Delete, F2, or F8).

If your soundcard is not onboard, make sure that it is properly seated in the PCI slot. If your card is working under Windows then this is not a problem.
(3) Check to see if the ALSA driver for your sound card exists. Go to http://www.alsa-project.org/alsa-doc/ (http://www.alsa-project.org/alsa-doc/) and search for your sound card (chipset) manufacturer in the dropdown box. You'll be given a matrix of the sound cards made by the manufacturer. Try to match the chipset you found in step 2 with the driver(green hyperlink text).
Success - You will have found the driver for your soundcard's chipset.

Failure - You will have not found the driver for your soundcard chipset. (at the moment I cannot help you, but stay tuned!)

(4) Now go back to the shell and type
sudo modprobe snd- Now, press the TAB key BEFORE pressing the ENTER key to see a list of modules. Try to find the module that matches the driver you found in step 3.


For example, my driver is a via82xx so I would type, sudo modprobe snd-via82xx.


Success


A success here means that your soundcard was installed, but it was not being loaded. Now you have loaded it for the current session.


To load it for all sessions (you will probably want to do this) you will have to edit /etc/modules (I think this is the file, I'll check once I get to my Dapper PC).


Type this into the shell
sudo nano /etc/modules


Add only the name of the module to be loaded at the end of the file. In my case, the via82xx module gave me sound so I added "snd-via82xx" to the end of the file.(iii) Make sure that you have all channels unmuted in alsamixer


See the alsamixer section


Play media using your favorite media player. Set your audio engine to alsa. In some cases, you have to configure your audio engine within another (media engine) like in Kaffiene in Kubuntu. If you hear sound, hurray!

One final step. Go onto Saving Sound Settings

Failure -You have two options


Move on to Getting the ALSA drivers from a *fresh* kernel. This step is easier and is recommended to users who might have been tinkering with their sound settings and want to revert back to the way it was just after installing Ubuntu (without reinstalling Ubuntu of course ;) )

Move on to ALSA driver Compilation, if you have not done so already. If you have, please post a new thread with your problem.

Getting the ALSA drivers from a *fresh* kernel
Sometimes, sound might be configured correctly, but for some reason or another (tinkering) it stops working. One way to go back to the old setup is to reinstall Ubuntu. However, this step is actually quite unnecessary since you are reinstalling everything because of one thing.
A faster way, is to just remove the problematic packages and reinstall them cleanly.

(1) Remove these packages
sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils

(2) Reinstall those same packages

sudo apt-get install linux-sound-base alsa-base alsa-utils

VERY IMPORTANT NOTE: Ubuntu (GNOME) users have reported that packages 'gdm' and 'ubuntu-desktop' are removed after removing the lsound packages. If this happens, then do the following

sudo apt-get install gdm ubuntu-desktop

(3) Reboot


Now you may ask "I already had the packages, so why did I go through the trouble of removing them, then installing them". The answer lies in the --purge option which removes all the extra information that accumulated from tinkering and upgrading. After doing a purge then install, the packages are unpackaged as if it they are brand new.

(4) At this point, try using
aplay -l you should get your soundcard listed.

Success - Your soundcard is detected. Go onto the Using alsamixer section, then try playing something on your music or media player.
Failure - Your card was not detected. You should try compiling your driver, so go onto ALSA drive Compilation.


ALSA driver Compilation


If you are here, then either your soundcard driver could not be loaded with modprobe, or you want to compile the drivers yourself from scratch. Good luck to you!

There are two main ways the sources of alsa-drivers are made available to you. One is though the apt-get system. Using this system would be the recommended system since most of the heavy lifting is done for you.

The other way, is getting the latest drivers from alsa-project.org. This page has the latest drivers available, which you might want to fix problems with. However, these have not been tested with Ubuntu and therefore should be used with caution.

Using alsa-source


Type the following to shell: (note: module-assistant is optional, it will compile the package for you)
sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant alsa-source


sudo dpkg-reconfigure alsa-source

You now have a big blue dialog box (left and right keys to choose 'Yes' and 'No', Enter key proceed). Answer yes (for ISA-PNP - recommended by package maintainers), then yes again (for debugging - recommended by package maintainers).

Now you must pick which driver you want to install. Use space to select and deselect modules, and up and down to navigate.

From General Help step 3, you should know the name of your driver. Deselect 'all' (the * will go away), and select your driver. In my case, I deselected 'all' then selected 'via82xx'. Hit Enter. Almost home free!


If you chose module-assistant
sudo module-assistant a-i alsa-source If the progress bar reaches 100% with no errors, you will have installed the drivers successfully. Resume this guide from General Help step 4.

If you did not choose module-assistant - Remember the name of your soundcard driver and use it place of the blue text below.
cd /usr/src sudo tar xjvf alsa-driver.tar.bz2 cd modules/alsa-driver

sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=<enter driver name here e.g. via82xx> --with-oss=yes



sudo make

sudo make install





If you get no error messages, you will have installed the drivers successfully.


Success - Resume this guide from General Help step 4.

Failure - Start a new thread in this thread of the forum. Paste the error message that you get and state that you were following instructions on this page.

Using drivers from alsa-project - update I now recommend using version 1.0.12rc1


The alsa-project route is very similar to the alsa-source route without the module-assistant.

First you would have to get the alsa-driver tar from alsa-project then pretty much do configure, make and make install again.

However, I do recommend that you make a specific directory when you compile something from source. Remember the name of your soundcard driver and use it place of the blue text below.



mkdir src
cd src

mkdir alsa

cd alsa

sudo apt-get install build-essential linux-headers-$(uname -r)
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.12rc1.tar.bz2

tar xvjf alsa-driver-1.0.12rc1.tar.bz2
cd alsa-driver-1.0.12rc1
sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=<enter driver name here e.g. via82xx> --with-oss=yes
sudo make
sudo make install


If you get no errors from doing the above then you have successfully compiled alsa-drivers from source. Resume this guide from General Help step 4.



Using alsamixer


Type this into a shell
alsamixerYou will now see what appears to be a graphical equalizer. It is more like ten different volume controls in the sample place.
To navigate around:
Left and Right Arrow Keys - Move left and right (if you move long enough in one direction you will get back to where you started - you will not fall off the screen :lol:)

Up and Down Arrow Keys - Increase and decrease volume respectively.

Letter M Key - Mutes/unmutes. If a channel is unmuted, then there is a green box underneath the volume slider. If the channel is muted, the box is grey.
Saving Sound Settings
Do this step to ensure that your alsamixer settings reload with each boot. First make sure you have your settings just the way you like them in alsamixer. Then do
sudo alsactl store 0 or if this is your nth sound card (where n is the number of soundcards in your computer) replace 0 with n-1. Many thanks to xpix for trying this out.-


Getting more than one application to use the soundcard at the same time



You might want to play a game and listen to music on your favorite music player at the same time. To do this successfully, you will have to use ALSA since it supports this feature the best. On all the music players I know of, you can configure the sound engine, to any module that is available.



The setting is usually found under something like Tools >>> Configure >>> Player Engines.


For games, it is a bit more tricky since there is not always a way to configure the player engine directly. Most games, however, do support the OSS. ALSA has an OSS module that allows OSS applications to use the ALSA driver.


To do this you will need the alsa-oss package
sudo apt-get install alsa-oss

After doing this step, it is very easy to use alsa-oss. In the shell, you can type 'aoss' then the name of the program name you want to use with alsa-oss.

Configuring default soundcards / stopping multiple soundcards from switching


Note: This section assumes that you have installed each soundcard properly.


In a shell, type
cat /proc/asound/modules


This will give the the name and index of each soundcard you have currently. Make a note of the names, and decide which one you want to be the default card.


Now type
sudo nano /etc/modprobe.d/alsa-base


At the very end of the file, add the following (assuming you have 3 cards with module names A, B and C and you want to have them in the order CAB)


options snd-C index=0
options snd-A index=1
options snd-B index=2


Getting MIDI To Work - *EXPERIMENTAL*

This section assumes you can successfully hear sound from your soundcard.

First of all, make sure that you actually have a MIDI port on your soundcard. Most onboard soundcards do not have a MIDI port.


Next, open up this file:



sudo nano /etc/modprobe.d/alsa-base


Then add this options line



options <snd module name here i.e. snd-via82xx> mpu_port=0x330
OR if you already have a options line for this soundcard add
mpu_port=0x330 to the line.


The default MIDI port is 330. You should verify this number in your BIOS if you are not sure. If the number is not listed, it is most likely that the number is 330 (add the 0x for the file).


If you get no errors, you have successfully installed your MIDI port. At the moment, I do not know if any further configuration is necessary.


Miscellaneous Tips and Tricks


Here are a few things that other people have dug up over the course of this guide. Not all tips are meant to work for all hardware (believe me hda-intel will probably have like a mini guide of it's own one day).


shaviro found the following from this post http://www.ubuntuforums.org/showthread.php?t=153752 (http://www.ubuntuforums.org/showthread.php?t=153752&highlight=touchpad+sony)
Useff had a very annoying problem where he could get sound through alsa from one user, but not through is main account. http://www.ubuntuforums.org/showthread.php?p=1221754 (http://www.ubuntuforums.org/showthread.php?p=1221754). Him and I managed to fix the problem by making sure the main account was in the audio group in /etc/groups (which he was) and deleting the .asoundrc file in the main account's /home directory.

Bo Rosén solved his ISA problem the following way. Thanks to FarEast for his help in the matter.



To Do:


Important - no particular order


Getting MIDI to work

Compiling alsa entirely (drivers, utils, oss, etc)

Getting line input to work if it does not already - for microphones, etc.

Getting SPDIF output to work if it does not already - for amplifiers, speakers with digital in.
On the backburner

Scripts for getting configuration that needs to be done in this post to be done automatically

Related


Getting keyboard multimedia keys to work - http://doc.gwos.org/index.php/MultimediaKeys (http://doc.gwos.org/index.php/MultimediaKeys)


(I personally like the non-keytouch route - configuring xmodmap and then using gnome-keybindings or for KDE (System Settings >> Regional and Language Settings >> Keyboard Shortcuts). The xmodmap route also works for XFCE, but I do not how to configure XFCE application keybindings.



Posts / References /Credits


Hoary Sound Broke (http://www.ubuntuforums.org/showthread.php?t=21211)


Problem with Azalia audio (http://ubuntuforums.org/showthread.php?t=181186)


MultipleCards (http://alsa.opensrc.org/index.php?page=MultipleCards) from alsa.opensrc..org


Volume Control does not save my settings after reboot (http://ubuntuforums.org/showthread.php?t=207107)


Every single sound problem error post I have read :-\"


The Ubuntu community for being energetic, dynamic, and polite :smile: providers of help with Ubuntu Linux in all its flavours.



I tried your guide on this thread and it worked like magic!!!!!!!!!!! You are a life safer. Bless u.

LordRaiden
July 17th, 2006, 05:04 AM
smbrow14 - your driver is installed. give the output of 'dmesg | grep snd'
If you don't get anything then that means you do not have problems. At this point, I suggest carefully looking at all your connections and making sure all media/MP3 players are using ALSA. Also look at alsamixer. Make sure the following are not muted: Master, PCM, DXS (all 4 of them). Master can safely be at 100%, PCM 80%~, and DXS should be 100%. Flip IEC 958 and IEC 958 Output on then check your results, then flip them off. You're not very far from getting sound, its now a settings/connection issue.

gbenga - Congratulations on getting it to work. One request though if you don't mind? Could you delete the quote of my entire guide? It's really long lol. I might move it to USDF if I can permission and if have time.

azmodean
July 18th, 2006, 03:22 AM
Attempted to follow the guide, but I'm not getting the expected output.

When I enter the command, "aplay -l", I ge the output:
**** List of PLAYBACK Hardware Devices ****

But nothing is listed.

"lspci -v" seems to give the proper output, including


0000:00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 3730
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11
Memory at ee000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <available only to root>

0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 3730
Flags: 66MHz, fast devsel, IRQ 11
I/O ports at e000 [size=256]
I/O ports at e400 [size=128]
Memory at ee081000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>



And finally, when I enter "sudo modprobe snd-intel8x0" there is once again no output.

I also tried the "fresh kernel" instructions, which worked normally (including uninstalling the desktop), but it did not restore sound.

One last bit of background, this is a very fresh install of Dapper Drake from a live cd. I installed once and sound was working, but the install had corrupted the winXP MBR, so I reinstalled both WinXp and Ubuntu, they both boot now, but no sound in Ubuntu.

p.s. This is my first linux install after years of claiming I was going to "get around to it soon", and I'm pretty hyped about it.

LordRaiden
July 18th, 2006, 04:19 AM
If sudo modprobe snd-intel8x0 works successfully, there is no output (no success message - a silent success so to speak). It is odd that aplay -l reports success without the card. Have you tried the hda-intel driver? Try it and see. If it does not work, go to https://bugtrack.alsa-project.org (https://bugtrack.alsa-project.org/) and post a bug report.

smbrow14
July 18th, 2006, 07:01 AM
smbrow14 - your driver is installed. give the output of 'dmesg | grep snd'




stephen@chook-n-coop:~$ dmesg | grep snd
[17179594.020000] snd_seq_dummy: disagrees about version of symbol snd_seq_create_kernel_client
[17179594.020000] snd_seq_dummy: Unknown symbol snd_seq_create_kernel_client


Could this be a problem?

LordRaiden
July 18th, 2006, 02:26 PM
smbrow14 -yes that looks like a problem, However, I thought snd-seq-dummy was not loaded. Check in you home folder for any .asoundrc file and delete it. Check your alsamixer settings as well. If all that does not wor, file a bug at https://bugtrack.alsa-project.org (https://bugtrack.alsa-project.org/).

jonjpeterson
July 18th, 2006, 04:12 PM
I'm still having no success with sound

Output from aplay -l

code:
**** List of PLAYBACK Hardware Devices ****
card 0: V8235 [VIA 8235], device 0: VIA 8235 [VIA 8235]
Subdevices: 3/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: V8235 [VIA 8235], device 1: VIA 8235 [VIA 8235]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: modem [VIA 82XX modem], device 0: VIA 82XX modem [VIA 82XX modem]
Subdevices: 1/1
Subdevice #0: subdevice #0

Full output from lspci -v

code:
0000:00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at d0000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, medium devsel, latency 0

0000:00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, medium devsel, latency 0

0000:00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, medium devsel, latency 0

0000:00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, medium devsel, latency 0

0000:00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Flags: bus master, medium devsel, latency 0

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: fc200000-fe2fffff
Prefetchable memory behind bridge: f2100000-fa0fffff
Secondary status: SERR
Capabilities: <available only to root>

0000:00:09.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 6833
Flags: bus master, slow devsel, latency 64, IRQ 185
Memory at febfe000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <available only to root>

0000:00:0a.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01)
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 0613
Flags: bus master, medium devsel, latency 168, IRQ 169
Memory at 24000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 20000000-21fff000 (prefetchable)
Memory window 1: 22000000-23fff000
I/O window 0: 00001000-000010ff
I/O window 1: 00001400-000014ff
16-bit legacy interface ports at 0001

0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device c912
Flags: bus master, medium devsel, latency 64, IRQ 177
I/O ports at e400 [size=32]
Capabilities: <available only to root>

0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device c912
Flags: bus master, medium devsel, latency 64, IRQ 177
I/O ports at e800 [size=32]
Capabilities: <available only to root>

0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device c912
Flags: bus master, medium devsel, latency 64, IRQ 177
I/O ports at ec00 [size=32]
Capabilities: <available only to root>

0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device c912
Flags: bus master, medium devsel, latency 64, IRQ 177
Memory at febfdc00 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <available only to root>

0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 120b
Flags: bus master, medium devsel, latency 32, IRQ 255
I/O ports at fc00 [size=16]
Capabilities: <available only to root>

0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 0412
Flags: medium devsel, IRQ 201
I/O ports at d800 [size=256]
Capabilities: <available only to root>

0000:00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 100b
Flags: medium devsel, IRQ 201
I/O ports at e000 [size=256]
Capabilities: <available only to root>

0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 0207
Flags: bus master, medium devsel, latency 64, IRQ 193
I/O ports at d400 [size=256]
Memory at febfd800 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: <available only to root>

0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel

0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01) (prog-if 00 [VGA])
Subsystem: TWINHEAD INTERNATIONAL Corp: Unknown device 0315
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
Memory at f4000000 (32-bit, prefetchable) [size=64M]
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at fe2f0000 [disabled] [size=64K]
Capabilities: <available only to root>


Also a little help. How do I get the terminal output into a little text box so that it is easier to read when I post questions?

LordRaiden
July 18th, 2006, 05:50 PM
Have a look at alsamixer. Make sure that you are changing the settings for via82xx not via82xx-modem.

smbrow14
July 19th, 2006, 12:15 AM
I checked the speaker connection and it was fine. I also booted into windows to make sure the speakers work (they do). I rebooted into Ubuntu but I still didn't get any sound. However, messing around with the alsamixer settings you mentioned fixed it. I have to have everything turned up to 100% to get the sound at a comfortable level (maybe I'm just deaf ;). Thanks a bunch for the tutorial and assistance!

jonjpeterson: Anything you want in a text-box goes in between &#91;CODE] and &#91;/CODE] tags.

ivotedforkodos
July 19th, 2006, 03:23 AM
I have lost my sound, and I don't know why. The only thing that I've done is apply the regular updates via Synaptic, including a few new kernels recently.

I'm not sure whether my sound card is detected or not. First, I have an ASUS Pundit P1 with Nvidia chipset, and the sound works fine in my Windows partition. Sounds was working fine under Dapper as well until a few days ago. When I do "lspci -v" the only thing related to sound that I see is this:

0000:00:10.1 0403: nVidia Corporation MCP51 High Definition Audio (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 81cb
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
Memory at fe028000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>

but when I do "aplay -l", I get:

aplay: device_list:221: no soundcards found...

Also, in the GNOME panel, there is a red crossbar icon over the speaker icon. If I click on this, I get an error message saying that no GStreamer plugins/devices are installed, but all of the gstreamer packages are installed. (Again, the sound was working fine a few days ago.) As far as I can tell, nothing that I've read in this thread seems to apply to my situation. I'd really like to avoid having to reinstall gdm, etc. Can anyone help?

Amorphous_Snake
July 19th, 2006, 08:29 AM
I have a problem with sound. I have a Creative Vibra 128 card. It used to work perfectly. Now, it may work and it may not.

I guess the problem is that something is occupying the sound card, because when I am in the "sound is present" time, everything runs perfectly, but when I am in the "no sound" time, a program like Beep media player says that my card may be occupied.

Note that this applies to all sounds, including startup and shutdown sounds. I have all volumes maxed up in the volume control. And I have all the codecs.

It's just weird!

paullinux
July 19th, 2006, 09:33 AM
How this tread made me going trough numerous garbage-bags at my garbage container...

The sound of my seperate desktop speakers were lousy, as if someone put them to loud for a long time. So I thought: well, trough away and buy new ones! But it was sunday, so I decided to use my stereo as a temporary sound system. Again the same problem. Meanwhile my wife just put all the garbage in the container. I tried every cable and stereo connections but..nothing..

Then I happened to come across this thread and saw something about Salsa mixer. Guess what... I reconfigured the salsa settings and "voila" perfect sound.

But having then a set of apparently perfect desktop speakers in 'one' of the garbage bags you can guess what I had to do next ....

Anyway I saved some money with this thread but boy you don't want to know the details on that... My children had a laugh though..

LordRaiden
July 19th, 2006, 02:12 PM
ivotedforkodos - I would try the *fresh* kernel install guide in your case. You might have to reinstall gdm, but that it not too difficult.

Amorphous_Snake - sound like an ALSA/OSS problem. Make sure that ALL your applications use alsa if possible. That includes your system sound settings, beep media player, and the rest. If one application is using oss, then it will block access to soundcard for everything else until it is closed properly.

Amorphous_Snake
July 19th, 2006, 02:39 PM
Thanks LordRaiden, but how can I do what you said? I am new to Linux. Can you please explain it and show me how to do it step by step.

LordRaiden
July 19th, 2006, 02:46 PM
It really depends upon the application. I think for the system sound, it is something like System --> Sound, then under engine, pick ALSA. For a media player, it would be something like Configure --> Engine --> output then pick ALSA.

Jalexxi
July 19th, 2006, 03:05 PM
I seem to have the same problem as Azmodean. I have too have an nForce board (nForce 2), I've loaded the intel8x0 module, but it gives no output. I followed the rest of the guide, but there's nothing that makes it work, unfortunately.

LordRaiden
July 19th, 2006, 03:09 PM
If you have a .asoundrc file in your home directory (/home/username) remove it then reboot and try again.

If it does not work, then I suggest you file a bug report at alsa-project. The link is in my signature.

Jalexxi
July 19th, 2006, 04:48 PM
I have no .asoundrc file. So that's it then? No way I can get the sound to work except file a bug report and hope it gets fixed sometime soon?

LordRaiden
July 19th, 2006, 06:26 PM
If the module is loaded and provides no sound, it can be one of three things.

1) Connection problem (physical connections, sound jacks, motherboard audio connectors)
2) Setting problem (this includes .asoundrc file, sound options in applications, and alsamixer channels)
3) Driver error (bad compile, errors in dmesg, or even no visible errors)

Try playing an MP3 and look at the visualization/track time indicator. If the visualizations are *playing* and the track timer is increasing, then something is playing. It could easily be 1) or 2)

If that does not work, you should get some error in dmesg stating that a related module was not loaded. If you do not, then you should file a bug report.

ivotedforkodos
July 19th, 2006, 11:48 PM
[QUOTE=LordRaiden;1274655]ivotedforkodos - I would try the *fresh* kernel install guide in your case. You might have to reinstall gdm, but that it not too difficult.

Thanks, LordRaiden. Check this out:

http://www.ubuntuforums.org/showthread.php?t=218685

Am I correct in thinking that I can just delete some configuration file inside my home directory, rather than reinstalling gdm entirely? If so, pleas e let me know if you have any ideas as to which one. Thanks.

FYI: ~/.xsession-errors contains a lot of this:



ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2102:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device

Pizza the Hutt
July 20th, 2006, 03:12 AM
I followed your guide step-by-step until I came to Alasa Driver Copilation and got the following:


user5@ubuntu:~$ sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant alsa-source
Password:
Reading package lists... Done
Building dependency tree... Done
build-essential is already the newest version.
Package linux-headers-2.6.12-9-386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package linux-headers-2.6.12-9-386 has no installation candidate

What should I do now?:-k

LordRaiden
July 20th, 2006, 04:11 AM
Pizza-the-Hut - what version kernel are you running? by the looks of it 2.6.12-9 is really old.

ivotedforkodos - i suggest that you try my guide first, but the file that you would delete in your hoem directory would be .asoundrc. Your errors look a bit more troublesome though (can't find card 0). Give it a shot. Honestly, reinstalling gdm is not too bad, as long as you do not reboot after the remove and you reinstall afterwards you will be fine.

Pizza the Hutt
July 20th, 2006, 11:18 PM
I should have the latest version, because I always install updates as soon as they are available.

SteveHoffmanUK
July 21st, 2006, 12:42 AM
Impressive Howto, but by following it I have completely buggered up my laptop.

My Dell Latitude -- which had been happily working under Dapper for several weeks -- had suddenly gone silent, maybe because of some flakey update who knows, so I was following the uninstall-then-reinstall bit in this Howto. I did the uninstall and the reinstall, then discovered the part of the Howto where you say:


VERY IMPORTANT NOTE: Ubuntu (GNOME) users have reported that packages 'gdm' and 'ubuntu-desktop' are removed after removing the lsound packages. If this happens, then do the following
Code:

sudo apt-get install gdm ubuntu-desktop

If you do that, at a certain point it asks you to

insert the disc labelled Ubuntu 6.06 _Dapper Drake_ - Alpha i386 (20060329.1) in the drive /cdrom/ and press enter

Unfortunately, my laptop does not have a built-in CD-ROM drive. You have to attach it externally, and if you don't do so before you boot, then the system doesn't recognise it. Maybe you have to mount it, but, being a Newbie, I'm not sure about how to do the mount command. so at this point I reboot my system, having first attached the external CD-ROM drive. When it reboots, I get only the command line, no GUI.

So I log in and then, following advice in another thread, key in this:

sudo aptitude update

It updates all the repositories (I think). Then I key in

sudo apt-get gdm ubuntu-desktop
It proceeds to list all the packages it will install, then it asks for the magic disc. I assume this is the current Ubuntu Live disc -- it's the only disc I've got for Ubuntu. So I put it in, close the drive and hit enter as instructed, and it simply repeats the instruction to insert the disc and press enter.

Is this the wrong disc?
Is it not reading the drive?

Who knows. The only thing I know at this point is that I can no longer use my laptop. Any suggestions would be welcome.
Sigh

ON EDIT-

I now strongly suspect the CD drive itself, a dodgy mechanism at best. With the Ubuntu live disc in the drive, a reboot should sense it and run it as a RAM-based live system, but it doesn't, and boots from the hard disc instead (boot sequence in the BIOS is CD/floppy/HDD). In summary, while this Howto triggered a problem, hardware is preventing its solution.

It raises an interesting question about why these uninstalls should require removal of seemingly unrelated and critical programs like gdm, ubuntu-desktop, nautilus, etc., but that's off-topic and best discussed elsewhere.

ivotedforkodos
July 21st, 2006, 01:09 AM
ivotedforkodos - i suggest that you try my guide first, but the file that you would delete in your hoem directory would be .asoundrc. Your errors look a bit more troublesome though (can't find card 0). Give it a shot. Honestly, reinstalling gdm is not too bad, as long as you do not reboot after the remove and you reinstall afterwards you will be fine.

OK, I tried reinstalling gdm as you suggested and that did NOT solve the problem. I do not (nor do any of the other users of this computer), have a .asoundrc file in my home directory. But I still think it has to be something in my home directory, since the other users have sound, and I hear the Ubuntu bongos at the GDM login screen. Please give me some other ideas. Could it be something in the .gnome folder?

Fatmaxlim
July 21st, 2006, 06:36 AM
Hello, what to do if there is no sound card listed after command lspci -v ?
In BIOS it's enabled and in Windows it works fine. I have onboard ICH5 Intel sound card. Thanks.

LordRaiden
July 22nd, 2006, 04:44 AM
SteveHoffmanUK - from the command-line do this


sudo nano /etc/apt/sources.list
The first few lines has a reference or two to the CD-ROM. use the '#' to comment out the line.

after that, press CTRL + O to save. Then


sudo apt-get update && sudo apt-get install gdm ubuntu-desktop

This will allow you to download gdm and ubuntu-desktop from the ubuntu repositories.

ivotedforkodos - look in this file


sudo nano /etc/group
each line in the file has the name of the group. Go to the audio line (they aren't alphabetical but the list is not too long). Add your username (the one without sound) to the audio line.

so if you line read
audio:x:29:user1,user2
it will now read (assuming you want to add the user 'newuser')
audio:x:29:user1,user2,newuser
Be very careful when editing that file.

Pizza the Hutt - Enter this line into a shell and paste the contents back.
uname -r You should have the latest version of the kernel for Dapper and 2.6.12 is not the latest. You should have something like 2.6.15.xx

Fatmaxlim - look if your soundcard is listed here http://www.alsa-project.org/alsa-doc/

SteveHoffmanUK
July 22nd, 2006, 07:34 AM
Lord Raiden

Thanks for the instructions. I am back in business; however, I still don't have sound! :(

I will go back to the start of this thread and carry on where I left off. Presumably this change I made (commenting out the ref to cdrom) means that it won't ask me again for me to use my Ubuntu disc should I want to reinstall something?

ivotedforkodos
July 22nd, 2006, 03:43 PM
ivotedforkodos - look in this file


sudo nano /etc/group
each line in the file has the name of the group. Go to the audio line (they aren't alphabetical but the list is not too long). Add your username (the one without sound) to the audio line.

so if you line read
audio:x:29:user1,user2
it will now read (assuming you want to add the user 'newuser')
audio:x:29:user1,user2,newuser
Be very careful when editing that file.


Unbelievable. That worked perfectly. Thanks, LordRaiden; you are the man! BTW, why would this have happened?

cyberdude
July 22nd, 2006, 07:05 PM
any tips on getting the master volume control to work with the cm9739 onboard sound? pcm slider does adjust most sound levels, but some sounds do come out at full volume...

LordRaiden
July 23rd, 2006, 04:53 AM
ivotedforkodos - Don't know. I remember another user having it a while back.

cyberdude - not familiar with your soundcard, but master alone should work. Try muting/unmuting master (it should do something). Leave your PCM at around 80, any higher and you might hear static. Are you using SPDIF? Sometimes the master only works on the analog or the SPDIF and not on both.

I'm thinking about moving this guide to the UDSF so that other users can put in their info as well (hopefully without breaking the layout).

cyberdude
July 23rd, 2006, 09:43 PM
cyberdude - not familiar with your soundcard, but master alone should work. Try muting/unmuting master (it should do something). Leave your PCM at around 80, any higher and you might hear static. Are you using SPDIF? Sometimes the master only works on the analog or the SPDIF and not on both.


no i'm not using SPDIF, just analog...muting/unmuting master does'nt effect the sounds at all...even when muted, sounds still play

motherboard (http://www.epox.com.tw/eng/products_content.php?ps=244) is based on nforce2 ,with c-media onboard sound (cmi9739)


](*,)

cyberdude
July 23rd, 2006, 10:17 PM
no i'm not using SPDIF, just analog...muting/unmuting master does'nt effect the sounds at all...even when muted, sounds still play

motherboard (http://www.epox.com.tw/eng/products_content.php?ps=244) is based on nforce2 ,with c-media onboard sound (cmi9739)


](*,)

just found this

For everyone who's missing volume control with his CMedia 9739 onboard
sound chip, here are the facts I found out so far. This chip is used
at least on Epox 8RDA3+ and maybe in every newer nforce2 chipset. (Who
knows where else it is used?)
The general problem with the 9739 is that it doesn't have a volume
control in hardware. As the technical reference (avail. at
http://www.cmedia.com.tw/e_t_twp.htm) states, there is no PCM volume
register on chip, only a PCM muting register. Strangely, it also
states that there is a _Master_ volume register where you should be
able to set the volume (not only muting)! But I had no success using
it; changes to that register have no effect. Maybe this is a hardware
bug, or the tech reference is wrong.
BTW. CMedia's OSS driver does volume control in software, so they know
about the problem...
So it seems that the best solution is to use some kind of software
volume control.

Pizza the Hutt
July 23rd, 2006, 10:37 PM
That's what I got:


user5@ubuntu:~$ uname -r
2.6.12-9-386


I don't know why I don't have the latest version. I upgraded to Dapper just two weeks ago and the update manager does not show me any new available updates.

LordRaiden
July 24th, 2006, 03:03 AM
Pizza the Hutt - you are using an older kernel - try doing
sudo apt-get update && sudo aptitude dist-upgrade

This should get you to the latest version of the kernel.

kitt
July 24th, 2006, 10:34 AM
Ubuntu cant play sounds!

Hi everyone,
All of a sudden, ubuntu has stopped playing sounds- BUT..I am able to play the sound files i want..its just that no program (games, ubuntu, etc.) is able to play any sounds.
Everything was working perfectly out-of-the-box, but now i can only play the sound files in the media players.

aplay returns this:
-------------------------------------------------------------------------
ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card 'Audio'
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2102:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:544: audio open error: No such device
-----------------------------------------------------------------------------

aplay -l returns:
-----------------------------------------------------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 1/1
Subdevice #0: subdevice #0
------------------------------------------------------------------
And heres what alsamixer throws up:
alsamixer: function snd_ctl_open failed for default: No such device
------------------------------------------------------------------
My machine: acer aspire 5004

LordRaiden
July 24th, 2006, 05:29 PM
kitt - Go through my guide at very beginning of this thread. It should help you get your sound back or at least find the reason as to you not having sound.

azmodean
July 25th, 2006, 03:35 AM
Finally resolved my issues with a kernel upgrade (from linux-image-2.6.15-23-386 to linux-image-2.6.15-26-386).

Additional issues with the earlier kernel I have not posted yet:
In addition to the "no feedback" symptoms I reported earlier, I recieved the same set of errors kitt reported when I invoked aplay (no "-l" switch)
Sometimes my sound hardware would be recognised, sometimes not, I could not tell any difference in the situations. As a matter of fact, I have an onboard sound card and a standalone sound card installed, and at times, neither, each of the cards, and both of the cards were recognised. Once again, I could never tell any difference in the system besides the fact that sound was or was not working.

eXecu7or
July 25th, 2006, 01:04 PM
I've got digital output on Intel HD Audio (ALC882D) by turning on the digital out from alsa mixer. As it appears, the codec is able to output both analog & digital at the same time. I was wondering if there is any way to get the line in outputted on the SPDIF. I've asked in a couple other treads, but this one seems to be the most "comprehensive". And another one: is there any chance to get Dolby Digital Live working in Ubuntu?

LordRaiden
July 25th, 2006, 06:27 PM
I think this is something that you would configure using a .asoundrc file. I would not know how since I don't have an HDA card or SPDIF output/speakers.

Pizza the Hutt
July 26th, 2006, 05:24 AM
I did that and still got the same old kernel:

user5@ubuntu:~$ sudo apt-get update && sudo aptitude dist-upgrade
Get:1 http://us.archive.ubuntu.com dapper Release.gpg [189B]
Get:2 http://us.archive.ubuntu.com dapper-updates Release.gpg [189B]
Get:3 http://security.ubuntu.com dapper-security Release.gpg [189B]
Get:4 http://us.archive.ubuntu.com dapper-backports Release.gpg [189B]
Hit http://us.archive.ubuntu.com dapper Release
Hit http://us.archive.ubuntu.com dapper-updates Release
Hit http://security.ubuntu.com dapper-security Release
Hit http://us.archive.ubuntu.com dapper-backports Release
Hit http://us.archive.ubuntu.com dapper/main Sources
Hit http://us.archive.ubuntu.com dapper/restricted Sources
Hit http://us.archive.ubuntu.com dapper/universe Packages
Hit http://us.archive.ubuntu.com dapper/multiverse Packages
Hit http://us.archive.ubuntu.com dapper/main Packages
Hit http://us.archive.ubuntu.com dapper/restricted Packages
Hit http://us.archive.ubuntu.com dapper/universe Sources
Hit http://security.ubuntu.com dapper-security/main Packages
Hit http://us.archive.ubuntu.com dapper/multiverse Sources
Hit http://us.archive.ubuntu.com dapper-updates/main Packages
Hit http://us.archive.ubuntu.com dapper-updates/restricted Packages
Hit http://us.archive.ubuntu.com dapper-updates/main Sources
Hit http://us.archive.ubuntu.com dapper-updates/restricted Sources
Hit http://us.archive.ubuntu.com dapper-backports/main Packages
Hit http://us.archive.ubuntu.com dapper-backports/restricted Packages
Hit http://us.archive.ubuntu.com dapper-backports/universe Packages
Hit http://us.archive.ubuntu.com dapper-backports/multiverse Packages
Hit http://us.archive.ubuntu.com dapper-backports/main Sources
Hit http://security.ubuntu.com dapper-security/restricted Packages
Hit http://security.ubuntu.com dapper-security/main Sources
Hit http://security.ubuntu.com dapper-security/restricted Sources
Hit http://us.archive.ubuntu.com dapper-backports/restricted Sources
Hit http://us.archive.ubuntu.com dapper-backports/universe Sources
Hit http://us.archive.ubuntu.com dapper-backports/multiverse Sources
Hit http://security.ubuntu.com dapper-security/universe Packages
Hit http://security.ubuntu.com dapper-security/multiverse Packages
Hit http://security.ubuntu.com dapper-security/universe Sources
Hit http://security.ubuntu.com dapper-security/multiverse Sources
Fetched 4B in 0s (4B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
user5@ubuntu:~$ uname -r
2.6.12-9-386

exgsr
July 26th, 2006, 04:07 PM
hi lord raiden..
i'm using dapper and sound blaster live! value.
the sound card is kindda old.. about 5 years my guess.
i've tried to follow everyother guide that available including yours.
however it's still bearing no fruit, my sound is still having quirks and hisses for any playback.
As i'm a very2 new beginner at ubuntu and linux in particular. i'm hoping you could assist me? is this possible. thanks.

dcmalllory
July 27th, 2006, 09:09 PM
LordRaiden - Let me give you the kudos you deserve for taking the time to help others. Our society, so it seems, has become so "me-me-me" that thinking of others is simply lost in the shuffle of everyday life. Thank you.

I have an NEC Versa FXi laptop. The sound worked fine with Hoary, but no longer worked when I installed Dapper. I did a clean install, so as to not leave any blivets behind due to an upgrade. Everything worked fine with the exception of sound.

I went through your excellent guide step by step, and tried everything in it, right down to compling new modules, etc. Alas, still no sound. I have pasted below the outputs of the commands you list. I included "lsmod" to show the modules loaded:

dcm@dcm-lt:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
Subdevices: 1/1
Subdevice #0: subdevice #0
dcm@dcm-lt:~$ lspci -v
0000:00:00.0 Host bridge: Intel Corporation 82440MX Host Bridge (rev 01)
Flags: bus master, medium devsel, latency 64

0000:00:00.2 Modem: Intel Corporation 82440MX AC'97 Modem Controller (prog-if 00 [Generic])
Subsystem: NEC Corporation: Unknown device 8086
Flags: fast devsel, IRQ 5
I/O ports at e800 [size=256]
I/O ports at ec00 [size=128]

0000:00:03.0 CardBus bridge: Texas Instruments PCI1420
Subsystem: NEC Corporation Versa Note VXi
Flags: bus master, medium devsel, latency 168, IRQ 10
Memory at 18000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
Memory window 0: 10000000-11fff000 (prefetchable)
Memory window 1: 12000000-13fff000
I/O window 0: 00001000-000010ff
I/O window 1: 00001400-000014ff
16-bit legacy interface ports at 0001

0000:00:03.1 CardBus bridge: Texas Instruments PCI1420
Subsystem: NEC Corporation Versa Note VXi
Flags: bus master, medium devsel, latency 168, IRQ 5
Memory at 18001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=05, subordinate=08, sec-latency=176
Memory window 0: 14000000-15fff000 (prefetchable)
Memory window 1: 16000000-17fff000
I/O window 0: 00001800-000018ff
I/O window 1: 00001c00-00001cff
16-bit legacy interface ports at 0001

0000:00:04.0 Multimedia audio controller: Creative Labs Ectiva EV1938
Subsystem: NEC Corporation: Unknown device 80c5
Flags: bus master, slow devsel, latency 64, IRQ 5
I/O ports at ef00 [size=64]
I/O ports at ef80 [size=32]
Capabilities: <available only to root>

0000:00:05.0 VGA compatible controller: Silicon Motion, Inc. SM720 Lynx3DM (rev b1) (prog-if 00 [VGA])
Subsystem: NEC Corporation: Unknown device 808a
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:07.0 ISA bridge: Intel Corporation 82440MX ISA Bridge (rev 01)
Flags: bus master, medium devsel, latency 0

0000:00:07.1 IDE interface: Intel Corporation 82440MX EIDE Controller (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at ffa0 [size=16]

0000:00:07.2 USB Controller: Intel Corporation 82440MX USB Universal Host Controller (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at ef40 [size=32]

0000:00:07.3 Bridge: Intel Corporation 82440MX Power Management Controller
Flags: medium devsel

0000:05:00.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Subsystem: Linksys WPC54G
Flags: bus master, fast devsel, latency 64, IRQ 5
Memory at 16000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <available only to root>

dcm@dcm-lt:~$ lsmod
Module Size Used by
binfmt_misc 12296 1
rfcomm 40216 0
l2cap 26244 5 rfcomm
bluetooth 49892 4 rfcomm,l2cap
ipv6 265728 6
ppdev 9220 0
speedstep_smi 5904 0
speedstep_lib 4484 1 speedstep_smi
cpufreq_userspace 4696 1
cpufreq_stats 5636 0
freq_table 4740 2 speedstep_smi,cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
ac 5252 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
arc4 2048 1
ieee80211_crypt_wep 4992 1
bcm43xx 124044 0
ieee80211softmac 29696 1 bcm43xx
ieee80211 37064 2 bcm43xx,ieee80211softmac
ieee80211_crypt 6272 2 ieee80211_crypt_wep,ieee80211
usbhid 39904 0
pcmcia 40508 0
joydev 10048 0
tsdev 8000 0
pcspkr 2180 0
rtc 13492 0
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
floppy 62148 0
snd_ens1371 25056 1
gameport 15496 1 snd_ens1371
snd_rawmidi 26784 1 snd_ens1371
snd_seq_device 8972 1 snd_rawmidi
snd_ac97_codec 92832 1 snd_ens1371
snd_pcm_oss 61728 0
snd_mixer_oss 19456 1 snd_pcm_oss
snd_pcm 99080 3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_timer 26500 1 snd_pcm
psmouse 36100 0
serio_raw 7300 0
i2c_piix4 9104 0
i2c_core 21904 2 i2c_acpi_ec,i2c_piix4
snd 62956 10 snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_co dec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 10208 1 snd
yenta_socket 28428 3
rsrc_nonstatic 13440 1 yenta_socket
snd_page_alloc 11272 1 snd_pcm
snd_ac97_bus 2304 1 snd_ac97_codec
pcmcia_core 42640 3 pcmcia,yenta_socket,rsrc_nonstatic
evdev 9856 2
ext3 135688 1
jbd 58772 1 ext3
ide_generic 1536 0
uhci_hcd 33680 0
usbcore 130692 3 usbhid,uhci_hcd
ide_cd 33028 0
cdrom 38560 1 ide_cd
ide_disk 17664 3
piix 11012 1
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit

I still have no sound; alsamixer shows all channels un-muted, but still no joy. If perhaps you glance at this and notice something that jumps out at you, I would be delighted.

Once again, thanks for the time you give the community.

Best Regards,

DCM

LordRaiden
July 27th, 2006, 09:45 PM
Pizza the Hutt - Do the following -


sudo apt-get install linux-image-2.6.15-25-386 I don't know what video card you have but hopefully you'll boto back into a graphical shell.

exgsr - go through my guide and post back if you get stuck somewhere.


dcmalllory -

2 things -

1) look in your home directory for a ".asoundrc" file.

If it exists: delete it, reboot, try playing sound.

2) If 1 did not help: look in /etc/group

first look at the file with out editing


cat /etc/group

VERY CAREFULLY, locate the line that starts with audio, and check that your username appears there.


If it does not, do


sudo nano /etc/group and edit the file. So if you line read

audio:x:29:user1,user2


it will now read (assuming you want to add the user 'newuser')


audio:x:29:user1,user2,newuser

save the file (CTRL + O), reboot, then try playing something again.

If does not work, then I recommend doing the *fresh* install in my guide. After that, I would suggest filing a bug-report (link in my signature) as your next course of action.

Skerit
July 27th, 2006, 11:11 PM
What's about this "sudo modprobe snd-" and tab trick? It isn't working properly... Well, to show all my modules the shell has to be empty and then I can press tab, otherwise it doesn't work ...

Anyway, I found the right driver thanks to the alsa site, my sound wasn't working at first but that was because I had the "Headphone jack sense" thing on (what is that, anyway?)

LordRaiden
July 27th, 2006, 11:43 PM
The sudo modprobe tab thing doesn't work as nicely as like, if you have all the modules installed, you'll get a list of over a 150 modules. It's more useful for some than others. I might get rid off the part about it if it gets really confusing.

exgsr
July 28th, 2006, 04:01 AM
exgsr - go through my guide and post back if you get stuck somewhere.


LordRaiden
Thank you for the reply.
Yes, i have earlier followed you guide. My soundblaster live! value is detected correctly and there is sound.
The only problem is that anything i play wave, mp3 or mpeg the will always be hiss or quirks breaking the sound. (so irritating)
i feel that i'm close but not close enuff to resolve this.
i've been tinkering away on the alsamixer but to no avail.

I've followed you guide for Getting the ALSA drivers from a *fresh* kernel but still after that the sound is broken.:sad:

i guess i'm hopeless when i comes to linux. currently everthing is working beautifully on my dapper. just this little tiny 'irritating' thing keeping me from enjoying my ubuntu.

as on your comprehensive guide, there is everything except what to do if there is sound but its broken :-s
greatly appreciate any input on how to go about this.
thanks!

LordRaiden
July 28th, 2006, 04:40 AM
Go into alsamixer, what level is your PCM at? setting it lower might help a bit.

rck_hitokiri
July 28th, 2006, 07:05 AM
i have a problem on my snd-es18xx i worked it out and got the sound workin. the problem is its like going on high and low pitches when playin any codec type. (e.g. mp3...etc...) i dont know whats wrong. please help out?

LordRaiden
July 28th, 2006, 05:56 PM
rck_hitokiri - look at your pcm settings in alsamixer. Make it lower if you need it. Try muting the microphone if you don't use it.

scarabaeus
July 29th, 2006, 08:17 PM
thanks for the guide. it did the trick and i'm happily listening to music now.

cheers

muz1
July 30th, 2006, 12:33 PM
Hey.
I wanted to first say thankyou for your post regarding stepping through sound problems. I did not follow it to the book but pretty much with your promptings, I got my sound to work. The problem is that it was working afew hours ago but now I have shut down my system, walked away for afew hours and now it does not work. HAs anyone else had this problem???

Cheers
Murray

joecr
July 30th, 2006, 04:03 PM
Hey.
I wanted to first say thankyou for your post regarding stepping through sound problems. I did not follow it to the book but pretty much with your promptings, I got my sound to work. The problem is that it was working afew hours ago but now I have shut down my system, walked away for afew hours and now it does not work. HAs anyone else had this problem???
Did you run the following to make your settings sticky? With the first one you just add your sound module to the list if it wasn't being detected. In my case I added snd-sbawe to the list of modules to load.

sudo nano /etc/modules
Then after loading you sound module, assuming it just wasn't loading, you need to still do the following. (At least I did in my case, I'm guessing here because I didn't see in the thread what you are running being listed.) From what I understand alsa sound is muted by default. That is according to the Old Sound Card article on the Wiki (https://help.ubuntu.com/community/forum/hardware/OldSoundCard).

alsamixer
Then you need to make the alsa settings sticky so that sound is not muted by default.

Saving Sound Settings
Do this step to ensure that your alsamixer settings reload with each boot. First make sure you have your settings just the way you like them in alsamixer. Then do
Code:

sudo alsactl store 0
or if this is your nth sound card (where n is the number of soundcards in your computer) replace 0 with n-1. Many thanks to xpix for trying this out.-
One note to LordRaiden I think it makes more sense to say “Do this step to ensure that your alsamixer settings reloaded with each boot.” At least to my American English.

waltn
July 30th, 2006, 08:06 PM
Many thanks for the excellent guide, LordRaiden. I have worked my way through all of it and still cannot find a solution to my problem. I have a HiFi-Link USB sound "card" that I use to connect my computer to my stereo system. I rip LPs using the internal on-board sound chip and want to play back through the HiFi-Link; this works perfectly under WinXP. However, under Dapper, I cannot get the HiFi-Link to work; I can select it with ALSA Mixer, but no output occurs. I have run the following commands:


walt@walt-ubuntu:~$ cat /proc/asound/modules
0 snd_intel8x0
1 snd_mpu401
2 snd_usb_audio

walt@walt-ubuntu:~$ asoundconf is-active

walt@walt-ubuntu:~$ asoundconf list
Names of available sound cards:
SI7012
UART
HiFiLink

walt@walt-ubuntu:~$ lsmod|grep sound
soundcore 10208 1 snd

walt@walt-ubuntu:~$ which audacity
/usr/bin/audacity

walt@walt-ubuntu:~$ ls -la /usr/bin/audacity
-rwxr-xr-x 1 root root 2509248 2006-05-10 22:55 /usr/bin/audacity

walt@walt-ubuntu:~$ sudo chgrp audio /usr/bin/audacity
Password:

walt@walt-ubuntu:~$ ls -la /usr/bin/audacity
-rwxr-xr-x 1 root audio 2509248 2006-05-10 22:55 /usr/bin/audacity

walt@walt-ubuntu:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HiFiLink [HiFi-Link], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

walt@walt-ubuntu:~$ dmesg|grep snd
[17179586.436000] usbcore: registered new driver snd-usb-audio

The folks from Xitel (the HiFi-Link makers) said that it appears that the internal chip is not releasing the sound resources. Is there a way to disable the internal sound playback while retaining the ability to use the internal capture capability? Any help is most gratefully appreciated!

CarbonPlexus
July 31st, 2006, 02:08 AM
LordRaiden, thanks for helping us who don't know what's wrong with our sound. I tried your guide but I still get no sound and I'm hoping someone can tell me something else to try. I have an Audigy sound card, here's some of the stats I've gotten back but I don't know if anything is out of place. My sound works in Windows and it worked in Breezy before I updated so it's not that the sound card doesn't work.


~$ cat /proc/asound/modules
0 snd_emu10k1
1 snd_usb_audio

~$ asoundconf list
Names of available sound cards:
Audigy
Camera

~$ lsmod|grep sound
soundcore 10208 1 snd

also "lspci -v" gave me


0000:00:0c.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Subsystem: Creative Labs SB0090 Audigy Player
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at d000 [size=32]
Capabilities: <available only to root>

and "lsmod | grep snd" gave me

snd_rtctimer 3340 1
snd_usb_audio 78784 1
snd_usb_lib 16640 1 snd_usb_audio
rtc 13492 1 snd_rtctimer
snd_emu10k1_synth 7296 0
snd_emux_synth 37376 1 snd_emu10k1_synth
snd_seq_virmidi 7680 1 snd_emux_synth
snd_seq_midi_emul 7168 1 snd_emux_synth
snd_seq_dummy 3844 0
snd_seq_oss 33536 0
snd_seq_midi 9376 0
snd_seq_midi_event 7552 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq 51984 10 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,s nd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi _event
snd_emu10k1 117156 4 snd_emu10k1_synth
snd_rawmidi 25504 4 snd_usb_lib,snd_seq_virmidi,snd_seq_midi,snd_emu10 k1
snd_ac97_codec 93088 1 snd_emu10k1
snd_ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 4 snd_usb_audio,snd_emu10k1,snd_ac97_codec,snd_pcm_o ss
snd_seq_device 8716 8 snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd _seq_oss,snd_seq_midi,snd_seq,snd_emu10k1,snd_rawm idi
snd_timer 25220 4 snd_rtctimer,snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 10632 2 snd_emu10k1,snd_pcm
snd_util_mem 4608 2 snd_emux_synth,snd_emu10k1
snd_hwdep 9376 4 snd_usb_audio,snd_emux_synth,snd_emu10k1
snd 55268 22 snd_usb_audio,snd_emux_synth,snd_seq_virmidi,snd_s eq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_ac97_co dec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_devi ce,snd_timer,snd_hwdep
soundcore 10208 1 snd
usbcore 130692 8 quickcam,acecad,snd_usb_audio,snd_usb_lib,usbhid,u hci_hcd,ehci_hcd

"aplay -l"

card 0: Audigy [Audigy 1 [SB0090]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: Audigy [Audigy 1 [SB0090]], device 3: emu10k1 [Multichannel Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0

and in /etc/modules I have

lp
mousedev
psmouse
sbp2
sr_mod
snd-seq-device
snd-seq-midi
snd-seq-oss
snd-seq-midi-event
snd-seq
via82cxxx
ide-cd
ide-disk
ide-generic

am I missing something in the /etc/modules list? I can't tell. I know the onboard sound is via82cxxx but I don't know which one is for the Audigy. Any help would be appreciated. Thank you ^_^

kendb3
July 31st, 2006, 06:51 AM
LordRaiden, first off thank you, really great thread, as I'm brandy dandy new to Linux. Gave this a bit of a go, but no luck. I've got an old system I installed Dapper on, its a PII Compaq, it has onboard sound, and the driver (which works fine in the Windows partition) is an ESS1887 driver. I went through a few of the steps and at some point figured what the hey, lets look at the BIOS, it had some odd settings such as either Auto-Detecting the associated speakers, or just telling the system that they are "Present" or not, as the monitor came with the system, and has built in speakers. I went and switched it to say they were just "Present" as opposed to Auto-Detect, figured no harm in that. Also from what I know about the system, the sound card itself supplies the power to the speakers, they do not have external power, found that out when I switched the monitor to another tower once.

This is what I am seeing so far:


kenny@Kenny-Linux:~$ aplay -l
aplay: device_list:221: no soundcards found...


kenny@Kenny-Linux:~$ lspci -v
0000:00:00.0 Host bridge: Intel Corporation 440LX/EX - 82443LX/EX Host bridge (r ev 03)
Flags: bus master, medium devsel, latency 64
Memory at 44000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:01.0 PCI bridge: Intel Corporation 440LX/EX - 82443LX/EX AGP bridge (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 00001000-00001fff
Memory behind bridge: 40000000-410fffff
Prefetchable memory behind bridge: 10000000-100fffff

0000:00:04.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
Subsystem: Netgear FA310TX
Flags: bus master, medium devsel, latency 66, IRQ 11
I/O ports at 2400 [size=256]
Memory at 41100000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at 10100000 [disabled] [size=256K]

0000:00:14.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
Flags: bus master, medium devsel, latency 0

0000:00:14.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) ( prog-if 80 [Master])
Flags: bus master, medium devsel, latency 64
I/O ports at 2020 [size=16]

0000:00:14.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 2000 [size=32]

0000:00:14.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
Flags: medium devsel, IRQ 9

0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/ 2X (rev 5c) (prog-if 00 [VGA])
Subsystem: Compaq Computer Corporation: Unknown device 0000
Flags: bus master, stepping, medium devsel, latency 66, IRQ 11
Memory at 40000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at 1000 [size=256]
Memory at 41000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 10000000 [disabled] [size=128K]
Capabilities: <available only to root>


kenny@Kenny-Linux:~$ sudo apt-get install build-essential linux-headers-$kenny module-assistant alsa-source
Reading package lists... Done
Building dependency tree... Done
Package linux-headers is not installed, so not removed
E: Couldn't find package module-assistant

So... no module assistant, not sure why, again, its all new to me, lol. So I tried the other method:


kenny@Kenny-Linux:~$ sudo apt-get install build-essential linux-headers-$kenny
Reading package lists... Done
Building dependency tree... Done
Package linux-headers is not installed, so not removed
The following extra packages will be installed:
binutils cpp cpp-4.0 dpkg-dev g++ g++-4.0 gcc gcc-4.0 libc6-dev libstdc++6-4.0-dev linux-kernel-headers make
Suggested packages:
binutils-doc cpp-doc gcc-4.0-locales debian-keyring gcc-4.0-doc lib64stdc++6 manpages-dev autoconf automake1.9 libtool
flex bison gcc-doc libc6-dev-amd64 lib64gcc1 glibc-doc libstdc++6-4.0-doc stl-manual
Recommended packages:
libmudflap0-dev
The following NEW packages will be installed:
binutils build-essential cpp cpp-4.0 dpkg-dev g++ g++-4.0 gcc gcc-4.0 libc6-dev libstdc++6-4.0-dev linux-kernel-headers
make
0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.0MB of archives.
After unpacking 47.1MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://security.ubuntu.com dapper-security/main binutils 2.16.1cvs20060117-1ubuntu2.1 [1407kB]
Get:2 http://us.archive.ubuntu.com dapper/main linux-kernel-headers 2.6.11.2-0ubuntu18 [1039kB]
Get:3 http://us.archive.ubuntu.com dapper/main libc6-dev 2.3.6-0ubuntu20 [2822kB]
Get:4 http://us.archive.ubuntu.com dapper/main cpp-4.0 4.0.3-1ubuntu5 [1987kB]
Get:5 http://us.archive.ubuntu.com dapper/main cpp 4:4.0.3-1 [31.0kB]
Get:6 http://us.archive.ubuntu.com dapper/main gcc-4.0 4.0.3-1ubuntu5 [513kB]
Get:7 http://us.archive.ubuntu.com dapper/main gcc 4:4.0.3-1 [5048B]
Get:8 http://us.archive.ubuntu.com dapper/main libstdc++6-4.0-dev 4.0.3-1ubuntu5 [1471kB]
Get:9 http://us.archive.ubuntu.com dapper/main g++-4.0 4.0.3-1ubuntu5 [2271kB]
Get:10 http://us.archive.ubuntu.com dapper/main g++ 4:4.0.3-1 [1386B]
Get:11 http://us.archive.ubuntu.com dapper/main make 3.80+3.81.b4-1 [286kB]
Get:12 http://us.archive.ubuntu.com dapper/main dpkg-dev 1.13.11ubuntu6 [163kB]
Get:13 http://us.archive.ubuntu.com dapper/main build-essential 11.1 [6826B]
Fetched 12.0MB in 25s (476kB/s)
Selecting previously deselected package binutils.
(Reading database ... 72172 files and directories currently installed.)
Unpacking binutils (from .../binutils_2.16.1cvs20060117-1ubuntu2.1_i386.deb) ...
Selecting previously deselected package linux-kernel-headers.
Unpacking linux-kernel-headers (from .../linux-kernel-headers_2.6.11.2-0ubuntu18_i386.deb) ...
Selecting previously deselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.3.6-0ubuntu20_i386.deb) ...
Selecting previously deselected package cpp-4.0.
Unpacking cpp-4.0 (from .../cpp-4.0_4.0.3-1ubuntu5_i386.deb) ...
Selecting previously deselected package cpp.
Unpacking cpp (from .../cpp_4%3a4.0.3-1_i386.deb) ...
Selecting previously deselected package gcc-4.0.
Unpacking gcc-4.0 (from .../gcc-4.0_4.0.3-1ubuntu5_i386.deb) ...
Selecting previously deselected package gcc.
Unpacking gcc (from .../gcc_4%3a4.0.3-1_i386.deb) ...
Selecting previously deselected package libstdc++6-4.0-dev.
Unpacking libstdc++6-4.0-dev (from .../libstdc++6-4.0-dev_4.0.3-1ubuntu5_i386.deb) ...
Selecting previously deselected package g++-4.0.
Unpacking g++-4.0 (from .../g++-4.0_4.0.3-1ubuntu5_i386.deb) ...
Selecting previously deselected package g++.
Unpacking g++ (from .../g++_4%3a4.0.3-1_i386.deb) ...
Selecting previously deselected package make.
Unpacking make (from .../make_3.80+3.81.b4-1_i386.deb) ...
Selecting previously deselected package dpkg-dev.
Unpacking dpkg-dev (from .../dpkg-dev_1.13.11ubuntu6_all.deb) ...
Selecting previously deselected package build-essential.
Unpacking build-essential (from .../build-essential_11.1_i386.deb) ...
Setting up binutils (2.16.1cvs20060117-1ubuntu2.1) ...

Setting up linux-kernel-headers (2.6.11.2-0ubuntu18) ...
Setting up libc6-dev (2.3.6-0ubuntu20) ...
Setting up cpp-4.0 (4.0.3-1ubuntu5) ...
Setting up cpp (4.0.3-1) ...

Setting up gcc-4.0 (4.0.3-1ubuntu5) ...
Setting up gcc (4.0.3-1) ...

Setting up make (3.80+3.81.b4-1) ...

Setting up dpkg-dev (1.13.11ubuntu6) ...
Setting up g++-4.0 (4.0.3-1ubuntu5) ...
Setting up libstdc++6-4.0-dev (4.0.3-1ubuntu5) ...

Setting up g++ (4.0.3-1) ...

Setting up build-essential (11.1) ...

Looked good I thought, next step:


kenny@Kenny-Linux:~$ cd /usr/src sudo tar xjvf alsa-driver.tar.bz2 cd modules/alsa-driver
kenny@Kenny-Linux:/usr/src$ sudo ./configure --with-kernel=/usr/src/linux-headers-$kenny --with-cards=ess18xx --with-oss=yes
sudo: ./configure: command not found

And thats where I fall apart :???:

Any thoughts? And sorry for the length, if you need me to edit some out, can do.

~Kendb3

LordRaiden
July 31st, 2006, 05:56 PM
waltn - you need to have your media player choose your Hi-Fi card for output. You would select ALSA as output, and hw:2,0 as your hardware (replace the field that says "default"). This can vary media player to media player so I cannot give specifics. You need to go to something like Tools --> Configure... --> Engine, and make the changes there.

CarbonPlexus - You seem to have a usb-audio module. Do you have USB speakers? They have their own built-in sound card and you would not be able to use the Audigy for output.

kendb3 - your soundcard is not being detected at all. If it not onboard, I think it could be an ISA card. You should use "--with-isapnp=yes" in your ./configure. Also, when I said to write $(uname -r), actually type $(uname -r) not your user name.

caseyboardman
July 31st, 2006, 06:58 PM
Thank you. This worked for me on Dapper Drake with the hda-intel drivers.

x64Jimbo
July 31st, 2006, 09:28 PM
Bump! :)
I'm looking for a way to make KDE make more sound. Right now, my sound level is very low, and I have to turn my speakers up pretty loud in order to hear anything at a decent volume, and pretty much full blast to fill the room with music. Considering that I know what these speakers are capable of from having used them in Windows, I'd like to find a way to pre-amp my sound inside the OS so that it comes out louder without having to crank the volume knob all the way up. I've already played with my mixer and all sliders are maxed. Is there a tweak for alsa that lets you set the volume PLUS a given amount or something? Maybe a program that listens to the sound in RAM and puts out the very same thing on another channel at the same time, doubling the output? I'm stumped.

LordRaiden
July 31st, 2006, 11:51 PM
Check the sliders for your media player as well as alsamixer. Look at settings for PCM and possible DXS (PCM should be at 80%, DXS should be 100%).

x64Jimbo
August 1st, 2006, 12:19 AM
As I said, all sliders are maxed. Everywhere. Turning PCM down to 80% makes no difference.

waltn
August 1st, 2006, 01:34 AM
waltn - you need to have your media player choose your Hi-Fi card for output. You would select ALSA as output, and hw:2,0 as your hardware (replace the field that says "default"). This can vary media player to media player so I cannot give specifics. You need to go to something like Tools --> Configure... --> Engine, and make the changes there.
Thank you for the reply. I have playing working with e.g RythmBox Player, but Audacity refuses to work. The only output device Audacity shows as available is /dev/dsp (same for capture).

My .asoundrc contains:
# ALSA library configuration file

# Include settings that are under the control of asoundconf(1).
# (To disable these settings, comment out this line.)
</home/walt/.asoundrc.asoundconf>

My .asoundrc.asoundconf file contains:
# ALSA library configuration file managed by asoundconf(1).
#
# MANUAL CHANGES TO THIS FILE WILL BE OVERWRITTEN!
#
# Manual changes to the ALSA library configuration should be implemented
# by editing the ~/.asoundrc file, not by editing this file.
!defaults.pcm.card HiFiLink
defaults.ctl.card HiFiLink
defaults.pcm.device 0
defaults.pcm.subdevice -1

If one of these should contain the hw:2,0, please indicate where.

Again, thanks for the help!
Walt

kendb3
August 1st, 2006, 05:09 AM
kendb3 - your soundcard is not being detected at all. If it not onboard, I think it could be an ISA card. You should use "--with-isapnp=yes" in your ./configure. Also, when I said to write $(uname -r), actually type $(uname -r) not your user name.

Ok, thanks for the info, I overthought the uname part a bit too much. I walked through the steps back up to getting what's below. Though I still get the error: "E: Couldn't find package module-assistant" which doesn't bother me as much as the error, ./configure: command not found, am I missing something important as far as the system is concerned?


kenny@Kenny-Linux:~$ cd /usr/src sudo tar xjvf alsa-driver.tar.bz2 cd modules/alsa-driver
kenny@Kenny-Linux:/usr/src$ sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=ess18xx --with-oss=yes
sudo: ./configure: command not found
kenny@Kenny-Linux:/usr/src$ sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=ess18xx --with-isapnp=yes
sudo: ./configure: command not found

Thanks again for the help man ;-)

~kendb3

CarbonPlexus
August 2nd, 2006, 01:11 AM
CarbonPlexus - You seem to have a usb-audio module. Do you have USB speakers? They have their own built-in sound card and you would not be able to use the Audigy for output.

I don't have USB speakers. I just have normal speakers plugged into the Audigy card. I do have a webcam that has a microphone in it. Would that be why I have a USB audio module? As far as I know I just have the onboard sound (via82cxxx) which I recently disabled in the bios and the Audigy sound card plugged into a PCI slot.

LordRaiden
August 2nd, 2006, 03:57 AM
Ok, thanks for the info, I overthought the uname part a bit too much. I walked through the steps back up to getting what's below. Though I still get the error: "E: Couldn't find package module-assistant" which doesn't bother me as much as the error, ./configure: command not found, am I missing something important as far as the system is concerned?


kenny@Kenny-Linux:~$ cd /usr/src sudo tar xjvf alsa-driver.tar.bz2 cd modules/alsa-driver
kenny@Kenny-Linux:/usr/src$ sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=ess18xx --with-oss=yes
sudo: ./configure: command not found
kenny@Kenny-Linux:/usr/src$ sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=ess18xx --with-isapnp=yes
sudo: ./configure: command not found

Thanks again for the help man ;-)

~kendb3

after doing the tar, you have to cd into the alsa-driver directory that was extracted i.e. cd alsa-driver. then do sudo ./configure...

CarbonPlexus - You driver is snd_emu10k1; however, it is obviously being loaded. Can you do
alsamixer and see what it says at the top (name of soundcard)? You'll get a whole bunch of volume sliders and switches to play with.

muz1
August 2nd, 2006, 04:06 AM
I will have to say that this tutorial is great. It gets my sound back but it just does not stick.
The fact that when I reboot the sound is there tells me that it works. The problem is that I can reboot the next day and it will not work. Coming from a windows background, I know that if there is a conflict during boot up, a service will not start. What I am trying to work out is does this happen with Linux.
Sys specs:
Ubuntu 6.06
AMD 1.8 gHz
1gig ram
Soundcard is specified as AK5370 but also has Via 8236 in the System > Preferences > Sound > Sounds > Default Sound Card Drop down box

Any assistance would rock.
Thanks in advance.
muz:-k

LordRaiden
August 3rd, 2006, 04:46 AM
do a reboot then do aplay -l in the console. If you get something about the driver being missing, add "snd-via82xx" to /etc/modules.

sawjew
August 3rd, 2006, 08:54 AM
I have tried everything in this guide, I have reinstalled the alsa drivers and installed from source, both Ubuntu source and ALSA source and still no go.

The sound works for applications that use OSS (e.g Frozen-Bubble) but nothing works for ALSA.

When I go to the Multimedia Systems Selector and select ALSA and test I get
ALSA - Advanced Linux Sound Architecture: Could not open resource for writing.
When I select ESD and test I get
ESD - Enlightenment Sound Daemon: Could not establish connection to sound server
When I select OSS and test it works.

No system sounds play even when I test them under >System>Preferences>Sound.

The system has 2 soundcards an onboard VIA and a PCI C-Media card. The onboard sound was working initially but none of the methods for selecting the PCI card worked so I disabled it in the BIOS and it no longer shows up in the system.

This card has worked perfectly in Hoary and Breezy, but I am almost ready to give up in Dapper.

aplay -l produces

**** List of PLAYBACK Hardware Devices ****
card 0: CMI8738MC6 [C-Media PCI CMI8738-MC6], device 0: CMI8738-MC6 [C-Media PCI DAC/ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CMI8738MC6 [C-Media PCI CMI8738-MC6], device 1: CMI8738-MC6 [C-Media PCI 2nd DAC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CMI8738MC6 [C-Media PCI CMI8738-MC6], device 2: CMI8738-MC6 [C-Media PCI IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0


lspci -v produces

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
Subsystem: Elitegroup Computer Systems: Unknown device 0989
Flags: bus master, medium devsel, latency 8
Memory at d0000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: d8000000-d9ffffff
Prefetchable memory behind bridge: d4000000-d7ffffff
Capabilities: <available only to root>

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <available only to root>

0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Flags: bus master, medium devsel, latency 32
I/O ports at d000 [size=16]
Capabilities: <available only to root>

0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d400 [size=32]
Capabilities: <available only to root>

0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d800 [size=32]
Capabilities: <available only to root>

0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
Flags: medium devsel, IRQ 9
Capabilities: <available only to root>

0000:00:0a.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e000 [size=256]
Capabilities: <available only to root>

0000:00:0c.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
Subsystem: D-Link System Inc DFE-538TX 10/100 Ethernet Adapter
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e400 [size=256]
Memory at da000000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF/SG AGP (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Fury
Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 10
Memory at d4000000 (32-bit, prefetchable) [size=64M]
I/O ports at c000 [size=256]
Memory at d9000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at d8000000 [disabled] [size=128K]
Capabilities: <available only to root>


cat /proc/asound/modules produces

0 snd_cmipci



asoundconf is-active

then
asoundconf list produces

Names of available sound cards:


I have no more ideas, can anyone help?

I have tried all sorts of fiddling in alsamixer but I can only get OSS applications to work.

muz1
August 3rd, 2006, 02:41 PM
do a reboot then do aplay -l in the console. If you get something about the driver being missing, add "snd-via82xx" to /etc/modules.

Hey Lord Raiden. Thanks for the help.
I did waht you said and this was the response.

**** List of PLAYBACK Hardware Devices ****
card 0: V8235 [VIA 8235], device 0: VIA 8235 [VIA 8235]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: V8235 [VIA 8235], device 1: VIA 8235 [VIA 8235]
Subdevices: 1/1
Subdevice #0: subdevice #0

I then went into the /etc/modules file and surely enough snd-via82xx was not there.
The problem is that I have put that in twice before and it disappears.
I know it saves it because after I reboot, it plays sound.
Then the next day, it disappears. I must admit though, it is nice to know what starts the sound.
Do you have any suggestions?
Cheers muchly
muz

geovino
August 3rd, 2006, 03:19 PM
Is Alsa the only sound drivers? I've heard of some others. I've been having trouble getting Xmms to be more stable when playing live streams. Is there a way to configure it so it doesn't freeze up so often?

BobSongs
August 4th, 2006, 01:36 AM
Moved to main thread area.

muz1
August 5th, 2006, 03:12 AM
Lord Raiden
A question for you if you have by any chance a spare second.
I have my system setup perfectly the way I want it. All apart from sound.
I put the snd-via82xx at the end of the /etc/modules file and the first time the sound worked.
The next time I booted, I did not hear the startup sound so I tried to play an mp4 and it said "Could not establish connection with sound server". At other times a program of process called Totem is mensioned to. I checked the /etc/modules file and the snd-via line is still there. (At the end).
Does it matter where I paste the snd-via command in the /etc/modules file?
This is really frustrating as I work with multimedia and I am trying my hardest not to go back to windows with my tail between my legs.

Cheers and thanks
Muz

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
psmouse
snd-via82xx

bnlandry
August 5th, 2006, 08:20 AM
I am at the end of my rope, trying to get sound to work in my Asus a62f notebook with Dapper. I am an Ubuntu newb, but I have learned alot trying to get some sound out of this thing. I get absolute silence throughout Ubuntu, but no errors. I have volume sliders, and changing their settings does squat. For the details of what I've done most recently, please look here (http://www.gensmetro.org/misc/troubleshoot.html).

Basically, I have attempted to use the Comprehensive Sound Problems Guide, to no avail. I have attempted multiple ways of installing the ALSA drivers, as well as attempting to install the Realtek drivers. for the most part, these installations go fine, but do not result in sound.

In my most recent ALSA-Project driver install with 1.0.12rc1, I did get an error. Make exited with:


/home/byron/src/alsa/alsa-driver-1.0.12rc1/pci/asihpi/hpi56301.c:86:22: error: dpi56301.h: No such file or directory

So there's that. Any assistance would be greatly appreciated. I know I haven't been very detailed, but it's tough considering everything I've tried. Also, please advise if I should post this somewhere else.

Thanks

mnow
August 5th, 2006, 08:43 AM
I have tried your resolv but when trying to re-install as in
sudo get-apt install linux-sound-base alsa-base alsa-utils I get "package linux-sound-base is not available, but is referred to by another package.".
Where may I have gone wrong?

Thanx,
mnow

silbar
August 7th, 2006, 03:07 PM
I posted a new thread after following these instructions: "SoundBlaster AWE 64: error following Lord Raiden's Solutions Guide". Posting this notice here in case some knowledgeable person might have missed it.

rck_hitokiri
August 7th, 2006, 04:53 PM
my sound is sounding like a broken old record or its pitching up and down. can someon please help me... i really need it. thanks

Olav
August 7th, 2006, 09:52 PM
This may help someone.

My cheap piece-of-trash motherboard has a built in VIA8235 sound chip. Every time I installed Ubuntu I had the same problem: in the Gnome volume applet the Master volume does nothing, I have to control the volume with the Headphone slider. It is annoying because volume control keys on my multimedia keyboard won't work either - they operate on the Master only.

Turns out to be an easy fix, once you know:


sudo gedit /etc/modprobe.d/alsa-base
add at the bottom: options snd-via82xx ac97_quirk=2
reboot

Possible values for the ac97_quirk are:

-1 = default, don't override
0 = disable
1 = use headphone control as master
2 = swap headphone and master controls
3 = for AD1985, turn on OMS bit and use headphone

(as found on http://alsa.opensrc.org/index.php?page=via8233)

Should work with other sound chips as well, if they have the same problem, just substitute snd-via82xx with the name of your driver.

Warrenpeace
August 9th, 2006, 02:24 PM
Okay, I'm completely new to Linux, and I'm just trying to get my feet wet with Ubuntu. I have a Soyo KT600 MoBo with Via 8237 audio (at least that's what Linux tells me).

I've tried all the suggestions here, and it still doesn't work. Can anyone help me? I'll post what ever needs to be posted.

Here is what aplay -l get's me:


**** List of PLAYBACK Hardware Devices ****
card 0: V8237 [VIA 8237], device 0: VIA 8237 [VIA 8237]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: V8237 [VIA 8237], device 1: VIA 8237 [VIA 8237]
Subdevices: 1/1
Subdevice #0: subdevice #0
miles@miles-desktop:~$


And this is lspci -v:


0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Capabilities: [c0] Power Management version 2

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: dde00000-dfefffff
Prefetchable memory behind bridge: cdd00000-ddcfffff
Capabilities: [80] Power Management version 2

0000:00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
Subsystem: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless
Flags: 66MHz, medium devsel, IRQ 193
Memory at dffe0000 (32-bit, non-prefetchable) [size=64K]
Memory at dffd0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2

0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
Subsystem: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller
Flags: bus master, medium devsel, latency 32, IRQ 169
I/O ports at ec00 [size=8]
I/O ports at e800 [size=4]
I/O ports at e400 [size=8]
I/O ports at e000 [size=4]
I/O ports at dc00 [size=16]
I/O ports at d800 [size=256]
Capabilities: [c0] Power Management version 2

0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Flags: bus master, medium devsel, latency 32, IRQ 169
I/O ports at fc00 [size=16]
Capabilities: [c0] Power Management version 2

0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at c800 [size=32]
Capabilities: [80] Power Management version 2

0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at cc00 [size=32]
Capabilities: [80] Power Management version 2

0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2

0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2

0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Flags: bus master, medium devsel, latency 32, IRQ 177
Memory at dfffbe00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2

0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: Elitegroup Computer Systems: Unknown device a101
Flags: medium devsel, IRQ 209
I/O ports at c400 [size=256]
Capabilities: [c0] Power Management version 2

0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
Flags: bus master, medium devsel, latency 32, IRQ 201
I/O ports at c000 [size=256]
Memory at dfffbd00 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2

0000:01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1) (prog-if 00 [VGA])
Subsystem: LeadTek Research Inc.: Unknown device 2937
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 185
Memory at de000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at dfee0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0

LordRaiden
August 9th, 2006, 06:40 PM
Warrenpeace - Your module is installed, I suggest you tweak your ALSAMixer settings.

Warrenpeace
August 9th, 2006, 07:17 PM
What would you recommend I try tweaking?

LordRaiden
August 9th, 2006, 08:25 PM
The PCM settings (around 80%), master volume, and the DXS channels (far right).

CarbonPlexus
August 9th, 2006, 09:26 PM
CarbonPlexus - You driver is snd_emu10k1; however, it is obviously being loaded. Can you do
alsamixer and see what it says at the top (name of soundcard)? You'll get a whole bunch of volume sliders and switches to play with.

In alsamixer it says Audigy 1 [SB0090] for the soundcard. I played with all the sliders and switches but still no sound. I tried muting and unmuting stuff too. I'm still not sure what's wrong with it if the driver's being loaded like you said. Thanks for your help so far, I really appreciate it.
Also for the options in alsamixer I have [Line] [CD] [Mic Boos] [Phone] [PC Speak] [Aux] [Audigy A] and [External]. I don't know if that helps at all. I know it seemed like when I first installed Dapper I had a lot more sliders but now I don't.

Warrenpeace
August 10th, 2006, 01:03 AM
Okay, so I've tried to mess with all the settings in alsa mixer, and it's not working for me. Does anyone have any ideas on what to do next, I'm pretty stuck at this point!

shanepardue
August 10th, 2006, 04:21 AM
i had sound, but it broke when i tried to update the driver. now i have no sound


aplay: device_list:221: no soundcards found...

this is how i broke the soundcard


sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
sudo apt-get install linux-sound-base alsa-base alsa-utils
sudo apt-get install gdm ubuntu-desktop

i've tried compiling the alsa-source and it goes through fine, but still no soundcard showing

teh_chris
August 10th, 2006, 07:12 AM
this is a good tutorial, definitely more info than i ever cared to know about sound cards.

i have a motherboard with an integrated via sound card.

aplay -l returns:
aplay: device_list:221: no sound cards found...

lspci -v says:
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7061
Flags: medium devsel, IRQ 185
I/O ports at eb00 [size=256]
Capabilities: [c0] Power Management version 2

sudo modprobe snd-via82xx returns no errors, but does not change the output of aplay -l

i know the sound card works cuz i have heard sound from it when i first installed ubuntu (and even remarked to myself, wow the sound worked out of the box).

i did the purge on the alsa with no luck, tho i did watch it take out gnome-applets, nautilus and gdm/ubuntu desktop

i also reinstalled the alsa source using the assistant, still, aplay seems to hate my sound card.

i added the snd-via82xx module in /etc/modules and even the options snd-via82xx ac97_quirk=2 to /etc/modprobe.d/alsa-base just for the hell of it. sitll aplayer mocks me with it's device_list:221: no sound cards found...

alsa miser listed the card as a via 8237 when i unmuted everything and cranked the volumes into the red.

i am pretty sure i had sound up until i added vnc4server and muted the sound in a remote session.

is there anything else i should try before i re-install ubuntu again?

is there a PCI sound card that is rated "bulletproof" that i could buy?

(you know, choose your software, then your hardware)

also, since sound and GDM are so closely tied, is there a way to block sound from everything but the session logged in at the console ( localhost:0 )?

LordRaiden
August 10th, 2006, 04:53 PM
shanepardue & teh_chris - can you both give the output of
dmesg | grep snd

shanepardue
August 10th, 2006, 05:00 PM
shanepardue & teh_chris - can you both give the output of
dmesg | grep snd

well, i have since restored a partition image and have my sound back, but i'm still stuck with the original problem. the audio doesn't match the video. i see people's mouths moving, but voices come after.

any ideas on that?

LordRaiden
August 10th, 2006, 08:30 PM
well, i have since restored a partition image and have my sound back, but i'm still stuck with the original problem. the audio doesn't match the video. i see people's mouths moving, but voices come after.

any ideas on that?
Is the sound "lagging behind" the video? Is it slow or beeping, chiriping etc.? If it is not, it would be a something with your video player.

shanepardue
August 10th, 2006, 08:37 PM
Is the sound "lagging behind" the video? Is it slow or beeping, chiriping etc.? If it is not, it would be a something with your video player.

it is lagging behind the video..no problems with sound other than that. i have tried both mplayer and totem and they have the same issue. i can try vlc and see if that helps.

so you think it's not the sound driver and that is in fact the software i'm using?

LordRaiden
August 10th, 2006, 09:04 PM
it is lagging behind the video..no problems with sound other than that. i have tried both mplayer and totem and they have the same issue. i can try vlc and see if that helps.

so you think it's not the sound driver and that is in fact the software i'm using?
Quite possibly. A newer sound driver would not mean your sound would play any faster (unless the older version had serious problems). It is probably a setting issue. Totem and mplayer are used by a lot of Ubuntuers so slow sound in those applications would have been fixed by now. Check the output engine and switch it to alsa if possible.

shanepardue
August 10th, 2006, 09:14 PM
Quite possibly. A newer sound driver would not mean your sound would play any faster (unless the older version had serious problems). It is probably a setting issue. Totem and mplayer are used by a lot of Ubuntuers so slow sound in those applications would have been fixed by now. Check the output engine and switch it to alsa if possible.

ok, im not at home near my linux box right now, but when i attempt to fix it this evening, i will check the output engine and possibly the cache. those are the only settings that come to mind regarding this idea. feel free to add any other ideas!

i appreciate your help!

shanepardue
August 11th, 2006, 01:18 AM
Quite possibly. A newer sound driver would not mean your sound would play any faster (unless the older version had serious problems). It is probably a setting issue. Totem and mplayer are used by a lot of Ubuntuers so slow sound in those applications would have been fixed by now. Check the output engine and switch it to alsa if possible.
how would you fix the issue if it happens with flash in firefox?

youtube and others are way off. i've noticed dvd's are ok, but the problem remains with compressed video as well as streaming.

rck_hitokiri
August 11th, 2006, 03:39 AM
hey guys! what do i have to do to enable using 2 apps at the same time without one of em getting errors that the sound driver is used by another app? i have alsa oss installed... e.g. hydrogen and audacity at the same time but surely on my box one isnt gonna play why the other is open. thanks! :D

Warrenpeace
August 11th, 2006, 04:40 AM
I fixed my sound. It was really easy, actually. I went to CompUSA and bought the cheapest card they had. It worked on boot up. Amazing!
:KS :KS

muz1
August 11th, 2006, 07:04 AM
Hi.
I am running Ubuntu 6.06 and am having a terrible time with sound.
It is so unstable.
It basically seems like only one thing can work with sound. Also as soon as something shuts down abnormally, sounds dies foreverything. Sometimes it will not come back after a reboot.

I have checked /etc/modules which contains the following.

lp
psmouse
snd-via82xx

Nothing has changed. Has anyone else experienced this???

Cheers
muz

Myrgen
August 11th, 2006, 06:13 PM
I am copying my own thread here, as it seems no one else can answer. I hope someone following this thread will be able to give me some advice.
QUOTE
I am new to Linux, and installed Ubuntu 5. I was very happy with it, no problems at all. Then I upgraded to Dapper Drake 6.06 (gnome), and problems started popping up.
1) Video started 'hiccuping'
2) Audio was hiccuping too
3) Mouse pointer is sluggish, making it a nightmare to do anything
4) Eventhough the system recognizes a blank disk inserted, when trying to burn it, it asks me to insert a new blank disk, eventhough I tried even with a very little file.
After doing a full reinstall, I added updates and apps one by one, changing some settings, one by one, rebooting each time. I finally found out that the source of the problem was: the sound card:
The system set the 'camera' as the default sound card, (Logitech webcam), shows only the microphone properties in the toolbar, and when I changed it to the VIA 82XX integrated sound card I have and rebooted, the sluggishness of the mouse came back with all the other issues.
I reset the default to 'camera', rebooted, and everything was fine again.
Everything except that I have no sound, hence no video either

Any idea, advice, suggestion? any help would be greatly appreciated.

***UPDATE*****
I followed the steps in the Comprehensive Sound Problem Solutions Guide, http://ubuntuforums.org/showthread.php?t=205449
up and including point (4). Everything looked fine. Then I rebooted... and the problems listed above returned.
Hence, I'm back to square one..
UNQUOTE

Thanks in advance for any help..

tjfitz
August 11th, 2006, 06:24 PM
Here is the problem I am having with sound. When I start up and log in, my sound works beautifully, but sometimes after being away from the machine for a while (not logging out, just letting the screen lock), when I come back and unlock the screen the sound doesn't work anymore. If I restart the machine the sound is fine (but for crying out loud this isn't a windoze box). I also tried
/etc/init.d/alsa-utils restart but that didn't help.
aplay -l and
lspci -v were successful, but at
sudo modprobe snd-<tab> I don't get anything that looks like it matches my soundcard (nForce2 chipset, "Onboard 6-channel AC 97 CODEC" audio, according to the manual). The last time this happened I went through the "getting the ALSA drivers from a fresh kernel" process, which worked temporarily. I haven't monkeyed around with any settings in ALSA that can't be accessed via alsamixer. Any ideas about what's causing this sporadic problem? I do play World of Warcraft under Cedega on this machine, which could possibly stress out the sound system, but I haven't observed a correlation between playing and losing sound output (primarily I don't notice that I've lost sound output until I try to play!). I'm going to reboot and this problem will probably be gone for a little while, but I'm sure it will show up again within the next few days.

LordRaiden
August 11th, 2006, 08:00 PM
tjfitz - i think your card is an hda-intel, so do:
sudo modprobe hda-intel

rck_hitokiri - see if you select "alsa" as an output engine for both apps under a Configuration/Tools/Settings menu. If you cannot do it for one or the other, run that application using alsa-oss. For example, suppose hydrogen does not have alsa output. Run
alsa-oss hydrogen, then audacity. It should work.

muz1 - when the sound stops working, do a
dmesg | grep snd and try doing
sudo modprobe snd-via82xx

Myrgen - try removing your camera and follow my instructions again, without the camera. Also, paste the output of

aplay -l
dmesg | grep snd

teh_chris
August 11th, 2006, 09:02 PM
appearantly is not denial so much as confusion:


dmesg | grep snd
[17179593.920000] snd_seq_dummy: disagrees about version of symbol snd_seq_create_kernel_client
[17179593.920000] snd_seq_dummy: Unknown symbol snd_seq_create_kernel_client

/etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
psmouse
snd-via82xx

Myrgen
August 11th, 2006, 09:07 PM
Thanks for helping!
dmesg | grep snd doesn't give any output at all.

output of aplay -l:
**** List of PLAYBACK Hardware Devices ****
card 1: V8235 [VIA 8235], device 0: VIA 8235 [VIA 8235]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: V8235 [VIA 8235], device 1: VIA 8235 [VIA 8235]
Subdevices: 1/1
Subdevice #0: subdevice #0

LordRaiden
August 12th, 2006, 01:04 AM
Myrgen - your soundcard is installed and since dmesg | grep snd did not give any output everything is ok.

Two things to check.
1) Is there a .asoundrc file in your home directory (i.e. /home/myrgen)? If there is delete it then reboot.

2) Go to /etc/group
cat /etc/group. Scroll over to the line where it says audio and see if your user name is on the line. If it is not you have to edit.
sudo nano /etc/group Go to the audio line, and add yourself

so if you have something like
audio:x:29:user and you wanted to add the user, "newuser" add the user like so
audio:x:29:user, newuser

teh_chris - You might need to recompile your drivers. However, since you said your sound was fine till you muted the sound using vncserver, you could try remotely logging in and checking if the sound is muted again. No idea at all if it would help, but it'd be a nice fix over a recompile.

louis_nichols
August 12th, 2006, 01:08 AM
I have an nForce2 chipset with an AC'97 card. In windows, I am able to use mic and line-in as outputs, to get 5.1 sound. The same thing must be possible in Ubuntu.

But how? Any ideas?

rck_hitokiri
August 12th, 2006, 04:48 AM
Didnt work raiden... sad to say... maybe im lacking repositories for audio or alsa?? you have any suggestions on this? im using ess audio drive (snd-es18xx) well anyway thanks for your time and help. Please inform me if you have any ideas... cheers.

Myrgen
August 12th, 2006, 10:14 AM
I did all that you said, but as soon as I rebooted, the horrendously sluggishness of the mouse returned, the terribly slow to react system was back.. I had sound though: the login tambourin was there.. and didn't stop. Had to revert all settings, re-plug the camera and reboot to have a working system. It seems that Ubuntu can't live with my via8235 card :(
Any further advice?

mcframe
August 12th, 2006, 10:52 AM
I have worked for weeks on my sound problem and finally solved it. Maybe it would help others, so I describe it over here.
In my case all modules were loaded correctly, aplay -l show the working soundcard, but no sound appeared neither in shell or kde.
I suspected the mixer settings but modifying or deleting /var/lib/alsa/asound.state had no effect. No I found out why: KDE also restores the mixer settings and if they are wrong somehow, this will be stored to /var/lib/alsa/asound.state as well.

In order to wipe out all stored mixer settings one has to delete /var/lib/alsa/asound.state as well as ~./.kde/share/config/kmixctrlrc and ~./.kde/share/config/kmixrc

But this does not change the actual wrong settings of the sound card, which are stored again to /var/lib/alsa/asound.state as soon as linux is rebootet. Unfortunately this would restore the settings at every new boot.
To disable storing of mixer levels on shutdown, remove /etc/rc[06].d/K50alsa-utils. To disable restoring of mixer
levels on bootup, rename the "S50alsa-utils" symbolic link in /etc/rcS.d/ to "K50alsa-utils"

Hope it helps someone out there
Cheers
mcframe

LordRaiden
August 12th, 2006, 02:52 PM
louis_nichols - I would not know know how to do that. In an music player like amarok, you can pick the kind of output you want (default, 5.1, headphones) but I don't know how you would enable it on the card. I think there might be better resources on alsa-project and alsa-wiki.

rck_hitokiri - Sorry, I meant
aoss hydrogen I also found some resources:
http://audacityteam.org/wiki/index.php?title=Linux_Issues
http://www.hydrogen-music.org/content/tutorial/manual_en.html#configurazioneAudioDriver

Apparently, hydrogen now works with ALSA, and audacity can be compiled with ALSA support. You would probably have to compile the latest versions but then you would not have to worry about one application controlling the sound.

Myrgen - I think your problem could be beyond just sound. I use a VIA8235 card in my setup and its working without sluggishness. If you really think sound is the problem, try disabling the VIA8235 in your BIOS. Also, since your mouse is sluggish, try unplugging then replugging, or using another mouse.

louis_nichols
August 12th, 2006, 03:36 PM
louis_nichols - I would not know know how to do that. In an music player like amarok, you can pick the kind of output you want (default, 5.1, headphones) but I don't know how you would enable it on the card. I think there might be better resources on alsa-project and alsa-wiki.

rck_hitokiri - Sorry, I meant
aoss hydrogen I also found some resources:
http://audacityteam.org/wiki/index.php?title=Linux_Issues
http://www.hydrogen-music.org/content/tutorial/manual_en.html#configurazioneAudioDriver

Apparently, hydrogen now works with ALSA, and audacity can be compiled with ALSA support. You would probably have to compile the latest versions but then you would not have to worry about one application controlling the sound.

Myrgen - I think your problem could be beyond just sound. I use a VIA8235 card in my setup and its working without sluggishness. If you really think sound is the problem, try disabling the VIA8235 in your BIOS. Also, since your mouse is sluggish, try unplugging then replugging, or using another mouse.

Thanks for the reply!

The thing is I've pretty much searched everywhere I could think of and tried everything I found, but no joy.

At the most, I had on line-out duplicated sound from line-in, which is pretty frustrating, because it seems so close!

LordRaiden
August 12th, 2006, 05:19 PM
Have you tried bug.alsa-project? They have more in depth knowledge about that feature.

Tyche
August 12th, 2006, 11:32 PM
When all else fails, see "ALSA Sound Problems - Solution". This describes where to go and what to do to actually install the Alsa drivers the way they should be installed.

It was the only thing that worked for me.

Craig
(Tyche)

kbabyxx
August 13th, 2006, 09:48 AM
Thanks, great guide. Additional contribution by Bo Rosén help me fix the problem of my soundblaster not being recognised by edubuntu 6.06

pneaveill
August 13th, 2006, 01:11 PM
When all else fails, see "ALSA Sound Problems - Solution". This describes where to go and what to do to actually install the Alsa drivers the way they should be installed.

It was the only thing that worked for me.

Craig
(Tyche)
Do you have a list of websites that we can glean from?

ronoc
August 13th, 2006, 04:30 PM
Guys,
Serious gripe.
Yesterday unknowingly I undid all the work to get my echoaudio layla 24 working by doing a distupgrade.
Is there anyway to revert back to the setup I had almost 24 hours ago.
Would I be correct in saying that the alsaversion on my machine was updated with a newer release without the modules which I had compiled-in previously. The hardware can be found. firmware is there. recompile alsa?.. pain!
C

jtbalt
August 13th, 2006, 06:10 PM
I had an issue with no sound showing up using a Soundblaster Extigy that plugs into the USB port even though it had been working previously, even when booting from the live CD. The unit worked fine in WinXP, but I could not get any sound while in ubuntu. I began following the troubleshooting guide and at one point in the install I noticed that the computer would try to shutdown but would just leave me unable to do anything and only with a cursor on the screen, requiring a press of the reset key.

Finally decided to do a clean install (not wanting to), but when I tried to save my web bookmarks to my USB thumbdrive I found that the computer did not "see" the USB drive. Some more poking around revealed that my ATI TV Wonder USB 2.0 was "locked" up and was preventing everything on my USB ports from being seen under linux, like the Extigy. A quick powerdown of the ATI TV Wonder unit and a system reset and everything was good as gold.

Not sure how to condense this, other than to say that if you suddenly lose sound when using an Extigy card, and it previously worked, make sure nothing else on the USB bus is causing the issue.

etitor
August 13th, 2006, 07:56 PM
LordRaiden,

Your guide is a wonderful contribution.

However, after spending many hours trying it without getting ALSA sound on my system, I discovered something that may be useful to mention here for the knowledge of those using, as me, a SPDIF connection from card to speakers in conjunction with the snd-ice1712 module (needed for ALSA sound on M-Audio Delta cards).

Bottom line: forget about configuration hassles. As is stated on the module page (but not often read, at least by me), snd-ice1712 doesn't support SPDIF connections. You have to let the ALSA sound out of your Delta card using the 6.5mm jacks (OSS sound works OK). A big nasty shortcoming in my opinion.

For the record, you can read the warning ("no spdif yet") here (http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Midiman%2FMAudio&card=Delta+66.&chip=ICE1712+%28Envy24%29&module=ice1712).

Hope it helps someone in need.

tjfitz
August 14th, 2006, 02:56 AM
tjfitz - i think your card is an hda-intel, so do:

Code:
sudo modprobe hda-intel

Unfortunately, this didn't turn up anything. However, after doing some more hunting, I am fairly certain the correct module is snd-intel8x0. I've added it to my /etc/modules and no recurrence yet, so possibly this is the correct solution. Thanks for your speedy reply, and my apologies for my tardy one!

rck_hitokiri
August 14th, 2006, 05:29 PM
[QUOTE=LordRaiden;1371226]louis_nichols - I would not know know how to do that. In an music player like amarok, you can pick the kind of output you want (default, 5.1, headphones) but I don't know how you would enable it on the card. I think there might be better resources on alsa-project and alsa-wiki.

rck_hitokiri - Sorry, I meant
aoss hydrogen I also found some resources:
http://audacityteam.org/wiki/index.php?title=Linux_Issues
http://www.hydrogen-music.org/content/tutorial/manual_en.html#configurazioneAudioDriver

Apparently, hydrogen now works with ALSA, and audacity can be compiled with ALSA support. You would probably have to compile the latest versions but then you would not have to worry about one application controlling the sound.

Thanks Doc. Helped Me a lot there. :D:D:D

Tyche
August 15th, 2006, 12:50 AM
Do you have a list of websites that we can glean from?

Sorry about the delay in getting back to you. To quote myself (the post I had placed in the main body):

I have finally resolved my sound-card problems, and offer this solution to others with the same "no sound" problem I have had.

Aparently, Ubuntu does not completely install Alsa, nor the sound devices necessary to operate the sound card. Instead, go to

http://www.alsa-project.org/alsa-doc/

Look up the sound card for your system by manufacturer (i.e. Creative Labs) to see if it is supported. This will take you to a page with the supported sound cards for that manufacturer listed. It will list the chipset and the driver. Click on the driver will take you to a page describing how to configure, make and install the Alsa drivers. Download the suggested files (use a second window/browser for this, so you can keep the instructions up).

SUGGESTION: To follow the directions, open a root terminal, or a standard one and log in as root (alternatively, you would have to preceed their instructions with sudo)

At the end of the directions, where it says to open alsamixer and adjust as necessary, you STILL may not be able to do so (the system may still not be able to find your sound card). RE-BOOT, and you should be able to open alsamixer.

BTW: I am NOT an expert in Linux, and don't know all the answers. I found this solution more by accident born of desperation than anything else, and it has taken me a number of months to find. If you have tried other solutions and have been unsuccessful, try this.

Craig
(Tyche)

pneaveill
August 15th, 2006, 02:16 AM
Appreciate the honesty with all that. Will work on that tomorrow (after a little sleep).

penquin
August 15th, 2006, 07:48 PM
in my /etc/modules do I put?

snd-cs4232 index=0 port=0x530 cport=0x538 isapnp=0 dma1=1 dma2=0 irq=5

because the sound card than works

pneaveill
August 15th, 2006, 08:26 PM
looking at http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Creative+Labs&card=Sound+Blaster+Audigy+ES.&chip=emu10k2&module=emu10k1#intro

and it says this:

NB. If you are using drivers before 0.9.4 then you need to run ./snddevices
If you use devfs then you should not run the snddevices script The snddevices script sets the permissions for the devices it creates to root. You should
chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi
forgive the noob question, but how do I find out which one I have/ need for my card? ](*,)

Tyche
August 16th, 2006, 12:38 AM
pneaveill,

When I compiled and installed the Alsa drivers, I found that none of the 4 devices had been set up. So, I took the gamble and ran ./snddevices, then changed the permissions as it suggested (actually, copy and paste). That's when I rebooted and it worked.

Craig
(Tyche)


looking at http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Creative+Labs&card=Sound+Blaster+Audigy+ES.&chip=emu10k2&module=emu10k1#intro

and it says this:

NB. If you are using drivers before 0.9.4 then you need to run ./snddevices
If you use devfs then you should not run the snddevices script The snddevices script sets the permissions for the devices it creates to root. You should
chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi
forgive the noob question, but how do I find out which one I have/ need for my card? ](*,)

pneaveill
August 16th, 2006, 12:42 PM
Been working on this for about 4 days now and still not getting it. Guess I am too much of a noob.


In a shell type these commands: Make a directory to store the alsa source code in.

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .
Now unzip and install the alsa-driver package
bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards=emu10k1 --with-sequencer=yes;make;make install
NB. If you are using drivers before 0.9.4 then you need to run ./snddevices

Guess i am having two issues with this.
(1) Maybe just a newbie thing. the cp /downloads thing -- what is that exactly? I have searched manually for it and it is not there. What am I missing?
(2) The TARball is unpacked and sitting on the drive. I just don't know what to do with it from here.

Please help

pneaveill
August 16th, 2006, 12:46 PM
Been working on this for about 4 days now and still not getting it. Guess I am too much of a noob. Maybe this will help:
modinfo soundcore
filename: /lib/modules/2.6.15-26-386/kernel/sound/soundcore.ko
description: Core sound module


In a shell type these commands: Make a directory to store the alsa source code in.

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .
Now unzip and install the alsa-driver package
bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards=emu10k1 --with-sequencer=yes;make;make install
NB. If you are using drivers before 0.9.4 then you need to run ./snddevices

Guess i am having two issues with this.
(1) Maybe just a newbie thing. the cp /downloads thing -- what is that exactly? I have searched manually for it and it is not there. What am I missing?
(2) The TARball is unpacked and sitting on the drive. I just don't know what to do with it from here.

Please help

pneaveill
August 16th, 2006, 01:25 PM
Been working on this for about 4 days now and still not getting it. Guess I am too much of a noob. Maybe this will help:
modinfo soundcore
filename: /lib/modules/2.6.15-26-386/kernel/sound/soundcore.ko
description: Core sound module


In a shell type these commands: Make a directory to store the alsa source code in.

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .
Now unzip and install the alsa-driver package
bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards=emu10k1 --with-sequencer=yes;make;make install
NB. If you are using drivers before 0.9.4 then you need to run ./snddevices

Guess i am having two issues with this.
(1) Maybe just a newbie thing. the cp /downloads thing -- what is that exactly? I have searched manually for it and it is not there. What am I missing?
(2) The TARball is unpacked and sitting on the drive. I just don't know what to do with it from here.

Please help

tjfitz
August 16th, 2006, 08:33 PM
Well, my box finally had the relapse (refer to my previous posts on this thread). Apparently adding snd-intel8x0 to /etc/modules didn't help. Of course, now I'm thinking, maybe it's not even installed??? I did
sudo modprobe snd-intel8x0 and there was nothing returned. I searched synaptic for the module name and didn't find anything. What next? Thanks!

pneaveill
August 16th, 2006, 10:46 PM
Hopefully this will only post once. Not sure what happened earlier. Anyway, I think what needs to happen is this to discover what is "really" in there:


modinfo soundcore

tjfitz
August 16th, 2006, 11:14 PM
pneaveill, I'm not sure who your post was directed at, but if at me, this is what I got:
$ modinfo soundcore
filename: /lib/modules/2.6.15-26-k7/kernel/sound/soundcore.ko
description: Core sound module
author: Alan Cox
license: GPL
alias: char-major-14-*
vermagic: 2.6.15-26-k7 SMP preempt K7 gcc-4.0
depends:
srcversion: DD426F1CCA2CC5F060F6F92

pneaveill
August 16th, 2006, 11:58 PM
As I am learning with this thing (yes, I am a noob also) that what your modinfo did was to state which kernel and such you have. What it also did was stated that there is a device tied to the kernel. THe good news is that you probably won't have to recompile the kernel. Meanwhile, a quick look at the pdf of your mobo docs reveals:
5. Audio
• Onboard 6-Channel AC 97 CODEC
• Professional digital audio interface supports optical S/PDIF OUT (NF7/NF7-S/NF7-M)
NVIDIA SoundStorm™ Technology with real-time Dolby Digital 5.1 encoder (NF7-S)

lspci | grep audio
lsmod | grep snd

pneaveill
August 17th, 2006, 12:49 AM
Attempting to compile alsa and not sure what is wrong with it. Here is what I have so far:

paul@server:~$ lsmod | grep snd
snd_emu10k1_synth 7296 0
snd_emux_synth 37376 1 snd_emu10k1_synth
snd_seq_virmidi 7680 1 snd_emux_synth
snd_seq_midi_emul 7168 1 snd_emux_synth
snd_seq_dummy 3844 0
snd_seq_oss 33536 0
snd_seq_midi 9376 0
snd_seq_midi_event 7552 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq 51984 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,s nd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi _event
snd_emu10k1 117284 3 snd_emu10k1_synth
snd_rawmidi 25504 3 snd_seq_virmidi,snd_seq_midi,snd_emu10k1
snd_ac97_codec 93088 1 snd_emu10k1
snd_ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 53664 0
snd_mixer_oss 18688 2 snd_pcm_oss
snd_pcm 89864 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device 8716 8 snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd _seq_oss,snd_seq_midi,snd_seq,snd_emu10k1,snd_rawm idi
snd_timer 25220 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 10632 2 snd_emu10k1,snd_pcm
snd_util_mem 4608 2 snd_emux_synth,snd_emu10k1
snd_hwdep 9376 2 snd_emux_synth,snd_emu10k1
snd 55268 69 snd_emux_synth,snd_seq_virmidi,snd_seq_oss,snd_seq ,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm_os s,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,s nd_hwdep
soundcore 10208 2 snd

shinigami414
August 17th, 2006, 10:39 AM
i run into an error when i try to build the package of the alsa-source with the module-assistant. can anyone please help me? here is what i get when i open the log.

module-assistant, log file viewer ├────────────────────┐
│ │
│ for i in control postinst postrm ; do \
│ if [ -f debian/$i.orig ]; then \ ▒
│ mv -f debian/$i.orig debian/$i ; \ ▒
│ fi ; \ ▒
│ done ▒
│ rm -f control-munge ▒
│ make mrproper ▒
│ make[1]: Entering directory `/usr/src/modules/alsa-driver' ▒
│ rm -f .depend *.o snd.map* ▒
│ rm -f /*.ver ▒
│ rm -f modules/*.o ▒
│ make[2]: Entering directory `/usr/src/modules/alsa-driver/acore' ▒
│ make[2]: Leaving directory `/usr/src/modules/alsa-driver/acore' ▒
│ make[1]: Leaving directory `/usr/src/modules/alsa-driver' ▒
│ rm -f configure-stamp ▒

│ <Ok>

pneaveill
August 17th, 2006, 02:45 PM
TO be honest, I have not even gotten this far, so will appeal to the more advanaced people here in the list. Sorry I cannot be more helpful.

tjfitz
August 17th, 2006, 07:23 PM
$ lspci | grep audio
0000:00:06.0 Multimedia audio controller: nVidia Corporation MCP2S AC'97 Audio Controller (rev a1)
$ lsmod|grep snd
snd_intel8x0 35804 1
snd_ac97_codec 99296 1 snd_intel8x0
snd_ac97_bus 2688 1 snd_ac97_codec
snd_pcm_oss 56352 0
snd_mixer_oss 20800 1 snd_pcm_oss
snd_pcm 96772 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 27204 1 snd_pcm
snd 60068 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 11040 1 snd
snd_page_alloc 11592 2 snd_intel8x0,snd_pcm

I'm not sure if this is helpful, because right now, my sound is working. Is it possible that one of my sound modules is being unloaded if my machine sits idle for an extended period of time? The next time the sound goes out I will do lsmod again and see if anything is missing.

tvmjr76
August 17th, 2006, 08:08 PM
Hello,

I followed the instructions using drivers from the alsa-project (tried both 12rc2 and 12rc3).

I do the ./configure ... and it appears to run fine. I then issue the make command and it appears to run fine for a while, but I get this error:

...
make[3]: Entering directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/pdaudiocf'
make[3]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/pdaudiocf'
make[3]: Entering directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/vx'
make[3]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/vx'
make[2]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia'
make[1]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2'
make -C /usr/src/linux-headers-2.6.15-26-386 SUBDIRS=/usr/src/alsa-driver-1.0.12rc2 CPP="gcc -E" CC="gcc" modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-26-386'
Makefile:536: /usr/src/linux-headers-2.6.15-26-386/arch/i386/Makefile: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.15-26-386/arch/i386/Makefile'. Stop.
make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-26-386'
make: *** [compile] Error 2


FYI, I am running ubuntu 6.06.1 on a sager 9860 laptop which has Realtek HD Audio. It looks like the hardware is being recognized okay:

Response to "aplay -l"

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0


Response to "lspci -v"
...
0000:00:1b.0 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
Subsystem: CLEVO/KAPOK Computer: Unknown device 0900
Flags: bus master, fast devsel, latency 0, IRQ 217
Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>
...

Any ideas?

Thanks

jocheem67
August 17th, 2006, 09:32 PM
Well, here's a little thank you for helping me out.

Got a ac '97 chip and a m-audio delta 1010 lt. The latter has never been working with ubuntu.
The whole m-audio thing with linux is a story on it's own I guess...

Got it working by editing the alsa.base file, and unmuting all the channels ( there's a lot of them..).
Further on I managed to make the delta my first soundcard as described.

Some issues: I lost all my system sounds, not being able getting them back yet = no problem.
The delta and alsa don't work with mplayer, am using oss instead ( but still with the delta instead of the realtek chip ). Totem and vlc do work though...

At least I've got some better sound now, and am pretty happy!

pneaveill
August 18th, 2006, 01:27 AM
Not sure how helpful this will be, but mine is doing very similar (misery loves company -- lol). Some basic system sounds work (ie, I can hear noise), but the music programs (too many to mention) are not working at all.

Help!!

crimsun
August 18th, 2006, 07:43 AM
Aparently, Ubuntu does not completely install Alsa, nor the sound devices necessary to operate the sound card.

If your sound is not audible by default, please file a bug using Launchpad against the linux-source-2.6.15 (for Dapper/6.06{,.1} LTS) source package.

The couple of us actively triaging audio bugs in Ubuntu do not actively follow the forums; the most effective means is to use the bugtracker.

Thanks.

pneaveill
August 18th, 2006, 10:22 PM
Strongly suspecting several of us here (myself being the first on the list) is such a noob that I am not sure we would know the difference between a "bug" and a "noob error".

abalone
August 19th, 2006, 01:58 PM
Another computer, another set of sound issues... not that I ever solved the last batch.

On my other computer I don't remember ever having a problem using multiple applications at the same time, unless maybe two or more of them were fighting over OSS. I could run Amarok, Kaffeine, Firefox' Flash-Plugin and Audacity at the same time, for example, and I never had to start anything with aoss.

Now not so. snd-82xx again:


0000:00:04.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
Flags: medium devsel, IRQ 5
I/O ports at b800 [size=256]
I/O ports at b400 [size=4]
I/O ports at b000 [size=4]
Capabilities: [c0] Power Management version 2

Everything seemed to be installed fine; I had sound and all. Nonetheless I followed the instructions posted and reinstalled the driver (using the apt-get method though because I'm so tired of working through twisty little howtos that I barely understand).

That didn't help.

Then I installed alsa-oss which however was "already the newest version".

That didn't help either.

audacity: "There was an error initializing the audio i/o layer. You will not be able to play or record audio. Error: Host error."

aoss audacity: No such message, but no available sound devices either.

I've been trying to use Sweep instead of Audacity, but it constantly freezes - either right away, or after recording.

I'm not sure aoss is doing its thing. Is there something left to configure?

Why didn't I have to worry about this on my other computer (with previous Ubuntus and SUSEs, and of course Windows)? Was my "audio app freedom" some sort of freak exception and a general unusability is the default?

Are there any ALSA-aware Audacity-like apps with non-horrible UIs that I might try?

CarbonPlexus
August 19th, 2006, 06:55 PM
Hi, I still have no sound even though I'm told my sound driver (snd-emu10k1) is loaded in the kernel and the ALSA mixer isn't muted. I was reading about other peoples sound problems and now I have more questions. I tried
$ dmesg | grep snd
[17179586.836000] usbcore: registered new driver snd-usb-audio

Is that good or bad? As far as I know my sound card should be using snd-emu10k1 not snd-usb-audio. Also when I check out the ALSA page to find out if my card is supported and what driver I should be using, how do I know which Creative Labs Sound Blaster Audigy card I have? There's ones that use emu10k1, usb-audio, and ca0106. Maybe I just don't have the right driver since I upgraded to Dapper from Breezy? Thanks in advance for any insight you could give me into my problem. I have this in /etc/modules


lp
mousedev
psmouse
sbp2
sr_mod
snd-card-sb8
snd-seq-device
snd-seq-midi
snd-seq-oss
snd-seq-midi-event
snd-seq
snd-emu10k1
ide-cd
ide-disk
ide-generic

Tyche
August 19th, 2006, 08:12 PM
If your sound is not audible by default, please file a bug using Launchpad against the linux-source-2.6.15 (for Dapper/6.06{,.1} LTS) source package.

The couple of us actively triaging audio bugs in Ubuntu do not actively follow the forums; the most effective means is to use the bugtracker.

Thanks.

Crimsun,

I have just spent the last hour going through bugzilla and malone in an attempt to figure out how to submit an appropriate bug report. Since I am not a programmer or developer, nor am I familiar with all of the packages involved in the creation of sound with a linux kernel, I find myself at a loss to explain the problem in terms that these particular bug tracking application would be able to accept and attached in the appropriate place. Basically, the bug tracking application, itself, has a user usability bug.

For your information:

HARDWARE -
Tyan mother board
Pentium PIII, 750 CPU
Creative Labs SoundBlaster Live! (driver - emu10k1)
Linux 2.6.15-23-686 (i686)

SOFTWARE -
Alsa (since I picked all the alsa packages that pertained to me and were available in Synaptic, such as alsa-base, alsa-utils, etc. as well as various plugins for things like mplayer, I am pretty confident that I had that particular base covered.)

PROBLEM - (Symptoms positive and negative)
Sound not operating.
Alsa mixer and Gnome mixer both reporting that there is no sound device installed.
No modules apparently installed.

SOLUTION -
Went to the Alsa web site, found my particular sound card, downloaded 3 packages and followed the directions on the page INCLUDING running ./snddevices. ReBoot. Sound now operating.

CONCLUSION -
The Ubuntu alsa packages, when installed, are not completing the operation of installing the sound devices (/dev/dsp /dev/mixer /dev/sequencer /dev/midi). This is fatal to the operation of sound on a GNU/Linux system. This is a particularly obnoxious problem considering that the sound was operating prior to the upgrade to this particular kernel (this also occurred on a clean install on a separate partition). Which particular package was responsible for the lack of sound devices I have no way of determining. However, since ./snddevices would not operate/could not be found until AFTER I had done ./compile ./make ./make install on the three packages, I have to conclude that something in the packages that Synaptic offered was lacking the appropriate programs/functions.

Craig
(Tyche)

abalone
August 19th, 2006, 11:06 PM
I could run Amarok, Kaffeine, Firefox' Flash-Plugin and Audacity at the same time, for example, and I never had to start anything with aoss.
And I found this still works when I plug in the Soundblaster PCI 128 I had scavenged and disabled the onboard sound in the BIOS Setup. Audacity didn't just run, it also record undistorted sound - no tweaking, no compiling, no anything: :o

Then various other things broke somewhere between the 7th and 10th attempt at Suspend-to-RAM. Such as my Windows installation. Now that hasn't happened in 6 years..

I do wonder though what's causing these discrepancies in OSS behaviour or whatever it is - used the same Kubuntu Dapper desktop install/live CD both times. Ahwell.

'ntoni
August 20th, 2006, 09:23 PM
Uhm I've got a alsa-related question but... it may be an off topic :-k
my system is affected by this already filed bug:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/34831
and I already installed the latest available alsa (1.0.11 and then 1.0.12rc2) and tried the patch https://lists.ubuntu.com/archives/kernel-team/2006-July/000943.html suggested.
They say they need a kernel log in order to continue working on this bug.
But when my computer crashes, my /var/log/kernel.log does not contain *any* information about the crash. How can I obtain a detailed and useful kernel log with the ubuntu shipped kernel? Is there any workaround?
Or: can I install the old breezy alsa package which worked well?

pneaveill
August 22nd, 2006, 01:09 PM
Uhm I've got a alsa-related question but... it may be an off topic :-k
my system is affected by this already filed bug:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/34831
and I already installed the latest available alsa (1.0.11 and then 1.0.12rc2) and tried the patch https://lists.ubuntu.com/archives/kernel-team/2006-July/000943.html suggested.
They say they need a kernel log in order to continue working on this bug.
But when my computer crashes, my /var/log/kernel.log does not contain *any* information about the crash. How can I obtain a detailed and useful kernel log with the ubuntu shipped kernel? Is there any workaround?
Or: can I install the old breezy alsa package which worked well?
Not sure how helpful this will be, but I did breezy to dapper upgrade on my studio machine and got similar problems as you describe with that new patch. To the best of my knowledge, I removed alsa completely, installed 1.0.12rc3 (ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.12rc3.tar.bz2) and skipped that new patch entirely.

As for the kernel dump: if not too much trouble, how about doing it before you load your gear up? My thought on it (despite being a noob) is this -- perhaps there would be enough info from it that someone with a bit more experience could look at it.

Hope that helped some. Otherwise, will defer to the others with a bit more experience.

Paul

fieldstone
August 22nd, 2006, 04:19 PM
Update:

I've fixed the problem listed below (I'm leaving it here for reference, just in case it helps explain what's going on), but now I have a different one. When I get to the place where I need to run alsamixer, it doesn't work - the message I get is:

alsamixer: function snd_ctl_open failed for default: no such device

Do I need to install a new version of alsa-utils or something?

------
I've done pretty well so far in following your guide, compiling the ALSA drivers (1.0.12rc2) myself, and installing them. However, I'm a little stuck now. (This is for an nForce sound chipset, the MCP51.) When I try to insert the module, though ("sudo modprobe snd-intel8x0"), I get the following messages:

WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.15-26-amd64-k8/kernel/sound/pci/ac97/snd-ac97-codec.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.15-26-amd64-k8/kernel/sound/pci/snd-intel8x0.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Checking dmesg gives me the following:

[ 1018.873475] snd_ac97_codec: disagrees about version of symbol snd_info_register
[ 1018.873608] snd_ac97_codec: Unknown symbol snd_info_register
[ 1018.873651] snd_ac97_codec: disagrees about version of symbol snd_ctl_add
[ 1018.873654] snd_ac97_codec: Unknown symbol snd_ctl_add
[ 1018.876096] snd_ac97_codec: disagrees about version of symbol snd_info_free_entry
[ 1018.876102] snd_ac97_codec: Unknown symbol snd_info_free_entry
[ 1018.876145] snd_ac97_codec: disagrees about version of symbol snd_interval_refine
[ 1018.876148] snd_ac97_codec: Unknown symbol snd_interval_refine
[ 1018.876193] snd_ac97_codec: disagrees about version of symbol snd_ctl_find_id[ 1018.876196] snd_ac97_codec: Unknown symbol snd_ctl_find_id
[ 1018.876270] snd_ac97_codec: Unknown symbol snd_verbose_printk
[ 1018.876310] snd_ac97_codec: disagrees about version of symbol snd_ctl_new1
[ 1018.876312] snd_ac97_codec: Unknown symbol snd_ctl_new1
[ 1018.876351] snd_ac97_codec: disagrees about version of symbol snd_ctl_remove_id
[ 1018.876358] snd_ac97_codec: Unknown symbol snd_ctl_remove_id
[ 1018.876408] snd_ac97_codec: disagrees about version of symbol snd_component_add
[ 1018.876411] snd_ac97_codec: Unknown symbol snd_component_add
[ 1018.876447] snd_ac97_codec: disagrees about version of symbol snd_pcm_hw_rule_add
[ 1018.876450] snd_ac97_codec: Unknown symbol snd_pcm_hw_rule_add
[ 1018.876499] snd_ac97_codec: disagrees about version of symbol snd_iprintf
[ 1018.876502] snd_ac97_codec: Unknown symbol snd_iprintf
[ 1018.876621] snd_ac97_codec: disagrees about version of symbol snd_device_new
[ 1018.876623] snd_ac97_codec: Unknown symbol snd_device_new
[ 1018.876720] snd_ac97_codec: disagrees about version of symbol snd_info_create_card_entry
[ 1018.876723] snd_ac97_codec: Unknown symbol snd_info_create_card_entry
[ 1018.880467] snd_intel8x0: Unknown symbol snd_ac97_pcm_close
[ 1018.880615] snd_intel8x0: Unknown symbol snd_ac97_resume
[ 1018.880730] snd_intel8x0: disagrees about version of symbol snd_pcm_new
[ 1018.880827] snd_intel8x0: Unknown symbol snd_pcm_new
[ 1018.880945] snd_intel8x0: disagrees about version of symbol snd_pcm_limit_hw_rates
[ 1018.881054] snd_intel8x0: Unknown symbol snd_pcm_limit_hw_rates
[ 1018.881182] snd_intel8x0: disagrees about version of symbol snd_card_register[ 1018.881285] snd_intel8x0: Unknown symbol snd_card_register
[ 1018.881423] snd_intel8x0: disagrees about version of symbol snd_card_free
[ 1018.881522] snd_intel8x0: Unknown symbol snd_card_free
[ 1018.881632] snd_intel8x0: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all
[ 1018.881759] snd_intel8x0: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
[ 1018.881899] snd_intel8x0: disagrees about version of symbol snd_card_proc_new[ 1018.882008] snd_intel8x0: Unknown symbol snd_card_proc_new
[ 1018.882131] snd_intel8x0: Unknown symbol snd_ac97_pcm_open
[ 1018.882295] snd_intel8x0: Unknown symbol snd_ac97_set_rate
[ 1018.882426] snd_intel8x0: Unknown symbol snd_ac97_update_bits
[ 1018.882556] snd_intel8x0: Unknown symbol snd_ac97_mixer
[ 1018.882682] snd_intel8x0: Unknown symbol snd_ac97_bus
[ 1018.882811] snd_intel8x0: Unknown symbol snd_verbose_printk
[ 1018.882991] snd_intel8x0: Unknown symbol snd_ac97_pcm_double_rate_rules
[ 1018.883134] snd_intel8x0: Unknown symbol snd_ac97_update_power
[ 1018.883257] snd_intel8x0: disagrees about version of symbol snd_card_new
[ 1018.883440] snd_intel8x0: Unknown symbol snd_card_new
[ 1018.883571] snd_intel8x0: Unknown symbol snd_ac97_suspend
[ 1018.883693] snd_intel8x0: disagrees about version of symbol snd_iprintf
[ 1018.883796] snd_intel8x0: Unknown symbol snd_iprintf
[ 1018.883909] snd_intel8x0: disagrees about version of symbol snd_pcm_lib_malloc_pages
[ 1018.884031] snd_intel8x0: Unknown symbol snd_pcm_lib_malloc_pages
[ 1018.884164] snd_intel8x0: disagrees about version of symbol snd_pcm_lib_ioctl[ 1018.884281] snd_intel8x0: Unknown symbol snd_pcm_lib_ioctl
[ 1018.884400] snd_intel8x0: disagrees about version of symbol snd_pcm_lib_free_pages
[ 1018.884522] snd_intel8x0: Unknown symbol snd_pcm_lib_free_pages
[ 1018.884662] snd_intel8x0: disagrees about version of symbol snd_pcm_set_ops
[ 1018.884769] snd_intel8x0: Unknown symbol snd_pcm_set_ops
[ 1018.884894] snd_intel8x0: disagrees about version of symbol snd_pcm_hw_constraint_list
[ 1018.885015] snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_list
[ 1018.885159] snd_intel8x0: disagrees about version of symbol snd_device_new
[ 1018.885265] snd_intel8x0: Unknown symbol snd_device_new
[ 1018.885477] snd_intel8x0: Unknown symbol snd_ac97_get_short_name
[ 1018.885602] snd_intel8x0: disagrees about version of symbol snd_pcm_suspend_all
[ 1018.885711] snd_intel8x0: Unknown symbol snd_pcm_suspend_all
[ 1018.885840] snd_intel8x0: Unknown symbol snd_ac97_pcm_assign
[ 1018.885961] snd_intel8x0: disagrees about version of symbol snd_pcm_hw_constraint_integer
[ 1018.886082] snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_integer
[ 1018.886254] snd_intel8x0: disagrees about version of symbol snd_pcm_hw_constraint_msbits
[ 1018.886381] snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_msbits
[ 1018.886598] snd_intel8x0: disagrees about version of symbol snd_pcm_period_elapsed
[ 1018.886709] snd_intel8x0: Unknown symbol snd_pcm_period_elapsed
[ 1018.886843] snd_intel8x0: Unknown symbol snd_ac97_tune_hardware

Any ideas on how to fix this?

TrendyDark
August 22nd, 2006, 09:35 PM
I would love to see how to get TeamSpeak and a game like Enemy Territory running on a soundcard that doesn't support hardware mixing.

segalion
August 23rd, 2006, 09:22 AM
My better recomendation reading for ALSA stuff is:

http://www.sabi.co.uk/Notes/linuxSoundALSA.html

It explains all simply and extense and actualized.
Sincerely, the best alsadoc I`ve seen.
@LordRaiden, please include it in first-post.

autrui
August 23rd, 2006, 09:39 AM
hi,

this thread is mighty long, so i hope i'm not asking questions that have already been answered.

i followed this guide and had success in every aspect, except no sound. that's one issue.. the real issue is a lot more annoying.

given that doing these things didn't work, i decided to return to "factory settings" with the --purge... and it also purged ubuntu-desktop + gdm. i installed gdm again, and that's fine, but ubuntu-desktop wasn't fine. then i made the mistake of trying to reboot--now, no GUI.

i have a root@compy:~# prompt; i tried "get-apt install ubuntu-desktop" but it complained that there were dependencies that i wasn't d/ling. so i added them, and here's a sample of about 5 almost identical lines (just different filenames):

gnome-applets: Depends: gnome-applets-data (= 2.14.1-0ubuntu3) but 2.14.3-0ubuntu1 is to be installed

any ideas what i can do about this? or should i get out the installation cd..

thanks so much..

(and if you can help me get sound after you help be get GUI, that'd be awesome :):) )

autrui

'ntoni
August 23rd, 2006, 07:38 PM
Have you tried to install manually every problematic package and *then* install the ubuntu-desktop one? Maybe it works.

autrui
August 23rd, 2006, 07:53 PM
Have you tried to install manually every problematic package and *then* install the ubuntu-desktop one? Maybe it works.

just tried that with the first dependency, "gnome-applets", and it had two dependenies; one of them had that weird error ("depends: gnome-applets-data (= 2.14.1-0ubuntu3) but 2.14.3-0ubuntu1 is to be installed") and the other was gnome-panel; i try to install gnome-panel and get the same type of error.

(in short, that didn't really work.)

is there any way to just reload ubuntu-desktop off the live cd? i can boot that no problem, but i don't know how to tell it to make repairs to the installed version on my HD.

any thoughts?

autrui

1Paul
August 23rd, 2006, 08:22 PM
Hi, my sound device is Creative Labs, SB Audigy. I have 7.1 surround speakers and I only get sound on 3 speakers(left-/right-front and sub).
I have tried to install some alsa drivers, but with no luck. I'm a bit new, so I dont know if I have the right driver, or if i need a new driver at all. Maybe it is a way to manage the speakers from my desktop?

thanks!

LordRaiden
August 23rd, 2006, 09:50 PM
segalion - I added you link and gave you credits for giving the link. Looks like an interesting, albeit long, read (I'll look into it soon).

autrui - Are you putting in the CD when trying to reinstall ubunu-desktop? I suggest you comment out the reference to the CD in your sources.list file.


sudo nano /etc/apt/sources.list

One of the first few lines will have an entry with something like Ubuntu Dapper Drake CD. Comment it out by placing a # sign in the beginning. You might also have two lines, one commented and one not commented, so comment out the one that not commented.
Then do
sudo apt-get update && sudo apt-get install ubuntu-desktop

If it still complains, try
sudo apt-get -f install && sudo aptitude dist-upgrade

autrui
August 23rd, 2006, 10:51 PM
in a moment of impatience and frustration, i reinstalled ubuntu. excluding my bookmarks in firefox, i'm already back to where i had left off.

my sound card is identified, the correct driver is named in the device manager, and alsamixer is all unmuted. however, i also went into "Open volume control" and put all those sliders were in audible ranges. (their settings were not the same as the settings in alsamixer.)

according to aplay, i have two cards (0 and 1), i assume that's the onboard and the pci. when i "Open volume control," and File > Change device, three things are listed, 0 (onboard - alsamixer), 1 (sound blaster live! - alsamixer) and 2 (analog devices ad1981b - oss mixer).

it occurs to me that maybe i just need to do the same thing with oss mixer as i did with alsamixer; or perhaps the third one is in error, and needs to be removed? (how do i do either of those things? ;) )

any suggestions?

thanks,

autrui

'ntoni
August 23rd, 2006, 11:12 PM
Hi, my sound device is Creative Labs, SB Audigy. I have 7.1 surround speakers and I only get sound on 3 speakers(left-/right-front and sub).
I have tried to install some alsa drivers, but with no luck. I'm a bit new, so I dont know if I have the right driver, or if i need a new driver at all. Maybe it is a way to manage the speakers from my desktop?

thanks!

I think you don't need any extra driver, just a little bit of manual configuration. Check out this page about the magic asoundrc file
http://alsa.opensrc.org/index.php?page=.asoundrc
With this file you can define how the sound is mapped to each speaker, and I think that you probably need to redirect the L channel to the rear L speaker as well, and the same for the R speaker. But the page in the link will be more useful, I hope.

'ntoni
August 23rd, 2006, 11:13 PM
in a moment of impatience and frustration, i reinstalled ubuntu. excluding my bookmarks in firefox, i'm already back to where i had left off.

my sound card is identified, the correct driver is named in the device manager, and alsamixer is all unmuted. however, i also went into "Open volume control" and put all those sliders were in audible ranges. (their settings were not the same as the settings in alsamixer.)

according to aplay, i have two cards (0 and 1), i assume that's the onboard and the pci. when i "Open volume control," and File > Change device, three things are listed, 0 (onboard - alsamixer), 1 (sound blaster live! - alsamixer) and 2 (analog devices ad1981b - oss mixer).

it occurs to me that maybe i just need to do the same thing with oss mixer as i did with alsamixer; or perhaps the third one is in error, and needs to be removed? (how do i do either of those things? ;) )

any suggestions?

thanks,

autrui

I suggest you to go in the BIOS and disable the onboard card. It's not useful anymore I think :p. I did it for my sblive, anyway.

'ntoni
August 23rd, 2006, 11:16 PM
Not sure how helpful this will be, but I did breezy to dapper upgrade on my studio machine and got similar problems as you describe with that new patch. To the best of my knowledge, I removed alsa completely, installed 1.0.12rc3 (ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.12rc3.tar.bz2) and skipped that new patch entirely.

As for the kernel dump: if not too much trouble, how about doing it before you load your gear up? My thought on it (despite being a noob) is this -- perhaps there would be enough info from it that someone with a bit more experience could look at it.

Hope that helped some. Otherwise, will defer to the others with a bit more experience.

Paul
Same problem with the last alsa :-(
I do now think it is a deeper kernel bug.

autrui
August 24th, 2006, 02:06 AM
I suggest you to go in the BIOS and disable the onboard card. It's not useful anymore I think :p. I did it for my sblive, anyway.


w0000t!! that helped. once i had that onboard disabled, and ran alsamixer, i was then editing the correct sound card's settings.

in the end, i had to enable everything EXCEPT "analog/digital output jack" (which now has the word "off" after it; this subtle and silly vulgarity reflects my mood.;)).

for those who may find themselves in my situation, the card is a Dell Sound Blaster Live! chip: SigmaTel STAC9708,11

thanks so much you guys! of course, this only means i'll bring more of my probems here!

autrui

Sewage
August 24th, 2006, 04:30 PM
I am having a pretty scary problem right now. D: I wasn't getting sound in firefox and decided to give this guide a go~ I made it to the ALSA driver Compilation bit and didn't notice any problems or errors, but when I rebooted it took me straight to terminal.

I tried reinstalling the gdm and that worked, but now after I log on it just hangs at the loading screen before where the splash would ordinarily pop up.

I've tried install ubuntu-desktop but it says I can because it can't install gnome terminal~

Am I screwed? D:

TrendyDark
August 24th, 2006, 07:20 PM
I'm still having problems with TeamSpeak. In theory, it'd easiest to get TS and a game working using alsa-oss correct?

But when I use aoss I get no sound in or out.

I have yet to try aoss on a game, while at the same time running teamspeak, but some suggestions could be cool.

I have an AC'97 Sound Card. I'm using the Intel8x0 alsa driver.

If that helps.

LordRaiden
August 24th, 2006, 08:54 PM
Sewage - Go to a terminal and do the following.

sudo apt-get clean
sudo nano /etc/apt/sources.list
There is one reference to the Ubuntu Dapper Drake CD-ROM at the top that is not commented with a # sign. Comment it out with # sign. Press CTRL + O to save then CTRL + X to exit. Now,


sudo apt-get update
sudo aptitude install ubuntu-desktop
sudo aptitude dist-upgrade

'ntoni
August 25th, 2006, 01:10 PM
I am having a pretty scary problem right now. D: I wasn't getting sound in firefox and decided to give this guide a go~ I made it to the ALSA driver Compilation bit and didn't notice any problems or errors, but when I rebooted it took me straight to terminal.

I tried reinstalling the gdm and that worked, but now after I log on it just hangs at the loading screen before where the splash would ordinarily pop up.

I've tried install ubuntu-desktop but it says I can because it can't install gnome terminal~

Am I screwed? D:

Have you tried to uninstall the new alsa driver you installed? If you can't get sound from firefox it's not an alsa problem but a firefox one, I think. Try to go in the directory where you compiled alsa and type:
make uninstall

LordRaiden
August 25th, 2006, 06:13 PM
Come to think of it, ALSA Driver compilation should not remove gdm and ubuntu-desktop. I think you tried the fresh kernel method. autrui tried the same and ended up reinstalling Ubuntu (something which you should not have to do).

tvmjr76
August 25th, 2006, 08:28 PM
Hello,

I followed the instructions using drivers from the alsa-project (tried both 12rc2 and 12rc3).

I do the ./configure ... and it appears to run fine. I then issue the make command and it appears to run fine for a while, but I get this error:

...
make[3]: Entering directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/pdaudiocf'
make[3]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/pdaudiocf'
make[3]: Entering directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/vx'
make[3]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia/vx'
make[2]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2/pcmcia'
make[1]: Leaving directory `/usr/src/alsa-driver-1.0.12rc2'
make -C /usr/src/linux-headers-2.6.15-26-386 SUBDIRS=/usr/src/alsa-driver-1.0.12rc2 CPP="gcc -E" CC="gcc" modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-26-386'
Makefile:536: /usr/src/linux-headers-2.6.15-26-386/arch/i386/Makefile: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.15-26-386/arch/i386/Makefile'. Stop.
make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-26-386'
make: *** [compile] Error 2


FYI, I am running ubuntu 6.06.1 on a sager 9860 laptop which has Realtek HD Audio. It looks like the hardware is being recognized okay:

Response to "aplay -l"

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0


Response to "lspci -v"
...
0000:00:1b.0 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
Subsystem: CLEVO/KAPOK Computer: Unknown device 0900
Flags: bus master, fast devsel, latency 0, IRQ 217
Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>
...

Any ideas?

Thanks


I still have not resolved this. Can someone help?

'ntoni
August 25th, 2006, 09:00 PM
I still have not resolved this. Can someone help?

have you installed the kernel header package?

aeg
August 25th, 2006, 09:07 PM
Excellent post.

I do not quite know what worked, but I purged alsa (and gnome, gdm, gnome-terminal, and about ten other 'useless' things ;-). Then, I tried to use alsamixer again, turning every thing ON!!! I was able to hear a faint bit of music somewhere.

Master was fully up, my keyboard and panel sound bars were on full, but PCM was zero. Pushing PCM up did the trick. In fact, Master seems to do nothing at all. What is PCM, anyway?

I'd recommend suggesting users use the UP arrow key, not just 'm' for mute. For posterity, I'm running an HP laptop (nw8240).

Thanks again for the HOWTO troubleshooter.

tvmjr76
August 25th, 2006, 09:11 PM
have you installed the kernel header package?

These are the instructions i followed:


sudo apt-get install build-essential linux-headers-$(uname -r)
wget ftp://ftp.alsa-project.org/pub/drive....12rc2.tar.bz2
tar xvjf alsa-driver-1.0.12rc2.tar.bz2
cd alsa-driver-1.0.12rc1
sudo ./configure --with-kernel=/usr/src/linux-headers-$(uname -r) --with-cards=<enter driver name here e.g. via82xx> --with-oss=yes
sudo make
(don't get past this point yet)
sudo make install


I used hda-intel as my card.

standards
August 26th, 2006, 10:05 PM
My sound works- I can listen to mp3s, play movies, hear the startup sounds etc. But Jack/Alsa suddenly stopped working. It worked prior to the xorg debacle last week, and I don't think I changed anything, so I'm wondering what happened? I upgraded to edgy in lieu of reinstalling dapper, but the problem persists.

jackd -d alsa

...
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
no message buffer overruns

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 1: Audigy [Audigy 1 [Unknown]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
...lots of subdevices...
card 1: Audigy [Audigy 1 [Unknown]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
...more subdevices...
card 1: Audigy [Audigy 1 [Unknown]], device 3: emu10k1 [Multichannel Playback]
...one more subdevice...

lspci -v

02:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Subsystem: Creative Labs Unknown device 0054
Flags: bus master, medium devsel, latency 32, IRQ 209
I/O ports at 9c00 [size=32]
Capabilities: [dc] Power Management version 2
02:09.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 03)
Subsystem: Creative Labs SB Audigy MIDI/Game Port
Flags: bus master, medium devsel, latency 32
I/O ports at 9800 [size=8]
Capabilities: [dc] Power Management version 2

lspci | grep audio

02:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)

lsmod | grep snd

snd_emu10k1_synth 10880 0
snd_emux_synth 50048 1 snd_emu10k1_synth
snd_seq_virmidi 10624 1 snd_emux_synth
snd_seq_midi_emul 10112 1 snd_emux_synth
snd_seq_dummy 6020 0
snd_seq_oss 45824 0
snd_seq_midi 12160 0
snd_seq_midi_event 11648 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq 77088 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,s nd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi _event
snd_emu10k1 151200 2 snd_emu10k1_synth
snd_ac97_codec 126936 1 snd_emu10k1
snd_ac97_bus 4352 1 snd_ac97_codec
snd_util_mem 7552 2 snd_emux_synth,snd_emu10k1
snd_usb_audio 100224 0

cat /etc/modules

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
psmouse
rtc

(i've rebooted after adding "snd-emu10k1" and modprobe'd snd-emu10k1/pcm/pcm-oss/etc to death)

I went through LordRaiden's howto [which is great, btw] and I also tried the rm .asound* trick someone else mentioned, but I still can't get jack working. And like I said, every other aspect of my sound is working fine except for this alsa_pcm thing. At this point I'm out of ideas.

Hopefully not too offtopic, but this seemed like the best thread to consult.

pneaveill
August 27th, 2006, 01:13 AM
My sound works- I can listen to mp3s, play movies, hear the startup sounds etc. But Jack/Alsa suddenly stopped working. Correct driver? I just purchased an audigy and was shocked by the number of drivers for that series. I had to check and double-check to make certain I had the correct drivers. Probably already know this, but don't forget to reboot when you load those correct drivers.


http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Creative_Labs#matrix



It worked prior to the xorg debacle last week, and I don't think I changed anything, so I'm wondering what happened?
Might help to have a bit more detail with this one. Someone with more experience can correct me if I am wrong, but the wrong driver has been known to cause this sort of thing. Even worse is a series of flaky drivers (audio/ video) could really flake out your computer.




I upgraded to edgy in lieu of reinstalling dapper, but the problem persists.


Not sure this was the wisest of moves, as it could be that you move a smaller series of problems into a much larger problem, as edgy is still sort of beta release.

Hope this helps somehow.

standards
August 28th, 2006, 02:03 AM
I think I figured it out.

I had a new midi/usb interface plugged in on bootup, which I guess was loaded prior to the soundcard because it was assigned the "hw:0" designation, thus bumping my soundcard from hw:0 to hw:1. So, the "normal" way I started jack {the simple way, which defaulted hw:0} was no longer working since the card was no longer at that address. Starting jack was "-d hw:1" solved this.

Alternatively I could just plug in the midi interface *after* boot, which then leaves the soundcard at hw:0 and assigns hw:1 to the midi interface.

IMHO this seems like poor design- in the sense that adding various peripheral sound interfaces/etc changes the hw address of the actual permanent, hardwired PCI soundcard. Seems like that should default to hw:0 no matter what.

Thanks for the advice though. I was second guessing my installing edgy to fix a sound problem too, but it's been solid so far!

pneaveill
August 28th, 2006, 02:48 AM
I think I figured it out.

I had a new midi/usb interface plugged in on bootup, which I guess was loaded prior to the soundcard because it was assigned the "hw:0" designation, thus bumping my soundcard from hw:0 to hw:1. So, the "normal" way I started jack {the simple way, which defaulted hw:0} was no longer working since the card was no longer at that address. Starting jack was "-d hw:1" solved this.

Alternatively I could just plug in the midi interface *after* boot, which then leaves the soundcard at hw:0 and assigns hw:1 to the midi interface.

IMHO this seems like poor design- in the sense that adding various peripheral sound interfaces/etc changes the hw address of the actual permanent, hardwired PCI soundcard. Seems like that should default to hw:0 no matter what.

Thanks for the advice though. I was second guessing my installing edgy to fix a sound problem too, but it's been solid so far!
Glad you got it figured out. Even more importantly, let's hope it stays that way.

Glad we could help.

abalone
August 28th, 2006, 06:09 PM
Another computer, another set of sound issues... not that I ever solved the last batch.

On my other computer I don't remember ever having a problem using multiple applications at the same time, unless maybe two or more of them were fighting over OSS. I could run Amarok, Kaffeine, Firefox' Flash-Plugin and Audacity at the same time, for example, and I never had to start anything with aoss.

Now not so. snd-82xx again:


0000:00:04.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
Flags: medium devsel, IRQ 5
I/O ports at b800 [size=256]
I/O ports at b400 [size=4]
I/O ports at b000 [size=4]
Capabilities: [c0] Power Management version 2

Everything seemed to be installed fine; I had sound and all. Nonetheless I followed the instructions posted and reinstalled the driver (using the apt-get method though because I'm so tired of working through twisty little howtos that I barely understand).

That didn't help.

Then I installed alsa-oss which however was "already the newest version".

That didn't help either.

audacity: "There was an error initializing the audio i/o layer. You will not be able to play or record audio. Error: Host error."

aoss audacity: No such message, but no available sound devices either.

I've been trying to use Sweep instead of Audacity, but it constantly freezes - either right away, or after recording.

I'm not sure aoss is doing its thing. Is there something left to configure?

Why didn't I have to worry about this on my other computer (with previous Ubuntus and SUSEs, and of course Windows)? Was my "audio app freedom" some sort of freak exception and a general unusability is the default?

Are there any ALSA-aware Audacity-like apps with non-horrible UIs that I might try?

I thought it might be a problem with the on-board sound of NewComputer but OldComputer doesn't have any issues even when I use the same sound card... not just the same model - the same physical card. It starts working great as soon as I put it in OldComputer. They're both running Dapper, installed from the same CD.

sawjew
August 29th, 2006, 12:30 AM
I can't help you with your sound problems but a good audio editing app is rezound. I have this as well as audacity and it provides a lot of features that audacity doesn't and it doesn't look too bad, not brilliant but usable.

pneaveill
August 29th, 2006, 02:56 AM
These are the instructions i followed:


I used hda-intel as my card.
tvmjr76 (http://www.ubuntuforums.org/member.php?u=150091), I think I owe you an apology. I thought I had it figured out, but did not. I was tired the other day, wiped out my machine and had to start over. To make a long story short, I was able to reproduce the problem you have/ had. I am still working on it and have not forgotten about you.

Meanwhile, in my case I started over with the Audigy card still in the machine. The computer shows the following:

lspci | grep audio
0000:00:12.0 Multimedia audio controller: Creative Labs SB Audigy LS
whereas,
lspci -v
0000:00:12.0 Multimedia audio controller: Creative Labs SB Audigy LS
Subsystem: Creative Labs: Unknown device 100a
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 2080 [size=32]
Capabilities: [dc] Power Management version 2 shows the above -- despite following the Alsa directions.

If someone could help us out here, we would appreciate it.

Thanks in advance

abalone
August 29th, 2006, 04:14 AM
I can't help you with your sound problems but a good audio editing app is rezound. I have this as well as audacity and it provides a lot of features that audacity doesn't and it doesn't look too bad, not brilliant but usable.
Thanks for the suggestion. It does look promising.

Like Audacity, it's fighting over the soundcard with whatever else is running at the time. Best I can do is load Rezound last, which will allow me to record - but not playback ("[some C++(?) function call] - the sound player is not initialized").

The config file registry.dat and docs mention ALSA but this kind of behaviour I've come to associate with OSS, and I've had several Rezound error messages mention OSS or /dev/dsp.

Or I start Rezound with JACK and then get to select alsa_pcm_etc. as output and capture channels, but the result is exactly the same... either the other app(s) won't be able to use sound, or - if those others are running already - JACK won't start (the playback device "hw:0" is already in use. Please stop the application using it and run JACK again).

I don't know JACK, admittedly. Maybe I need to re-route it all through JACK somehow. Is that even possible or does every application have to be designed for it? It's all pretty fiddly already so I suppose it couldn't possibly stop here :p:-|

pneaveill
August 30th, 2006, 06:27 PM
These are the instructions i followed:


I used hda-intel as my card.
In trying to reproduce what happened here, I ended up running exactly what you did 3x. Will have to look again, but which drivers do you need for your card again? What I see about halfway through is this:

alsa-driver-1.0.12rc3/pci/emu10k1/
alsa-driver-1.0.12rc3/pci/emu10k1/Makefile
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1.c
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1_callback.c
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1_main.c
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1_patch.c
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1_synth.c
alsa-driver-1.0.12rc3/pci/emu10k1/emu10k1x.c
alsa-driver-1.0.12rc3/pci/emu10k1/emufx.c
alsa-driver-1.0.12rc3/pci/emu10k1/emumixer.c
alsa-driver-1.0.12rc3/pci/emu10k1/emumpu401.c
alsa-driver-1.0.12rc3/pci/emu10k1/emupcm.c
alsa-driver-1.0.12rc3/pci/emu10k1/emuproc.c
alsa-driver-1.0.12rc3/pci/emu10k1/io.c
alsa-driver-1.0.12rc3/pci/emu10k1/irq.c
alsa-driver-1.0.12rc3/pci/emu10k1/memory.c
alsa-driver-1.0.12rc3/pci/emu10k1/p16v.c
alsa-driver-1.0.12rc3/pci/emu10k1/timer.c
alsa-driver-1.0.12rc3/pci/emu10k1/voice.c

Can someone with experience tell me if this is supposed to load? If it is not supposed to load, then why is it there? Another question, where are my audigy SE (ca0106) drivers?

Please help!!

pneaveill
August 30th, 2006, 09:29 PM
Excellent post. PCM was zero. Pushing PCM up did the trick. In fact, Master seems to do nothing at all. What is PCM, anyway?

I'd recommend suggesting users use the UP arrow key, not just 'm' for mute. Thanks again for the HOWTO troubleshooter.

PCM = pulse code modulation (http://en.wikipedia.org/wiki/Pulse-code_modulation) (or in overly simplified, non-techie, English), it refers to a form of digital audio.