Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed/updated the latest alas driver (1.0.7) which now loads the module for my sound card (ESS Maestro 3).
The only problem now is - (and theres always a catch) it mutes everything on startup so I've got to go into volume control and unmute everything!!!
During the make-install process it did warn me that alsa mutes everything by default so the question now is, how do i change the defaults?!?
But I'm afraid I was a little too optimistic on my last post. My ESS Maestro 3 module isn't actually loading on startup, just a generic sound module (which is muted anyway). The upside now is that I can run ANY program (eg XMMS) to initialise the ess maestro 3 module.
So what I've been doing (after initialising the ess maestro module) is opening up gnome-volume-control and unmuting things.
Then I'd run alsamixer just to make sure the changes took affect.
I'd run 'alsactl store' which would update the asound.state file.
Only problem now is, when I restart the computer everything goes back to its defaults, including all the changes I made to asound.state.
I don't know if this info helps at all, but I also ran depmod and my current modprobe.conf reads:
# Note: for use under 2.4, changes must also be made to modules.conf!
alias eth0 e100
alias snd-card-0 snd-maestro3
alias usb-controller uhci-hcd
alias ieee1394-controller ohci1394
install sound-slot-0 /sbin/modprobe --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
#remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove sound-slot-0
and my modules.conf reads:
alias eth0 e100
alias sound-slot-0 maestro3
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias usb-controller usb-uhci
alias ieee1394-controller ohci1394
# Note: for use under 2.6, changes must also be made to modprobe.conf!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.