https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bugzilla@go4more.de --- Comment #1 from Takashi Iwai 2011-08-10 10:03:18 UTC --- Does this happen without pulseaudio? Try the following - - Logout, go to runlevel 3, login as root - Kill all sound apps, including stale pulseaudio daemons - Run "rcalsasound stop" - Back up /var/lib/alsa/asound.state - Remove /var/lib/alsa/asound.state - Reboot with boot option "3", not to start desktop - Check the mixer status -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bugzilla@go4more.de --- Comment #3 from Takashi Iwai 2011-08-10 18:05:32 UTC --- (In reply to comment #2)

Happens without pulseaudio, too.

Did you test the procedure above? Or just citing the post?

According to this post: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/... it is a general problem with kernel 3.0 and the Intel HD-driver.

No, it's no generic problem. Likely specific to certain codec chips. If the test procedure in comment 1 exhibits the same problem, please run "alsa-info.sh --no-upload" and attach the generated output. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c Alex Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bugzilla@go4more.de | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c6 --- Comment #6 from Alex Müller 2011-08-12 16:11:32 UTC --- If you're so keen on the wording: Yes, I did it that way - if not, I would have said so! Deleting the file and using runlevel 3 does not change anything. Again the buzzing feedback. (Starting in runlevel 3 has the only effect of alsamixer not working because it fails to connect to the pulseaudio demon.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c7 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bugzilla@go4more.de --- Comment #7 from Takashi Iwai 2011-08-12 16:36:40 UTC --- (In reply to comment #6)

If you're so keen on the wording: Yes, I did it that way - if not, I would have said so!

Well, that's not sure (depending on the quality of bug reporter :)

Deleting the file and using runlevel 3 does not change anything. Again the buzzing feedback.

OK, I suppose this is not through "Capture" but the analog-loopback channels, i.e. "Line Playback Volume", "Front Mic Playback Volume" and "Rear Mic Playback Volume". Right? I wonder, though, how these are enabled. Basically the driver shouldn't touch these volumes. If it's a driver issue, I'd need more data described below. If it's outside the driver (e.g. alsactl program triggered by udev), we'll need to track more deeply later.

(Starting in runlevel 3 has the only effect of alsamixer not working because it fails to connect to the pulseaudio demon.)

You can pass -c0 option to alsamixer to skip PA routing. One more favor to ask you: in runlevel 3, unload the sound driver (e.g. via "rcalsasound stop" as root), then load the driver manually with probe_only=1 option. Then get /proc/asound/card0/codec#* file, and attach here. (After that, you can reload the driver via "rcalsasound restart" again to back to normal.) This will give a fresh codec register status before the driver probe, so I can track down any driver issue via emulator. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c9 --- Comment #9 from Alex Müller 2011-08-14 04:58:05 UTC --- Created an attachment (id=445729) --> (http://bugzilla.novell.com/attachment.cgi?id=445729) Output of /proc/asound/card0/codec#0 My system has two "sound cards": One is the onboard sound (#0) and the other the HDMI sound of the gfx card (#1). As far as I can judge, the output as appended is from the onboard sound. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c11 --- Comment #11 from Alex Müller 2011-08-14 05:14:20 UTC --- Right now I'm a bit puzzled. Right after reporting the above postings, for which I played around a bit with runlevels, alsa and alsamixer I did a complete reboot. Not for the first time today, but this time the system started up without any buzzing noise and a working sound system. Maybe the 3.0.1 update changed something, after all? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=710194 https://bugzilla.novell.com/show_bug.cgi?id=710194#c13 --- Comment #13 from Alex Müller 2011-08-14 16:45:17 UTC --- Just for the record ;): I didn't unmute anything - stuff was simply suddenly unmuted by default at about the time kernel 3.0 came around. KMix, Pulseaudio etc. cannot be the culprits, as the buzzing started as soon as the kernel configured its devices (must be one of the first messages at boot time), at a time where nothing else is messing around with the audio devices. This went on for weeks and dozens of boots as long as kernel 3.0 was installed, the problem also survived a new install and a freshly created user account. Now that 3.0.1 is around, I have inconsistent behavior, however, things seem to go in the right direction: Probably for the first few boots today some older configuration files still had the wrong settings (e.g. I had the phenomenon that the buzzing one time started only at the moment KDE started up). As the 3.0.1 changelog contains some lines about a wrong pin assignment with Realtek-chips, I hope this fix will have fixed my problem, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.