Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Yes. Please run this script and post the results. If possible, try downloading the newest release, alsa-driver-1.0.15rc1 and installing it before running this script. chances are there is better support for your system through a different model, if not full out-of-the-box support. In any case, it would be better to have accurate support for your laptop instead of using a 6-stack configuration that enable channels that don't exist on your hardware.
Sound Capture doesn't work while running a Virtualbox-WindowsXP guest under Ubuntu
After installing alsa-driver-1.0.15rc1 and rebooting I ran the alsa-info.sh > output. Sound capture is working with this driver version.
Unfortunately I found out, that sound capture doesn't work while I'm running my Virtualbox-WindowsXP-guest (on my Ubuntu host) (Sound output works in both systems at the same time. Capture doesn't work neither in Ubuntu nor in the Virtualbox-WindowsXP, while it is running).
This is may be a more Virtualbox-related problem, but may be someone had the same problem too.
First, did you try any of the newer models listed for the alc883 codec, or is this in "auto" mode? I'd like to be able to add more accurate support for your system. One test you could run is to recompile the drivers with "./configure --with-debug=detect --with-cards=hda-intel". This will add more output to dmesg that will tell me which ports are being configured for which function.
Second, on the Virtualbox-WindowsXP-guest sound issue, try this experiment:
Boot Linux host OS. Set mixer levels and do a full function test (record, playback, etc). Next, take a snapshot of the audio settings (cat /proc/asound/card0/codec#1 > ~/no-vm.out ). Now, start VirtualBox with XP and test audio in XP. If capture is disabled, take another snapshot of the audio settings in Linux (cat /proc/asound/card0/codec#1 > ~vm.out ). Don't change any mixer settings in between. Now, you can do a diff on the two files to see what changed (or send me both files and I can determine what changed). Send them to my userid <AT> gmail.com.
I hope this information is useful... Tell me, if you need anymore! I'm really interested in a working sound capture system [since certain voip programs need Windows. I don't know may be some programs should run with wine, but I prefer VirtualBox]. Thanks for your help!
I'm thinking the medion-md2 will be more accurate, based on your dmesg output. Please try it and let me know. Try the others as well.
Also, on the Virtualbox portion, can you access /proc/asound/card0/codec#1 while Virtualbox is running? I haven't used this VM software yet, but if you can, that would tell me if Windows is changing any of the audio settings.
Last edited by GrueMaster; 09-04-2007 at 01:26 AM.
I believe you misunderstood my previous post, I should have written more clearly. In my previous post the first diff was while running VirtualBox, the second after closing it. After starting it again the diff was empty and the third is after closing it again. no-vm.out was updated only while VirtualBox was not running, vm.out was updated only while VirtualBox was running.
The medion-md2 made sound capture work under VirtualBox-WindowsXP-guest and under linux while VirtualBox was running. Somehow the modprobe worked only while VirtualBox wasn't running AND sometimes I did not take effect even while VirtualBox wasn't running.
Is there a efficient way to determine which of these drivers fits best, or have I to change the driver, to test sound, start the VM test sound, shutdown VM each time? And should the dmesg line "Unknown model for ALC883, trying auto-probe from BIOS" disappear with the right driver?
Now I'll place medion-md2 in the /etc/modprobe.d/alsa-base and test, how steady it will be working. Later I'll add the results to this post.
Edit: Ok, seems to be working fine. The mentioned line disappeared from dmesg, here is the current output. And an other problem was fixed too :-) - using headphones, sound was played through the speakers too, now the speakers are muted while headphones are put in.
Thank you very much for your help, I'll add later informations about troubles if occurring.
Unfortunately, the only way to ensure clean testing is to make sure that no software is accessing the audio device while unloading/reloading drivers. But it appears that the "medion-md2" model fixes your system. To further verify, I have created a patch here. If you could test it, that would be great, and I can submit it for inclusion in 1.0.15.
To apply the patch, follow these steps:
cd <alsa-driver>/alsa-kernel # replace <alsa-driver> with the path to the driver version you downloaded.
patch -p1 < FSC-1818.patch
make && sudo make install # this will just rebuild snd-hda-intel with the patch. Shouldn't need to reconfigure.
After the patched driver is installed, make sure there are no "model=<model>" options in /etc/modprobe*, and reload the driver.
Run more tests, and if everything looks good, I'll upload this later this week.
The bad news: I wrote "seems to be working fine" - was wrong.
medion-md2 made the microphone work under VirtualBox-WindowsXP (VB-XP), but the speakers were muted _not only_ while headphones plugged in, they did not work completely And the capture volume was really low and adjusting it in alsamixer was really strange, only a certain pitch level was hearable, higher and lower pitches shut the microphone down... so this driver was not the right one. I tested the other models too, some of them made the microphone work under VB-XP (3stack-6ch, haier-w66), but the speakers weren't working. 3stack-hp was quite similar to medion-md2, but sometimes the speakers were working...
The good news: Capture works now with the default driver (no option) while VB-XP is not running. I don't know may be because of the new alsa version. I'm sorry, my testing quality was quite bad - I should have found out this earlier. But this reduces the problem: Only while VB-XP is running, capture is not working.
I think based on this information, the patch is obsolete. Do you have any further suggestions, how to make capturing work in VB-XP and Linux while VB-XP is running? Thank you for your good support until now!
Full audio support with 6stack-dig, except capture doesn't work when running virtualbox.
Capture works with virtualbox when using medion-md2, but nothing else works.
This is correct, but in default mode (without any options) the alsamixer view and behaviour is different from 6stack-dig and seems to me fitting better to the hardware. I don't know how to determine which model is selected in the default mode (in case that "default model" is no distinct name).
I have an Asrock 4CoreDual-VSTA with an ALC888. The snd-hda-intel module was selected automatically by Yast on OpenSUSE 10.2. Without the model param, the module reports this as an ALC883 and defaults to the 3stack-dig config. I have now added 6stack-dig which should be the correct config for this board. My problem is that although the microphone can be heard, the volume is very low and the capture level control seems to have no effect on it. If I turn of the capture on the level control the microphone is muted so I know it's partially working. I'm using Skype for this.
For me things mostly work correctly. Sometimes, like today I couldn't get any signal from the mic into any application. Tried alsaconf, rebooted, messed with KMix and Volume Control and boom!, it works.
Same infamous Gigabyte 965P-S3.
Last edited by Andersonian; 09-11-2007 at 05:14 AM.
Andersonian: Your system is listed in the newer driver code. Please download alsa-1.0.15rc1 from http://alsa-project.org and try it.
asd0 & Mr_Flibble: Could you reconfigure the modules with "./configure --with-cards=hda-intel --with-debug=detect && make && sudo make install"? This will generate some debugging output in dmesg. Before reloading the driver with debugging enabled, run "dmesg -c >/dev/null" to clear the dmesg log, then reload the driver without any model options and send me the output.