Hi again,
Does really nobody have an idea where that could come from.
Just what I guess it looks like someone holds a semaphore locked (does
this locking for registers happen inside of alsa?), maybe it does not
get released since the driver still stucks in initialisation. Could
that be?
Any ideas
Hi again,
well it seems this problem was either Fedora specific or has been
resolved in some later versions of alsa or what else cause these
troubles.
Ive just tried a 200mb live linux cd powered by linux 2.6.16 and
everything works as expected, how nice sound can be!!
thanks a lot, lg Clemens
2
Hello again,
Sorry for all the nerving reports and the generated traffic :-/
> Ive just tried a 200mb live linux cd powered by linux 2.6.16 and
> everything works as expected, how nice sound can be!!
Seems I've been euphoric, today I updates my Fedora-Core4 system via
yum with the latest availab
Hi again,
I was able to solve the problem, I thought it would maybe a good idea
to post it here if someone maybe search the archives in future having
the same problem.
In /etc/modprobe.conf the module for the sound-card was specified
"snd-intel8x0", however the right name is of the appropriate mo
On Wed, 2006-04-05 at 17:00 +0200, Clemens Eisserer wrote:
> Hi again,
>
> Does really nobody have an idea where that could come from.
> Just what I guess it looks like someone holds a semaphore locked (does
> this locking for registers happen inside of alsa?), maybe it does not
> get released sin
On Wed, 2006-04-05 at 17:00 +0200, Clemens Eisserer wrote:
> Hi again,
>
> Does really nobody have an idea where that could come from.
> Just what I guess it looks like someone holds a semaphore locked (does
> this locking for registers happen inside of alsa?), maybe it does not
> get released sin
Hi Lee,
> > Please try to identify the last kernel that worked. If all that was
> > changed was hardware, it could be a hardware problem.
>
> Argh, sorry for the double reply, my mailer crashed (again) while
> sending this...
No problem, just happy that you replied at all :-)
Ok, I'll try to dow
On Wed, 2006-04-05 at 13:46 -0400, Lee Revell wrote:
> Please try to identify the last kernel that worked. If all that was
> changed was hardware, it could be a hardware problem.
Argh, sorry for the double reply, my mailer crashed (again) while
sending this...
Lee
---
