Fedora Core 2 and audio

[Steve Cooke]

Hi,

I'm new to this list; not all that new to Linux though. I recently 
upgraded from RedHat 8 (Psyche?) to Fedora Core 2. Maybe I expected too 
much, but when I started up xmms there was no audio from the audio 
interface - I use headphones plugged into the headphone jack of the 
audio interface. Xmms worked out of the box on RedHat 8.

I poked around a bit and found that I might need something called ALSA. 
I found source for 'alsaplayer-0.99.76' compiled and tried to run it. It 
gives a 'Failed to load output plugin "alsa". Trying defaults.
zsh: segmentation fault  alsaplayer' error. I have no idea what an 
output plugin is, let alone an ALSA one.

I poked around some more and found an RPM that might do the trick called 
'alsaplayer-0.99.76-2.1.fc2.fr.i386.rpm' I downloaded that and tried 
installing it - only to find it had failed some dependency checks:
	libid3tag.so.0 is needed by alsaplayer-0.99.76-2.1.fc2.fr
	libmad.so.0 is needed by alsaplayer-0.99.76-2.1.fc2.fr
	libsndfile.so.1 is needed by alsaplayer-0.99.76-2.1.fc2.fr
	libsndfile.so.1(libsndfile.so.1.0) is needed by 
alsaplayer-0.99.76-2.1.fc2.fr
	libxosd.so.2 is needed by alsaplayer-0.99.76-2.1.fc2.fr
I'm lost. I have no idea what these are. If they were so important why 
weren't they part of the core install?

I then poked around some more and found something called 
'alsa-oss-1.0.5' You guessed it - I downloaded and tried to install it 
to no avail. the ./configure gave up the ghost complaining that - 
'checking for libasound headers version >= 0.9.0... not present.
configure: error: Sufficiently new version of libasound not found.' I 
assume this means I do not have a sufficiently new version of libasound 
installed. I looked around and downloaded 'alsa-lib-1.0.3a-2.i386.rpm,' 
compiled for Fedora Core 2, which I proceeded to install. The install 
told me 'package alsa-lib-1.0.3a-2 is already installed.'

To quote someone else on this list, 'WTF?' How hard is it to get sound 
working on a Linux machine? Any help would be very much appreciated.

(A very frustrated) Steve Cooke.

[Florin Andrei]

On Mon, 2004-06-28 at 16:48, Steve Cooke wrote:

>  I recently 
>  upgraded from RedHat 8 (Psyche?) to Fedora Core 2. Maybe I expected too 
>  much, but when I started up xmms there was no audio from the audio 
>  interface - I use headphones plugged into the headphone jack of the 
>  audio interface. Xmms worked out of the box on RedHat 8.
>  
>  I poked around a bit and found that I might need something called ALSA. 
>  I found source for 'alsaplayer-0.99.76' compiled and tried to run it. 
No, don't do that!!! :-)

Everything you need is included in the FC2 install kit. ALSA is the new
sound mega-driver that's included by default in the new linux-2.6 kernel
series.

Try and run the audio mixer and see if there are some channels muted by
default. Or fire up an xterm and run alsamixer in it (it's a different
kind of mixer, the ALSA native mixer), unmute the muted channels, wiggle
the volume levels up and down and see if that solves the problem.

>  I poked around some more and found an RPM that might do the trick
> called 
>  'alsaplayer-0.99.76-2.1.fc2.fr.i386.rpm' I downloaded that and tried 
>  installing it - only to find it had failed some dependency checks: 
Good! :-)

>  I then poked around some more and found something called 
>  'alsa-oss-1.0.5' You guessed it - I downloaded and tried to install it 
>  to no avail. the ./configure gave up the ghost complaining that -  
Good! :-)

>  installed. I looked around and downloaded
> 'alsa-lib-1.0.3a-2.i386.rpm,' 
>  compiled for Fedora Core 2, which I proceeded to install. The install 
>  told me 'package alsa-lib-1.0.3a-2 is already installed.' 
Good! :-)

I said "good" the first two times because you don't need that crap, and
in fact it might hurt if you install it.

Just install all ALSA-related packages from the FC2 install kit - that
should provide you with all the software you need. To do so, run:

yum install *alsa* system-config-soundcard

>  To quote someone else on this list, 'WTF?' How hard is it to
> get sound 
>  working on a Linux machine? Any help would be very much appreciated. 
Install the ALSA packages and the sound config utility. Then run the
sound config utility. Reboot.

If it still doesn't work, see the mixer tricks indicated above.

>  (A very frustrated) Steve Cooke. 
<shrug>

Tough it up, man, the sound infrastructure changed _a_lot_ since RH8,
some glitches with some systems are to be expected. You're just among
the unlucky few. But generally speaking, ALSA is a heck of a lot better
than OSS.

Once you figure out the problem, there are plenty of multimedia apps on
FreshRPMS:

http://freshrpms.net/packages/

Just add these three lines to /etc/yum.conf:

[freshrpms]
name=Fedora Linux $releasever - $basearch - freshrpms
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/fresh...

Then "yum install PackageName" will automagically install the
desired package for you. The packages on that site include:
- an XMMS version which can play MP3 files (the XMMS included
with FC2 cannot play MP3)
- Xine (a universal multimedia player)
- mozilla-totem (a multimedia plugin for Mozilla based on the
Xine engine)
- alsaplayer, if you really want it ;-)
- heaps and loads of other nice m/media things

If you want to prevent yum from using packages from FreshRPMS,
just comment out those 3 lines in yum.conf

Good luck,

-- 
Florin Andrei

http://florin.myip.org/

[Steve Cooke]

Hi,
Florin Andrei wrote:
>  On Mon, 2004-06-28 at 16:48, Steve Cooke wrote: 
>  Everything you need is included in the FC2 install kit. ALSA is the
> new
>  sound mega-driver that's included by default in the new linux-2.6 kernel
>  series.
>  
>  Try and run the audio mixer and see if there are some channels muted by
>  default. Or fire up an xterm and run alsamixer in it (it's a different
>  kind of mixer, the ALSA native mixer), unmute the muted channels, wiggle
>  the volume levels up and down and see if that solves the problem. 
Thanks very much. It all works beautifully now. One of your comments 
pointed to a possible clue - I ran system-config-soundcard and that 
seemed to do the trick.

I guess a possible followup question would be "is there a list of these 
system-config-... thingys somewhere?"

I tried to run yum but that failed also:
'Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
retrygrab() failed for:
 
http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/headers...
   Executing failover method
failover: out of servers to try
Error getting file 
http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/headers...
[Errno 4] IOError: <urlopen error >

I assume there is a config file somewhere that will allow me to set a 
proxy or some such. If I can get it running I may try the rest of your 
suggestions - the packages on FreshRPMS look rather interesting...

Thanks again for your help. My machine now feels complete!
Steve Cooke.

[Florin Andrei]

On Mon, 2004-06-28 at 18:33, Steve Cooke wrote:

>  I guess a possible followup question would be "is there a list
> of these 
>  system-config-... thingys somewhere?" 
Either look at the install CDs, or browse one of the on-line Fedora
repositories, or be lazy and pull a:

yum list system-config*

>  I tried to run yum but that failed also
>  I assume there is a config file somewhere that will allow me to set a 
>  proxy or some such. 
export http_proxy="http://your.proxy.here:8080"

(Replace proxy hostname and port with the proper settings on your
network.)

Then run yum.

To make this config bit permanent, create the file
/etc/profile.d/proxy.sh and put in it the "export" line i indicated
above. Logout/login and it should work.
Then all your command-line utilities (wget, links, etc.) should "see"
this proxy, not only yum.

The name of the file is not critical, just make sure it's in
/etc/profile.d and it has a .sh extension.

>  If I can get it running I may try the rest of your 
>  suggestions - the packages on FreshRPMS look rather interesting... 
You could install those packages manually, but yum makes the whole
process orders of magnitude simpler and faster.

>  Thanks again for your help. My machine now feels complete! 
Glad to hear that.

-- 
Florin Andrei

http://florin.myip.org/

DHCP and MySQL

[Alejandro Navarro]

Anyone knows where to find documentation that explains how to integrate the
DHCP with a MySQL data base?

The issue is that I have a work scenario with many users in multiples
subnets that take addresses from a DHCP server running FC2.

This is a managing problem because only the clients that are declared with
their respective MAC can receive an IP address. In a few words, the
dhcp.conf gets bigger every day and I have to edit a file text any time I
want to add a user.

Is there any way to force the DHCP service to not to read the dhcp.conf file
to authorize the leases, and instead to take the data base information
running in MySQL??? Something similar to mounting a Freeradius running
against a MySQL data base.

I hope my explanation was clear enough.

Regards

Alejandro

DHCP and MySQL

[Jason L Tibbitts III]

> >>>> "AN" == Alejandro Navarro
> <anavarro(a)dinanet.net.co&gt; writes: 
AN> Is there any way to force the DHCP service to not to read the
AN> dhcp.conf file to authorize the leases, and instead to take the
AN> data base information running in MySQL?

I think you'd have to do quite a bit of coding to make that work.
However, I do recall seeing patches to integrate ISC DHCPd and LDAP:

http://www.lunytune.net/isc-ldap.html
http://www.newwave.net/~masneyb/

(beware using any of the 3.0.1 release candidates before rc14).

 - J<

DHCP and MySQL

[Alejandro Navarro]

Ok i see this info but this have a problem for me .. Other daemon in the sky
(LDAP), i need basical DHCP and MySQL integration, but if not other way :-(
........


Regards

alejandro

-----Mensaje original-----
De: fedora-list-bounces(a)redhat.com [mailto:[e-mail]]
En nombre de Jason L Tibbitts III
Enviado el: Lunes, 28 de Junio de 2004 09:24 p.m.
Para: For users of Fedora Core releases
Asunto: Re: DHCP and MySQL

> >>>> "AN" == Alejandro Navarro
> <anavarro(a)dinanet.net.co&gt; writes: 
AN> Is there any way to force the DHCP service to not to read the 
AN> dhcp.conf file to authorize the leases, and instead to take the data 
AN> base information running in MySQL?

I think you'd have to do quite a bit of coding to make that work.
However, I do recall seeing patches to integrate ISC DHCPd and LDAP:

http://www.lunytune.net/isc-ldap.html
http://www.newwave.net/~masneyb/

(beware using any of the 3.0.1 release candidates before rc14).

 - J<


--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

DHCP and MySQL

[Jeff Vian]

On Mon, 2004-06-28 at 21:23, Jason L Tibbitts III wrote:
>  >>>>> "AN" == Alejandro Navarro
> <anavarro(a)dinanet.net.co&gt; writes:
>  
>  AN> Is there any way to force the DHCP service to not to read the
>  AN> dhcp.conf file to authorize the leases, and instead to take the
>  AN> data base information running in MySQL?
>   
One easy way would be to do an update to the mysql table, then have a
tag part of the script used to update the database with adds/deletes
that writes an updated dhcp.conf file from the new values in the
database.  this would basically automate it so you only have to poke the
values into the database and you would be done.


Although if you were to write a patch for dhcp to use an sql table of
some flavor it would likely be appreciated by many.
 
>  I think you'd have to do quite a bit of coding to make that
> work.
>  However, I do recall seeing patches to integrate ISC DHCPd and LDAP:
>  
>  http://www.lunytune.net/isc-ldap.html
>  http://www.newwave.net/~masneyb/
>  
>  (beware using any of the 3.0.1 release candidates before rc14).
>  
>   - J<
>

[Steve Cooke]

Florin Andrei wrote:
> >I tried to run yum but that failed also
> >I assume there is a config file somewhere that will allow me to set a 
> >proxy or some such.
>  
>  export http_proxy="http://your.proxy.here:8080"
>  Then run yum.
>   
Thank you once again.

Bloody hell!! Well, I did what you suggested I do to get yum to work, 
and ran 'yum list.' It must have downloaded 50 or more packages! It also 
told me that system-config-soundcard is installed (thank you yum - the 
fact that I used it before should have alerted me to the fact that it 
was installed!!) and that it is the latest version. I'll do as you say 
and avoid the alsaplayer.

BTW, is there a reason for the spurning of alsaplayer?

Regards,
Steve Cooke.

[Florin Andrei]

On Mon, 2004-06-28 at 22:31, Steve Cooke wrote:

>  Bloody hell!! Well, I did what you suggested I do to get yum to work,
>
>  and ran 'yum list.' It must have downloaded 50 or more packages! 
Well, first time you run it for each new site added to yum.conf
(including the default one that's already included) it will download a
ton of header files, which are not big, but are many. :-)
2rd time and next, it will only download new headers, which are much
fewer.

It will usually download/install a lot of packages first time you run
"yum update".

>  BTW, is there a reason for the spurning of alsaplayer? 
It's a fine player, but XMMS is more capable.

-- 
Florin Andrei

http://florin.myip.org/

[Gordon Keehn]

Steve Cooke wrote:
>  Hi,
>  Florin Andrei wrote:
>  
> > On Mon, 2004-06-28 at 16:48, Steve Cooke wrote:
>  
>  
> > Everything you need is included in the FC2 install kit. ALSA is the new
> > sound mega-driver that's included by default in the new linux-2.6 kernel
> > series.
> >
> > Try and run the audio mixer and see if there are some channels muted by
> > default. Or fire up an xterm and run alsamixer in it (it's a different
> > kind of mixer, the ALSA native mixer), unmute the muted channels, wiggle
> > the volume levels up and down and see if that solves the problem.
>  
>  
>  Thanks very much. It all works beautifully now. One of your comments 
>  pointed to a possible clue - I ran system-config-soundcard and that 
>  seemed to do the trick.
>   
    What do you do when system-config-soundcard tells you your CSC4232 
sound processor doesn't exist.  In the ooold days, sndconfig used to be 
able to find and configure it fine!
    Cheers,
Gordon Keehn

[Florin Andrei]

On Tue, 2004-06-29 at 12:59, Gordon Keehn wrote:

>  What do you do when system-config-soundcard tells you your CSC4232 
>  sound processor doesn't exist. 
1. File a bug report with bugzilla.redhat.com (BTW, Steve Cooke should
do that as well, since it's not ok for the installer to not be able to
configure the card properly, yet the config utility to work fine later
on)

2. All sound driver configuration is done in /etc/modprobe.conf - if you
set up that file correctly, sound should start to work.
Go to http://www.alsa-project.org/ and see in the documentation how to
configure /etc/modprobe.conf manually for your card.

BTW, is it CSC4232 or CS4232? The former does not match anything, the
latter matches Turtle Beach and Cirrus Logic stuff.

http://www.alsa-project.org/alsa-doc/index.php?vendor=All#matrix

Click on the Details link for the type of card that matches.

Or go to http://www.alsa-project.org/alsa-doc/ if you know the
manufacturer precisely and select it in the menu.

I would try this first:

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-cs4232
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

If nothing works, ask on the alsa-user mailing list.

-- 
Florin Andrei

http://florin.myip.org/

[Fritz Whittington]

On or about 2004-06-29 16:17, Florin Andrei whipped out a trusty #2 
pencil and scribbled:

> On Tue, 2004-06-29 at 12:59, Gordon Keehn wrote:
>
>   
>
> >What do you do when system-config-soundcard tells you your CSC4232 
> >sound processor doesn't exist.
> >    
> >
>
> BTW, is it CSC4232 or CS4232? The former does not match anything, the
> latter matches Turtle Beach and Cirrus Logic stuff.
>   
>  
Indeed, I just did a make menuconfig, and the CS4232 is NOT built-in NOR 
marked as a module.

-- 
Fritz Whittington
TI Alum - http://www.tialumni.org

[Gordon Keehn]

Florin Andrei wrote:

[Snip]

>  
>  BTW, is it CSC4232 or CS4232? The former does not match anything, the
>  latter matches Turtle Beach and Cirrus Logic stuff.
>   
    You may well be right.  The offending machine is at home, and (at 
the moment) I am not.  My original appending was based on hastily (and 
somewhat illegibly) scribbled notes, and is subject to some degree of 
interpretation.
    Cheers,
Gordon Keehn

[William Hooper]

Florin Andrei said:
>  On Tue, 2004-06-29 at 12:59, Gordon Keehn wrote:
>  
>  
> > What do you do when system-config-soundcard tells you your CSC4232
> > sound processor doesn't exist.
>  
>  1. File a bug report with bugzilla.redhat.com (BTW, Steve Cooke should
>  do that as well, since it's not ok for the installer to not be able to 
>  configure the card properly, yet the config utility to work fine later on) 
system-config-soundcard doesn't support ISA cards.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122838

-- 
William Hooper

[Steve Cooke]

Florin Andrei wrote:

>  1. File a bug report with bugzilla.redhat.com (BTW, Steve Cooke
> should
>  do that as well, since it's not ok for the installer to not be able to
>  configure the card properly, yet the config utility to work fine later
>  on) 
No, I won't do that. I have flagged the fact that I had a problem, and 
that it is now fixed. I now have no way to replicate the problem, short 
of doing a cleanskin install - which I, unfortunately, currently have no 
time for.

The second reason for not wishing to file a bug report is that I really 
don't know whether the problem was the result of my ignorance/ineptitude 
or a genuine problem. I fiddled with the alsamixer (as you suggested) 
and ran the soundcard config utility (as you also indicated may help) 
and either of those could have done the trick.

The third reason for me not filing a bug report is that I really do not 
believe it *that* important that sound works right out of the box. I 
don't know - is there a mini howto on this matter? Maybe that would be a 
better way to go, rather than hassling guys who are probably already 
flat out dealing with much more pressing issues than some ignoramus (me) 
complaining that the sound does not work. The fact that everything else 
worked first time is something that should be mentioned however - the 
guys involved with Fedora Core 2 distro have obviously gone out of their 
way to make it an almost no-brainer to install Linux.

Regards, and thanks again for the prompt help,
Steve Cooke.

[Gordon Keehn]

Steve Cooke wrote:

>  Florin Andrei wrote:
>  
>  (Among other things ...)
>  
>  The third reason for me not filing a bug report is that I really do not 
>  believe it *that* important that sound works right out of the box.  
Hey, guys
    If Linux is a private game for geeks with horn-rimmed glasses, 
shaggy beards, and hair on their palms, then that is an acceptable 
answer, but if Linux is EVER to be accepted popularly, that is the wrong 
way to go.  Especially with a sound chip that is found on a significant 
percentage of the older boxes that Linux gets installed on.
    Regardless of Windows' many faults and flaws, M'squat insures by 
bribery, intimidation, or whatever, that common hardware DOES work 
"right out of the box".  While I'm a newbie with Linux I do consider 
myself reasonably competent.  If, after scanning this forum, and the 
FAQs, and Google, I still can't get my sound card to work (or my USB Zip 
drive, but that's another issue), then it's time to hang it up.  I have 
a day job, a wife, and a few other things that take precedence over 
trying to force Linux to recognise a legacy sound chip.
    Cheers,
Gordon Keehn

[William Hooper]

Gordon Keehn said:
> > The third reason for me not filing a bug report is that I really
> do not
> >  believe it *that* important that sound works right out of the box.
>  
>  Hey, guys
>  If Linux is a private game for geeks with horn-rimmed glasses,
>  shaggy beards, and hair on their palms, then that is an acceptable answer,
>  but if Linux is EVER to be accepted popularly, that is the wrong way to
>  go.  Especially with a sound chip that is found on a significant 
>  percentage of the older boxes that Linux gets installed on. Regardless of
>  Windows' many faults and flaws, M'squat insures by
>  bribery, intimidation, or whatever, that common hardware DOES work "right
>  out of the box".   
Funny, I just installed WinXP on a Dell Optiplex GX260 and it didn't find the Video,
NIC, or Sound card.

No matter what OS you use there is always going to be some hardware that you have to do
work to install.

-- 
William Hooper

[Steve Cooke]

Gordon Keehn wrote:
>  Steve Cooke wrote:
>  
> > Florin Andrei wrote:
> >
> > (Among other things ...)
> >
> > The third reason for me not filing a bug report is that I really do 
> > not believe it *that* important that sound works right out of the box. 
>  
>  
>  Hey, guys
>     If Linux is a private game for geeks with horn-rimmed glasses, shaggy 
>  beards, and hair on their palms, then that is an acceptable answer, but 
>  if Linux is EVER to be accepted popularly, that is the wrong way to go.  
>  Especially with a sound chip that is found on a significant percentage 
>  of the older boxes that Linux gets installed on.
>     Regardless of Windows' many faults and flaws, M'squat insures by 
>  bribery, intimidation, or whatever, that common hardware DOES work 
>  "right out of the box".  While I'm a newbie with Linux I do consider 
>  myself reasonably competent.  If, after scanning this forum, and the 
>  FAQs, and Google, I still can't get my sound card to work (or my USB Zip 
>  drive, but that's another issue), then it's time to hang it up.  I have 
>  a day job, a wife, and a few other things that take precedence over 
>  trying to force Linux to recognise a legacy sound chip. 
I think you misunderstood my points, and you have also misrepresented 
what I said. Taken out of context, as you have chosen to do, it *does* 
look bad. What I said (among other things) is:

'The third reason for me not filing a bug report is that I really do not 
believe it *that* important that sound works right out of the box. I 
don't know - is there a mini howto on this matter? Maybe that would be a 
better way to go, rather than hassling guys who are probably already 
flat out dealing with much more pressing issues than some ignoramus (me) 
complaining that the sound does not work. The fact that everything else 
worked first time is something that should be mentioned however - the 
guys involved with Fedora Core 2 distro have obviously gone out of their 
way to make it an almost no-brainer to install Linux.'

I would prefer you not take what I have said out of context in order to 
make a point.

Secondly, my *main* point was that I do not know whether there was a 
problem with the Fedora distribution, or whether it was my 
ignorance/ineptitude, that caused the audio to 'not work.' Given that I 
am not in the position to try to replicate the problem, I will err on 
the side of caution and not file a defect report. That is, I am prepared 
to say that it was probably my fault rether than the Fedora distribution.

Steve Cooke.

[Rob Solomon]

> >>The third reason for me not filing a bug report is that I
> really do not 
> >>believe it *that* important that sound works right out of the box.
> >
> >Hey, guys
> >    If Linux is a private game for geeks with horn-rimmed glasses, shaggy 
> > beards, and hair on their palms, then that is an acceptable answer, but 
> > if Linux is EVER to be accepted popularly, that is the wrong way to go.
> >Especially with a sound chip that is found on a significant percentage of 
> >the older boxes that Linux gets installed on.
> >    Regardless of Windows' many faults and flaws, M'squat insures by 
> > bribery, intimidation, or whatever, that common hardware DOES work 
> > "right out of the box".  While I'm a newbie with Linux I do consider 
> > myself reasonably competent.  If, after scanning this forum, and the 
> > FAQs, and Google, I still can't get my sound card to work (or my USB Zip 
> > drive, but that's another issue), then it's time to hang it up.  I have 
> > a day job, a wife, and a few other things that take precedence over 
> > trying to force Linux to recognise a legacy sound chip.
>
> I think you misunderstood my points, and you have also misrepresented what 
> I said. Taken out of context, as you have chosen to do, it *does* look 
> bad. What I said (among other things) is:
>
> 'The third reason for me not filing a bug report is that I really do not 
> believe it *that* important that sound works right out of the box. I don't 
> know - is there a mini howto on this matter? Maybe that would be a better 
> way to go, rather than hassling guys who are probably already flat out 
> dealing with much more pressing issues than some ignoramus (me) 
> complaining that the sound does not work. The fact that everything else 
> worked first time is something that should be mentioned however - the guys 
> involved with Fedora Core 2 distro have obviously gone out of their way to 
> make it an almost no-brainer to install Linux.'
>
> I would prefer you not take what I have said out of context in order to 
> make a point.
>
> Secondly, my *main* point was that I do not know whether there was a 
> problem with the Fedora distribution, or whether it was my 
> ignorance/ineptitude, that caused the audio to 'not work.' Given that I am 
> not in the position to try to replicate the problem, I will err on the 
> side of caution and not file a defect report. That is, I am prepared to 
> say that it was probably my fault rether than the Fedora distribution.
>
> Steve Cooke. 
I am a newbie that can't get his soundcard to work.  It's an ancient 
Ensoniq Soundscape Elite that works in Win.  I think I agree there's a bug here

[Fritz Whittington]

On or about 2004-06-29 14:59, Gordon Keehn whipped out a trusty #2 
pencil and scribbled:

>  Steve Cooke wrote:
>
> > Hi,
> > Florin Andrei wrote:
> >
> >> On Mon, 2004-06-28 at 16:48, Steve Cooke wrote:
> >
> >
> >
> >> Everything you need is included in the FC2 install kit. ALSA is the new
> >> sound mega-driver that's included by default in the new linux-2.6 
> >> kernel
> >> series.
> >>
> >> Try and run the audio mixer and see if there are some channels muted by
> >> default. Or fire up an xterm and run alsamixer in it (it's a different
> >> kind of mixer, the ALSA native mixer), unmute the muted channels, 
> >> wiggle
> >> the volume levels up and down and see if that solves the problem.
> >
> >
> >
> > Thanks very much. It all works beautifully now. One of your comments 
> > pointed to a possible clue - I ran system-config-soundcard and that 
> > seemed to do the trick.
> >
>
>     What do you do when system-config-soundcard tells you your CSC4232 
>  sound processor doesn't exist.  In the ooold days, sndconfig used to 
>  be able to find and configure it fine!
>     Cheers,
>  Gordon Keehn
>
>  
You re-configure the kernel with the module for your CSC4232 card 
checked, and re-build it.  First, do the command "dmesg | less"  and 
look at the output.  A portion of mine is:

isapnp: Scanning for PnP cards...
pnp: SB audio device quirk - increasing port range
pnp: AWE32 quirk - adding two ports
isapnp: Card 'Creative SB AWE64  PnP'
isapnp: 1 Plug & Play card detected total

...so the system found my sound card hardware.   The problem is that the 
module that runs it was not compiled in the kernel as shipped.  (VERY 
anoying that nothing I could find told me that the module failed to 
load; all you get is the message that there is no sound hardware.....)  
What was more confusing is that every RH up through FC1 had the module, 
and everything worked fine.  But FC2 didn't.  Once I re-made the kernel, 
sound was just fine.

-- 
Fritz Whittington
TI Alum - http://www.tialumni.org