A sound problem one more time.- THE SOLUTION AT LAST (PLEASE NOTE)
Mikael Larsson
mikael.larsson at bredband.net
Thu Feb 14 19:07:06 UTC 2008
Hello
I don't think the 'enable: N' is whats messing snd-hda-intel up.
I tried to run the alsa-info.sh script on my computer wish have two
kernels, one where snd-hda-intel works and one where it dosen't.
They both reported 'enable: N'.
The only difference I could se was that the working kernel also loaded
the snd_seq_dummy module, so I tried to load that manualy on the none
working one but with no luck.
This is the output from the working 2.6.23.9-85.fc8 kernel:
http://pastebin.ca/904073
This is the output from the none working 2.6.23.15-137.fc8 kernel:
http://pastebin.ca/904084
tor 2008-02-14 klockan 12:01 -0500 skrev Mark C. Allman:
> On Wed, 2008-02-13 at 22:43 +0100, Nigel Henry wrote:
> > On Wednesday 13 February 2008 21:34, Frank Chiulli wrote:
> > > On Feb 13, 2008 10:09 AM, Nigel Henry <cave.dnb2m97pp at aliceadsl.fr> wrote:
> > > > On Wednesday 13 February 2008 15:58, Aaron Konstam wrote:
> > > > > On Tue, 2008-02-12 at 21:07 -0800, Frank Chiulli wrote:
> > > > > > On Feb 12, 2008 1:17 PM, Aaron Konstam <akonstam at sbcglobal.net> wrote:
> > > > > > > I got no answer to my question about sound in f8 working only as
> > > > > > > root, so let me ask the question a different way.
> > > > > > >
> > > > > > > This could only happen if some vital component in processing sound
> > > > > > > has the wrong permissions. Could any one suggest what that
> > > > > > > component could be? This is very frustrating.
> > > > > > > --
> > > > > > > ===================================================================
> > > > > > >==== To the systems programmer, users and applications serve only to
> > > > > > > provide a test load.
> > > > > > > ===================================================================
> > > > > > >==== Aaron Konstam telephone: (210) 656-0355 e-mail:
> > > > > > > akonstam at sbcglobal.net
> > > > > > >
> > > > > > > --
> > > > > > > fedora-list mailing list
> > > > > > > fedora-list at redhat.com
> > > > > > > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> > > > > >
> > > > > > Aaron,
> > > > > > I had the same problem. But I was also getting a startup message
> > > > > > about a syntax error in
> > > > > > /etc/security/console.perms.d/50-default.perms on line 19 at 0600.
> > > > > > The error was a right paren instead of a greater than: <sound)
> > > > > > <sound>
> > > > > >
> > > > > > Once I corrected that sound worked just fine.
> > > > > >
> > > > > > Frankt
> > > > >
> > > > > Your a genius. Or at least you had the critical piece of information.
> > > > > My /etc/security/console.perms.d/50-default.perms had no sound clauses
> > > > > at all. It had no cdrom clauses either. Once that correction was made
> > > > > sound works. I will have to remember to check that in the future.
> > > > >
> > > > >
> > > > > But how could that have happened. I assume it was related to the system
> > > > > not recognizing the sound card.
> > > >
> > > > Hi Aaron. I'm glad you have the problem resolved. I'd had a look in my
> > > > F8's /etc/security/console.perms.d/50-default.perms, after seeing Franks
> > > > post, and it's as below.
> > > >
> > > > # device classes -- these are shell-style globs
> > > > <pilot>=/dev/pilot
> > > > <scanner>=/dev/scanner* /dev/usb/scanner*
> > > > <rio500>=/dev/usb/rio500
> > > > <fb>=/dev/fb /dev/fb[0-9]* \
> > > > /dev/fb/*
> > > > <kbd>=/dev/kbd
> > > > <joystick>=/dev/js[0-9]*
> > > > <gpm>=/dev/gpmctl
> > > > <dri>=/dev/nvidia* /dev/3dfx* /dev/dri/card*
> > > > <mainboard>=/dev/apm_bios
> > > > <pmu>=/dev/pmu
> > > > <bluetooth>=/dev/rfcomm*
> > > > <irda>=/dev/ircomm*
> > > > <dvb>=/dev/dvb/adapter*/*
> > > >
> > > > # permission definitions
> > > > <console> 0600 <pilot> 0660 root.uucp
> > > > <console> 0660 <scanner> 0660 root.lp
> > > > <console> 0600 <fb> 0600 root
> > > > <console> 0600 <kbd> 0600 root
> > > > <console> 0600 <joystick> 0600 root
> > > > <console> 0700 <gpm> 0700 root
> > > > <console> 0600 <mainboard> 0600 root
> > > > <console> 0600 <rio500> 0600 root
> > > > <console> 0600 <pmu> 0600 root
> > > > <console> 0600 <bluetooth> 0600 root
> > > > <console> 0600 <irda> 0600 root
> > > > <console> 0600 <dvb> 0600 root
> > > >
> > > > <xconsole> 0600 /dev/console 0600 root.root
> > > > <console> 0600 <dri> 0600 root
> > > >
> > > > As you can see there are no sound, or cdrom clauses, and the fresh
> > > > install of F8 picked up the soundcard (audigy2 soundblaster) ok. Apart
> > > > from disabling the infamous pulseaudio, the only other thing necessary
> > > > was to add alias, and options lines for snd-usb-audio in
> > > > /etc/modprobe.conf, so that my usb midi keyboard didn't end up in the
> > > > card0 position.
> > > >
> > > > It would be nice to know which soundcard Frank Chiulli has on his
> > > > machine, that gave a similar problem to you, and if the soundcard was
> > > > picked up automatically when he did the install, or whether he had to run
> > > > system-config-soundcard to configure the card, and only after doing that,
> > > > discovered the badline in /etc/security/console.perms.d/50-default.perms.
> > > >
> > > > Aaron. Do you still have to add a "modprobe snd-cs4236" line in
> > > > /etc/rc.local in F8, as you had to do since FC6, as per your earlier
> > > > post?
> > > >
> > > > I wonder if this is a kernel, or Alsa related problem, as you said it
> > > > wasn't limited to Fedora 6 onwards, but also on Ubuntu 6.06, 7.2, and
> > > > 7.10, therefore the problem with snd-cs4236 does not, on the face of it
> > > > appear to be distro specific. By the way, and IIRC, I thought I read
> > > > somewhere that support for isa soundcards was not as it used to be.
> > > >
> > > > Would you download this script, as below, run it, and post the link to
> > > > pastebin back. It may well provide some usefull info about your machine,
> > > > soundcard, etc.
> > > >
> > > > http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh
> > > >
> > > > It may be usefull to the Alsa development folks, and I'll post the
> > > > pastebin link there, with all the relevant details regarding your isa
> > > > soundcard, and what is necessary to get it to work.
> > > >
> > > > Nice to have the sounds working again eh!
> > > >
> > > > All the best.
> > > >
> > > > Nigel.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > fedora-list mailing list
> > > > fedora-list at redhat.com
> > > > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> > >
> > > 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.
> >
> 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 at 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
> -- Allman Professional Consulting, Inc.
> -- www.allmanpc.com, 617-947-4263
>
> BusinessMsg -- the secure, managed, J2EE/AJAX Enterprise IM/IC solution
>
>
>
>
More information about the fedora-list
mailing list