Bug 26454

Summary:	[sound] mixer volume settings on Maestro-2E (Diamond Monster MX400) card do not reflect true volume range on card.
Product:	Base System	Reporter:	nate <nate>
Component:	kern	Assignee:	freebsd-multimedia (Nobody) <multimedia>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description nate 2001-04-09 09:30:00 UTC

Device appears to be functioning in that I can hear the music I am playing, however the volume level with mixer settings at max is barely audible. I can only hear it when I turn my speaker volume to max, and only because of the speaker amp.

This machine dual-boots into Windows2k and the volume level is normal there.

Volume setting changes via the mixer do have an effect on the level, but the max setting in the mixer is not even close to the full output of the card.

Both the audio and dsp devices output at the same volume levels.

Fix: 

Unknown
How-To-Repeat: 	N/A

Comment 1 nate 2001-04-11 00:50:56 UTC

pcm0: <ESS Technology Maestro-2E> port 0xb000-0xb0ff irq 10 at device 10.0 
on pci0
setmap (5ca000, 4000), nseg=1, error=0
pcm0: Maestro DMA base: 0x5ca000
pcm0: ac97 codec id 0x83847609 (SigmaTel STAC9721/9723)
pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, 
SigmaTel
3D Enhancement
pcm0: ac97 primary codec extended features AMAP
setmap (5d5000, 4000), nseg=1, error=0
pcm0: pch[0].offset = 0xb000
setmap (5f2000, 4000), nseg=1, error=0
pcm0: pch[1].offset = 0x28000
setmap (5fa000, 4000), nseg=1, error=0
pcm0: pch[2].offset = 0x30000
setmap (602000, 4000), nseg=1, error=0
pcm0: pch[3].offset = 0x38000

If that's any help.

I'm willing to hack on the code a bit if you can give me a general idea of 
where to begin.

Comment 2 Kris Kennaway freebsd_committer

2001-07-13 01:55:40 UTC

Responsible Changed
From-To: freebsd-bugs->cg

Over to Mr sound

Comment 3 peterglavas 2002-03-08 06:13:24 UTC

Hi,
	I appear to have this exact problem however with a different card.

	The card is a Creative Vibra 128 (not onboard).

"
pcm0: <AudioPCI ES1373-8> port 0xe400-0xe43f irq 11 at device 9.0 on pci0

FreeBSD Audio Driver (newpcm) Mar  8 2002 15:38:43
Installed devices:
pcm0: <AudioPCI ES1373-8> at io 0xe400 irq 11 (1p/1r/0v channels duplex)
"

	Was a fix found? I'll keep looking either way.

Thanks,

Peter.

Comment 4 rob 2002-03-25 02:07:08 UTC

Hello,

I am having the same problem with a Dell Latitude CP M233XT.  This laptop contains a Crystal 4237B sound chip as reported from the BIOS.

When I use a kernel with the newpcm drivers I get sound out fine.  However the only mixer level that I can adjust is that of "cd".  The remaining mixer levels are all reported as "0" and can't be adjusted.  When I use a kernel which contains the old deprecated snd drivers I can adjust the mixer levels but as expected the sound quality is less than desirable.

The given sound chip is not PnP.

Here is my kernel config for both options:

SoundBlaster Pro 3.2 (PCM Drivers)

kernel configuration:

  device pcm
  device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15
  device pca0 at isa? port IO_TIMER1

dmesg output:

  sbc0: <SoundBlaster Pro> at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0
  pcm0: <SB DSP 3.02> on sbc0
  pca0 at port 0x40 on isa0

SoundBlaster Pro 3.2 (Old Drivers)

kernel configuration:

  device snd
  device sb0 at isa? port 0x220 irq 5 drq 1
  device sbxvi0 at isa? drq 5
  device sbmidi0 at isa? port 0x330

dmesg output:

  sb0 at port 0x220 irq 5 drq 1 on isa0
  snd0: <SoundBlaster Pro 3.2> 
  sb0: driver is using old-style compatibility shims

Any help would be appreciated.

Thanks,
Rob
-- 
Robert Getschmann
mailto:rob@getschmann.org
http://getschmann.org/

Comment 5 Mark Linimon freebsd_committer

2004-09-09 20:33:44 UTC

Responsible Changed
From-To: cg->sound

With permission, reassign to mailing list alias.

Comment 6 Alexander Leidinger freebsd_committer

2005-09-11 12:52:45 UTC

State Changed
From-To: open->feedback

Do you still see this problem on 5.[34] or -current?

Comment 7 Mark Linimon freebsd_committer

2005-12-04 02:36:16 UTC

State Changed
From-To: feedback->closed

Feedback timeout (> 2 months).