From: Cornelius Creedon <neil@box1.staller.sunysb.edu>
To: linux-sound@vger.kernel.org
Subject: Re: awe64 not initializing on 2.2.2
Date: Sun, 14 Mar 1999 12:17:34 +0000 [thread overview]
Message-ID: <marc-linux-sound-92141443808574@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92139407200837@msgid-missing>
this message has occured to me in the past due to inaccurate or
insufficient options to the module.
are you specifying io, irq, dma, etc?
ie "modprobe sb io=0x220 irq=5 dma=1 dma16=5" or whatever...
if so do these match up with the card's config?
sounds like a pci card, right? does it appear in /proc/pci?
-cc
On Sun, 14 Mar 1999, Eric Tork wrote:
> I'm having quite a runaround with getting my awe64 to work with a
> 2.2.2 kernel. This is what I get when I run modprobe:
>
> /lib/modules/2.2.2/misc/sb.o: init_module: Device or resource busy
>
> if a cat my /dev/sndstat, there's no installed driver, no config
> options, nada.
>
> I upgraded everything that I needed to upgrade in the Changes file
> for the kernel, making sure that my modutils was properly installed.
> Insmod -V returns the correct version number (2.1.121) I'm at my wit's
> end.
>
> Thanx in advance
> - E
> --
> __________________________________
> Eric A. Tork
> "The Man Behind the Machine"
> Network Technician, Central Community College
> Hastings, Ne. (402) 461-2576
>
> "The only thing we learn from history
> is that we don't learn from history"
> ___________________________________
>
next prev parent reply other threads:[~1999-03-14 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 8:36 awe64 not initializing on 2.2.2 Eric Tork
1999-03-14 12:17 ` Cornelius Creedon [this message]
1999-03-14 20:04 ` Michael B. Trausch
1999-03-14 20:05 ` Erik de Castro Lopo
1999-03-14 21:26 ` Hannu Savolainen
1999-03-14 21:44 ` Eric Tork
1999-03-16 4:57 ` Cornelius Creedon
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=marc-linux-sound-92141443808574@msgid-missing \
--to=neil@box1.staller.sunysb.edu \
--cc=linux-sound@vger.kernel.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