matter what I do to "/etc/modprobe.conf" or how many times I run
"alsaconf". I've made sure my soundcard isn't muted and "lsmod"
shows all the proper drivers are loaded proving "hotplug" has found
"snd_emu10k1". Tools like "aplay" _look_ like they're working but
just don't ... mmmm ... sound that way.
Has anyone else run into this problem? Any suggestions for what I
might be missing?
Thanks ahead of time.
-------------------------------------------------------------------
Hi. I got an audigy 2 value which uses the same driver. Currently I'm using my own kernel and I don't have any problems. If I remember correctly I had issue when I upgraded to 2.6.13rc1. I had to play with the setting currently what turn of my audio know in alsa is Audigy Analog/Digital Output Jack. And then I always have Analog Mix all the way up. Hopefully that works if it doesn't I would just such trying different combos in alsa mixer.
On 10/10/05, Don Melton <[EMAIL PROTECTED]> wrote:
Sound is still dead for me after the upgrade to kernel 2.6.13 no
matter what I do to "/etc/modprobe.conf" or how many times I run
"alsaconf". I've made sure my soundcard isn't muted and "lsmod"
shows all the proper drivers are loaded proving "hotplug" has found
"snd_emu10k1". Tools like "aplay" _look_ like they're working but
just don't ... mmmm ... sound that way.
Has anyone else run into this problem? Any suggestions for what I
might be missing?
Thanks ahead of time.
--
Don
On Oct 1, 2005, at 11:55 PM, Tobias Powalowski wrote:
> Hi due to the monster upgrade in the last hours be prepared for
> some things:
>
> Remember this points:
> devfs is removed from kernel26, get ready for udev.
> the /dev/discs entries will not work anymore on boot prompt. Please
> change it
> according to kernel26 install message.
>
> Sound issues:
> 2.6.13 introduces a new alsa update. If you have sound problems,
> please remove
> your alsa entries from /etc/modprobe.conf and rerun alsaconf.
>
> If your system hangs on boot after upgrade on loading modules
> (perhaps you use
> hotplug or lshwd), try to use "init s" on boot prompt to be able to
> repair
> your rc.conf and or modprobe.conf.
>
> Please be patient until the mirrors are fully synced.
> Today is bugsquashing day so join #arch-bugs, to help us to find/
> solve issues.
>
> greetings
> tpowa
> --
> Tobias Powalowski
> Archlinux Package Maintainer (tpowa)
> http://www.archlinux.org
> [EMAIL PROTECTED]
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
--
Matthew G.
Website http://msg43.homeip.net
AIM: msg431 MSN: [EMAIL PROTECTED] GTalk: [EMAIL PROTECTED]
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
