Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4308 - desktop howto contains slightly incorrect setup info for ALSA
Summary: desktop howto contains slightly incorrect setup info for ALSA
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: [OLD] Documentation (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Arcady Genkin (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-29 01:51 UTC by Glen Coates
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glen Coates 2002-06-29 01:51:43 UTC
- desktop HOWTO currently instructs users to update /etc/modules.autoload with
the new ALSA modules, however they should really be updating the
/etc/modules.d/alsa file which is not mentioned in the HOWTO.

- the HOWTO currently instructs users to add the alsa scripts to runlevel
default, when it should really be runlevel boot.

- the HOWTO currently refers to the ALSA initscript as 'alsa', but in the
current ebuilds it is called 'alsasound'.

- the HOWTO also neglects to mention the necessary step of running `alsactl
store` to preserve the mixer settings beyond the next boot.

- optionally, the HOWTO might like to mention that users can emerge alsa-xmms to
add native ALSA compatibility to xmms, which is likely to be the most frequent
use of the ALSA drivers on the majority of systems :)
Comment 1 John Davis (zhen) (RETIRED) gentoo-dev 2002-08-12 23:26:19 UTC
- desktop HOWTO currently instructs users to update /etc/modules.autoload with
the new ALSA modules, however they should really be updating the
/etc/modules.d/alsa file which is not mentioned in the HOWTO.

--FIXED in the current version that is on the website

- the HOWTO currently instructs users to add the alsa scripts to runlevel
default, when it should really be runlevel boot.

--FIXED in the current version that is on the website

- the HOWTO also neglects to mention the necessary step of running `alsactl
store` to preserve the mixer settings beyond the next boot.

--is this necessary? ALSA saved my settings after reboot w/o running this cmd.

- optionally, the HOWTO might like to mention that users can emerge alsa-xmms to
add native ALSA compatibility to xmms, which is likely to be the most frequent
use of the ALSA drivers on the majority of systems :)

--done in my updated desktop guide.
Comment 2 Matthew Kennedy (RETIRED) gentoo-dev 2002-09-22 15:57:39 UTC
zhen,

there's a slight problem with the desktop configuration guide with the step on
how to configure alsa.

   "You'll want to replace snd-card-emu10k1 with your sound card. " 

should be 

   "You'll want to replace snd-emu10k1 with your sound card."

Most likely its a hang-over from the alsa-0.5 days.

Matt
Comment 3 John Davis (zhen) (RETIRED) gentoo-dev 2002-09-29 12:29:40 UTC
Not going to change this because the file in modules.d still lists it as this.

//ZhEN
Comment 4 Arcady Genkin (RETIRED) gentoo-dev 2002-09-29 14:01:14 UTC
Actually, the file in modules.d has "snd-ens1371".  Have a look at the file
/usr/portage/media-sound/alsa-driver/files/alsa-modules.conf.
Comment 5 John Davis (zhen) (RETIRED) gentoo-dev 2002-10-01 13:16:02 UTC
I have looked at both, and I still do not think this should be changed due to 
the fact that it is *right*. I am using ALSA 9, what are you using?

//ZhEN
Comment 6 Arcady Genkin (RETIRED) gentoo-dev 2002-10-01 17:47:38 UTC
Not sure what you mean...  What is right?  The snd-emu10k1 form is right, not
snd-card-emu10k1.  The latter is from alsa 0.5.
Comment 7 John Davis (zhen) (RETIRED) gentoo-dev 2002-10-07 18:11:35 UTC
Arg, could it be possible that it is an artifact from alsa .5 on my system? I 
am using .9 and I still have the "old" format as you call it..

//ZhEN
Comment 8 Arcady Genkin (RETIRED) gentoo-dev 2002-10-26 14:36:31 UTC
I'm going to close this now, as this seems to have been fixed in the latest docs.