@druelan
Did you check the "preferences" for switching on the other controls?
@druelan
Did you check the "preferences" for switching on the other controls?
Thanks for the quick reply. On Alsa 10.0.17 all controls are checked and they are what you can see in the pic, but I can't remember if I rechecked after the upgrade to Alsa 10.0.18a. I'm going to reinstall it today using the .14 version of your script to see if there are new controls among the mic boost.
Hi there.
I do have similar issues! Controls always load default values after
login.
I just had a look at the start script /etc/init.d/alsa-utils , which
is in charge for restoring the config.
perhaps you try following:
1. cd /var/lib/alsa
2. sudo ln -s /etc/asound.state asound.state
3. Play around with the controls and restart
Let me know, if it works. I guess it will.
I am not sure yet if it is gonna be an ALSA or Ubuntu issue. I doubt though that it has something to do
with the upgrade-script.
BTW:
When playing with the controls of my 2nd soundcard by muting them
I realized that the sliders are moved to the bottom when reopening
the gnome-mixer-applet.
Instead of just muting the channels they put them to 0, which is IMO a fault.
Can anybody confirm this behaviour?
Cheers
Last edited by soundcheck; December 16th, 2008 at 01:36 PM.
ALSA just confirmed that the alsactl issue is an Ubuntu/Debian issue.
I also reported the issue on launchpad https://bugs.launchpad.net/ubuntu/+s...ux/+bug/308587
Cheers
Last edited by soundcheck; December 16th, 2008 at 03:46 PM.
I actually closed the Ubuntu ticket again, since I learned that Debian
is patching alsa-utils and the asound.state issue on purpose just to
put that file under /var/lib/alsa.
My earlier workaround was in fact the solution to the issue.
So - for now I'll stay with the workaround. I'll implement it into the
script Rev. 1.15.
I recommend to implement above workaround or to run Rev. 1.15.
Let me know if you're experiencing problems.
Cheers
Try these module options on snd-hda-intel in /etc/modprobe.d/alsa-base:
ALC269
basic Basic preset
quanta Quanta FL1
eeepc-p703 ASUS Eeepc P703 P900A
eeepc-p901 ASUS Eeepc P901 S101
fujitsu FSC Amilo
auto auto-config reading BIOS (default)
e.g.
snd-hda-intel index=0 model=eeepc-p901
Ok:
* Auto, eeepc-p703 eeepc-p901 and fujitso did not show anything new.
* Basic enables something similar to 1.0.16 + Hardy (even the internal beeper, wich I thoght this machine lacked).
* Quanta shows something similar to basic, but different labels (PC speaker instead of beeper, seems more for desktop than notebook).
So, basic seems the best here. Later I will do some tests in Skype.
Final picture to complete the collection
BTW, I've tested this setting on a non upgraded 1.0.17 kernel and has no effect, so seems that Alsa 1.0.18a got improvements but needs to improve the bios detection.
Thank you so much soundcheck for the help solving this. Here, another "thank" for your collection
Last edited by druellan; December 17th, 2008 at 01:09 AM.
You made my day.
Thank you for taking the time to write this, soundcheck. It's taken me further than any other method thus far. My problems are certainly not caused by the script, but might be good to know about.
Short story - sound was working, I upgraded to 8.04 then 8.10 and somewhere during this my sound stopped working. Ubuntu will recognize the card via lspci:and alsaconf can find the card and complete, but aplay -l returns nothing but an error:Code:lspci -v 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) Subsystem: Hewlett-Packard Company Device 30bf Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10 Memory at c0000000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable- Capabilities: [6c] HyperTransport: MSI Mapping Enable+ Fixed+ Kernel modules: snd-hda-intel
Any of the mixer or sound control tools also return errors, as will (dun dun dun) modprobe snd-hda-intel:Code:aplay: device_list:217: no soundcards found...
Of note - AlsaUpdater installed the link here:Code:FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.27-9-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg snd_hda_intel: Unknown parameter `stack'
/lib/modules/2.6.27-9-generic/kernel/sound/modules
but I found an snd-hda-intel.ko file here:
/lib/modules/2.6.27-9-generic/kernel/sound/pci/hda
which I replaced with a link to the AlsaUpdater files like the one in the first directory, much like another user in this topic.
Plenty of reboots and --purge and permission checking and whatnot. I followed Debugging Sound Problems and the Comprehensive Sound Problem Solutions Guide and several other guides as far as possible - I'm running short on things to try and hoping someone can see something I can't. If not, I'll run through one of the officialish guides again and see about filing a bug.
Bookmarks