From: Marios Andreopoulos <opensource@andmarios.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] KWORLD 323U, kernel panic when trying to access ALSA interface
Date: Wed, 4 Nov 2009 20:33:48 +0200 [thread overview]
Message-ID: <200911042033.48257.opensource@andmarios.com> (raw)
In-Reply-To: <829197380910150853l6797a053qd2d9e05ec3b7552e@mail.gmail.com>
Just a small update.
After this message of yours: http://www.linuxtv.org/pipermail/linux-dvb/2009-October/032442.html
I tried again the v4l-dvb tree and now my card works without problems!
I don’t know what the problem was with your tree. I think another tree I had used previously copied it’s modules to a non standard location in /lib/modules/current-kernel/ and thus its modules took precedence over the kernels’, yours’ or v4l-dvb’s modules.
It just happened that I upgraded my kernel recently and found out that v4l-dvb works now.
Thanks!
On Thursday 15 of October 2009, you Devin Heitmueller wrote:
>
> Hello Marios,
>
> Sorry about the extended delay on this. Please try out the following
> tree and see if you still hit a panic:
>
> http://www.kernellabs.com/hg/~dheitmueller/em28xx-audio-panic
>
> Cheers,
>
> Devin
>
>
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2009-11-04 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 15:50 [linux-dvb] KWORLD 323U, kernel panic when trying to access ALSA interface Marios Andreopoulos
2009-09-28 15:56 ` Devin Heitmueller
2009-09-28 16:09 ` Marios Andreopoulos
2009-10-15 15:53 ` Devin Heitmueller
2009-10-15 17:23 ` Marios Andreopoulos
2009-11-04 18:33 ` Marios Andreopoulos [this message]
2009-11-04 18:42 ` Devin Heitmueller
2009-09-28 16:19 ` Marios Andreopoulos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200911042033.48257.opensource@andmarios.com \
--to=opensource@andmarios.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.