From: neologix@free.fr
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] ATI IXP - Unknown symbol -> no sound
Date: Fri, 13 Oct 2006 18:07:45 +0200 [thread overview]
Message-ID: <1160755665.452fb9d128a2b@imp5-g19.free.fr> (raw)
In-Reply-To: <1160754364.4201.1.camel@mindpipe>
Hi.
Thanks for your reply, but it can't be this, because I build my own kernel.
I tried with vanilla kernel, and Debian's one, but I'm still experiencing these
problems. What's weird is that this doesn't happen everytime, maye one out of
5, or something, and I never had these kind of problems with <= 2.6.15
Well, I could just not use modules, but I'd like to know what's going wrong, and
if it's a kernel bug, have it spotted and hopefully fixed.
cheers
Selon Lee Revell <rlrevell@joe-job.com>:
> On Fri, 2006-10-13 at 17:01 +0200, neologix@free.fr wrote:
> > Hello.
> >
> > short:
> > [2.6.18] ATI IXP - Unknown symbol -> no sound
> >
> > longer:
> > I have an ATI IXP sound card, and since kernel 2.6.17, sometimes I have no
> sound
> > when I boot.
> > The card dosn't appear in /proc/asound/cards
> >
> > The relevant log part are given below
> > What is weird is that the modules are loaded, and that it doesn't happen
> > everytime.
> > I have a P4 with hyperthreading enabled (I don't know if it plays a part).
> > The thing is that before 2.6.17, I never had problems
>
> Sounds like your ALSA modules were built against a different kernel.
>
> Lee
>
>
prev parent reply other threads:[~2006-10-13 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 15:01 neologix
2006-10-13 15:46 ` Lee Revell
2006-10-13 16:07 ` neologix [this message]
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=1160755665.452fb9d128a2b@imp5-g19.free.fr \
--to=neologix@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®