From: Thomas Schuering <linux-dvb@ts4.de>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: alan@redhat.com, video4linux-list@redhat.com,
Nicholas Magers <Nicholas.Magers@lands.nsw.gov.au>,
LInux DVB <linux-dvb@linuxtv.org>,
Ben Caldwell <benny.caldwell@gmail.com>
Subject: Re: [linux-dvb] Dvico Dual 4 card not working.
Date: Wed, 2 Apr 2008 14:46:20 +0200 [thread overview]
Message-ID: <20080402124620.GA25986@ts4.de> (raw)
In-Reply-To: <37219a840804011319h6fa0d69elbf95b308236e2179@mail.gmail.com>
Hi Mike,
On Tue, Apr 01, 2008 at 04:19:45PM -0400, Michael Krufky wrote:
>
> Can you try using the v4l-dvb master branch hg repository on
> linuxtv.org again, after applying the attached patch (see below)
Let's see:
mv v4l-dvb v4l-dvb.old
hg clone http://linuxtv.org/hg/v4l-dvb/
cd v4l-dvb
patch -p1 < xc-instance.patch
make
make install
sync
shutdown -r
> Please let me know if this fixes the problem, and I'll produce a new
> patch afterwards.
I don't know what problem you're refering to - the machine comes up
successfully, but you can't use the card.
I used 'scan' for testing what gives an entry in /var/log/kern.log:
xc2028 0-0061: Loading 3 firmware images from xc3028-dvico-au-01.fw, type: DViCO DualDig4/Nano2 (Australia), ver 2.7
Then the process 'kdvb-fe-0' eats up 100% CPU-time,
the keyboard is dead. The machine hangs.
Hope this helps.
Regards, Thomas
os: Ubuntu 7.10
Linux tronn 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64 GNU/Linux
DViCO DualDig4 rev. 1.0
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-04-02 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 2:31 Dvico Dual 4 card not working Nicholas Magers
2008-04-01 15:41 ` Ben Caldwell
2008-04-01 20:19 ` Michael Krufky
2008-04-02 12:46 ` Thomas Schuering [this message]
2008-04-02 15:20 ` [linux-dvb] " Ben Caldwell
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=20080402124620.GA25986@ts4.de \
--to=linux-dvb@ts4.de \
--cc=Nicholas.Magers@lands.nsw.gov.au \
--cc=alan@redhat.com \
--cc=benny.caldwell@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=mkrufky@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox