I have a sound card witch is intel-hda (intel-g45-devibex)...

My laptop is Brand new Sony VAIO VPCEB12FD...

I'm using Fedora 13 beta because its kernel is 2.6.33 + (and higher)

it is 100% compatible with Linux... Only the sound card problem...

i tried to increase the volume and the PCM and the speakers (headphones) usnig Alsamixer and aumix.

but the sound was too low but microphone worked like a charm!

Even the HDMI sound worked very well!

but the strange thing low sound from output...

Thanks!

Lash everything up full in alsamixer.

Presuming that doesn't work, there's some python script (hda-analyser?) on the alsaproject.org site. Grab that and you can play with the private parts of the HDA chip. Also remember that the hda-intel module has a menu in the kernel build, and it has support for a variety of chips. Try grep HDA .config on your kernel config
Lastly,

we

don't

need so many spare lines in your post :-)

1 members found this post helpful.

Whenever I have a sound problem, I try (as root):This usually works, unless pulseaudio is thrown into the mix, then all bets are off...

I find that maxing the volume on the Master, PCM, and Beep devices is the way to go on my Fedora 13 systems

i need to know how can i choose the defualt sound card...


maybe its : gedit /etc/pulse/daemon.conf









___________________________________________________________________________
If you don't know about me... I'm 13 yrs old with Fedora 13 believe me.

1 members found this post helpful.

[QUOTE=business_kid;3935599]Lash everything up full in alsamixer.

Presuming that doesn't work, there's some python script (hda-analyser?) on the alsaproject.org site. Grab that and you can play with the private parts of the HDA chip. Also remember that the hda-intel module has a menu in the kernel build, and it has support for a variety of chips. Try grep HDA .config on your kernel config
___________________________________________________________________________
business_kid! You are totally right i just need any one to upload me hda-analyzer becuase the website has epired! NOOOO! what a luck april 16 ..

does anyone have it please upload it!

I have it, but cannot upload it as they don't want tar.gz attachments on this list.If you have anywhere I can upload it let me know. Otherwise send a mail to my nic at gmail. You'll need to swap the '_' for a '.'

1 members found this post helpful.

Send it to my email: (nothing lol bot user)



Thank you...for supporting...

You may or may not want to remove that plain text link to your email.

1 members found this post helpful.

There's various ways to set your default soundcard. You can set it in .asoundrc, but only apps that use native alsa will adhere to that rule. You can set it in some application. And you can just reindex your soundcards so the one you want is device 0 (default).

~/.asoundrc
...
defaults.pcm.card 2
...

Where 2 would match your /proc/asound/cards list for the desired device.

/etc/modprobe.d/alsa_custom.conf (or whatever you have yours at)
...
options snd-usb-audio index=0
options snd-atiixp index=1
options snd-atiixp-modem index=2
...

I tend to remove the distro's definitions and mv mine in. But I'm probably not a typical user.

mplayer -ao alsa:device=usb_audio file.wav

where usb_audio is defined in your .asoundrc. Or use the hw: equivalent name. And varying other ways depending on the application.

pcm.usb.audio {
type hw
card 2
}

It could also be that you have some sort of softvol setup and it's set low.

$ amixer

1 members found this post helpful.

Try running alsaconf, then rebooting (or just restarting alsa if you know how), then run alsamixer -c0. Turn the far-left volume control to about 90, and see if it works. The speaker-test command works well for that, it plays pink noise (aka static) on your speakers.

1 members found this post helpful.

@talalpro:

I sent that script tar over to your email. Get your email out of the post now, as there are bots that search for such things and yopu will increase your spam otherwise.

1 members found this post helpful.

but can anyone help me with hda_analyzer becuase there a lot of people worked...






Thanks for everyone!

You are largely on your own with the chip. Note the situation now, and you can always get back. Then try turning on a few things. Search alsaproject.org for docs

1 members found this post helpful.