after installing opensuse 11.1 all works well the only
problem i have is that there comes a strange sound out my speakers off
my notebook it is a scratching sound .
Is there a way to make this go away it is the only distribution where i
have the problem i had it also in opensuse 11.0 normally i use gnome but
i have the same problem with kde 3.5.10 and kde 4.1.
what must i do to make this go away because i like to use suse because
it is my favorite distro please help me :’(
While I imagine oldcpu will be the fellow to help you out, what are
your mixer settings (look in KMix)? Is the sound constant? Or does it
just happen occasionally?
kpt_j_t_kirk;1916852 Wrote:
> after installing opensuse 11.1 all works well the only
> problem i have is that there comes a strange sound out my speakers off
> my notebook it is a scratching sound .
> Is there a way to make this go away it is the only distribution where i
> have the problem i had it also in opensuse 11.0 normally i use gnome but
> i have the same problem with kde 3.5.10 and kde 4.1.
> Some more detail. to support zak89’s suggestion, is you could go to YaST
> Hardware > Sound > Other > Volume and move the volume bars there up to
75% (about - you need to iterative this to get the best level). Then
close YaST and go to your mixer, and back off on your PCM and master
volume.
If this is a Laptop PC, test this with battery ONLY, and also with
nominal wired AC power.
If the above does not help, you could provide more information. To
provide more information, with your PC connected to the Internet, can
you provide the output URL of running the following in a gnome-terminal
or a kde konsole:
Code:
/usr/sbin/alsa-info.sh
When the script completes it will pass you a URL. Please post that URL
here.
Also, please copy and paste the following into a gnome-terminal or
konsole and post the output here.::rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
rpm -q padevchooser pavucontrol pavumeter paman paprefs
uname -a
cat /etc/modprobe.d/sound::
I know you are just trying to make it easier (by putting this in a
thread where you believe a user has the same problem), but in truth this
makes it much harder for me. I end up having multiple users, on the
same thread, that I have to support, and I have to keep the users
separate in my mind as I iterate back and forth with support. I have to
hunt up and down in the thread to figure out what user is which. What
post corresponds to what. Plus the users tend to get confused whether
my support suggestions are for them, or for the other person in the
thread. This is because 95% of the time, the users have different
hardware, and that means the problem often has a different solution.
You did not explain what you have tried. Could you please go to YaST >
Hardware > Sound > Other > Volume and move the volume bars there up to
75% (about - you need to iterative this to get the best level). Then
close YaST and go to your mixer, and back off on your PCM and master
volume.
If that does not work, then please let me know.
And be careful, because it may now be difficult to sort your hardware
specifics from that of user kpt_j_t_kirk.
If the above does not help, you could provide more information. To
provide more information, with your PC connected to the Internet, can
you provide the output URL of running the following in a gnome-terminal
or a kde konsole:
Code:
/usr/sbin/alsa-info.sh
When the script completes it will pass you a URL. Please post that URL
here.
Also, please copy and paste the following into a gnome-terminal or
konsole and post the output here.::rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
rpm -q padevchooser pavucontrol pavumeter paman paprefs
uname -a
cat /etc/modprobe.d/sound::
i have try it via yast but without result.
Here is the output i made in the terminal
kpt_j_t_kirk, thats the change history of your updating the diagnostic
script. Thats not useful to me.
Please run that script again, please be careful, and this time please
provide the correct URL it provides. You can run the script by
typing:::/usr/sbin/alsa-info.sh::thanks!
oldcpu;1917099 Wrote:
> kpt_j_t_kirk, thats the change history of your updating the diagnostic
> script. Thats not useful to me.
>
> Please run that script again, please be careful, and this time please
> provide the correct URL it provides. You can run the script by
> typing:::/usr/sbin/alsa-info.sh::thanks!
kpt_j_t_kirk;1917133 Wrote:
> This may be better?
>
> http://tinyurl.com/7cckjq
OK, so your PC has a Conexant CX20549, which I believe is another name
for the CX5045 (from here: ‘Search results - AlsaProject’
(http://tinyurl.com/5nxsbg) ) .
In an above post, I asked that you go to YaST > Hardware > Sound >
Other > Volume and move your volume levels up to 75% (about - you need
to iterative this to get the best level). Then close YaST and go to your
mixer, and back off on your PCM and master volume.
You stated you did this.
But when I look at your mixer output I see this:
!!Amixer output
!!-------------
!!-------Mixer controls for card 0 [Intel]
Card hw:0 ‘Intel’/‘HDA Intel at 0xde300000 irq 22’
Mixer name : ‘Conexant CX20549 (Venice)’
Simple mixer control ‘Master’,0
Capabilities: pvolume pswitch pswitch-joined
Front Left: Playback 43 100%] [0.00dB] [on]
Front Right: Playback 43 100%] [0.00dB] [on]
Simple mixer control ‘PCM’,0
Capabilities: pvolume pswitch
Front Left: Playback 20 100%] [0.00dB] [on]
Front Right: Playback 20 100%] [0.00dB] [on]100% in both.
Clearly you did NOT back off on your master and PCM volume. There is no
point in us proceeding until you do so, as that could be your problem.
