LinuxMCE Forums
General => Users => Topic started by: Crawtech on June 24, 2008, 02:04:48 am
-
Hi all
I am having some problems with my setup up i have a Hauppauge Wintv-Nova-T-500 install and i am using Mythtv all works fine most of the time but probably once a day i get no signal strength and myth can't get a channel lock
Now if i do a quick reload router all is fine again till next time which could be 1 day or two days but it will do it again
I have made some changes to /etc/modprobe/options this is what i have added
options dvb-usb-dib0700 force_lna_activation=1 (this option turns the LNA on)
options usbcore autosuspend=-1 (this option stops the card from going into standby)
Any help would be nice as this problem has been driving me mad
-
I have the same problem (with Mythtv and VDR).
I've just find some solution for testing on the ubuntu and mythubuntu forum:
1. EIT scanning disabled
2. usbcore autosuspend = -1
3. disable remote polling
4. 200ms tuning delay.
I use VDR for the moment and have to switch again on Mythtv to test those.
-
Hi pga57
thanks i will try it as well and let you know how i get on :)
-
Hi Hgait,
I have switch again on Mythtv and use:
"usbcore autosuspend = -1" in /etc/modprobe.d/options
and
100ms tuning delay for each capture card.
For the moment all is ok !!!
Philippe
-
Hi
I am still having problems it is like the options usbcore autosuspend=-1 has stoped working and the card is going to sleep after sometime
-
Hi Hgait,
You're right. After a few days, i get again a no signal strength and myth can't get a channel lock. :-(
If you find something....
Philippe
-
I'm having the same problem! Did either of you guys find a solution? I'm using the Hauppauge Nova-T-500.
As you say, can't get a channel lock after a day so, with everything else working fine. I then need to reset the core.
And there doesn't seem to be any pattern to it!!
-
I'm having the same problem! Did either of you guys find a solution? I'm using the Hauppauge Nova-T-500.
As you say, can't get a channel lock after a day so, with everything else working fine. I then need to reset the core.
And there doesn't seem to be any pattern to it!!
Here my capturecard setup:
INSERT INTO `capturecard` (`cardid`, `videodevice`, `audiodevice`, `vbidevice`, `cardtype`, `defaultinput`, `audioratelimit`, `hostname`, `dvb_swfilter`, `dvb_recordts`, `dvb_sat_type`, `dvb_wait_for_seqstart`, `skipbtaudio`, `dvb_on_demand`, `dvb_diseqc_type`, `firewire_port`, `firewire_node`, `firewire_speed`, `firewire_model`, `firewire_connection`, `dvb_hw_decoder`, `dbox2_port`, `dbox2_httpport`, `dbox2_host`, `signal_timeout`, `channel_timeout`, `parentid`, `dvb_tuning_delay`, `contrast`, `brightness`, `colour`, `hue`, `diseqcid`) VALUES
(1, '0', '', '', 'DVB', 'DVBInput', NULL, 'dcerouter', 0, 1, 0, 1, 0, 1, NULL, 0, 2, 0, NULL, 0, 0, 31338, 80, NULL, 500, 3000, 0, 0, 0, 0, 0, 0, 0),
(2, '1', '', '', 'DVB', 'DVBInput', NULL, 'dcerouter', 0, 1, 0, 1, 0, 1, NULL, 0, 2, 0, NULL, 0, 0, 31338, 80, NULL, 500, 3000, 0, 150, 0, 0, 0, 0, 0);
It work for about july 2008 !
Philippe
-
Hi Philippe,
Thanks for your reply, great to hear you have a solution.
Could you please explain in slightly more detail what I need to do exactly? I am no expert with LinuxMCE! I'm assuming I have to insert that code in somewhere? Thank you!
-
Hi Purps,
Hi Philippe,
Thanks for your reply, great to hear you have a solution.
Could you please explain in slightly more detail what I need to do exactly? I am no expert with LinuxMCE! I'm assuming I have to insert that code in somewhere? Thank you!
I send you the database content of my capturecard table, but it is not enought.
Here the entiere solution I find on some forums and I use on my config. Yesterday I was not on my computer and forgot some things.
It is not my redaction, I'm french and my english is to poor ! ;-)
----------------------------------------
# solution 3:
There is a bug somewhere. Probably in the driver or the card’s firmware. The result is that a tuner stops. The main issue is that it stops silently, and MythTV continues to use it as if it was fine. You end up with recorded programs of zero length.
I stabilized the system and went around this by doing three things:
* I told MythTV to be less aggressive when tuning a channel and take more time to do it
* I told MythTV to release the tuners when it does not use them
* I told MythTV to gather EPG data using EIT only on the first tuner
Here is how to do this:
1. Go to the MythTV backend setup and edit the capture cards:
1. mythtv-setup main screen
2. Select the first tuner:
2. Capture cards list
3. Then edit the Recording Options:
3. Card 0 settings
4. Make sure that:
* Open DVB card on demand is selected
* Use DVB card for active EIT scan is selected
* you have increased the DVB tuning delay (I used 150 ms)
4. Card 0 recording options
5. Finish, then edit the second tuner:
2. Capture cards list
6. Then edit the Recording Options:
5. Card 1 settings
7. Make sure that:
* Open DVB card on demand is selected
* Use DVB card for active EIT scan is not selected
* you have increased the DVB tuning delay (I used 150 ms)
6. Card 1 recording options
8. Finish. Escape, Escape, etc… to get out of the setup.
I have not been losing any tuner or any recording since I’ve done that.
----------------------------------------
Voilà !
I expect now that you can resolve your problem.
A bientôt !
Philippe
-
Merci beaucoup! :-) I will try this later, will let you know how I get on!
Thanks again.
Purps.
-
purps.
I'm having the same problem! Did either of you guys find a solution? I'm using the Hauppauge Nova-T-500.
As you say, can't get a channel lock after a day so, with everything else working fine. I then need to reset the core.
And there doesn't seem to be any pattern to it!!
Itś the famous "usb dicsonnect" issue you have.
Look in dmesg and you probably see a lot of usb errors.
There is no real fix for this issue with this particular card at the moment.
Several patches claim to solve the problem but the do not.
/niz23
-
But I'm not using a USB card, it's a PCI one - does the issue remain the same?
-
Btw, unlike the other two chaps, "quick reload router" doesn't appear to fix it - I have to do a proper restart of the core. Just though I'd add that in case it's relevant.
-
But I'm not using a USB card, it's a PCI one - does the issue remain the same?
Well actually the T500 has an onboard USB hub that connects both of the tuners back to the PCI bus... so that is why its affected by the usb disconnect problem.
Andrew
-
So what would be a recommended alternative to this Dual DVB-T Card?
Cheers
Joe
-
So what would be a recommended alternative to this Dual DVB-T Card?
Cheers
Joe
Well the are not too many options currently. We are testing the Dvico FusionHDTV Dual Digital 4;
http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#DViCO (http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#DViCO)
This card so far does not seem to suffer any of the usb related problems that the T500 suffers from (even though it also uses an on-board usb hub to connect the tuners).
All the best
Andrew
-
I am finding lots of issues with my Dvico FusionHDTV Dual Digital 4. The "version 1" cards are OK but version 2 card support is very new.
Andrew- what are your Dvico cards? Mine show up using "lsusb" as 0fe9:db98
-
Thanks for your replies Andrew - you always make sense!
May I say that I think the Nova-T-500 is really good, it's just this one issue that's bugging me.
Hope we see a solution to this problem at some point in the future.
-
Would using VDR instead of MythTV get around this USB disconnect problem?
If not, is there anything else I could try? I'm assuming that installing the new alpha version of LMCE would sort it out.... but is that going to give me problems with anything else? At the moment I am only using LMCE for TV (watching and recording) and media playback.
-
I am finding lots of issues with my Dvico FusionHDTV Dual Digital 4. The "version 1" cards are OK but version 2 card support is very new.
Andrew- what are your Dvico cards? Mine show up using "lsusb" as 0fe9:db98
Hi Indulis,
I cant confirm the Manufacturer:Device ID right now as its a long weekend here for Easter and none of our test Core's have a Dvico installed right now. However I can confirm that our units are Rev2 cards.
All the best
Andrew
-
Would using VDR instead of MythTV get around this USB disconnect problem?
If not, is there anything else I could try? I'm assuming that installing the new alpha version of LinuxMCE would sort it out.... but is that going to give me problems with anything else? At the moment I am only using LinuxMCE for TV (watching and recording) and media playback.
We are using the Kworld KW-DVB-T 399U USB twin tuner stick right now with the latest v4l-dvb drivers for the AF9015 etc used in this stick (check on http://www.linuxtv.org (http://www.linuxtv.org) for details etc). We dont see any disconnects at all with this stick and the performance seems to be very good indeed. I would suggest getting one if you in the market for a twin tuner DVB-T capability.
All the best
Andrew
-
Would using VDR instead of MythTV get around this USB disconnect problem?
If not, is there anything else I could try? I'm assuming that installing the new alpha version of LinuxMCE would sort it out.... but is that going to give me problems with anything else? At the moment I am only using LinuxMCE for TV (watching and recording) and media playback.
We are using the Kworld KW-DVB-T 399U USB twin tuner stick right now with the latest v4l-dvb drivers for the AF9015 etc used in this stick (check on http://www.linuxtv.org (http://www.linuxtv.org) for details etc). We dont see any disconnects at all with this stick and the performance seems to be very good indeed. I would suggest getting one if you in the market for a twin tuner DVB-T capability.
All the best
Andrew
Thanks for the reply.
Unfortunately I am already in possession of two Hauppauge Nova-T-500s! So would like to make those work if possible. I'm assuming that using VDR (I understand you utilise this instead of Myth, Andrew?) won't solve the problem then?
-
Would using VDR instead of MythTV get around this USB disconnect problem?
If not, is there anything else I could try? I'm assuming that installing the new alpha version of LinuxMCE would sort it out.... but is that going to give me problems with anything else? At the moment I am only using LinuxMCE for TV (watching and recording) and media playback.
We are using the Kworld KW-DVB-T 399U USB twin tuner stick right now with the latest v4l-dvb drivers for the AF9015 etc used in this stick (check on http://www.linuxtv.org (http://www.linuxtv.org) for details etc). We dont see any disconnects at all with this stick and the performance seems to be very good indeed. I would suggest getting one if you in the market for a twin tuner DVB-T capability.
All the best
Andrew
Thanks for the reply.
Unfortunately I am already in possession of two Hauppauge Nova-T-500s! So would like to make those work if possible. I'm assuming that using VDR (I understand you utilise this instead of Myth, Andrew?) won't solve the problem then?
Hi again,
Sorry I did not completely answer your earlier post. The problem with the T500 is not specific to MythTV or vdr at all. It appears to be related to i2c and other usb related errors and is specific to the T500 design (or more specifically the usb hub controller used in it). Some people are reporting better experiences with the T500 under Kubuntu 810... but I have to say that we dont see these ourselves in our tests. We have literally dozens of these cards in stock...so we would love to have a fix for this problem too!!
All the best
Andrew
-
You're seeing the same USB disconnect problem in 810, or new problems entirely?
Maybe I will take a look at those USB sticks you have recommended then. Are they relatively easy to set up? I am no programmer!
Thanks.
-
You're seeing the same USB disconnect problem in 810, or new problems entirely?
Maybe I will take a look at those USB sticks you have recommended then. Are they relatively easy to set up? I am no programmer!
Thanks.
We see the same problems under 0810 for the T500's... mainly i2c errors.
The KW-DVB-T 399U needs the latest v4l-dvb drivers and after that is plug-n-play. I will try and get a wiki article uploaded that covers this ;-)
Andrew
-
That would be absolutely fantastic, thank you.
I was also thinking of going over to VDR instead of using Myth as well - am I biting off more than I can chew here, or is VDR relatively easy to set up as well? (I have looked at the wiki page, but it does look a bit daunting to me). Also, may I ask why you prefer VDR to Myth?
Thanks again.
-
That would be absolutely fantastic, thank you.
I was also thinking of going over to VDR instead of using Myth as well - am I biting off more than I can chew here, or is VDR relatively easy to set up as well? (I have looked at the wiki page, but it does look a bit daunting to me). Also, may I ask why you prefer VDR to Myth?
Thanks again.
We like vdr for a number of reasons;
- Its a light weight app that is focused on DVB
- It supports the v4l-dvb api so that a single tuner can deliver all channels on a MUX simultaneously (latests MythTV I believe uses v4l-dvb too now)
- Its internal OSD UI is stb like and again light weight
vdr is reasonably easy to setup and should be even more so in 0810. Under 0710 the integration and setup still needs some manual config however.
The good news is that the v4l-dvb driver update will allow the KW twin tuner to work in MythTV or vdr.
Andrew
-
You're seeing the same USB disconnect problem in 810, or new problems entirely?
Maybe I will take a look at those USB sticks you have recommended then. Are they relatively easy to set up? I am no programmer!
Thanks.
We see the same problems under 0810 for the T500's... mainly i2c errors.
The KW-DVB-T 399U needs the latest v4l-dvb drivers and after that is plug-n-play. I will try and get a wiki article uploaded that covers this ;-)
Andrew
Hi Andrew, as much as I hate to hassle you, did you manage to upload this wiki article? Apologies if you have already, I just can't find it!
Cheers.
-
Another question I had about this KW sticks....
Do you supply many systems with two or more of these sticks in the core, ie four or more tuners? And if so, do they work ok?
Regarding this thread http://forum.linuxmce.org/index.php?topic=8000.0, I also wondered whether it is possible to change the directory (preferably to a secondary hard disk) that holds the recordings using VDR in 710?
-
You're seeing the same USB disconnect problem in 810, or new problems entirely?
Maybe I will take a look at those USB sticks you have recommended then. Are they relatively easy to set up? I am no programmer!
Thanks.
We see the same problems under 0810 for the T500's... mainly i2c errors.
The KW-DVB-T 399U needs the latest v4l-dvb drivers and after that is plug-n-play. I will try and get a wiki article uploaded that covers this ;-)
Andrew
Hi Andrew, as much as I hate to hassle you, did you manage to upload this wiki article? Apologies if you have already, I just can't find it!
Cheers.
Hi,
Sorry I did not get time last week. I'll get onto this on Monday.
Andrew
-
Another question I had about this KW sticks....
Do you supply many systems with two or more of these sticks in the core, ie four or more tuners? And if so, do they work ok?
Regarding this thread http://forum.linuxmce.org/index.php?topic=8000.0, I also wondered whether it is possible to change the directory (preferably to a secondary hard disk) that holds the recordings using VDR in 710?
We have started to supply systems with 1/2/3 KW Sticks installed internally. Under 0710 there is no automatic way to configure recording to another partition or drive but this can be done using a symlink to the second partition.
Andrew
-
Don't know if this will help anybody: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500)
-
Another question I had about this KW sticks....
Do you supply many systems with two or more of these sticks in the core, ie four or more tuners? And if so, do they work ok?
Regarding this thread http://forum.linuxmce.org/index.php?topic=8000.0, I also wondered whether it is possible to change the directory (preferably to a secondary hard disk) that holds the recordings using VDR in 710?
We have started to supply systems with 1/2/3 KW Sticks installed internally. Under 0710 there is no automatic way to configure recording to another partition or drive but this can be done using a symlink to the second partition.
Andrew
I did try with the symlinks (with MythTV, not VDR), but they kept disappearing after reboots! Any idea why this might be? Also, Thom seems to be dead against symlinks (see aforementioned thread) - I take it you haven't seen any instability issues with this approach?
And thanks in advance for doing the wiki page, it is much appreciated.
-
Don't know if this will help anybody: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500)
Will check out this page again tomorrow - it has been vandalised.
-
Hi All
Just leting every one know that the Happauge Wintv-Nova-T-500 seems to work flawlessly under 810 and Mythtv but we need to make a device template for it now
-
ihas.
Hi All
Just leting every one know that the Happauge Wintv-Nova-T-500 seems to work flawlessly under 810 and Mythtv but we need to make a device template for it now
I do not agree.
It´s a fine card but...
Have done extensive testing with this card both under 0710 and 0810.
It work better in 0810 but there are still problems.
For example i2c errors. When those happen you wont be able to tune the card anymore without a reboot.
Some motherboards seem to work better than others but the main underlying problem still exist, even 0810.
What firmware are you using to test with?
/niz23
-
niz - what is your take on the comments made on that wiki article linked to, on linuxtv? It seems heavily to imply that the i2c problems were solved, however it doesn't make much sense. At first it says the i2c problems were resolved in v1.2, but that this fw introduced new remote control problems (which has a workaround), then it goes on to say that the remote control problems, too, have been solved, but also under v1.2.... in other words, as if they have applied some subsequent fixes to the fw, but not bothered to increment the version number. Either way, it does explicitly state that the 1.2 fw has resolved those i2c problems.... have you tried the "new" version of v1.2 or only the "old" version of v1.2? :)
-
colinjones,
niz - what is your take on the comments made on that wiki article linked to, on linuxtv? It seems heavily to imply that the i2c problems were solved, however it doesn't make much sense. At first it says the i2c problems were resolved in v1.2, but that this fw introduced new remote control problems (which has a workaround), then it goes on to say that the remote control problems, too, have been solved, but also under v1.2.... in other words, as if they have applied some subsequent fixes to the fw, but not bothered to increment the version number. Either way, it does explicitly state that fw 1.2 has resolved those i2c problems.... have you tried the "new" version of v1.2 or only the "old" version of v1.2? :)
It was probably the old v1.20 version of the firmware that I tested.
Going to do another test to see if stability have changed.
In my experience the card can work stable for 1-2 weeks and then suddenly you see "usb disconnect" or i2c error.
Another time it might just work a few days before it stop working.
I know others here have done a lot of testing with this card too.
/niz23
-
Don't know if this will help anybody: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500)
Will check out this page again tomorrow - it has been vandalised.
This is the main LinuxTV wiki page for keeping tabs on how progress towards a stable T500 driver is coming along...I'm afraid as you will see at the end of the article it is still not stable and you will experience usb disconnects and i2c errors still. As is noted on this page there are some basic hardware errors and problems with the current drivers and the dib_0700 used in the Card.
Our experience with this card still is its problematic and will give you stability problems...its a great pity as this card is in many other respects really very good.
Andrew
-
Don't know if this will help anybody: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500)
Will check out this page again tomorrow - it has been vandalised.
This is the main LinuxTV wiki page for keeping tabs on how progress towards a stable T500 driver is coming along...I'm afraid as you will see at the end of the article it is still not stable and you will experience usb disconnects and i2c errors still. As is noted on this page there are some basic hardware errors and problems with the current drivers and the dib_0700 used in the Card.
Our experience with this card still is its problematic and will give you stability problems...its a great pity as this card is in many other respects really very good.
Andrew
Point taken. I am going to order a couple of KWorld 399Us in just a moment as you have suggested. Thanks for all of your help.
You mentioned that you use symlinks to change the recording directory - I haven't had much success with this, as on my current setup they seem to dissapear after the core has been rebooted! Any idea why this might be?
-
See the very brief Wiki article below on how to upgrade your LinuxMCE-0710 installation so that it will auto-detect a Kworld KW-DVB-T 399U DVB-T usb stick;
http://wiki.linuxmce.org/index.php/Kworld_KW-DVB-T_399U (http://wiki.linuxmce.org/index.php/Kworld_KW-DVB-T_399U)
The upgraded v4l-DVB modules installed by this lib will allow the 399U to be auto-detected correctly and will also improve support of other newer DVB-T tuners too.
All the best
Andrew
-
That's fantastic, thank you. My 399Us have just arrived, so will give this a try during the week.
Any comment on the symlinks? Mine always seem to disappear after a reboot, which means my smaller OS hard disk fills up with recordings extremely quickly.
Thanks again for your help.