All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000543]: Noisy sound, broken mixer with via8235 (driver regression)
Date: Wed, 13 Oct 2004 04:49:14 +0200 (CEST)	[thread overview]
Message-ID: <20041013024914.B85961B00B@server.perex-int.cz> (raw)


A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000543
======================================================================
Reported By:                obsidian
Assigned To:                
======================================================================
Project:                    ALSA - driver
Bug ID:                     543
Category:                   PCI - via82xx
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               Debian Sarge
Kernel Version:             2.6.8-1-k7
======================================================================
Date Submitted:             09-25-2004 23:15 CEST
Last Modified:              10-13-2004 04:49 CEST
======================================================================
Summary:                    Noisy sound, broken mixer with via8235 (driver regression)
Description: 
Sound is "shimmery" or "staticky" - noticeably bad. Mixer "master volume"
has no effect. "PCM volume" cannot be adjusted. "DXS https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000001" volume has an
effect but not "correct" - i.e. zero != silent. I do get the message (at
boot): 

via82xx: Assuming DXS channels with 48k fixed sample rate.
         Please try dxs_support=1 or dxs_support=4 option
         and report if it works on your machine.

This is a big prob. on this particular machine, which is supposed to
connect to the stereo and play mp3s, among other things.

Sound works normally outside Linux, and in Linux 2.4 with some Alsa 0.9.*.
But with Linux 2.6 and alsa 1.0.5/6, bleah.

I have been googling and troubleshooting all day. Here's what I've already
tried:

dxs_support=1, 2, 3 and 4 

This makes zero difference, so I thought I might be doing it wrong; I
tried it in modprobe.conf, modprobe.d/sound, and manually as an argument
to modprobe, i.e. "modprobe snd-via82xx dxs_support=1", also with both
rmmod'ing all alsa-related modules and rebooting altogether. 

Is there any way to tell if a dxs_support or other argument has been acted
on? It really felt like they were all ignored. I could never get that
original message to happen anytime but at boot, not matter what I did.
modprobe -v did show an "insmod" line with the parameter(s) on it,
though.

ac97_quirk=0,1,2,3,4

No effect.

Various kernel boot parameters, both alone and in combination with the
above:

noapic, nolapic, acpi=off, and pci=noacpi.

No effect. (BTW, I am currently running with all 4.) 

Frustrating, because it seemed from searching a great many people have the
exact same problem I do, but none of the many, varying "worked for me"
answers have helped me.

I'm a developer, somewhat kernel-savvy, and at your disposal. What do we
try first?
======================================================================

----------------------------------------------------------------------
 obsidian - 09-26-2004 01:09 CEST 
----------------------------------------------------------------------
Still no solution, but there are new details.

By loading snd-via82xx from /etc/modules, and putting the driver options
on the line in that file, I was finally able to get them to take effect
(i.e. items available in the mixer would change, 48k message wouldn't
display, etc). I ran through the tests again (rebooting every time) with
different values of dxs_settings and ac97_quirk. 

ac97_quirk seemed to have no effect anyway.

By varying dxs_settings I observed dxs volume controls disappearing from
alsamixer with some values. Otherwise everything was the same ("shimmery"
sound, master volume ignored, etc) and so this only had the effect of
making it impossible to influence the volume altogether.

----------------------------------------------------------------------
 obsidian - 09-26-2004 01:24 CEST 
----------------------------------------------------------------------
One more thing: I observed this in alsamixer. Surprised it hasn't popped up
in too many other places, but I noticed that the chip (CM9739) correlates
exactly with the same mixer issues I'm having:

Card: VIA 8235
Chip: C-Media Electronics CMI9739

See:
http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg10120.html

This doesn't overlap with sound quality issues, however.

----------------------------------------------------------------------
 obsidian - 09-26-2004 02:27 CEST 
----------------------------------------------------------------------
I upgraded to the current BIOS. No effect.

----------------------------------------------------------------------
 SirPreme - 10-11-2004 15:13 CEST 
----------------------------------------------------------------------
I have the same problem and I couldn't find a way to solve this. I'm using
a via82xx, too.

This is what makes it working on 2.4, I think:
If you compile OSS together with your soundcard into the kernel (or as a
module), it works fine, but then you donnot use real ALSA.. :/

Please, fix this bug..

----------------------------------------------------------------------
 tiwai - 10-11-2004 15:56 CEST 
----------------------------------------------------------------------
You should try dxs_support=4.  It works on more mobos.

Don't change ac97_quirk for CM9739.
The CM9739 has no PCM volume control indeed.
You need the software volume control in each app.

----------------------------------------------------------------------
 obsidian - 10-12-2004 02:06 CEST 
----------------------------------------------------------------------
I already tried setting dxs_support to 4. This only had the effects I
described above - did not fix the problem.

What can we try next?

----------------------------------------------------------------------
 tiwai - 10-12-2004 13:06 CEST 
----------------------------------------------------------------------
Try dxs_support=2, then you'll have no DXS multi-channel control.
This should be identical with the kernel OSS/Free driver.

If this doesn't fix the sound quality, it's because the output level
is too big (due to the lack of DAC attenuation control).  Try to
reduce the signal level in software.  E.g. xmms ALSA output has
the software volume control.

With dxs_support=4 (or 1), you have VIA DXS volume control, and can
reduce the playback volume with this control, too.
Note that the control seems inear, so it's peaky.

----------------------------------------------------------------------
 obsidian - 10-13-2004 04:49 CEST 
----------------------------------------------------------------------
When I tried dxs_settings=2 before, it did not fix the issue. The sound was
shimmery no matter what software was the audio source, and no matter what
the intensity of the sound. 

With other dxs_settings values, the sound was shimmery whether the 1st dxs
channel's volume was set high, low or anywhere in between. It was actually
the most noticeable when the sound was quiet. 

What else can I try?

Bug History
Date Modified  Username       Field                    Change              
======================================================================
09-25-04 23:15 obsidian       New Bug                                      
09-25-04 23:15 obsidian       Distribution              => Debian Sarge    
09-25-04 23:15 obsidian       Kernel Version            => 2.6.8-1-k7      
09-26-04 01:09 obsidian       Bugnote Added: 0001913                       
09-26-04 01:24 obsidian       Bugnote Added: 0001914                       
09-26-04 02:27 obsidian       Bugnote Added: 0001915                       
10-11-04 15:13 SirPreme       Bugnote Added: 0002078                       
10-11-04 15:56 tiwai          Bugnote Added: 0002080                       
10-12-04 02:06 obsidian       Bugnote Added: 0002086                       
10-12-04 13:06 tiwai          Bugnote Added: 0002090                       
10-13-04 04:49 obsidian       Bugnote Added: 0002109                       
======================================================================


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

             reply	other threads:[~2004-10-13  2:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13  2:49 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-28 13:55 [ALSA - driver 0000543]: Noisy sound, broken mixer with via8235 (driver regression) bugtrack
2005-04-09 14:14 bugtrack
2004-10-13  8:48 bugtrack
2004-10-12 11:06 bugtrack
2004-10-12  0:06 bugtrack
2004-10-11 13:56 bugtrack
2004-10-11 13:13 bugtrack
2004-09-26  0:27 bugtrack
2004-09-25 23:24 bugtrack
2004-09-25 23:09 bugtrack
2004-09-25 21:15 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041013024914.B85961B00B@server.perex-int.cz \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.