From: Jonathon Horsman <jonathon.horsman@bulletinwireless.com>
To: linux-sound@vger.kernel.org
Subject: S3 Sonic Vibes Linux driver
Date: Tue, 17 Jun 2003 00:17:48 +0000 [thread overview]
Message-ID: <marc-linux-sound-105580909208205@msgid-missing> (raw)
Greetings,
I obtained this email address from the MAINTAINERS file in the 2.4.21
kernel source. Apologies if this is the wrong place to ask.
The specified URL in MAINTAINERS:
http://www.ife.ee.ethz.ch/~sailer/linux/pciaudio.html
does not work! I assume should be updated to ~tom/linux/pciaudio.html
Having upgraded from the 2.4.19 kernel, I now receive the following
error when attempting to load the sonicvibes kernel:
kernel: sv: version v0.31 time 12:14:29 Jun 17 2003
kernel: PCI: Found IRQ 12 for device 02:00.0
kernel: PCI: Failed to allocate resource 7(0-1f) for 02:00.0
kernel: sv: cannot allocate DDMA controller io ports
This is a Redhat 7.3 box, the motherboard does have onboard sound but
this has been disabled at the bios, so I don't think it should affect it.
Your site gives a command line option: dmaio=x
However I'm uncertain what parameter should be passed here.
lspci -vv gives:
02:00.0 Multimedia audio controller: S3 Inc. SonicVibes
Subsystem: Unknown device 8000:8000
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 12
Region 0: I/O ports at 9000 [size\x16]
Region 1: I/O ports at 9400 [size\x16]
Region 2: I/O ports at 9800 [size=4]
Region 3: I/O ports at 9c00 [size=4]
Region 4: I/O ports at a000 [size=8]
Any suggestions would be great
Cheers
Jonathon
next reply other threads:[~2003-06-17 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 0:17 Jonathon Horsman [this message]
2003-06-17 18:28 ` S3 Sonic Vibes Linux driver Thomas Sailer
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-105580909208205@msgid-missing \
--to=jonathon.horsman@bulletinwireless.com \
--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