Bug 115873

Summary:	support for ES1983S Maestro-3i soundcard
Product:	[Fedora] Fedora	Reporter:	Dimitri Papadopoulos <dimitri.papadopoulos>
Component:	firstboot	Assignee:	Brent Fox <bfox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 19:01:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dimitri Papadopoulos 2004-02-16 19:04:02 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.6) Gecko/20040113

Description of problem:
This is probably more related to the kernel than to firstboot. If so,
sorry about that, I wasn't sure which component to choose.

I'm running firstboot manually from the command-line, because of bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115678

This is the command-line:
$ export LANG=en_US.UTF-8
$ firstboot

The system is a Dell Latitude CPx laptop (model PPX, Latitude C family).

I get past the first pages, "Welcome", "License Agreement", "Date and
Time", "Display", "User Account". There's a problem with "Sound Card"
though.

The "Sound Card" page displays:
	Vendor: ESS Technology
	Model:  ES1983S Maestro-3i PCI Audio Accelerator
	Module: snd-maestro3

Then I click on button "Play test sound". The first time I ran the
test I got no error message, but the test failed: no sound was played.
So I answered "No" to the message box asking "Did you hear the sample
sound?".

After rebooting, I have been consistently seeing this additional
message when performing the same routine:
	The snd-maestro3 driver could not be loaded. This
	soundcard may not be compatible with Red Hat Linux.

This soundcard used to work properly with FC1.


Version-Release number of selected component (if applicable):
firstboot-1.3.3-3

How reproducible:
Always

Comment 1 Bill Nottingham 2004-02-16 20:24:45 UTC

What happens if you just load it by hand, run 'aumix' or 'alsamixer'
to turn up the volume,and then play a sound?

Comment 2 Dimitri Papadopoulos 2004-02-17 09:43:09 UTC

Actually the module *is* loaded, if that's what you mean:
	# lsmod
	[...]
	snd_maestro3           25636  1
	snd_ac97_codec         52612  1 snd_maestro3
	[...]
	# 

I'm unable to find "alsamixer" on the system:
	# locate alsamixer
	/usr/share/man/fr/man1/alsamixer.1.gz
	# 

I tried "aumix". The volume was indeed set at minimum. I modified the
colume level and was then able to hear the terminal bell or play a
sound for example with:
	# cat /usr/share/man/fr/man1/alsamixer.1.gz > /dev/dsp
	# 

However I'm still unable to hear the sample sound from within
firstboot. So I answer "No" to the dialog that asks "Did you hear thee
sample sound?" and then I get this message "Automatic detection of the
sound card did not work. Audio will not be available on the system.
Please click OK to continue."

After that I can't play sounds. If I run "aumix" again, I see that the
volume level is actually set to 0.

Just a guess: Maybe firstboot is resetting the volume level to 0? This
is what I see on the console...
	# firstboot
	[...]
	* dccprobe retruned bogus values:
	ID:   None
	Name: None
	HorizSync: None
	VertSync:  None
	
	vol set to 0, 0, P
	pcm set to 0, 0
	speaker set to 0, 0
	mic set to 0, 0, R
	cd set to 0, 0, P
	[...]
	#

Comment 3 Brent Fox 2004-02-20 16:30:33 UTC

Firstboot needs to override the default ALSA volume setting, which is 0.

*** This bug has been marked as a duplicate of 115932 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:01:19 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.