public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joe Menola <menola@sbcglobal.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: More ALSA trouble
Date: Fri, 30 Dec 2005 18:39:04 -0600	[thread overview]
Message-ID: <200512301839.04828.menola@sbcglobal.net> (raw)
In-Reply-To: <1135987771.10978.3.camel@camille.espersunited.com>

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

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-12-31  0:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30 21:56 [gentoo-user] More ALSA trouble Michael Sullivan
2005-12-30 22:24 ` [gentoo-user] " Francesco Talamona
2005-12-30 23:43   ` Michael Sullivan
2005-12-31  0:00     ` Joe Menola
2005-12-31  0:09       ` Michael Sullivan
2005-12-31  0:39         ` Joe Menola [this message]
2005-12-31  1:15           ` Michael Sullivan
2005-12-31  2:12             ` Joe Menola
2005-12-31  3:05 ` [gentoo-user] " Qiangning Hong
2005-12-31  6:31   ` Michael Sullivan
2005-12-31  8:01   ` Michael Sullivan
2005-12-31 18:03   ` Michael Sullivan
2005-12-31 20:03     ` Abhay Kedia
2006-01-01  0:33       ` Michael Sullivan
2006-01-01  8:22         ` Abhay Kedia
2006-01-01 16:39           ` Michael Sullivan
2006-01-01 19:15             ` Abhay Kedia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200512301839.04828.menola@sbcglobal.net \
    --to=menola@sbcglobal.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox