From: Roger E Critchlow Jr <rec@elf.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: tecra 8100 / ymfpci
Date: Fri, 12 Dec 2003 09:39:33 -0700 [thread overview]
Message-ID: <3FD9EF45.7060200@elf.org> (raw)
In-Reply-To: <3FCE77D2.8000204@elf.org>
Greetings --
The alsa ymfpci drivers haven't worked on toshiba tecra 8100's
since 0.5. But the OSS drivers derived from the 0.5 alsa drivers
work fine. This is a non-deterministic problem in 1.0.0.rc2.
I've found that I can switch the ymfpci on or off by
repeatedly starting/aplaying/stopping the alsa sound system.
About one time in 3, 4, 5, or more, the sound chip will work,
all the other times I get static out of the speakers.
Specifically, all I'm doing is looping over:
/etc/init.d/alsasound start
aplay /usr/share/sounds/startup3.wav
/etc/init.d/alsasound stop
and most times through the loop I hear static, but sometimes I
hear startup3.wav played instead.
/sbin/lspci -vvxxs <ymfpci bus address> produces identical output
in all cases: alsa producing sound, alsa producing static, or old
oss driver producing sound, the lspci run in each case after the
aplay/play was finished.
I have the current Planet CCRMA kernel-2.4.23.ll, alsa drivers
(1.0.0.rc2), and source installed. I can run any with/without
comparisons that might be useful, or compile patches, or whatever.
(This kernel, by the way, only boots with the options pci=noacpi
or acpi=off, otherwise the boot hangs when initializing the pcmcia
slots. This goes for 2.6.0 and any other acpi enabled kernel that
I've tried on the tecra 8100.)
-- rec --
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-12-12 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 23:54 tecra 8100 / ymfpci Roger E Critchlow Jr
2003-12-12 16:39 ` Roger E Critchlow Jr [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=3FD9EF45.7060200@elf.org \
--to=rec@elf.org \
--cc=alsa-devel@lists.sourceforge.net \
/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