Re: [gentoo-user] alsa and kernel 2.6 question
Ian Truelsen <[EMAIL PROTECTED]> writes: > With the alsa modules now built into 2.6, should I load the snd_* > modules with the alsasound init script or via the modules.autoload? You may as well compile them in. Matt -- Matthew Kennedy Gentoo Linux Developer Bugs go to http://bugs.gentoo.org! -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa and kernel 2.6 question
On Mon, 19 Jan 2004 18:25:05 -0500 Bill Roberts <[EMAIL PROTECTED]> wrote: > > Okay. However, when I load the alsasound script I get a series of > > errors of which this one is representative: > > > > * Loading snd_emu10k1 > > FATAL: Module snd_emu10k1 already in kernel. > > > > I know they are built as modules. What is causing these errors? > > > Don't listen to my advice, I have never actually gotten alsa to > work, but... In 2.6, there are two ways of setting up ALSA. > First, compile it in the kernel, in which case you don't need to > load a module. Second, don't compile it in the kernel but as a > module (use M instead of *), then load the module. There seems to > be differing opinions on which method is less likely to fail. > Fair enough. It does work though, even with all the errors. I build everything that I can as modules, the system seems to think that they are not, or something is loading them before the alsasound script does. I think I will accept them as aesthetic for the moment and try to revive my glibc crippled box at the moment :( Always an adventure. -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org Signature key (742B740D) available at pgp.mit.edu pgp0.pgp Description: PGP signature
Re: [gentoo-user] alsa and kernel 2.6 question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill Roberts wrote: | Don't listen to my advice, I have never actually gotten alsa to | work, but... It's not that hard, what specific problems did you have? | In 2.6, there are two ways of setting up ALSA. | First, compile it in the kernel, in which case you don't need to | load a module. Second, don't compile it in the kernel but as a | module (use M instead of *), then load the module. Alsa is usually way more than one module. This box for example is: | lsmod|grep snd snd-pcm-oss38788 0 snd-mixer-oss 13296 1 [snd-pcm-oss] snd-seq-midi3744 0 (autoclean) (unused) snd-emu10k1-synth 4700 0 (autoclean) (unused) snd-emux-synth 26972 0 (autoclean) [snd-emu10k1-synth] snd-seq-midi-emul 4928 0 (autoclean) [snd-emux-synth] snd-seq-virmidi 3048 0 (autoclean) [snd-emux-synth] snd-emu10k172468 1 (autoclean) [snd-emu10k1-synth] snd-pcm59424 0 (autoclean) [snd-pcm-oss snd-emu10k1] snd-hwdep 4736 0 (autoclean) [snd-emu10k1] snd-util-mem1296 0 (autoclean) [snd-emux-synth snd-emu10k1] snd-page-alloc 6068 0 (autoclean) [snd-emu10k1 snd-pcm] snd-rawmidi12992 0 (autoclean) [snd-seq-midi snd-seq-virmidi snd-emu10k1] snd-ac97-codec 41272 0 (autoclean) [snd-emu10k1] snd-seq-oss26656 0 (unused) snd-seq-midi-event 3328 0 [snd-seq-midi snd-seq-virmidi snd-seq-oss] snd-seq38864 2 [snd-seq-midi snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event] snd-timer 14436 0 [snd-pcm snd-seq] snd-seq-device 4064 0 [snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-emu10k1 snd-rawmidi snd-seq-oss snd-seq] snd32196 0 [snd-pcm-oss snd-mixer-oss snd-seq-midi snd-emux-synth snd-seq-virmidi snd-emu10k1 snd-pcm snd-hwdep snd-util-mem snd-rawmidi snd-ac97-codec snd-seq-oss snd-seq-midi-event snd-seq snd-timer snd-seq-device] soundcore 3940 10 [snd] | There seems to | be differing opinions on which method is less likely to fail. I've never had a real problem with it. It's especially easy with the Gentoo docs having spelled out every single command and all: http://www.gentoo.org/doc/en/desktop.xml#doc_chap5 - -- ** * ____ _ * * ___/ /__ ___ / /_(_)__ ___ __ __ ___ __ _ * * / _ / -_)_- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFADG2loAq8t3CabwcRAm+6AKCooEw8Yq0wv6YGCAjtfwBNetcdHQCeK9G0 OehZPq4F9QIjan8MJzbz0cY= =fPjf -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa and kernel 2.6 question
On 12:43 Mon 19 Jan , Ian Truelsen wrote: > On Mon, 19 Jan 2004 19:56:00 + > Mike Williams <[EMAIL PROTECTED]> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Monday 19 January 2004 19:37, Ian Truelsen wrote: > > > With the alsa modules now built into 2.6, should I load the snd_* > > > modules with the alsasound init script or via the modules.autoload? > > > > The init script. > > - From a module perspective nothing has changed. The modules are still > > named the same, and end up in roughly the same place (depmod sorts out > > the actual location) > > > Okay. However, when I load the alsasound script I get a series of errors > of which this one is representative: > > * Loading snd_emu10k1 > FATAL: Module snd_emu10k1 already in kernel. > > I know they are built as modules. What is causing these errors? > > -- > Ian Truelsen > Email: [EMAIL PROTECTED] > AIM: ihtruelsen > Homepage: http://www.ihtruelsen.dyndns.org > Signature key (742B740D) available at pgp.mit.edu > Don't listen to my advice, I have never actually gotten alsa to work, but... In 2.6, there are two ways of setting up ALSA. First, compile it in the kernel, in which case you don't need to load a module. Second, don't compile it in the kernel but as a module (use M instead of *), then load the module. There seems to be differing opinions on which method is less likely to fail. -- Bill Roberts -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa and kernel 2.6 question
On Mon, 19 Jan 2004 19:56:00 + Mike Williams <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Monday 19 January 2004 19:37, Ian Truelsen wrote: > > With the alsa modules now built into 2.6, should I load the snd_* > > modules with the alsasound init script or via the modules.autoload? > > The init script. > - From a module perspective nothing has changed. The modules are still > named the same, and end up in roughly the same place (depmod sorts out > the actual location) > Okay. However, when I load the alsasound script I get a series of errors of which this one is representative: * Loading snd_emu10k1 FATAL: Module snd_emu10k1 already in kernel. I know they are built as modules. What is causing these errors? -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org Signature key (742B740D) available at pgp.mit.edu pgp0.pgp Description: PGP signature
Re: [gentoo-user] alsa and kernel 2.6 question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 19 January 2004 19:37, Ian Truelsen wrote: > With the alsa modules now built into 2.6, should I load the snd_* > modules with the alsasound init script or via the modules.autoload? The init script. - From a module perspective nothing has changed. The modules are still named the same, and end up in roughly the same place (depmod sorts out the actual location) - -- Mike Williams -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFADDZQInuLMrk7bIwRAlPkAKCnRLkPH/7ewtVqmbygNOUBU8lwhgCdGMed lVpwOJyFnoomEM6EL7AJGJQ= =hBNc -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
[gentoo-user] alsa and kernel 2.6 question
With the alsa modules now built into 2.6, should I load the snd_* modules with the alsasound init script or via the modules.autoload? -- Ian Truelsen Email: [EMAIL PROTECTED] AIM: ihtruelsen Homepage: http://www.ihtruelsen.dyndns.org Signature key (742B740D) available at pgp.mit.edu pgp0.pgp Description: PGP signature
