Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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've finally got sound working after a resintall of the latest kernel
also using PCI Sound blaster card. Now something weird keeps
happening.. Initially ALSA starts but there is no sound so i run
alsaconf and great stuff sound is working.. I've disabled the onboard
sound in the bios. I run aslactl store to keep the settings or so i
think but when i reboot again no sound.. i have to run alsa config each
time.. since it requires user input i can't just call it on boot up.
Hi,
I had a problem similar, which was the mixer volumes were getting reset to zero on each reboot, as alsactl doesnt seem to work to save mixer settings, so see if this is the problem and if you find a solution then let me know,
"alsactl store" will record you current volume settings and they are restored by running "alsactl restore"
maybe you just need to add it to some init script (not sure which one for redhat)
so i'm thinking now that it's not the default volumes or tthe starting of alsa because i've checked these time and time again and they always look fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.