From: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] fm801 driver status?
Date: Fri, 13 Dec 2002 12:15:24 +0100 [thread overview]
Message-ID: <3DF9C14C.4010204@gmx.de> (raw)
In-Reply-To: s5h3cp3uorz.wl@alsa2.suse.de
Takashi Iwai wrote:
>you can check this also via lspci command.
>in the output of lspci in your last mail, the i/o ports and irq are
>missing. please check again?
>
here we go...
00:0b.0 Multimedia audio controller: Fortemedia, Inc Xwave QS3000A
[FM801] (rev a0)
Subsystem: Fortemedia, Inc: Unknown device 1319
Flags: bus master, medium devsel, latency 40, IRQ 10
I/O ports at ec00 [size=128]
Capabilities: [dc] Power Management version 1
00:0b.1 Input device controller: Fortemedia, Inc Xwave QS3000A [FM801]
(rev a0)
Subsystem: Fortemedia, Inc: Unknown device 1319
Flags: bus master, medium devsel, latency 40, IRQ 11
Capabilities: [dc] Power Management version 1
the first entry seems to be the audio functionality, the second one must
be the game port.
IRQ 10 is shared with USB controller, IRQ 11 is shared with VGA controller.
>>The soundcard is working correctly under win98 without the need to
>>change any hardware or bios settings.
>>win98 reports:
>>fm801 pci audio, IRQ 10, I/O: EC00-EC7F
>>plus
>>fm801 pci audio, IRQ 11
>>and 'no conflicts'. I.e. win98 shows up the same IRQs used as lspci,
>>that should be correct, then. But lspci doesn't name any memory regions
>>used by this card. Do you have any idea what I could try? (I'll test
>>some other bios settings, mounting the card in another slot when I find
>>some spare time).
>>
>>
>
>what is the bios configuration? pnp os is yes? then set it to no.
>is ACPI enabled on kernel?
>
>
pnp was set to 'yes' in bios. I set it to 'no', but the system still
locks after loading alsa driver. To be more precisely: I did modprobe
snd-fm801, started aplay, stopped aplay, started arecord and after some
seconds the system hang. But the system hang just some seconds after
modprobing without using the audio device in a try before.
Here's the /var/log/messages output before(after) the system hangs:
Dec 12 19:13:27 localhost kernel: PCI: Found IRQ 10 for device 00:0b.0
Dec 12 19:13:27 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2
Dec 12 19:13:27 localhost kernel: PCI: Sharing IRQ 10 with 00:07.3
Dec 12 19:13:27 localhost kernel: PCI: Found IRQ 11 for device 00:0b.1
Dec 12 19:13:27 localhost kernel: ALSA ../alsa-kernel/pci/fm801.c:922:
unable to grab region 0x0-0x7f
Dec 12 19:14:56 localhost syslogd 1.4.1: restart.
ACPI is not enabled in kernel (but APM is, which should not be a
problem, I think).
Any further hints? I just don't want to crash my filesystems too often.
Hopefully, ext3 does its job.
Ahh! Perhaps I should remount read-only next time :-)
fe
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
prev parent reply other threads:[~2002-12-13 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 14:45 fm801 driver status? Friedrich Ewaldt
2002-12-12 15:08 ` [Alsa-user] " Takashi Iwai
2002-12-12 16:27 ` Friedrich Ewaldt
2002-12-12 17:32 ` Takashi Iwai
2002-12-13 9:53 ` Thierry Vignaud
2002-12-13 11:17 ` Friedrich Ewaldt
2002-12-13 16:29 ` Takashi Iwai
2002-12-13 16:33 ` Thierry Vignaud
2002-12-13 16:57 ` Friedrich Ewaldt
2002-12-13 17:02 ` Takashi Iwai
2002-12-13 18:24 ` Friedrich Ewaldt
2002-12-16 15:12 ` Takashi Iwai
2002-12-16 20:55 ` Friedrich Ewaldt
2002-12-17 18:11 ` Takashi Iwai
2002-12-18 13:28 ` Friedrich Ewaldt
2002-12-19 11:31 ` Takashi Iwai
2002-12-19 20:21 ` Friedrich Ewaldt
2002-12-13 11:15 ` Friedrich Ewaldt [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=3DF9C14C.4010204@gmx.de \
--to=friedrich.ewaldt@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.