FC4

Lnx805 · 09-04-2005, 01:34 AM

I recently set up a drive with FC4 and there's no sound output. The card is detected, but on boot-up I get the error: "Error Initializing Driver - Invalid Argument, Setting Sound to Null". The sound card is a TB Santa Cruz which has the CS4630 chip.
Which file has the sound driver arguments and where is it located? ALSA is installed, but after running a serch I was unable to find ALSAconf. Additionally I checked alsamixer and everthing is on.

When I run "lspci -v", the card is deteted as follows:

Code:

Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
Subsystem: Voyetra Technologies: Unknown device 3357
Flags: bus master, slow devsel, latency 32, IRQ 10
Memory at e3102000 (32-bit, non-prefetchable) [size=4K]
Memory at e3000000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [40] Power Management version 2

If I run "modinfo soundcore" I get the following:

Code:

filename: /lib/modules/2.6.11-1.1369_FC4/kernel/sound/soundcore.ko
description: Core sound module
author: Alan Cox
license: GPL
alias: char-major-14-*
vermagic: 2.6.11-1.1369_FC4 686 REGPARM 4KSTACKS gcc-4.0
depends:
srcversion: E11490DC3F523551C4C2A6D

This appears to be a generic module that may not be compatible[?].

Here's the output for "lsmod" (snd mods only):

Code:

snd_cs46xx             92969  1
gameport               18633  2 snd_cs46xx
snd_rawmidi            30305  1 snd_cs46xx
snd_ac97_codec         75961  1 snd_cs46xx
snd_seq_dummy           3653  0
snd_seq_oss            37057  0
snd_seq_midi_event      9153  1 snd_seq_oss
snd_seq                62289  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          8781  4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            51185  0
snd_mixer_oss          17857  2 snd_pcm_oss
snd_pcm               100169  3 snd_cs46xx,snd_ac97_codec,snd_pcm_oss
snd_timer              33605  2 snd_seq,snd_pcm
snd                    57157  10 snd_cs46xx,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              10913  2 snd
snd_page_alloc          9669  2 snd_cs46xx,snd_pcm

It appears to be loading the correct module, so I'm guessing this is a configuration issue[?]. Ironically this same h/w ran fine with R/H9[?].

Thanks for any input...

Simon Bridge · 09-04-2005, 02:45 AM

the alsa controls in FC4 seem to have slightly different names to those you see in many posts. do apropos alsa to see what I mean.

Code:

$ apropos alsa
aconnect             (1)  - ALSA sequencer connection manager
ainit                (8)  - configuration tool for ALSA
alsactl              (1)  - advanced controls for ALSA soundcard driver
alsamixer            (1)  - soundcard mixer for ALSA soundcard driver, with ncurses interface
amidi                (1)  - read from and write to ALSA RawMIDI ports
amixer               (1)  - command-line mixer for ALSA soundcard driver
aplay                (1)  - command-line sound recorder and player for ALSA soundcard driver
arecord [aplay]      (1)  - command-line sound recorder and player for ALSA soundcard driver
aseqdump             (1)  - show the events received at an ALSA sequencer port
aseqnet              (1)  - ALSA sequencer connectors over network
speaker-test         (1)  - command-line speaker test tone generator for ALSA

You have "set up a drive"? What does this mean? (Excuse me.)

Have you tried to auto-configure the sound card?
main > desktop > system settings > soundcard detection

Lnx805 · 09-04-2005, 02:45 PM

Hi Simon,
Here's my apropos alsa:

Code:

aconnect             (1)  - ALSA sequencer connection manager
ainit                (8)  - configuration tool for ALSA
alsactl              (1)  - advanced controls for ALSA soundcard driver
alsamixer            (1)  - soundcard mixer for ALSA soundcard driver, with ncur                               ses interface
amidi                (1)  - read from and write to ALSA RawMIDI ports
amixer               (1)  - command-line mixer for ALSA soundcard driver
aplay                (1)  - command-line sound recorder and player for ALSA soun                               dcard driver
arecord [aplay]      (1)  - command-line sound recorder and player for ALSA soun                               dcard driver
aseqdump             (1)  - show the events received at an ALSA sequencer port
aseqnet              (1)  - ALSA sequencer connectors over network
speaker-test         (1)  - command-line speaker test tone generator for ALSA

It looks similar...

re: setup; also means to install...

And, yes I have tried "Soundcard Detect". When I click test, nothing is heard. I've also tried different settings in the KDE "Control Center" and still get the "null" response. What's frustrating is this wasn't an issue with R/H9. I have R/H on another drive and when I boot up with that, the sound works fine.
I'm guessing it's just an "argument" [driver option] that needs to be tweaked. Where that config file can be found, is the question...

Thanks again...

Simon Bridge · 09-06-2005, 12:39 AM

[~]$ slocate alsa.conf
/etc/alsa/alsa.conf

There is always the possibility that FC4's alsa has remapped your jacks.
Try rerunning the autoconfigure script with the speaker-plug in different jacks.

Lnx805 · 09-09-2005, 12:03 AM

Update: I checked /etc/hotplug/blacklist and found my soundcard driver listed, [I don't know why it was listed?]. I removed it, rebooted and then soundcard detector - "test sound" worked!
I guess that corrected the argument issue...[?]

Thx again...

Simon Bridge · 09-09-2005, 10:46 PM

A driver suually gets blacklisted if some other is expected to bind to it and a conflict will arise otherwise. It seems you don't have the expected driver. However, if everything works OK for now I wouldn't worry about it. If you have sound trouble in future - like after an update - you mey need to re-blacklist that driver.

If I were you, I'd leave the driver line in the table only commented out - followed by a note to explain to your future self what you did

Lnx805 · 09-10-2005, 12:17 AM

Quote:

I'd leave the driver line in the table only commented out

Great idea... Thx again!