Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
I'm completely new to Linux and as a result completely new to these forums--hi!
I'm operating off a dv4 HP Pavilion laptop and made the switch to Ubuntu because frankly, this little lappy can't handle the bulk and unnecessary resource whorage that Vista requires. Happily, every driver that I had doubts about working after the switch to Linux has made the transition with flying colors; the only thing that didn't was the audio driver. This is where it gets weird; Ubuntu recognizes the actual driver and displays it in my sound mixer. I've read other help forums and tried the alsamixer test to see if it was actually recognized, and again it showed as being fully functional. Absolutely no part of my mixer is muted at this point, yet I still get zero sound.
Is there anyone who has had a similar problem or perhaps knows a solution? Linux seems to be perfectly recognizing the audio driver yet I still get no sound. Any help or advice would be greatly appreciated!
I got a couple hits from Launchpad. Try this first:
Quote:
I recently bought a HP DV7-1003EA, also suffering duff audio, jitter, echo type effect.
Looking at /proc/interrupts, I realised I wasn't getting any interrupts from the codec (cat /proc/asound/card0/codec#0 tells me it is an IDT 92HD71B7X), so I assumed it wasn't getting initialised properly. Not sure the snd-hda-intel driver knows what it is really, so went searching for a way to educate it.
Permission Denied... did you use sudo? You will not be able to write the line without root permissions.
Code:
sudo echo "options snd-hda-intel enable_msi=1" >> /etc/modprobe.d/alsa-base
^ ^ |<--------------^----------------->| ^^ |<--------^------------>|
| | | | +-- File to echo to
| | | +-------------- Redirectors, 2 of them means Append
| | | (1 would mean overwrite, very bad in
| | | this case)
| | +------------------------------------ Line to echo (add)
| +------------------------------------------------------ echo, writes following text to screen
| (unless redirected)
+----------------------------------------------------------- gives you root permissions (will
require password, pass doesn't echo)
Without it, writing to system files
will be prevented with a permission
error.
That would suggest then that the file was locked (in use). You may have to do the edit as root while nothing else is running.
Reboot, in grub select the recovery mode, then in the following menu ask for the console. Then you should be able to type the command above (without the sudo this time, as you will be root). Type reboot in order to reboot as normal.
I just tried the above directions to no avail, I'm still receiving no sound output. Should I have received some sort of confirmation after inputting the command in the recovery command line?
Also, there are two kernel options for recovery mode, 2.6.27-11-generic as well as 2.6.27-7 generic--I used the 2.6.27-11 kernel recovery mode to input the command. I'm not sure if an earlier kernel version would allow this command to run correctly??
I actually had to create that file in order to edit it, so the that's the only line in the file.. SHOULD there be that file fully created and full of info?
A Newbie's Getting Started Guide to Linux
Learn the basics of the Linux operating systems. Get to know what it is all about, and familiarize yourself with the practical side. Basically, if you're a complete Linux newbie and looking for a quick and easy guide to get you started this is it. subscribe
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe