On Fri, 2005-12-30 at 18:39 -0600, Joe Menola wrote: > On Friday 30 December 2005 6:09 pm, Michael Sullivan wrote: > > On Fri, 2005-12-30 at 18:00 -0600, Joe Menola wrote: > > > On Friday 30 December 2005 5:43 pm, Michael Sullivan wrote: > > > > I ran alsaconf (again). When it tried to start alsasound it gave all > > > > those same errors again. > > > > > > Alsaconf is only used for modular kernels. Running it on compiled in > > > modules tends to muck up the system pretty good. > > > The easiest way to fix this is go back to alsa drivers compiled as > > > modules and run alsaconf. > > > I manged to fix my system after I made the same error, but the process > > > was such a run around that I couldn't explain how I did it. lol > > > > > > -jm > > > > I'm confused. The ALSA stuff is compiled into my kernel AS modules. > > You say "the easiest was to fix this is to go back to alsa drivers > > compiled as modules and run alsaconf" Isn't that what I did yesterday? > > I'm confused as well...I was replying to your earlier post today in which you > stated... > "Yesterday I compiled a kernel with ALSA support for my card compiled in. > I booted with that kernel yesterday and everything worked great. Today > when I booted into Linux I got errors when alsasound tried to start. > Here are the errors:" > > "Compiled in" says to me that you built your kernel with alsa support built > in, sorry if I misunderstood. > > -jm > I meant that I compiled ALSA with support for my sound card as modules...
-- [email protected] mailing list
