From: LuftHans <LuftHans@asu.edu>
To: linux-sound@vger.kernel.org
Subject: Re: Vibra 16V PnP <-> SuSE 5.3 ?
Date: Sat, 13 Mar 1999 01:02:33 +0000 [thread overview]
Message-ID: <marc-linux-sound-92128723514199@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92124872211270@msgid-missing>
On Fri, 12 Mar 1999, Rico Dreier wrote:
> Hello,
moin Rico,
> I'm trying to activate a Vibra 16C PnP under SuSE 5.3. Independent of the selected
> Interrupt 5 or 7 an error occurs during the boot process saying that the interrupt
> test failed (no other devices use INT5/7 -> /proc/interrupts). The soundcard can
> not be configured by using YaST since it is not possible to reach the respective
> menu entry.
I had this same prob with a soundblaster under SuSE, RedHat and Slackware (I
switched from Slackware to SuSE and played with RedHat just to try it out).
The problem was BIOS was locking it out. I changed IRQ 5 to be available for
isapnp and it was immediately taken by my scsi card and video card, so I
loaded the soundcard at IRQ 11 :).
> The kernel is compiled with audio support etc. selected, but I'm not sure if all
> the sound options are set correctly :-/ Does the card only work by using the
> isapnp tool, and does anybody have a valid isapnp.conf file for SoundBlaster Vibra
> 16C or 16X?
>
> Inserting the sound module with insmod or modprobe leads to unresolved symbols.
Same prob I had. This was under 2.0.3x, 2.1.x and 2.2.x. Once I changed the
bios AND went to a higher irq it worked. Just moving to a higher irq before
hadn't worked...
ciao,
der.hans
> Thanks for every hint,
> Bye, Rico
# +++++++++++=================+++++++++++ #
# LuftHans@asu.edu #
# http://home.pages.de/~lufthans/ #
# I've got a photographic memory, #
# but I'm lousy photographer. - der.hans #
# ======+++++++++++++++++++++++++++++++++====== #
prev parent reply other threads:[~1999-03-13 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 14:17 Vibra 16V PnP <-> SuSE 5.3 ? Rico Dreier
1999-03-13 1:02 ` LuftHans [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=marc-linux-sound-92128723514199@msgid-missing \
--to=lufthans@asu.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