Hi all,
I just got myself a Nova-TD stick and plugged it in to one of my MythTV
boxes just for the fun of it ;). I've noted on the linuxtv.org web that
there is currently no support for this DVB stick. Is there any way I can
help out with that? I'd consider myself a decent programmer (although I
I have posted twice, with no appearance in the list, a message about
remote control errors (tons of them in syslog!). I saw that you made a
commit in your tree about remote control stuff. Is that related? I'll
try a new build tonight.
If the sample below is what your remote control errors in
I'll try to test it also. Is there any possibility that this patch
gets included into main HG repository?
I guess we will have to wait until Patrick comes back from his vacation.
I would *not* recommend committing the patch to the HG repo.
I consider it an ugly fix that doesn't take care
1) system (uname -a)
Linux ragnyr.garth.anden.nu 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007
i686 i686 i386 GNU/Linux
2) lspci-output
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub
(rev 02)
00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express
Can I ask you a few questions about the TD stick,
1. How is reception compared to the nova-t 500
I think it is pretty similar, though I don't have any exact numbers to
give you at this time. I'm going to do an overhaul of my cabling (with a
better quality amplifier and splitter); I've got a
I have a strange problem with my Nova-TD Stick (USB ID 2040:9580).
A couple of months ago, I rebuilt my antenna setup and replaced all the
cables, the amplifier and splitter by high-quality versions, and since
then all the other cards (one Nova-T 500 and one Nova-T Stick) have
gotten much
I have just built and started using the new HG, the unknown code problem
with the remote support in my stick flooding /var/log/messages was a pain,
but that was solved by simply wrapping the sensors in LX tape to prevent
it receiving codes ;)
If you're not going to use the sensor, disable the
If you're not going to use the sensor, disable the RC polling by
adding the following line to your modprobe.conf:
options dvb_usb disable_rc_polling=1
That's a cleaner solution in my opinion.
That one is for the wiki.
Is there a place/file describing all those options?
Not
On Wed, 2008-01-30 at 17:05 +0100, Patrick Boettcher wrote:
On Wed, 30 Jan 2008, Jonas Anden wrote:
If you're not going to use the sensor, disable the RC polling by
adding the following line to your modprobe.conf:
options dvb_usb disable_rc_polling=1
That's a cleaner
I have a hunch about this problem...
I had this problem (I tink 3 times last weekend) after initially
updating my hg tree and recompiling the modules. I then turned on full
debugging for the dib0700 module in order to try to see what happens
when it goes wrong, but with full debugging on I
Hi all,
I have a hunch about this problem...
...
This, ... leads me to believe that this is timer-induced. Something
can't keep up. Adding debugging makes the operations slightly slower
(the module needs to do additional IO to speak to syslogd), and this
delay seems to be enough to keep it
Hmm... typical, isn't it? Just about ten minutes after I've sent out the
patch, the second tuner died again. It appears this is *not* enough to
fix the issue. Please discard the previous mail.
// J
On Mon, 2008-02-04 at 19:28 +0100, Jonas Anden wrote:
Hi all,
I have a hunch about
Not too much comfort, but...
Maybe a different problem, but the tuner is really lost until a reboot
all the same.
You don't need to reboot to regain the other tuner. I use the following:
service mythbackend stop
modprobe -r dvb_usb_dib0700
modprobe dvb_usb_dib0700
service mythbackend start
In any case, especially to that problem with unknown key code I think it
is time to change the IR-behavior of the DVB-USB.
My problem is, I don't know how.
My naive idea would be, that the IR-code is reporting each key (as raw as
possible) without mapping it to an event to the event
Wouldn't going away from an event interface kill a possible direct link
between the remote and X?
Yes, it would.
The way I see it, LIRC is an additional layer that may be one too many
in most cases. From my point of view, it is a relative pain I could do
without. But I may have tunnel
The strange thing is that modinfo does not say anything about a level 15
debug for the dvb_usb_dib0700 module.
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700
The debug value is a bit field, with each bit representing a different
category. With all bits on (ie
16 matches
Mail list logo
