Re: Nova-T 500 does not survive reboot

Re: Nova-T 500 does not survive reboot

[Soeren Moch]

 >>> Hi,
 >>>    Any news on this? I'd like to try the URB patch someone mentioned,
 >>> but I
 >>> can't find the link.
 >>
 >> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html
 >>
 >> I am running a current dvb tree with this patch.
 >>
 >> so far so good.
 >>
 >> I did not find the time to check if I regained proper reboots, though. I
 >> know, sad excuse...
 >>
 >> nico
 >>
 >>
 >
 > I'll give it a try. Thanks for the tip!
 > Cheers,
 >   Eduard

Hi nico, Eduard,

can you confirm that the patch solves your Nova-T 500 boot problem?
In this case I would resend the buffer count part as separate patch to
Patrick.

S:oren

Re: Nova-T 500 does not survive reboot

[Nicolas Will]

On Fri, 2009-05-22 at 15:30 +0200, Soeren Moch wrote:
> >>> Hi,
>  >>>    Any news on this? I'd like to try the URB patch someone mentioned,
>  >>> but I
>  >>> can't find the link.
>  >>
>  >> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html
>  >>
>  >> I am running a current dvb tree with this patch.
>  >>
>  >> so far so good.
>  >>
>  >> I did not find the time to check if I regained proper reboots, though. I
>  >> know, sad excuse...
>  >>
>  >> nico
>  >>
>  >>
>  >
>  > I'll give it a try. Thanks for the tip!
>  > Cheers,
>  >   Eduard
> 
> Hi nico, Eduard,
> 
> can you confirm that the patch solves your Nova-T 500 boot problem?
> In this case I would resend the buffer count part as separate patch to
> Patrick.

It doesn;t appear to fix it.

I'll retry this evening, after the F1 Grand Prix.

Nico

Re: DVB USB stream parameters

[Soeren Moch]

> I don't know exactly why (the USB/HW background for that is not 
> present in my brain), but at some point having less than 39480B for 
> one (high-level) URB for the dib0700 resulted in never having any URB 
> returning from the USB stack. I chose 4 of them because .. I don't 
> remember. It seems even 1 is working.

I vote for a single high-level URB. Besides the memory savings this is 
the only way I could get my nova-td stick working.
(see this thread: 
http://www.mail-archive.com/linux-media@vger.kernel.org/msg06376.html ) 
The patch runs flawlessly
on my vdr system for months now.

> I remember someone telling me that this is due to something in the 
> firmware. I need to wait for some people to be back from whereever 
> they are to know exactly what's going on (that's why I haven't 
> responded yet).
I hope you can sort out the dib0700_streaming_ctrl problems...

Soeren

dib0700 i2c problem / mt2266 patch

[Soeren Moch]

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Patrick,

when you are discussing dib0700 issues with dibcom, there is an
additional one for the list:
When using dib0700 in dual mode (on my nova-td stick), from
time to time a tuner hangs up. I never observed this behavior in
single mode. It seems to me that there is no proper locking within
the dib0700 firmware when accessing both tuner i2c buses
"simultaneously".

Since I only need UHF channels, I use the attached patch to decrease
the number of i2c transactions and tuner registers, which are involved
in the channel switch. This solved the tuning problems.

Besides the i2c problem, maybe it might be a good idea to integrate
this patch into the mt2266 driver anyway, because it considerably
speeds up the channel switch.

Regards,
S:oren




[-- Attachment #2: mt2266.patch --]
[-- Type: text/x-patch, Size: 2062 bytes --]

--- drivers/media/common/tuners/mt2266.c.orig	2009-06-29 22:11:08.000000000 +0200
+++ drivers/media/common/tuners/mt2266.c	2009-06-29 22:21:01.000000000 +0200
@@ -137,7 +137,6 @@ static int mt2266_set_params(struct dvb_
 	freq = params->frequency / 1000; // Hz -> kHz
 	if (freq < 470000 && freq > 230000)
 		return -EINVAL; /* Gap between VHF and UHF bands */
-	priv->bandwidth = (fe->ops.info.type == FE_OFDM) ? params->u.ofdm.bandwidth : 0;
 	priv->frequency = freq * 1000;
 
 	tune = 2 * freq * (8192/16) / (FREF/16);
@@ -145,21 +144,24 @@ static int mt2266_set_params(struct dvb_
 	if (band == MT2266_VHF)
 		tune *= 2;
 
-	switch (params->u.ofdm.bandwidth) {
-	case BANDWIDTH_6_MHZ:
-		mt2266_writeregs(priv, mt2266_init_6mhz,
-				 sizeof(mt2266_init_6mhz));
-		break;
-	case BANDWIDTH_7_MHZ:
-		mt2266_writeregs(priv, mt2266_init_7mhz,
-				 sizeof(mt2266_init_7mhz));
-		break;
-	case BANDWIDTH_8_MHZ:
-	default:
-		mt2266_writeregs(priv, mt2266_init_8mhz,
-				 sizeof(mt2266_init_8mhz));
-		break;
-	}
+        if (priv->bandwidth != params->u.ofdm.bandwidth) {
+          priv->bandwidth = (fe->ops.info.type == FE_OFDM) ? params->u.ofdm.bandwidth : 0;
+          switch (params->u.ofdm.bandwidth) {
+          case BANDWIDTH_6_MHZ:
+            mt2266_writeregs(priv, mt2266_init_6mhz,
+                             sizeof(mt2266_init_6mhz));
+            break;
+          case BANDWIDTH_7_MHZ:
+            mt2266_writeregs(priv, mt2266_init_7mhz,
+                             sizeof(mt2266_init_7mhz));
+            break;
+          case BANDWIDTH_8_MHZ:
+          default:
+            mt2266_writeregs(priv, mt2266_init_8mhz,
+                             sizeof(mt2266_init_8mhz));
+            break;
+          }
+        }
 
 	if (band == MT2266_VHF && priv->band == MT2266_UHF) {
 		dprintk("Switch from UHF to VHF");
@@ -327,6 +329,7 @@ struct dvb_frontend * mt2266_attach(stru
 
 	priv->cfg      = cfg;
 	priv->i2c      = i2c;
+	priv->bandwidth= BANDWIDTH_8_MHZ;
 	priv->band     = MT2266_UHF;
 
 	if (mt2266_readreg(priv, 0, &id)) {

Re: Nova-T 500 does not survive reboot

[Soeren.Moch]

> Apr 29 22:42:41 favia kernel: [   72.272045] ehci_hcd 0000:07:01.2:  
> force halt; handhake ffffc20000666814 00004000 00000000 -> -110
> [...]
> Do you know if the issue is the same with a Nova-TD stick? If it is,
> then I could be able to use debugging as an excuse to buy one, and then
> add 2 tuners to the system when all is done :o)

I had the same "ehci_hcd force halt" error when I was debugging the
Nova-TD dual-stream-switchon-problem:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html

Reducing the urb count to 1 (as included in the patch) solved the
"ehci_hcd force halt" issue for me.

S:oren

Re: Nova-T 500 does not survive reboot

[Nicolas Will]

On Thu, 2009-04-30 at 13:56 +0200, Soeren.Moch@stud.uni-hannover.de
wrote:
> > Apr 29 22:42:41 favia kernel: [   72.272045] ehci_hcd
> 0000:07:01.2:  
> > force halt; handhake ffffc20000666814 00004000 00000000 -> -110
> > [...]
> > Do you know if the issue is the same with a Nova-TD stick? If it is,
> > then I could be able to use debugging as an excuse to buy one, and
> then
> > add 2 tuners to the system when all is done :o)
> 
> I had the same "ehci_hcd force halt" error when I was debugging the
> Nova-TD dual-stream-switchon-problem:
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html
> 
> Reducing the urb count to 1 (as included in the patch) solved the
> "ehci_hcd force halt" issue for me.

I mention that the URB part is a quick hack.

You were asking for opinions on that, and apparently did not get any
feedback.

Time for another call?

Nico

Re: Nova-T 500 does not survive reboot

[Nicolas Will]

On Thu, 2009-04-30 at 16:08 +0100, Nicolas Will wrote:
> 
> I mention that the URB part is a quick hack.

*you* mention, I wouldn't dare... ;o)

Nico

Nova-T 500 does not survive reboot

[Nicolas Will]

Hello all,

I am running an hg clone from a few days ago with firmware 1.20 on a
64-bit Ubuntu Intrepid (2.6.27 kernel).

I have noticed that for some time now the card/driver/firmware
combination does not like warm reboots.

If I reboot the system and try to use any Nova-T 500 tuner, I
immediately get the mt2060 I2C errors.

If I completely shut down the system, remove the power, then reboot, all
is fine.

I have missed most of the linux-media traffic, I was still stuck on
linux-dvb. Have I missed some discussions about this?

Thanks!

Nico

Re: Nova-T 500 does not survive reboot

[Eduard Huguet]

Nicolas Will <nico <at> youplala.net> writes:

> 
> Hello all,
> 
> I am running an hg clone from a few days ago with firmware 1.20 on a
> 64-bit Ubuntu Intrepid (2.6.27 kernel).
> 
> I have noticed that for some time now the card/driver/firmware
> combination does not like warm reboots.
> 
> If I reboot the system and try to use any Nova-T 500 tuner, I
> immediately get the mt2060 I2C errors.
> 
> If I completely shut down the system, remove the power, then reboot, all
> is fine.
> 
> I have missed most of the linux-media traffic, I was still stuck on
> linux-dvb. Have I missed some discussions about this?
> 
> Thanks!
> 
> Nico
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


Hi, Nicholas

I posted the very same thing 3 days ago:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973


This is something that has been occuring lately, since some months ago. I don't
know when exactly was this bug introduced, but it has been in HG for a couple of
months at least. I can remenber that other guy posted about this issue some time
ago, but I can't find the link.


And for what I see, Janne Grunau is also having problems with the card. See what
he have just posted...:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973

Best regards, 
  Eduard Huguet

Re: Nova-T 500 does not survive reboot

[Nicolas Will]

On Thu, 2009-04-30 at 10:16 +0000, Eduard Huguet wrote:
> Nicolas Will <nico <at> youplala.net> writes:
> 
> > 
> > Hello all,
> > 
> > I am running an hg clone from a few days ago with firmware 1.20 on a
> > 64-bit Ubuntu Intrepid (2.6.27 kernel).
> > 
> > I have noticed that for some time now the card/driver/firmware
> > combination does not like warm reboots.
> > 
> > If I reboot the system and try to use any Nova-T 500 tuner, I
> > immediately get the mt2060 I2C errors.
> > 
> > If I completely shut down the system, remove the power, then reboot, all
> > is fine.
> > 
> > I have missed most of the linux-media traffic, I was still stuck on
> > linux-dvb. Have I missed some discussions about this?
> > 
> > Thanks!
> > 
> > Nico
> Hi, Nicholas
> 
> I posted the very same thing 3 days ago:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973

Argh, I missed it (I don't really like gmame's archiving... I will need
to get used to it).

I have the same :


Apr 29 22:42:41 favia kernel: [   72.272045] ehci_hcd 0000:07:01.2: force halt; handhake ffffc20000666814 00004000 00000000 -> -110


then


Apr 29 22:43:02 favia kernel: [   92.900094] mt2060 I2C write failed
Apr 29 22:43:02 favia kernel: [   92.905830] mt2060 I2C write failed (len=2)
Apr 29 22:43:02 favia kernel: [   92.905835] mt2060 I2C write failed (len=6)
Apr 29 22:43:02 favia kernel: [   92.905838] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [   92.912552] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [   92.920572] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [   92.928552] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [   92.936554] mt2060 I2C read failed
Apr 29 22:43:02 favia kernel: [   92.944552] mt2060 I2C read failed
...............

and at one point I get the following before I shut down


Apr 29 22:44:27 favia kernel: [  177.818215] dvb-usb: could not submit URB no. 0 - get them all back
Apr 29 22:44:27 favia kernel: [  177.818222] dvb-usb: error while enabling fifo.




> 
> 
> This is something that has been occuring lately, since some months ago. I don't
> know when exactly was this bug introduced, but it has been in HG for a couple of
> months at least. I can remenber that other guy posted about this issue some time
> ago, but I can't find the link.


I'm with that too. I was just really busy at the time to dig into it.



> 
> 
> And for what I see, Janne Grunau is also having problems with the card. See what
> he have just posted...:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973


I saw that one too, it arrived as I subscribed to the proper list.

I'm not directly concerned now, but I will be facing this too when I
will want to upgrade my system to the current Ubuntu release.


Soooooo...

What can I/we do to help track/fix this?

I'm game for a bit of testing, within reason, though, at the system is
in production.

Do you know if the issue is the same with a Nova-TD stick? If it is,
then I could be able to use debugging as an excuse to buy one, and then
add 2 tuners to the system when all is done :o)

Nico
http://www.youplala.net/linux/home-theater-pc/

Re: Nova-T 500 does not survive reboot

[Nicolas Will]

On Thu, 2009-04-30 at 10:16 +0000, Eduard Huguet wrote:
> I can remenber that other guy posted about this issue some time
> ago, but I can't find the link.

http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/2423/focus=2591

I guess.

nico
getting used to gmame :o)

Re: Nova-T 500 does not survive reboot

[Eduard Huguet]

Nicolas Will <nico <at> youplala.net> writes:

> 
> Hello all,
> 
> I am running an hg clone from a few days ago with firmware 1.20 on a
> 64-bit Ubuntu Intrepid (2.6.27 kernel).
> 
> I have noticed that for some time now the card/driver/firmware
> combination does not like warm reboots.
> 
> If I reboot the system and try to use any Nova-T 500 tuner, I
> immediately get the mt2060 I2C errors.
> 
> If I completely shut down the system, remove the power, then reboot, all
> is fine.
> 
> I have missed most of the linux-media traffic, I was still stuck on
> linux-dvb. Have I missed some discussions about this?
> 
> Thanks!
> 
> Nico
> 

Hi, 
   Any news on this? I'd like to try the URB patch someone mentioned, but I
can't find the link.

Best regards, 
  Eduard

Re: Nova-T 500 does not survive reboot

[Eduard Huguet]

>> Hi,
>>    Any news on this? I'd like to try the URB patch someone mentioned,
>> but I
>> can't find the link.
>
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html
>
> I am running a current dvb tree with this patch.
>
> so far so good.
>
> I did not find the time to check if I regained proper reboots, though. I
> know, sad excuse...
>
> nico
>
>

I'll give it a try. Thanks for the tip!
Cheers,
  Eduard