https://bugzilla.novell.com/show_bug.cgi?id=710194
https://bugzilla.novell.com/show_bug.cgi?id=710194#c7
Takashi Iwai
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.