FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i updated my FC4 to FC5 with yum, and after i have problem with audio.
My kernel is 2.6.16-1.2080_FC5.
In /log/messages i found following:
Apr 8 14:24:09 pelikan kernel: cx2388x alsa driver version 0.0.5 loaded
Apr 8 14:24:09 pelikan kernel: ACPI: PCI Interrupt 0000:00:0a.1[A] -> GSI 17 (level, low) -> IRQ 18
Apr 8 14:24:09 pelikan kernel: cx88/1: CX88x/0: ALSA support for cx2388x boards
Apr 8 14:24:09 pelikan kernel: cannot find the slot for index 0 (range 0-0)
Apr 8 14:24:09 pelikan kernel: VIA 82xx Audio: probe of 0000:00:11.5 failed with error -12
I dont know what to do, is anybody who knows where is the problem?
Please help me.
------- System Config Soundcard --------
Sat Apr 8 13:06:02 CEST 2006
------- lspci --------
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0a.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
00:0a.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
Ran into similar problem - although mine was intermittent (sometimes the system boots OK; other times, it reports "VIA 82xx Audio: probe of 0000:00:11.5 failed with error -12" in /var/log/messages. Found relief from info in ALSA-Configuration.txt of the alsa-driver-1.0.13.tar.bz2 distribution, under the heading "Module Autoloading Support". Added the following lines in /etc/modprobe.d/alsa.conf:
# ALSA portion
options snd cards_limit=2
alias snd-card-0 snd-via82xx
alias snd-card-1 cx88-alsa
options snd-via82xx index=0
options cx88-alsa index=1
# OSS/Free portion
alias sound-slot-0 snd-via82xx
alias sound-slot-1 cx88-alsa
That seemed to fix the problem for me. Hope this helps with yours.
Note, my configuration:
Linux xyz.lan 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 athlon i386 GNU/Linux
AMD Athlon(TM) XP 2500+,
------- /proc/asound/version --------
Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 2006 UTC).
I am running into the same problem myself. Mine, too, is intermittent. The situation with me is that I have a dual-boot system with Microsoft Windows (for work) and Fedora 7 (for personal). What I have noticed, tonight, is that if I boot into Windows first, do my thing there, and then boot into Fedora 7, my Sound Blaster Live! 5.1 sound card does not work in Linux. However, if I just turn my computer off and turn it back on after 30 seconds, and boot into Fedora 7, the sound card works. I do not understand why this is the case... the only logical thing I can think of is an address problem that remains in memory when booting from Windows to Linux (probably not a good conclusion, but it is the only thing I can think of as to why this is happening). I know that it has something to do with my TV card (MSI TV@nyware) because when I took it out, my sound card works just fine.
PuffServe gave me an idea where to look for settings; the problem is that the file no longer is in Fedora 7. However, I modified the /etc/modprobe.conf file and moved my sound card up. This modification made my sound card the default card. (I also have a [built-in the motherboard] VIA sound card in there and it is disabled in the BIOS, but Fedora 7 [oddly] still sees it.)
Also, there is this post on FedoraForum that points out the same issue as we are having. One guy even mentions this:
And this is something new with FC5. Never had any problems with FC4. This box also has SUSE 10.0 and Mandriva 2005 LE on it. No problems there either.
I personally love using Fedora (based on my personal experience and tastes, Fedora has been the best distribution for me, [looking forward to Fedora 8]), and I would hate to change over to a new distribution just to get something to work. I will try other distributions and see what happens. I have already tried OpenSUSE and I am not a fan of how it handles software management (same thing with Ubuntu). I'll give Mandriva a shot and see what happens.