fm801 driver status?
Hi!
I've got a fm801 based sound card which locks my computer completely some seconds after loading the alsa driver module. I compiled drivers with debug=detect -- please see my mail(s) from 12/09/2002 on alsa userlist for more info. What else could I do? Meanwhile I found several reports describing the same problem. Therefore my question(s): Should it be possible to run a fm801 soundcard using the 0.9.0rc6 or cvs driver? Anyone who has installed such a card successfully? Any ideas what I'm doing wrong? (I have installed some other soundcards using alsa09 without problems.) Thanks a lot in advance!
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/
At Thu, 12 Dec 2002 15:45:29 +0100,
Quoted 12 lines · Friedrich Ewaldt
Hi!
I've got a fm801 based sound card which locks my computer completely some seconds after loading the alsa driver module. I compiled drivers with debug=detect -- please see my mail(s) from 12/09/2002 on alsa userlist for more info. What else could I do? Meanwhile I found several reports describing the same problem.
Therefore my question(s): Should it be possible to run a fm801 soundcard using the 0.9.0rc6 or cvs driver? Anyone who has installed such a card successfully? Any ideas what I'm doing wrong? (I have installed some other soundcards using alsa09 without problems.)
it looks like a hardware problem rather than the driver itself. as lspci shows, your fm801 card has no resources at all. something wrong with either the soundcard itself or the combination with the mobo...
can you verify the hardware?
Takashi
-------------------------------------------------------
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/
Hi,
many thanks for your quick reply! Here's some more info:
Mandrake Control Center recognices the card as follows (partly in german, sorry, but perhaps that's no problem in ERL/NUE ;-) ):
Hersteller: Fortemedia, Inc
Bus: PCI
Bus: 1319:801:1319:1319
Standort auf den Bus: 0:b:0
Beschreibung: Xwave QS3000A [FM801]
Modul: snd-fm801
Medienklasse: MULTIMEDIA_AUDIO
I had no alsa installed while running hardware detection.
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).
TIA
fe
Quoted 11 lines · Takashi Iwai
At Thu, 12 Dec 2002 15:45:29 +0100,
Quoted 6 lines · Friedrich Ewaldt
Hi!
I've got a fm801 based sound card which locks my computer completely some seconds after loading the alsa driver module. I compiled drivers with debug=detect -- please see my mail(s) from 12/09/2002 on alsa userlist for more info. What else could I do? Meanwhile I found several reports describing the same problem. Therefore my question(s): Should it be possible to run a fm801 soundcard using the 0.9.0rc6 or cvs driver? Anyone who has installed such a card successfully? Any ideas what I'm doing wrong? (I have installed some other soundcards using alsa09 without problems.)
Quoted 10 lines
it looks like a hardware problem rather than the driver itself. as lspci shows, your fm801 card has no resources at all. something wrong with either the soundcard itself or the combination with the mobo...
can you verify the hardware?Takashi
-------------------------------------------------------
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/
At Thu, 12 Dec 2002 17:27:38 +0100,
Quoted 15 lines · Friedrich Ewaldt
Hi,
many thanks for your quick reply! Here's some more info:Mandrake Control Center recognices the card as follows (partly in german, sorry, but perhaps that's no problem in ERL/NUE ;-) ):
Hersteller: Fortemedia, Inc
Bus: PCI
Bus: 1319:801:1319:1319
Standort auf den Bus: 0:b:0
Beschreibung: Xwave QS3000A [FM801]
Modul: snd-fm801
Medienklasse:MULTIMEDIA_AUDIO
Quoted 1 line
I had no alsa installed while running hardware detection.
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?
Quoted 11 lines
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?
Takashi
-------------------------------------------------------
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/
Quoted 10 lines · Takashi Iwai
Quoted 10 lines
Mandrake Control Center recognices the card as follows (partly in german, sorry, but perhaps that's no problem in ERL/NUE ;-) ):
Hersteller: Fortemedia, Inc
Bus: PCI
Bus: 1319:801:1319:1319
Standort auf den Bus: 0:b:0
Beschreibung: Xwave QS3000A [FM801]
Modul: snd-fm801
Medienklasse:MULTIMEDIA_AUDIO
this information came frome harddrake which uses libldetect (which is also used by lspcidrake).
bus is vendor_id:card_id:subvendor_id:subcard_id
bus position (Standort auf den Bus) is pci_bus:pci_device:pci_function Beschreibung is of course description of the device and Hersteller is vendor
module is of course kernel module
the driver association is made by libldetect from/usr/share/ldetect-lst/pcitable :
tv@vador ~ $ fgrep fm801 /usr/share/ldetect-lst/pcitable
0x1319 0x0801 "snd-fm801" "Fortemedia, Inc|Xwave QS3000A [FM801]" 0x1319 0x1000 "snd-fm801" "Fortemedia, Inc|FM801 PCI Audio"
Quoted 1 line
Quoted 1 line
I had no alsa installed while running hardware detection.
alsa drivers're included in mandrake kernel
Quoted 1 line
you can check this also via lspci command.
lspcidrake -v will give him the module too
Quoted 2 lines
in the output of lspci in your last mail, the i/o ports and irq are missing. please check again?
in order to have the full information, i would like Friedrich to send us the following information (what i call the classic bug sound tester) :
"lspcidrake -v | fgrep AUDIO" will tell you which driver your card use by default
"grep snd-slot /etc/modules.conf" will tell you what driver it currently uses
"/sbin/lsmod" will enable you to check if its module (driver) is loaded or not
"/sbin/chkconfig --list sound" and "/sbin/chkconfig --list alsa" will tell you if sound and alsa services're configured to be run on initlevel 3
"aumix -q" will tell you if the sound volume is muted or not
"/sbin/fuser -v /dev/dsp" will tell which program uses the sound card.
this will tell us at which stage the problem happen
-------------------------------------------------------
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/
Hi!
For new test results see the end of this mail.
Quoted 35 lines · Thierry Vignaud
Quoted 12 lines · Takashi Iwai
Quoted 12 lines
Mandrake Control Center recognices the card as follows (partly in german, sorry, but perhaps that's no problem in ERL/NUE ;-) ):
Hersteller: Fortemedia, Inc
Bus: PCI
Bus: 1319:801:1319:1319
Standort auf den Bus: 0:b:0
Beschreibung: Xwave QS3000A [FM801]
Modul: snd-fm801
Medienklasse:MULTIMEDIA_AUDIOthis information came frome harddrake which uses libldetect (which is also used by lspcidrake).
bus is vendor_id:card_id:subvendor_id:subcard_id
bus position (Standort auf den Bus) is pci_bus:pci_device:pci_function Beschreibung is of course description of the device and Hersteller is vendor
module is of course kernel modulethe driver association is made by libldetect from
/usr/share/ldetect-lst/pcitable:tv@vador ~ $ fgrep fm801
/usr/share/ldetect-lst/pcitable0x1319 0x0801 "snd-fm801" "Fortemedia, Inc|Xwave QS3000A [FM801]" 0x1319 0x1000 "snd-fm801" "Fortemedia, Inc|FM801 PCI Audio"
Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
I had no alsa installed while running hardware detection.
alsa drivers're included in mandrake kernel
No, sorry. I recompiled the kernel with sound but without alsa because I wanted to use an alsa version newer than rc2 to check if the problem was solved already. I already installed rc6 and a newer cvs version on another mdk9.0 system without problems. I should have done recompiling/installing the kernel and newer alsa version correctly.
Quoted 7 lines
Quoted 3 lines
you can check this also via lspci command.
lspcidrake -v will give him the module too
I already attached my lspci -v outputs in two previous mails, but to be sure they get to where they should ...
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
Quoted 9 lines
Quoted 4 lines
in the output of lspci in your last mail, the i/o ports and irq are missing. please check again?
in order to have the full information, i would like Friedrich to send us the following information (what i call the classic bug sound tester) :
Quoted 7 lines
"lspcidrake -v | fgrep AUDIO" will tell you which driver your card use by default
"grep snd-slot
/etc/modules.conf" will tell you what driver it currently uses
I threw out all entries regarding soundcards from modules.conf. modprobing the snd-fm801 module is enough to cause the problems.
Quoted 3 lines
"
/sbin/lsmod" will enable you to check if its module (driver) is loaded or not
no sound module is loaded (because nothing there in modules.conf) up to the point where I do a 'modprobe snd-fm801'. As soon as I do, the following modules are added:
snd-fm801 9772 0 (unused) snd-pcm 71328 0 [snd-fm801] snd-mpu401-uart 3840 0 [snd-fm801] snd-rawmidi 15424 0 [snd-mpu401-uart] snd-opl3-lib 7652 0 [snd-fm801] snd-timer 12908 0 [snd-pcm snd-opl3-lib] snd-hwdep 5152 0 [snd-opl3-lib] snd-ac97-codec 31620 0 [snd-fm801] snd 36076 0 [snd-fm801 snd-pcm snd-mpu401-uart snd-rawmidi snd-opl3-lib snd-timer snd-hwdep snd-ac97-codec] soundcore 4068 0 [snd]
Quoted 8 lines
"
/sbin/chkconfig--list sound" and "/sbin/chkconfig--list alsa" will tell you if sound and alsa services're configured to be run on initlevel 3"aumix -q" will tell you if the sound volume is muted or not
no mixer problems
Quoted 3 lines
"
/sbin/fuser-v/dev/dsp" will tell which program uses the sound card.
none. I've deactivated artsd and have no other sound daemon installed. The only programs that produce sound are controlled by me. (But now I know that even hitting backspace once in Konsole causes a beep that locks the system. Not really! The END of the beep does! see below)
Quoted 5 lines
this will tell us at which stage the problem happen
OK. I've done new tries. Now I know that modprobing snd-fm801 causes the following to be written in /var/log/messages:
Dec 13 11:53:24 localhost kernel: ALSA ../alsa-kernel/pci/fm801.c:922:
unable to grab region 0x0-0x7f
If I do not produce any sound output, the system does not lock up as I've written before (I must have caused an error beep in a KDE terminal. I've tried this: Causing a beep locks the system immediately). Sorry for the misleading information. My fault. After another reboot (always interesting if the filesystem was damaged ;-) ), I modprobed snd-fm801 and used aplay to play a wav file. It does without problems. But at the same time the playback stops, the system locks up. So, in summary, the critical moment is stopping playback on the fm801. I think, I've read the same problem description somewhere before. What could I try next?
Thanks for all your help so far!
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/
At Fri, 13 Dec 2002 12:17:33 +0100,
Quoted 18 lines · Friedrich Ewaldt
Quoted 8 lines
Quoted 4 lines
you can check this also via lspci command.
lspcidrake -v will give him the module too
I already attached my lspci -v outputs in two previous mails, but to be sure they get to where they should ...
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
Quoted 5 lines
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
i need the pci vendor/device id for them.
could you give me the output of "lspci -n" for two devices above? the audio chip should be 0x1319:0x0801.
Takashi
-------------------------------------------------------
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/
Quoted 2 lines · Takashi Iwai
i need the pci vendor/device id for them.
could you give me the output of "lspci -n" for two devices above?
or "lspcidrake -v" if you have ldetect package installed but not pciutils
-------------------------------------------------------
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/
Takashi Iwai schrieb:
[...]
Quoted 14 lines
Quoted 7 lines
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 1Quoted 5 lines
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
Quoted 4 lines
i need the pci vendor/device id for them.
could you give me the output of "lspci -n" for two devices above? the audio chip should be 0x1319:0x0801.
lspci -n output:
00:0b.0 Class 0401: 1319:0801 (rev a0)
00:0b.1 Class 0980: 1319:0801 (rev a0)
and that's part of the output of 'lspcidrake -v':
snd-fm801 : Fortemedia, Inc|Xwave QS3000A [FM801]
[MULTIMEDIA_AUDIO] (vendor:1319 device:0801 subv:1319 subd:1319)
snd-fm801 : Fortemedia, Inc|Xwave QS3000A [FM801] [INPUT_OTHER]
(vendor:1319 device:0801 subv:1319 subd:1319)
does this information help or do you need any other outputs? thanks! (The fm801 chip on this card is one of the older models without SPDIF input. I looked this up some time ago because I saw the possibility to get an digital input with this card using an soldering iron and some el. parts for a few cents)
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/
At Fri, 13 Dec 2002 17:57:10 +0100,
Quoted 22 lines · Friedrich Ewaldt
Takashi Iwai schrieb:
[...]Quoted 14 lines
Quoted 7 lines
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 1Quoted 5 lines
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 1Quoted 4 lines
i need the pci vendor/device id for them.
could you give me the output of "lspci -n" for two devices above? the audio chip should be 0x1319:0x0801.
Quoted 4 lines
lspci -n output:
00:0b.0 Class 0401: 1319:0801 (rev a0)
00:0b.1 Class 0980: 1319:0801 (rev a0)
thanks, could you try the attached patch?
at least, the weird messages for allocation of invalid i/o ports should disappear. not sure whether this cures the lock-up problem, though.
Takashi
Quoted 7 lines · Takashi Iwai
Quoted 6 lines
lspci -n output:
00:0b.0 Class 0401: 1319:0801 (rev a0)
00:0b.1 Class 0980: 1319:0801 (rev a0)
Quoted 9 lines
thanks, could you try the attached patch?
at least, the weird messages for allocation of invalid i/o ports should disappear. not sure whether this cures the lock-up problem, though.Takashi
done. The error in /var/log/messages doesn't appear any longer (I only get these 'sharing IRQ ...' messages). Thanks! But the system still locks up when stopping playback :-(
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/
At Fri, 13 Dec 2002 19:24:49 +0100,
Quoted 16 lines · Friedrich Ewaldt
Quoted 13 lines · Takashi Iwai
Quoted 6 lines
lspci -n output:
00:0b.0 Class 0401: 1319:0801 (rev a0)
00:0b.1 Class 0980: 1319:0801 (rev a0)thanks, could you try the attached patch?
at least, the weird messages for allocation of invalid i/o ports should disappear. not sure whether this cures the lock-up problem, though.
Quoted 6 lines
Quoted 3 lines
Takashi
done. The error in
/var/log/messagesdoesn't appear any longer (I only get these 'sharing IRQ ...' messages). Thanks! But the system still locks up when stopping playback :-(
to be sure, could you elaborate the symptom again and the detail of your system (kernel version, applied patches, ALSA version)? especially, please check the following:
- loading the module and unloading it immediately works?
- the port and irq number are correct, i.e. match with the resources listed on lspci?
- playback (via aplay) works? does the system hang up at the start, during the playback or at the stop?
- during the playback, does the count in /proc/interrupts increases? (check with another terminal)
a typical reason of such a hang up is either the wrong spinlocks, unexpected infinite loops in the driver code, or the interrupt storms. if it's the interrupt storm, then it can be related with the hardware, often motherboard chipset, or BIOS version.
or, could it be because of ACPI? did you apply it?
ciao,
Takashi
-------------------------------------------------------
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/
Hi!
Hopefully, the following information is of some help.
Quoted 4 lines · Takashi Iwai
to be sure, could you elaborate the symptom again and the detail of your system (kernel version, applied patches, ALSA version)?
kernel: 2.4.19-16mdkcustom, compiled with sound and without alsa. I compiled from the kernel source delivered with mandrake 9.0 and did not apply any patches.
alsa: cvs snapshot 2002-12-09.tar.bz2 with your patch (that fixes the i/o port error in /var/log/messages) applied
system:
duron 850, 128 MB PC 133
NMC (the name changed to enmic, I think) board, KT-133 chipset with via686a. Award bios 01/10/2001-8363-686A-6A6LMNM9C-00
Quoted 4 lines
especially, please check the following:
- loading the module and unloading it immediately works?
yep. /proc/asound builds up immediately, lsmod shows snd, ... modules immediately after modprobing
Quoted 3 lines
- the port and irq number are correct, i.e. match with the resources listed on lspci?
info from /proc/asound/cards:
FM801-AS at 0xec00, irq 10
lspci output:
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]
(IRQ 10, I/O ec00 also shown by window?)
Quoted 3 lines
- playback (via aplay) works? does the system hang up at the start, during the playback or at the stop?
playback works. I even hear the correct sound when I plug in headphones :-) The system locks when stopping playback. (If only I had infinite audio files...)
Quoted 4 lines
- during the playback, does the count in
/proc/interruptsincreases? (check with another terminal)
the count at '10' (I assume this is irq 10) increases during playback by approx. 10-15 per second.
Quoted 7 lines
a typical reason of such a hang up is either the wrong spinlocks, unexpected infinite loops in the driver code, or the interrupt storms. if it's the interrupt storm, then it can be related with the hardware, often motherboard chipset, or BIOS version.
or, could it be because of ACPI? did you apply it?
I unselected ACPI before compiling the kernel. ACPI is switched off in the bios. (I have only APM running as power management)
Quoted 5 lines
ciao,
Takashi
Is there anything else I could do?
cheers,
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/
At Mon, 16 Dec 2002 21:55:01 +0100,
Quoted 7 lines · Friedrich Ewaldt
Quoted 5 lines
especially, please check the following:
- loading the module and unloading it immediately works?
yep.
/proc/asoundbuilds up immediately, lsmod shows snd, ... modules immediately after modprobing
ok.
Quoted 6 lines
Quoted 3 lines
- the port and irq number are correct, i.e. match with the resources listed on lspci?
info from
/proc/asound/cards:
FM801-AS at0xec00, irq 10
Quoted 8 lines
lspci output:
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](IRQ 10, I/O ec00 also shown by window?)
ok, looks fine, too.
Quoted 6 lines
Quoted 3 lines
- playback (via aplay) works? does the system hang up at the start, during the playback or at the stop?
playback works. I even hear the correct sound when I plug in headphones :-) The system locks when stopping playback. (If only I had infinite audio files...)
hmm...
Quoted 6 lines
Quoted 4 lines
- during the playback, does the count in
/proc/interruptsincreases? (check with another terminal)the count at '10' (I assume this is irq 10) increases during playback by approx. 10-15 per second.
ok, that's normal.
Quoted 9 lines
Quoted 7 lines
a typical reason of such a hang up is either the wrong spinlocks, unexpected infinite loops in the driver code, or the interrupt storms. if it's the interrupt storm, then it can be related with the hardware, often motherboard chipset, or BIOS version.
or, could it be because of ACPI? did you apply it?I unselected ACPI before compiling the kernel. ACPI is switched off in the bios. (I have only APM running as power management)
ok, then it shouldn't be a problem.
perhaps do you see something out in the kernel messages on console 10 (alt+f10) when the system hangs? well, after hang up, you cannot switch the console, but you can start aplay on a certain console, switch with alt+f10 and wait until the playback is finished.
anyway, could you try the attached patch?
if you see something on the kernel messages such like kernel panic or oops, we can track the point...
ciao,
Takashi
Hi Takashi!
Thank you very much for your work!
The last patch solved the problem. No system hangs anymore. Looking back, I must say it was not *that* practical to reboot the system every time I used the audio device :-)
The sound quality is ok (I wouldn't expect it any better with this cheap card). Using my impulse response program, I also recognized that the overall D/A + A/D latency is constant (32 samples) as expected. (I could never see this before because using my cs46xx based xfire the latency changes in the range of 200 - 258 samples with every run. Bad - the xfire has much better sound quality. Is this a hint that pcm_link() doesn't work with cs46xx or is this maybe due to the DSP structure of the xfire?)
Using aplay, at the end of the audio file the last played samples get repeated once. This doesn't happen with 'play', 'cat somefile /dev/dsp' or 'artsplay'. But when I cause an error beep in a shell, I first hear the beep and then the last samples played back before by any program like aplay, play, xmms,... I can reproduce this as many time as I like, i.e. the samples remain in the soundcard buffer all the time. Another issue regarding aplay: playing back mono wav with a sampling frequency below 44k1, the sound get's crackled. This also doesn't happen with the other playback programs.
Now I don't know if these small problems result from playing back through the alsa device directly or if they are caused by aplay. Sorry to say I've no other native alsa app installed at the moment to do tests (e.g. alsa output for xmms ...).
Quoted 6 lines · Takashi
perhaps do you see something out in the kernel messages on console 10 (alt+f10) when the system hangs? well, after hang up, you cannot switch the console, but you can start aplay on a certain console, switch with alt+f10 and wait until the playback is finished.
I can switch with alt+f1 .. +f6 to the consoles 1 ..6, alt+f7 is X, but alt+f8 and alt+f10 only show a blinking cursor at the top. Does that mean that there are no messages or are I'm doing something wrong? (I don't see any messages that I can read in /var/log/messages afterwards)
Quoted 3 lines
anyway, could you try the attached patch?
of course.
Quoted 4 lines
if you see something on the kernel messages such like kernel panic or oops, we can track the point...
sorry, but...
... no more kernel problems to report ;-)
Quoted 6 lines
ciao,
Takashi
cheers
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/
At Wed, 18 Dec 2002 14:28:09 +0100,
Quoted 11 lines · Friedrich Ewaldt
Hi Takashi!
Thank you very much for your work!
The last patch solved the problem. No system hangs anymore. Looking back, I must say it was not *that* practical to reboot the system every time I used the audio device :-)
The sound quality is ok (I wouldn't expect it any better with this cheap card). Using my impulse response program, I also recognized that the overall D/A + A/D latency is constant (32 samples) as expected.
good to hear that!
Quoted 6 lines
(I could
never see this before because using my cs46xx based xfire the latency changes in the range of 200 - 258 samples with every run. Bad - the xfire has much better sound quality. Is this a hint thatpcm_link()doesn't work with cs46xx or is this maybe due to the DSP structure of the xfire?)
might be a chip limitation, but might be a dsp code which currently we are using...
Quoted 9 lines
Using aplay, at the end of the audio file the last played samples get repeated once. This doesn't happen with 'play', 'cat somefile
/dev/dsp' or 'artsplay'. But when I cause an error beep in a shell, I first hear the beep and then the last samples played back before by any program like aplay, play, xmms,... I can reproduce this as many time as I like, i.e. the samples remain in the soundcard buffer all the time. Another issue regarding aplay: playing back mono wav with a sampling frequency below 44k1, the sound get's crackled. This also doesn't happen with the other playback programs.
hmm, this could have been a cause of the last hang-up. the unexpected interrupt was not caught by the handler.
could you check /proc/asound/card0/pcm0p/sub0/hw_params for each case? also, please try the attached patch (the drivers should be compiled with --with-debug=full) and see what shown in the kernel messages. this will print the current ply_ctrl register value.
the patch is to the latest cvs. the cvs tree already includes the last fix and some additions for pause/release and spdif-out.
Quoted 13 lines
Now I don't know if these small problems result from playing back through the alsa device directly or if they are caused by aplay. Sorry to say I've no other native alsa app installed at the moment to do tests (e.g. alsa output for xmms ...).
Quoted 6 lines · Takashi
perhaps do you see something out in the kernel messages on console 10 (alt+f10) when the system hangs? well, after hang up, you cannot switch the console, but you can start aplay on a certain console, switch with alt+f10 and wait until the playback is finished.
Quoted 4 lines
I can switch with alt+f1 .. +f6 to the consoles 1 ..6, alt+f7 is X, but alt+f8 and alt+f10 only show a blinking cursor at the top. Does that mean that there are no messages or are I'm doing something wrong? (I don't see any messages that I can read in
/var/log/messagesafterwards)
not sure, but it should depend on the configuration or the distribution.
anyway, it doesn't matter, the problem looks almost solved :)
Takashi
Hi!
Quoted 9 lines · Takashi Iwai
At Wed, 18 Dec 2002 14:28:09 +0100,
Quoted 4 lines · Friedrich Ewaldt
Using aplay, at the end of the audio file the last played samples get repeated once. This doesn't happen with 'play', 'cat somefile
/dev/dsp' or 'artsplay'. But when I cause an error beep in a shell, I first hear the beep and then the last samples played back before by any program like aplay, play, xmms,... I can reproduce this as many time as I like, i.e. the samples remain in the soundcard buffer all the time. Another issue regarding aplay: playing back mono wav with a sampling frequency below 44k1, the sound get's crackled. This also doesn't happen with the other playback programs.
Quoted 5 lines
hmm, this could have been a cause of the last hang-up. the unexpected interrupt was not caught by the handler.
could you check
/proc/asound/card0/pcm0p/sub0/hw_paramsfor each case?
Here's the output of /proc/asound/card0/pcm0p/sub0/hw_params for a 8Bit mono 11kHz wav file:
*** played with 'play'
access: RW_INTERLEAVED
format: U8
subformat: STD
channels: 1
rate: 11025 (11025/1)period_size: 8192buffer_size: 65536tick_time: 10000
OSS format: U8
OSS channels: 1
OSS rate: 11025
OSS period bytes: 8192
OSS periods: 8
*** played with 'aplay'
access: RW_INTERLEAVED
format: U8
subformat: STD
channels: 1
rate: 11025 (11025/1)period_size: 149buffer_size: 5513tick_time: 10000
*** xmms, oss output:
access: RW_INTERLEAVED
format: U8
subformat: STD
channels: 1
rate: 11025 (11025/1)period_size: 256buffer_size: 8192tick_time: 10000
OSS format: U8
OSS channels: 1
OSS rate: 11025
OSS period bytes: 256
OSS periods: 32
*** xmms, alsa output
access: MMAP_INTERLEAVED
(if MMAP deactivated in xmms: access: RW_INTERLEAVED)
format: U8
subformat: STD
channels: 1
rate: 11025 (11025/1)period_size: 149buffer_size: 5513tick_time: 10000
Sound is ok with play and xmms/OSS output, but with aplay and xmms/ALSA it is noisy and crackled as if it were bad FM radio transmission (with and without MMAP mode, MMAP doesn't change anything). That's only true for mono files with low sampling rates. Stereo files are ok using alsa or oss device.
Using xmms/ALSA, another problem occurs:
If xmms finishes playback of one file and starts the next of the playlist, output sounds like if it were mixed with helicopter noise. To stop this distortion I can press the 'pause' button twice or press 'stop' + 'playback'. The same distortion occurs when I start playback of the same or another file of the playlist while playback of one file is running. I can see (better: hear) this problem with stereo 44kHz files and ALSA output. Using OSS output, this problem doesn't occur. I don't see this problem using xmms/ALSA on an similar system (some software) with another soundcard.
Quoted 7 lines
also, please try the attached patch (the drivers should be compiled with --with-debug=full) and see what shown in the kernel messages. this will print the current
ply_ctrlregister value.
the patch is to the latest cvs. the cvs tree already includes the last fix and some additions for pause/release and spdif-out.
I patched against the cvs snapshot from december 9th with all your previous patches applied before. I'll also test with latest cvs if I find some more time.
Here's some output of /var/log/syslog after applaying the last patch and compiling with debug=full:
after error beep in shell:
Dec 19 19:43:13 localhost kernel: ALSA ../alsa-kernel/pci/fm801.c:395: prepare: ply_ctrl = 0x180
(after the beep I hear loud noise or the last audio samples played before by any audio player. These samples are played with wrong speed, probably because the beep is played back at another sampling rate)
after playing mono wav file 8Bit, 11kHz using aplay or play:
Dec 19 19:44:15 localhost kernel: ALSA ../alsa-kernel/pci/fm801.c:395: prepare: ply_ctrl = 0x380
after playing stereo wav file 16Bit, 44.1kHz using aplay or play:
Dec 19 19:45:00 localhost kernel: ALSA ../alsa-kernel/pci/fm801.c:395: prepare: ply_ctrl = 0xc980
The messages are repeated for every playback.
Do these play_ctrl values show anything? They are the same for 'aplay' as for 'play' (and xmms, too). But playing back with native alsa apps, I have some trouble that I don't have when I use /dev/dsp. The values seem to depend only on the audio format. Does this info help? ciao
fe
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating? Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
Quoted 4 lines · Takashi Iwai
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.
Quoted 13 lines
Quoted 12 lines
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).Quoted 1 line
Quoted 1 line
Quoted 4 lines
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/