Re: FC5 Sound Problems - yes, I did search!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday 14 June 2006 19:42, Jeremy Thompson wrote:
> ALL,
>   Got FC5 up and running, no sound out of my speakers however.  I have
> checked all the sound configs I could find and nothing is muted.  I am
> using a SoundBlaster Audigy 2 to a Creative 6.1 Surround Sound System using
> 3 jacks.  I have checked sound levels though the gnome config options and
> they are all unmuted as well as 'alsamixer'.  In
> 'system-configure-soundcard' and default audio is set to 'Labs SB Audio',
> with a default PCM device of 'emu10k1'.
>
>   I google searched as well as searched through the archives and the
> nearest solution I could find was to try the how-to here -
>
> http://people.redhat.com/stransky/alsa/
>
>   However I just updated and am running a kernel of -
>
> ----
> [[email protected] ~]# uname -r
> 2.6.16-1.2133_FC5
> ----
>
> The only devel package I could find at -
>
> ----
> 5/ -> i386 -> os -> Fedora -> RPMS ->
> ----
>
> was -
>
> ----
> [ ]    kernel-devel-2.6.15-1.2054_FC..>
> [ ]    kernel-devel-2.6.15-1.2054_FC..>
> ----
>
> and I should use  - kernel-devel-2.6.16-1.2133_FC5.rpm.  Well.. google
> found nothing and neither did searching the rest of the downloads site.
>
> I am including commands I saw other emails ask for incase anyone can help.
>
> lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890
> South]
> 00:0a.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
> 00:0a.1 Input device controller: Creative Labs SB Audigy MIDI/Game port
> (rev 04)
> 00:0a.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev
> 04) 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
> Gigabit Ethernet (rev 10)
> 00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID
> Controller (rev 80)
> 00:0f.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1Controller (rev 81)
> 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1Controller (rev 81)
> 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1Controller (rev 81)
> 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
> 1.1Controller (rev 81)
> 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
> [KT600/K8T800/K8T890 South]
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc.
> VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Miscellaneous Control
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon
> 9600]
> 01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600]
> (Secondary)
>
>  lspci -n
> 00:00.0 0600: 1106:0282
> 00:00.1 0600: 1106:1282
> 00:00.2 0600: 1106:2282
> 00:00.3 0600: 1106:3282
> 00:00.4 0600: 1106:4282
> 00:00.7 0600: 1106:7282
> 00:01.0 0604: 1106:b188
> 00:0a.0 0401: 1102:0004 (rev 04)
> 00:0a.1 0980: 1102:7003 (rev 04)
> 00:0a.2 0c00: 1102:4001 (rev 04)
> 00:0d.0 0200: 10ec:8169 (rev 10)
> 00:0f.0 0101: 1106:3149 (rev 80)
> 00:0f.1 0101: 1106:0571 (rev 06)
> 00:10.0 0c03: 1106:3038 (rev 81)
> 00:10.1 0c03: 1106:3038 (rev 81)
> 00:10.2 0c03: 1106:3038 (rev 81)
> 00:10.3 0c03: 1106:3038 (rev 81)
> 00:10.4 0c03: 1106:3104 (rev 86)
> 00:11.0 0601: 1106:3227
> 00:11.5 0401: 1106:3059 (rev 60)
> 00:18.0 0600: 1022:1100
> 00:18.1 0600: 1022:1101
> 00:18.2 0600: 1022:1102
> 00:18.3 0600: 1022:1103
> 01:00.0 0300: 1002:4152
> 01:00.1 0380: 1002:4172
>
>   I am at my end and am extremely frustrated.  I want to leave windows
> behind, but this is killing my enthusiasm.

Hi Jeremy. I have an Audigy2 soundblaster PCI card. FC!,2,3,and 4 are working 
fine with it. FC5 is on the other machine with an Ensoniq card, but using 
your kernel Europes "Final Countdown" is banging out of my soundsystem at the 
mo.

The Alsamixer settings for the Audigy2 soundblaster card that I need for 
stereo output are. Master up, PCM up, Front up, and the 1st emu10k1 slider 
up. The "Audigy A" switch needs to be unmuted, or you won't get any sound. 
For playback of Audio CD's, "Audigy C" needs to be up.

I think there is a bit of special magic needed for 6.1 surround, but at least 
you should be getting output to 2 speakers.

There is an Alsa tool to check speakers. Just type on the CLI as user.
speaker-test --channels=6

Dont give up. You can post to, [email protected]  after 
subsribing to the list, if you are seriously stuck. This card does work ok, 
so perhaps it's just a config problem

The Alsa user mailing list is at.
https://lists.sourceforge.net/lists/listinfo/alsa-user

Just a few usefull commands.

To check if Alsa is running  (su to root on the CLI to run these)
/etc/rc.d/init.d/alsasound stop
then
/etc/rc.d/init.d/alsasound start

To verify the installed soundcard, and the alsa driver version
cat /proc/asound/cards
cat /proc/asound/version

To see which modules are loaded type.
/sbin/lsmod
All the Alsa ones are prefixed by "snd"

USB midi keyboards plugged in, and switched on were a problem with FC1, and 
FC2. The USB starts up early in the boot sequence and the keyboards/other 
none sound card midi devices were being detected as soundcards and set as 
card0. Consequently the real soundcard was being set as card1, resulting in 
no sounds. Since FC4 this problem seems to have been fixed, and I've had no 
problems. The real soundcard has been set as card0, and midi stuff on the USB 
as card 1.

See how that lot goes. Nigel.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux