All of lore.kernel.org
 help / color / mirror / Atom feed
From: "sonofzev@iinet.net.au" <sonofzev@iinet.net.au>
To: linux-media@vger.kernel.org,
	"'sonofzev @ iinet . net . au'" <sonofzev@iinet.net.au>
Subject: Re: Fwd: [linux-dvb] dvico dual express continuuing issues.
Date: Mon, 16 Feb 2009 20:51:03 +0900	[thread overview]
Message-ID: <50636.1234785063@iinet.net.au> (raw)


>
>Hi All 
>
>In december I posted a message regarding some issues with the dvico driver.
>
>http://www.linuxtv.org/pipermail/linux-dvb/2008-December/031137.html
>
>The kernel is reporting incorrect callback of the firmware. Also, if the tuner
>isn't being used for a few hours, I then get errors from mythtv about it not
>being able to contact the backend and only rebooting the system will fix the
>problem (restarting mythbackend and frontend does not help).
>
>I eventually reported this as fixed to do with bios settings but I was wrong.
>
>I have done alot more testing and have found that it seems to be only after
>mythtv has accessed the device where this problem beings begins... 
>
>I will try the latest hg version and see what happens. I will also try another tv
>application and see if that makes a difference (but I really would like to
>continue using mythtv as I have 2 other frontends). 
>
>More information.. (and questions). 
>I know I definitely didn't have this problem with earlier versions of the driver
>(roughly pre September.. Chris Pascoe's original version actually seemed more
>stable although didn't report correct signal strength) 
>The cpu is a an opteron 170 
>2GB of OCZ DDR500 RAM (clocked at standard 400 of course, not overclocking this
>thing actually unless watching HD it is usually sitting at 1000MHZ)
>Nvidia 7600 GS video card (as I read horrible things about my onboard ATI
>chipset) using nvidia drivers not using xvmc however. 
>I have eliminated the motherboard as since I originally reported the issue I have
>changed mobo (from nvidia nforce4 chipset to ati chipset.... primarily to get a
>micro atx mobo for my HTPC case). 
>Fairly standard kernel with pre-emption (should I be using an rt patched kernel??)
>Are there any other kernel options I should remove or add??? 
>I am using the most recent unstable Gentoo release of mythtv (0.21_p19046) but
>saw the same problem on the most recent stable release too. 
>Are there any compile time options (or USE flags) I need to set or unset??
>The system also houses my third tuner/second card, a dvico fusion lite (older pci
>version rock solid stable).. Are there any modules.conf settings I need to look
>out for (although it worked before ...).... 
>
>As I said, I will try out the latest hg version tonight.. but any advice would be
>appreciated greatly!!!
>
>cheers
>
>Allan 
>

Same result with the hg version updated tonight. 

I haven't had a chance to use another tv app yet as we are currently watching TV. 

I will send a further update later. 

             reply	other threads:[~2009-02-16 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 11:51 sonofzev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-16  5:21 Fwd: [linux-dvb] dvico dual express continuuing issues sonofzev

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=50636.1234785063@iinet.net.au \
    --to=sonofzev@iinet.net.au \
    --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.