Skip to contentSkip to conversation

Hauppauge NOVA-T 500 falls over after warm reboot

DISCUSSION uTaR 2 participants 6 messages Mar 3, 2009 – Mar 5, 2009 Media (V4L/DVB)

lore
Share & tools
lore

uTaR

author
#0 lore raw

Just thought I would report some unusual behaviour I am seeing on my Nova-T 500. Basically the card works fine with a cold boot but falls over rapidly after a warm reboot.

This started after I compiled the latest v4l source tree (as at 22 Feb
09) due to me adding a Tevii S650 to my system. At first I thought it was the Tevii which was causing the problem but testing showed the Nova falls over irrespective of if the Tevii is attached.

I'm running Ubuntu with 2.6.27-11 and I never had this issue with v4l running "out of the box."

Sample of the log after the Nova falls over follows:

[  117.920002] ehci_hcd 0000:05:00.2: force halt; handhake f88f4c14
00004000 00000000 -> -110
[  129.412342] mt2060 I2C write failed
[  132.412253] mt2060 I2C write failed
[  133.713596] mt2060 I2C write failed
[  136.712264] mt2060 I2C write failed
[  138.004603] mt2060 I2C write failed
[  141.004564] mt2060 I2C write failed
[  147.177361] mt2060 I2C write failed
[  150.176124] mt2060 I2C write failed
[  171.026988] mt2060 I2C write failed
[  171.041701] mt2060 I2C write failed (len=2)
[  171.041824] mt2060 I2C write failed (len=6)
[  171.041922] mt2060 I2C read failed
#1 lore raw

Hi,
Same here. I've been observing the same behaviour in the lastest
times. I can't say exactly since when this happens, though.

I've observed that stopping mythbackend, unloading the driver with 'rmmod dvb_usb_dib0700' and rebooting again seems to fix the problem.

By the dmesg it seems like, on a warm reboot, it fails to detect the card as 'warm' state (dmesg says it's 'cold'), so it attempts to load the firmware again, which fails and leaves the card in an unusable state.

Best regards,
Eduard

2009/3/3 uTaR <[email protected]>:

Quoted 34 lines

Just thought I would report some unusual behaviour I am seeing on my Nova-T 500.  Basically the card works fine with a cold boot but falls over rapidly after a warm reboot.

This started after I compiled the latest v4l source tree (as at 22 Feb
09) due to me adding a Tevii S650 to my system.  At first I thought it was the Tevii which was causing the problem but testing showed the Nova falls over irrespective of if the Tevii is attached.

I'm running Ubuntu with 2.6.27-11 and I never had this issue with v4l running "out of the box."

Sample of the log after the Nova falls over follows:

[  117.920002] ehci_hcd 0000:05:00.2: force halt; handhake f88f4c14 00004000 00000000 -> -110
[  129.412342] mt2060 I2C write failed
[  132.412253] mt2060 I2C write failed
[  133.713596] mt2060 I2C write failed
[  136.712264] mt2060 I2C write failed
[  138.004603] mt2060 I2C write failed
[  141.004564] mt2060 I2C write failed
[  147.177361] mt2060 I2C write failed
[  150.176124] mt2060 I2C write failed
[  171.026988] mt2060 I2C write failed
[  171.041701] mt2060 I2C write failed (len=2)
[  171.041824] mt2060 I2C write failed (len=6)
[  171.041922] mt2060 I2C read failed
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

author
#2 lore raw
Quoted 8 lines

Hi,
Same here. I've been observing the same behaviour in the lastest
times. I can't say exactly since when this happens, though.

I've observed that stopping mythbackend, unloading the driver with 'rmmod dvb_usb_dib0700' and rebooting again seems to fix the problem.

Quoted 7 lines

By the dmesg it seems like, on a warm reboot, it fails to detect the card as 'warm' state (dmesg says it's 'cold'), so it attempts to load the firmware again, which fails and leaves the card in an unusable state.

Best regards,
Eduard

Thanks for the reply.

In my case the Nova is correctly identified as being in the "warm" state after a reboot, however it still falls over either before I can even start playing TV or within a minute or so of actually playing TV.

#3 lore raw

Have you tried rmmoding the module (dvb_usb_dib0700) and reloading it? I think that it was in such a case where it then wrongly detected the card as 'cold', attempting to reload it, which failed.

2009/3/3 uTaR <[email protected]>:

Quoted 31 lines
Quoted 8 lines

Hi,
Same here. I've been observing the same behaviour in the lastest
times. I can't say exactly since when this happens, though.

I've observed that stopping mythbackend, unloading the driver with 'rmmod dvb_usb_dib0700' and rebooting again seems to fix the problem.

Quoted 7 lines

By the dmesg it seems like, on a warm reboot, it fails to detect the card as 'warm' state (dmesg says it's 'cold'), so it attempts to load the firmware again, which fails and leaves the card in an unusable state.

Best regards,
Eduard

Thanks for the reply.

In my case the Nova is correctly identified as being in the "warm" state after a reboot, however it still falls over either before I can even start playing TV or within a minute or so of actually playing TV.

author
#4 lore raw
Quoted 4 lines

Have you tried rmmoding the module (dvb_usb_dib0700) and reloading it? I think that it was in such a case where it then wrongly detected the card as 'cold', attempting to reload it, which failed.

No as if I do a cold boot there isn't an issue. I just thought I would report this so that the developers were aware.

Many thanks for the suggestion though.

#5 lore raw

A Dijous, 5 de març de 2009 20:57:38, utar va escriure:

Quoted 7 lines
Quoted 3 lines

Have you tried rmmoding the module (dvb_usb_dib0700) and reloading it? I think that it was in such a case where it then wrongly detected the card as 'cold', attempting to reload it, which failed.

No as if I do a cold boot there isn't an issue. I just thought I would report this so that the developers were aware.

Quoted 6 lines

Many thanks for the suggestion though.

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi,
I agree, the cold reboot does nothave this problem. Anyway, in a case a
cold reboot is not possible (I sometimes reboot my backend remotely), stopping the backend and unloading the driver before rebooting seems to also work fine.

This might be a clue also about what's happening, anyway.

Best regards