From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Udo Hoerhold <maillists@goodontoast.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SoundBlaster Live! with kernel 2.5.x
Date: Wed, 16 Apr 2003 08:18:59 -0700 [thread overview]
Message-ID: <20030416081859.5a2f37af.rddunlap@osdl.org> (raw)
In-Reply-To: <200304160200.57995.maillists@goodontoast.com>
On Wed, 16 Apr 2003 02:00:57 -0400 Udo Hoerhold <maillists@goodontoast.com> wrote:
| On Wednesday 16 April 2003 12:58 am, Randy.Dunlap wrote:
| > >
| > > I have the exact configuration you have above. The soundcard is
| > > detected, but I do get one error:
| > >
| > > Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
| > > Version 0.9.2 (Thu Mar 20$
| > > Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
| > > snd-card-0. error = -16
| > > Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr
| > > 15 22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
| > > Apr 15 22:17:45 hobbiton kernel: ALSA device list:
| > > Apr 15 22:17:45 hobbiton kernel: #0: Sound Blaster Live! (rev.7) at
| > > 0xdf80, irq 10
| > >
| > > I've been ignoring modprobe errors because I know there are some issues
| > > with 2.5 kernel and modules, and I'm compiling everything into the
| > > kernel. Could this be causing a problem, though?
| >
| > I don't think you need to be ignoring module problems now.
| >
| > Do you have emu10k1 built as loadable module or in-kernel?
| >
| > -16 error is saying that the IO region or the IRQ is busy so the
| > driver can't allocate it.
| >
| > Is /sbin/modprobe a current version (for 2.5.50++ and recent)?
| >
| > ~Randy
|
| It's compiled into the kernel. I'm not sure why I would be getting modprobe
| errors, everything is compiled in. I have module-init-tools 0.9.11a, which
| is the right modprobe for 2.5.46 and up, right?
That sounds right for tools.
But if emu10k1 is built into the kernel, you don't need to modprobe it at all.
Why is that happening? Do you actually have emu10k1 module also?
It should have errors when loading if the device is already claimed.
--
~Randy
next prev parent reply other threads:[~2003-04-16 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 0:01 Udo Hoerhold
2003-04-16 1:49 ` Robert Love
[not found] ` <200304152228.11010.maillists@goodontoast.com>
2003-04-16 4:34 ` Udo Hoerhold
2003-04-16 4:58 ` Randy.Dunlap
2003-04-16 6:00 ` Udo Hoerhold
2003-04-16 15:18 ` Randy.Dunlap [this message]
2003-04-16 0:40 Alistair Strachan
2003-04-16 4:29 ` Udo Hoerhold
2003-04-16 14:07 ` Alistair Strachan
2003-04-16 15:33 Paolo Ciarrocchi
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=20030416081859.5a2f37af.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maillists@goodontoast.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®