On Tuesday 14 August 2007 08:39, Yunus wrote: > > Tim wrote: > >> On Mon, 2007-08-13 at 14:09 +0200, Nigel Henry wrote: > >>> another point to do with the sound test, is that when you press the > >>> play sound button, you may or may not hear the sound even if the > >>> soundcard is setup ok, because pretty much by default alsamixer has > >>> sound muted to save your speakers and hearing > >> > >> I thought the volume control on the test panel allowed you to overcome > >> that? I have to admit that I haven't had it come up in a muted mode, to > >> start with, to have to deal with that situation, and know whether that > >> would work. > > > > The problem you can run into is that the volume control in the test > > panel is only controlling one volume setting. You may need to adjust > > more then one control before you can hear anything. This is > > especially true with the Intel HDA chipset, because if the driver is > > using the wrong model, you may be adjusting the wrong control. > > (There are different "models" using the exact same chipset, but > > connecting things to different pins.) > > > > Mikkel > > There no drop-down lists to try out other options in test sound step (FC7 > installation process). > > I have run alsamixer, kmixer and "fc7 gnome mixer" (sorry i forget the name > for this default fc7 mixer). > There is nothing wrong with alsamixer, kmixer and "fc7 gnome mixer" > I also have run "soundcard detection" but still could not make the sound > works. > > Here is the content of modeprobe.conf ( I don't know whether this file has > to do with my sound problem): > alias eth0 tg3 > > alias scsi_hostadapter ata_piix > > alias scsi_hostadapter1 ahci > > alias snd-card-0 snd-hda-intel > > options snd-card-0 index=0 > > options snd-hda-intel index=0 > > > yunus Hi Yunus. Your modprobe.conf seems ok, but I believe you need to add a model option to one of the lines. I spent a bit of time on Google today, and a link on a post to the alsa developers list moved me to download the latest snapshot of the alsa driver. The post also suggested looking in ALSA-configuration.txt, which I found in the unpacked tarball. For the snd-hda-intel module, and the following chipsets refer to Acer Travelmate laptops. ALC260, and ALC883/888. You'll probably find that alsamixer shows the chipset as one of these. The suggestion for both of these is to set an option of "model=acer" (without the double quotes). It's worth a go, so open a konsole (CLI), su to root, and in a text editor, Gedit, Kwrite, etc, go to /etc/modprobe.conf, and change the last line that you show above, so that it says. options snd-hda-intel index=0 model=acer Save, then close the text editor. Still as root, run depmod -a, then reboot while praying. Whether this will work or not I don't know, but you only have to read through the ALSA-configuration.txt doc, to see how many variations there are (up to now), for chipsets that use snd-hda-intel. Links below. For the latest snapshot of the Alsa driver. ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ After unpacking the tarball you will find ALSA-configuration.txt in: alsa-kernel/Documentation I don't how new you are to linux Yunus, but when I started I was clueless about doing anything with tarballs, so here's a bit of info on unpacking them. Make a new directory (folder) in your /home/user directory, named Alsa-driver, for example. Download the tarball from the link above, saving it to your newly created directory. Next open a Konsole (CLI), and cd to the directory you saved the snapshot to. So it goes like this when you open the Konsole. cd Alsa-driver tar xjvf alsa-driver-hg20070814.tar.bz2 A new directory will be created in your Alsa-driver directory, named alsa-driver-hg20070814. You will find the ALSA-configuration.txt file within this directory using the path as above. And just for info, if the file had ended in tar.gz, you would unpack it using tar xzvf. "z" signifies gz (gunzip) compression, and "j" bz2 (bunzip) compression. The "x" is extract, the "v" is verbose, so you get some text in the terminal during the unpacking, and the "f" is file. Sorry if I'm wandering off on a tangent. Try the model=acer option, and see if things improve. All the best. Nigel.
