When I get this kind of problems....I load VLC and or TVtime
they will load the needed libraries correctly if no major kernel changes
vlc.org (FRANCE) or freshrpms.net
Phil
Nigel Henry wrote:
On Friday 15 February 2008 20:32, Mark C. Allman wrote:
On Fri, 2008-02-15 at 20:09 +0100, Nigel Henry wrote:
On Friday 15 February 2008 02:35, Mark C. Allman wrote:
On Thu, 2008-02-14 at 22:13 +0100, Nigel Henry wrote:
On Thursday 14 February 2008 18:01, Mark C. Allman wrote:
On Wed, 2008-02-13 at 22:43 +0100, Nigel Henry wrote:
On Wednesday 13 February 2008 21:34, Frank Chiulli wrote:
Nigel,
I have a Sound Blaster Live! Value. This is an older machine.
F8 detected the card automatically. Unfortunately I can't tell
you exactly when I got the error. I had tried lots of things
to get sound to work but never did. It wasn't a big deal.
Then I was looking at something else when I was the error. I
figured that I would take a look at it. It seems like an easy
fix. It seems pretty obvious to me what was wrong. So I
corrected it. Then sound worked.
Frank
Thanks for the reply Frank. I was hoping that you would say that
your card was also an isa one, and would tie it in with Aarons
problems.
It's nice to see that both of you have resolved the problem, but
what's going on to cause these problems is beyond me.
As you see from what I posted above, my audigy2 soundblaster was
detected ok, and apart from disabling pulseaudio by removing
alsa-plugins-pulseaudio, and adding the usual lines to
/etc/modprobe.conf for my usb midi keyboard that uses
snd-usb-audio, the sounds are working ok.
Anyway, the fact that both you and Aaron now have sounds is the
main thing. Quite why you've both had problems, and me none, I've
no idea. That's computers for you.
Nigel.
Mark says:
When I run the "alsa-info.sh" script I see an error message when it
tries to collect the data that says something like "no soundcard
found." I think it's the same error that I see when I run aplay to
list out cards:
[mcallman@prez tmp]$ aplay -l
aplay: device_list:205: no soundcards found...
Also, when I look at the script results, I see the following at
about line 65 (this is after I tried "model=toshiba" in
modprobe.conf even though my laptop is a Dell XPS 1710):
Loaded sound module option
--------------------------
Module: snd_hda_intel
enable : N
id : <NULL>
index : 0
model : toshiba
position_fix : 0
power_save : 0
power_save_controller : Y
probe_mask : -1
single_cmd : N
Could the "enable: N" line be the key here? For those of you that
have sound working, what do you see listed for "enable?"
If it helps, you can look at all the test results that the script
uploaded at:
http://pastebin.ca/903970
-- Mark C. Allman, PMP
Hi Mark. I've sort of lost the plot a bit, but do you have your sound
working now?
I ask because the Alsa development folks are working hard on
resolving problems, particularly with the hda intel cards. Alsa
driver 1.0.16 has just been released, and I see many patches being
applied to the hda intel codecs, including your STAC9200 one.
Nigel.
Sound works using:
Pidgin
VLC (playing Rush/Tom Sawyer right now)
RealAudio
It does not work for:
gnome-cd (won't start a track)
grip (starts reading tracks, but no sound)
aplay/arecord ("no soundcard found")
Flash in Firefox
system-config-soundcard (everything's there--just no sound!!)
I can pipe a ".au" file (if I remember the extension correctly)
to /dev/audio and I hear it.
Some "/proc/asound" stuff:
[mcallman@prez X11]$ ls /proc/asound/
card0 cards devices hwdep Intel modules oss pcm seq timers version
[mcallman@prez X11]$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xdfffc000 irq 21
[mcallman@prez X11]$ ls /proc/asound/card0
codec#0 codec#1 id oss_mixer pcm0c pcm0p pcm1p
[mcallman@prez X11]$ cat /proc/asound/pcm
00-01: STAC92xx Digital : STAC92xx Digital : playback 1
00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 1
[mcallman@prez X11]$ cat /proc/asound/modules
0 snd_hda_intel
[mcallman@prez X11]$ cat /proc/asound/devices
2: : timer
3: : sequencer
4: [ 0- 1]: digital audio playback
5: [ 0- 0]: digital audio playback
6: [ 0- 0]: digital audio capture
7: [ 0- 1]: hardware dependent
8: [ 0- 0]: hardware dependent
9: [ 0] : control
[mcallman@prez X11]$ ls -ld /proc/asound/Intel
lrwxrwxrwx 1 root root 5 2008-02-14 20:18 /proc/asound/Intel ->
card0
Any suggestions would be welcome. If any of the Alsa development folks
would like a test bed to try out ideas just let me know.
-- Mark C. Allman
Hi Mark. I know I've got pulseaudio on the brain, as I had problems with
it, and disabled it, but have you got the default install of F8, where
pulseaudio is enabled? I ask because of the sound apps that you have
working. Realplayer uses OSS, VLC uses natively OSS, or Alsa, and also
Gnomes ESD. Not sure about Pidgin (Gaim), but I believe it uses OSS for
it's sounds. Puzzling why Alsa apps won't work.
If you havn't messed with pulseaudio since installing F8, I think I'd do
a: yum remove alsa-plugins-pulseaudio
having done that I'd see if now aplay, audio cd's, etc work.
Enough for now.
Nigel.
The only PulseAudio package I have installed is
pulseaudio-libs-0.9.8-5.fc8. It's needed for
libflashsupport-000-0.1.svn20070904.
Hi Marc. Sorry for the delay in replying. I spent a while today going back
through the alsa-devel archives, and the only reference to the Dell XPS 1710,
was one for the Dell XPS M1710w (which may well be the same machine), and was
to do with a problem with the subwoofer not working with the alsa 1.0.14
driver, and on a Suse install. See below for the thread.
http://mailman.alsa-project.org/pipermail/alsa-devel/2007-August/subject.html
I'll contact the guy directly, after you've replied to this post, to see if he
had any problems with getting sound working on his machine. I'd like to
clarify some things with you first though.
First, and I hate to say the word, but pulseaudio. I know you have removed
most of the pulseaudio packages, but would you confirm that the
"alsa-plugins-pulseaudio" package is no longer installed. Yumex should show
if it's installed, or rpm -q alsa-plugins-pulseaudio.
Secondly, and just out of interest, do you have access to alsamixer on the
command line?
Thirdly. You have model options for snd-hda-intel set as model=toshiba. From
the ALSA-configuration.txt file, that's in the alsa driver tarball, I see the
following model options, including one for the Dell XPS M1710
(model=dell-m23). It's worth trying that one, as it seems pretty specific.
See below for the full list of options. (It's for the 1.0.15 alsa driver)
STAC9200
ref Reference board
dell-d21 Dell (unknown)
dell-d22 Dell (unknown)
dell-d23 Dell (unknown)
dell-m21 Dell Inspiron 630m, Dell Inspiron 640m
dell-m22 Dell Latitude D620, Dell Latitude D820
dell-m23 Dell XPS M1710, Dell Precision M90
dell-m24 Dell Latitude 120L
dell-m25 Dell Inspiron E1505n
dell-m26 Dell Inspiron 1501
dell-m27 Dell Inspiron E1705/9400
gateway Gateway laptops with EAPD control
The OSS packages I have installed:
alsa-oss-libs-1.0.14-3.fc8
nss_compat_ossl-0.9.2-3.fc8
alsa-oss-1.0.14-3.fc8
alsa-plugins-oss-1.0.15-2.fc8
-- Mark C. Allman
Over to you, and all the best.
Nigel.
|
