Skip to contentSkip to conversation

Nova-T-500 disconnects - They are back!

linux-dvb Nicolas Will 14 participants 45 messages Mar 21, 2008 – Mar 31, 2008 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using 2.6.24, 64-bit.

And the disconnects are back.

I was using a rather ancient v4l-dvb tree, so I grabbed a new one, and saw no improvement.

It may be very well linked to the remote, I was recording anything when this one struck, just using the remote.

I may even have been tuned on the neighbouring cx88 DVB-S card.

Mar 21 21:57:54 favia kernel: [ 7283.416866] dib0700: Unknown remote controller key:  9  0  1  0
Mar 21 21:58:05 favia kernel: [ 7294.501676] dib0700: Unknown remote controller key:  9  0  1  0
Mar 21 21:58:08 favia kernel: [ 7297.111367] usb 10-1: USB disconnect, address 2
Mar 21 21:58:08 favia lircd-0.8.3pre1[5982]: error reading '/dev/input/event6'
Mar 21 21:58:08 favia lircd-0.8.3pre1[5982]: caught signal
Mar 21 21:58:08 favia lircd-0.8.3pre1[5982]: closing '/dev/input/event6'
Mar 21 21:58:08 favia kernel: [ 7297.154576] mt2060 I2C write failed
Mar 21 21:58:08 favia NetworkManager: <debug> [1206136688.229829] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_2040_9950_4028166400_logicaldev_input'). 
Mar 21 21:58:09 favia kernel: [ 7298.074147] mt2060 I2C write failed (len=2)
Mar 21 21:58:09 favia kernel: [ 7298.074153] mt2060 I2C write failed (len=6)
Mar 21 21:58:09 favia kernel: [ 7298.074156] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.082072] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.090025] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.098098] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.106028] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.114051] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.122059] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.129494] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.137497] mt2060 I2C read failed
Mar 21 21:58:09 favia kernel: [ 7298.145993] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.292331] mt2060 I2C write failed (len=2)
Mar 21 21:58:10 favia kernel: [ 7299.292337] mt2060 I2C write failed (len=6)
Mar 21 21:58:10 favia kernel: [ 7299.292340] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.300318] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.308313] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.317636] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.328044] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.332266] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.341351] mt2060 I2C read failed
Mar 21 21:58:10 favia kernel: [ 7299.348291] mt2060 I2C read failed

dmesg, lsusb -v, lspci -vvv in here:

http://www.youplala.net/~will/htpc/disconnects/

The system is described there:

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

I have

options dvb-usb-dib0700 force_lna_activation=1
options options usbcore autosuspend=-1

in /etc/modprobe.d/options

I remain available for any testing and documenting this new step back.

Nico
hopes that the F1 Grand Prix will be recorded tonight :o/

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#1 lore raw

Il giorno ven, 21/03/2008 alle 22.51 +0000, Nicolas Will ha scritto:

Quoted 5 lines

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using 2.6.24, 64-bit.

Quoted 7 lines

And the disconnects are back.

I was using a rather ancient v4l-dvb tree, so I grabbed a new one, and saw no improvement.

It may be very well linked to the remote, I was recording anything when this one struck, just using the remote.

Hi Nico, did you apply my patch? If so could you please try it with a clean unpatched tree? I'd like to know if this is someway related to my patch or to dib0700_rc_setup calls.
BTW, I'm evaluating too an early switch from gusty to hardy, did you experienced any problem? Is it usable? I've heard something about libc6 failures.. has it been fixed?
Thanks

Filippo

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#2 lore raw
Quoted 13 lines · Filippo Argiolas

Il giorno ven, 21/03/2008 alle 22.51 +0000, Nicolas Will ha scritto:

Quoted 3 lines

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using

2.6.24,

Quoted 5 lines

64-bit.

And the disconnects are back.

I was using a rather ancient v4l-dvb tree, so I grabbed a new one,

and

Quoted 2 lines

saw no improvement.

Quoted 8 lines
Quoted 1 line

It may be very well linked to the remote, I was recording anything

when

Quoted 1 line

this one struck, just using the remote.

Hi Nico, did you apply my patch? If so could you please try it with a clean unpatched tree? I'd like to know if this is someway related to my
patch or to dib0700_rc_setup calls.

I would doubt it, but why not.

I'll give it a try.

Quoted 2 lines

BTW, I'm evaluating too an early switch from gusty to hardy, did you experienced any problem?

None, it went nicely, as usual, the package management system is nice, as well as the processes around it.

Just be aware that the kernel upgrade will make your nova-t-500 unstable like mine. But if you are willing to look into the code, go ahead!

Quoted 1 line

Is it usable?

Very as a mythtv system. For a desktop, I would wait a bit more, FF3 is not there yet, Compiz sees a lot of breakage too. I have a couple of machines on Hardy.

Quoted 2 lines

I've heard something about libc6
failures.. has it been fixed?

A long time ago, that was only a matter of hours until the fix was out.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#3 lore raw

Guys,

Well, the disconnects are not remote-related, at least the last disconnect happened with no interaction whatsoever.

There was no activity on the tuners (like recording) at the time either (last one had finished 20mn before).

I'm not even sure that there was any EIT scanning going on.

Mar 23 10:32:40 favia kernel: [ 8244.672148] dib0700: Unknown remote controller key:  6 3C  1  0
Mar 23 10:32:41 favia kernel: [ 8245.734970] dib0700: Unknown remote controller key:  6 3C  1  0
Mar 23 10:33:18 favia kernel: [ 8282.337362] dib0700: Unknown remote controller key:  6 3C  1  0

There is quite some time between the last remote use and the disconnect:

Mar 23 10:54:10 favia kernel: [ 9532.658799] usb 4-1: USB disconnect, address 2
Mar 23 10:54:10 favia lircd-0.8.3pre1[5992]: error reading '/dev/input/dvb-ir'
Mar 23 10:54:10 favia kernel: [ 9532.693940] mt2060 I2C write failed
Mar 23 10:54:10 favia NetworkManager: <debug> [1206269650.277733] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_2040_9950_4028166400_logicaldev_input'). 
Mar 23 10:54:10 favia lircd-0.8.3pre1[5992]: caught signal
Mar 23 10:54:10 favia lircd-0.8.3pre1[5992]: closing '/dev/input/dvb-ir'

The delay is quite interesting too, and there is that dvb-usb error that I do not remember seing with 2.6.22 kernels:

Mar 23 10:57:50 favia kernel: [ 9752.272265] dvb-usb: error while stopping stream.
Mar 23 10:57:50 favia kernel: [ 9752.274256] mt2060 I2C write failed (len=2)
Mar 23 10:57:50 favia kernel: [ 9752.274260] mt2060 I2C write failed (len=6)
Mar 23 10:57:50 favia kernel: [ 9752.274261] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.280342] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.288306] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.296243] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.303877] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.311829] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.320208] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.328272] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.335949] mt2060 I2C read failed
Mar 23 10:57:50 favia kernel: [ 9752.344194] mt2060 I2C read failed
Mar 23 10:57:51 favia kernel: [ 9753.491057] mt2060 I2C write failed (len=2)
Mar 23 10:57:51 favia kernel: [ 9753.491064] mt2060 I2C write failed (len=6)
Mar 23 10:57:51 favia kernel: [ 9753.491067] mt2060 I2C read failed
Mar 23 10:57:51 favia kernel: [ 9753.499046] mt2060 I2C read failed
Mar 23 10:57:51 favia kernel: [ 9753.506578] mt2060 I2C read failed
Mar 23 10:57:51 favia kernel: [ 9753.514949] mt2060 I2C read failed

.....

Nico
not having any fun

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#4 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#5 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#6 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 30 lines · Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

A bit off-topic but how do you get the date/time thing ? I only get the time-since-boot and that is so enoying

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#7 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 2 lines · Patrik Hansson

A bit off-topic but how do you get the date/time thing ? I only get the time-since-boot and that is so enoying

I don't know if this is how Nicolas does it, but one method is to use the Gnome System Log viewer, then copy and paste from that.

Cheers,

John

Signature · 6 lines
John Veness, MythTV user, UK, DVB-T

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#8 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 6 lines · John Veness
Quoted 2 lines · Patrik Hansson

A bit off-topic but how do you get the date/time thing ? I only get the time-since-boot and that is so enoying

I don't know if this is how Nicolas does it, but one method is to use the Gnome System Log viewer, then copy and paste from that.

My syslog daemon does it for me.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#9 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Nicolas Will
Quoted 20 lines · Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

Quoted 7 lines

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

This is really a cry for help.

I am not a coder, I don't even know where my K&R C book that I bought 17 years ago is anymore, so I cannot dive into the code and pretend to understand it.

But I can push, pull, help coordinate, document, hg clone, compile, install, reboot, test, report, publish results on the wiki, and more if needed.

That card was nearly working 100%, then something broke, and we are back to the status we had 1 year ago.

Please, please, please...

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#10 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 47 lines · Nicolas Will
Quoted 20 lines · Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

Quoted 7 lines

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

This is really a cry for help.

I am not a coder, I don't even know where my K&R C book that I bought 17 years ago is anymore, so I cannot dive into the code and pretend to understand it.

But I can push, pull, help coordinate, document, hg clone, compile, install, reboot, test, report, publish results on the wiki, and more if needed.

That card was nearly working 100%, then something broke, and we are back to the status we had 1 year ago.

Please, please, please...

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

When you get a disconnect what is needed for you to be able to get it back ? Just so there is no missunderstanding.

I´m running sasc-ng as cardemulator to be able to use my card for the encrypted channels here in Sweden and i only have to restart that (and of course mythtv-backend) and the tuner is back.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#11 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 57 lines · Patrik Hansson
Quoted 47 lines · Nicolas Will
Quoted 20 lines · Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug

Quoted 7 lines

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug

Can that help, or would more be needed?

There was zero remote usage at the time.

This is really a cry for help.

I am not a coder, I don't even know where my K&R C book that I bought 17 years ago is anymore, so I cannot dive into the code and pretend to understand it.

But I can push, pull, help coordinate, document, hg clone, compile, install, reboot, test, report, publish results on the wiki, and more if needed.

That card was nearly working 100%, then something broke, and we are back to the status we had 1 year ago.

Please, please, please...

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Quoted 8 lines

When you get a disconnect what is needed for you to be able to get it back ? Just so there is no missunderstanding.

I´m running sasc-ng as cardemulator to be able to use my card for the encrypted channels here in Sweden and i only have to restart that (and of course mythtv-backend) and the tuner is back.

The driver will be held back from unloading as long as a devicenode is open. So restarting all applications which accesses the device nodes should definitely help if that problem comes up.

Markus

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#12 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Nicolas Will

I know how you feel.

I´ve been there but now my box is stable,

root@media:~# uname -a
Linux media 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
GNU/Linux

My v4l-dvb is from 2008-01-28 and I have patched it with (or atleast the patches in that dir are),
dib0700-start-streaming-fix.patch
dib300mc_tuning_fix.diff
MT1060_IF1_freq_set.diff
and a patch wich I think is for UHF.

Shall I gzip my source and give you a link?

/Henrik

Quoted 45 lines · Nicolas Will
Quoted 20 lines · Nicolas Will

Guys,

I was running with the following debug options when I got a disconnect:

options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
options usbcore autosuspend=-1

/var/log/messages is here:

http://www.youplala.net/~will/htpc/disconnects/messages-with_debug<http://www.youplala.net/%7Ewill/htpc/disconnects/messages-with_debug>

Quoted 7 lines

and slightly different data:

http://www.youplala.net/~will/htpc/disconnects/syslog-with_debug<http://www.youplala.net/%7Ewill/htpc/disconnects/syslog-with_debug>

Can that help, or would more be needed?

There was zero remote usage at the time.

This is really a cry for help.

I am not a coder, I don't even know where my K&R C book that I bought 17 years ago is anymore, so I cannot dive into the code and pretend to understand it.

But I can push, pull, help coordinate, document, hg clone, compile, install, reboot, test, report, publish results on the wiki, and more if needed.

That card was nearly working 100%, then something broke, and we are back to the status we had 1 year ago.

Please, please, please...

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#13 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

One more thing.

I used to run my mythbox on an AMD64 in 64bit on a Nforce 4, but I switched to a 32bit P4.
This was because my workaround nova-td stick didn´t work with the USB controllers on the nforce board and I needed the PCI slots, I very quickly switched from the TD to the Nova-t 500 to test the streaming patch and it has worked since. On my 64Bit machine I had problems with disconnects on the TD also.

Is there any differences in disconnects in 64 vs 32 bit systems?

Unfortunatly my 2,6GHz P4 is to slow, or barely coping to be able to handle the nice 2x deinterlacing
so all is not well here either.

/Henrik

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#14 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Henrik Beckman
Quoted 6 lines · Henrik Beckman

I know how you feel.

I´ve been there but now my box is stable,

root@media:~# uname -a
Linux media 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
GNU/Linux

Sure, my system was stable with 2.6.22 too.

Quoted 7 lines

My v4l-dvb is from 2008-01-28 and I have patched it with (or atleast the patches in that dir are), dib0700-start-streaming-fix.patch dib300mc_tuning_fix.diff
MT1060_IF1_freq_set.diff
and a patch wich I think is for UHF.

I am well aware of those, I am trying to keep the wiki page updated as much as I can (camelreef is me).

If you grab a recent tree, all those patches have been merged and you will not need to apply them anymore.

There is only last patch on the wiki that gives remote key repeats, but it should get in the main tree soon, Patrick put it in his branch.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#15 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 11 lines · Nicolas Will
Quoted 6 lines · Henrik Beckman

I know how you feel.

I´ve been there but now my box is stable,

root@media:~# uname -a
Linux media 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
GNU/Linux

Sure, my system was stable with 2.6.22 too.

Linux IKA 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux Not stable at all here, got 2 disconnects in 2 hours.
So it can't just be the kernel.

Quoted 20 lines
Quoted 8 lines

My v4l-dvb is from 2008-01-28 and I have patched it with (or atleast the patches in that dir are), dib0700-start-streaming-fix.patch dib300mc_tuning_fix.diff
MT1060_IF1_freq_set.diff
and a patch wich I think is for UHF.

I am well aware of those, I am trying to keep the wiki page updated as much as I can (camelreef is me).

If you grab a recent tree, all those patches have been merged and you will not need to apply them anymore.

There is only last patch on the wiki that gives remote key repeats, but it should get in the main tree soon, Patrick put it in his branch.

Quoted 7 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#16 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 10 lines · Patrik Hansson
Quoted 7 lines · Nicolas Will
Quoted 5 lines · Henrik Beckman

I know how you feel.

I´ve been there but now my box is stable,

root@media:~# uname -a
Linux media 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007

i686

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

GNU/Linux

Sure, my system was stable with 2.6.22 too.

Linux IKA 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
Not stable at all here, got 2 disconnects in 2 hours.
So it can't just be the kernel.

Well, fine.

What we need here is a developer.

What a developer needs is info, without it, he will not be able to help.

I've posted logs, now your turn.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#17 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 9 lines · Nicolas Will

Well, fine.

What we need here is a developer.

What a developer needs is info, without it, he will not be able to help.

I've posted logs, now your turn.

Adding the following lines in your /etc/modprobe.d/options would be a good start:

options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1

Then post the lines of /var/log/syslog and /var/log/messages around the disconnect event.

Better post them somewhere on a web page or a pastebin.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#18 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

I think we are better of trying to pin the problem down to a point where we can switch it on/off with a change of kernel or dvb code, may I humbly suggest.

Verify if the current tree is stable on 2.6.22.
Verify if it breaks with a newer kernel, then check for changes in the changelog regarding usb.
Collecting debug info about the disconnects is probably very good, let´s hope someone takes pity on us.

I had problems until my recent config, at the same moment it was stable I stopped tinkering and haven´t dared to upgrade anything since. My bet is that the dibcom stuff does something ugly and that there is changes in the kernel usb code (or even config) that makes the problem reappear.

/Henrik

Quoted 29 lines · Nicolas Will
Quoted 9 lines · Nicolas Will

Well, fine.

What we need here is a developer.

What a developer needs is info, without it, he will not be able to help.

I've posted logs, now your turn.

Adding the following lines in your /etc/modprobe.d/options would be a good start:

options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1

Then post the lines of /var/log/syslog and /var/log/messages around the disconnect event.

Better post them somewhere on a web page or a pastebin.

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#19 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

I hope this isn't too off topic but I wanted to add that I've found disconnects less problematic using myth-tv if I turn active EIT. It will still collect EIT when you watch/record TV but I find thats sufficient.

Before I did this I was getting an awful lot of disconnects, I switched to 2.6.24.3-12.fc8 when I upgraded to myth 0.21, using v4l repo. Now they are fewer and if it does happen then it will recover as soon as the tuners are no longer in use because myth releases them. Eg live tv -> disconnect -> quite live tv -> go back, it works. dmesg shows that the card has been restarted. Beats a script to restart the backend (which I used to use) when it disconnects.

Perhaps that information will make someone else's life less painful :)

On an somewhat unrelated note, I was wondering about the firmware. Am I right in thinking this is closed-source (from Hauppauge)? Could this mess be caused by the firmware falling over -> device dies -> usb disconnect or other symptoms (like losing a tuner) depending on how the USB layer responds? Not that I have a clue..

Chris.

PS I might have got passive/active muddle up, you want the setting that *doesn't* cause the card to be perpetually in use.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#20 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 8 lines · Chris Simmons

On an somewhat unrelated note, I was wondering about the firmware. Am I
right in thinking this is closed-source (from Hauppauge)? Could this mess be caused by the firmware falling over -> device dies -> usb disconnect or other symptoms (like losing a tuner) depending on how the
USB layer responds? Not that I have a clue..

There is certainly a link with the firmware.

Patrick had solved issues by releasing a new version.

This is why it is so important that he gets involved as soon as he can find time.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#21 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 23 lines · Nicolas Will
Quoted 8 lines · Chris Simmons

On an somewhat unrelated note, I was wondering about the firmware. Am I
right in thinking this is closed-source (from Hauppauge)? Could this mess be caused by the firmware falling over -> device dies -> usb disconnect or other symptoms (like losing a tuner) depending on how the
USB layer responds? Not that I have a clue..

There is certainly a link with the firmware.

Patrick had solved issues by releasing a new version.

This is why it is so important that he gets involved as soon as he can find time.

Nico

Quoted 5 lines

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Tried to collect some info from logs.
messages:
http://pastebin.com/f5cc1bc26
syslog:
http://pastebin.com/f402477c9
debug:
http://pastebin.com/f187de73a

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#22 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 31 lines · Patrik Hansson
Quoted 23 lines · Nicolas Will
Quoted 8 lines · Chris Simmons

On an somewhat unrelated note, I was wondering about the firmware. Am I
right in thinking this is closed-source (from Hauppauge)? Could this mess be caused by the firmware falling over -> device dies -> usb disconnect or other symptoms (like losing a tuner) depending on how the
USB layer responds? Not that I have a clue..

There is certainly a link with the firmware.

Patrick had solved issues by releasing a new version.

This is why it is so important that he gets involved as soon as he can find time.

Nico

Quoted 5 lines

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Quoted 8 lines

Tried to collect some info from logs.
messages:
http://pastebin.com/f5cc1bc26
syslog:
http://pastebin.com/f402477c9
debug:
http://pastebin.com/f187de73a

Should have added that the mythfrontend was not watching tv.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#23 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Patrik Hansson
Quoted 8 lines · Patrik Hansson

Tried to collect some info from logs.
messages:
http://pastebin.com/f5cc1bc26
syslog:
http://pastebin.com/f402477c9
debug:
http://pastebin.com/f187de73a

This is missing a bit of context.

And I see no disconnect there.

The mt2060 i2c read/write errors are, I think, a by-product of something else, and not the real problem. A disconnect happens, then you see the mt2060 i2c error, not the other way around.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#24 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 20 lines · Nicolas Will
Quoted 8 lines · Patrik Hansson

Tried to collect some info from logs.
messages:
http://pastebin.com/f5cc1bc26
syslog:
http://pastebin.com/f402477c9
debug:
http://pastebin.com/f187de73a

This is missing a bit of context.

And I see no disconnect there.

The mt2060 i2c read/write errors are, I think, a by-product of something else, and not the real problem. A disconnect happens, then you see the mt2060 i2c error, not the other way around.

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

hmm, ok this is odd.
I searched my entire syslog and messages and the only disconnect i have is from now during the reboot to get the tuner back.

So i have the following:
This morning everything is fine.
In the afternoon i loose a tuner, restarting mythtv-backend and so on does not bring it back.
I reboot and tuner comes back.
I check the logs and have 0 disconnects.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#25 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 11 lines · Patrik Hansson

hmm, ok this is odd.
I searched my entire syslog and messages and the only disconnect i have is from now during the reboot to get the tuner back.

So i have the following:
This morning everything is fine.
In the afternoon i loose a tuner, restarting mythtv-backend and so on does not bring it back.
I reboot and tuner comes back.
I check the logs and have 0 disconnects.

You have another problem.

You lose a tuner.

I get a card that disconnects completely, I lose both tuners and the remote, and get a flood of mt2060 i2c errors, but after the disconnect.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#26 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 15 lines · Nicolas Will
Quoted 11 lines · Patrik Hansson

hmm, ok this is odd.
I searched my entire syslog and messages and the only disconnect i have is from now during the reboot to get the tuner back.

So i have the following:
This morning everything is fine.
In the afternoon i loose a tuner, restarting mythtv-backend and so on does not bring it back.
I reboot and tuner comes back.
I check the logs and have 0 disconnects.

You have another problem.

Quoted 9 lines

You lose a tuner.

I get a card that disconnects completely, I lose both tuners and the remote, and get a flood of mt2060 i2c errors, but after the disconnect.

Nico

Oh, ok.
I thought they all were the same, my mistake.
wonder if anyone else on the list have made the same mistake, if so please let me know (in a new tread or something).
I´ll shut up now.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#27 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

I've got one of these (which is described on it's mythTV wiki page as "fully and reliably supported") in a server that I'm trying to use as a mythtv backend. It seems I have become one of the many people having problems with this card and linux. mythtv tells me it can't get a channel lock, and dmesg tells me:

usb 3-1: USB disconnect, address 2
mt2060 I2C write failed
dvb-usb: error while stopping stream.

Interestingly, trying to run lsusb at this point seems to get stuck inside a system call or something because it never exits and kill -9 doesn't kill it. Restarting mythbackend gets everything back.

This is on kernel 2.6.24-gentoo-r3, with hardware:
Gigabyte G33-DS3R motherboard (Intel G33 chipset) Intel Q6600
2GB RAM (dual channel DDR2-800)

I'm using the dvb-usb-dib0700-1.10.fw firmware.

I saw somewhere on the archives that someone found the problem went away with the following options to modprobe:
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1

Problem hasn't gone away (but seems less frequent), and I figure someone here could use the debugging data so here's the relevant part of my syslog:
http://pastebin.com/f34ed8e20
(disconnect even is pretty much at the top, and down the bottom is where I restarted mythbackend).

Ian Cullinan

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#28 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Hi,

it's the the kernel version that causes the problem, you should compile it yourself or get it from gentoo somehow.
I Think issue affects all USB-DVB-T users with kernel 2.6.24

see this post:
https://bugs.launchpad.net/ubuntu/+bug/209603

or

this list (solved post)

-antti-

2008/3/30, Ian Cullinan <[email protected]>:

Quoted 51 lines

I've got one of these (which is described on it's mythTV wiki page as "fully and reliably supported") in a server that I'm trying to use as a mythtv backend. It seems I have become one of the many people having problems with this card and linux. mythtv tells me it can't get a channel lock, and dmesg tells me:

usb 3-1: USB disconnect, address 2
mt2060 I2C write failed
dvb-usb: error while stopping stream.

Interestingly, trying to run lsusb at this point seems to get stuck inside a system call or something because it never exits and kill -9 doesn't kill it. Restarting mythbackend gets everything back.

This is on kernel 2.6.24-gentoo-r3, with hardware:
Gigabyte G33-DS3R motherboard (Intel G33 chipset) Intel Q6600
2GB RAM (dual channel DDR2-800)

I'm using the dvb-usb-dib0700-1.10.fw firmware.

I saw somewhere on the archives that someone found the problem went away with the following options to modprobe:

options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1

Problem hasn't gone away (but seems less frequent), and I figure someone here could use the debugging data so here's the relevant part of my syslog:
http://pastebin.com/f34ed8e20
(disconnect even is pretty much at the top, and down the bottom is where I restarted mythbackend).

Ian Cullinan

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Signature · 1 line
-Antti-

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#29 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 5 lines · On Monday 31 March 2008 20:44:50 Antti Luoma wrote:

Hi,

it's the the kernel version that causes the problem, you should compile it yourself or get it from gentoo somehow.
I Think issue affects all USB-DVB-T users with kernel 2.6.24

Not so.

I've been running Nova T-500 for three weeks with 4 disconnects in the first 24 hours but none since on a stock debian 2.6.24 kernel

Quoted 2 lines

see this post:
https://bugs.launchpad.net/ubuntu/+bug/209603

I hope this solves the problem others seem to be plagued with, but I'm puzzled as to why it's so stable here

Andy

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#30 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 11 lines · Andy Carter
Quoted 5 lines · On Monday 31 March 2008 20:44:50 Antti Luoma wrote:

Hi,

it's the the kernel version that causes the problem, you should compile it yourself or get it from gentoo somehow.
I Think issue affects all USB-DVB-T users with kernel 2.6.24

Not so.

I've been running Nova T-500 for three weeks with 4 disconnects in the first 24 hours but none since on a stock debian 2.6.24 kernel

Has the patch been applied already to the stock debian kernel? The code was committed early in the month (March 8, IIRC). Ubuntu is in kernel freeze for the next release, so it's possible it just didn't make the cutoff.

Quoted 9 lines
Quoted 4 lines

see this post:
https://bugs.launchpad.net/ubuntu/+bug/209603

I hope this solves the problem others seem to be plagued with, but I'm puzzled as to why it's so stable here

Andy

There seems to be a couple of common factors in the problem reports -- marginal or poor signal and using active EIT to get the programme guide. My signal hovers around 52-64 percent, with a booster. I think my antenna need replacing. My disconnects reduced quite a bit when I turned off the Active EIT setting, although i still get disconnected frequently.

Then again, maybe it's just the alignment of the planets out your way...

-Eamonn

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#31 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

In reply to Patrik Hansson
Quoted 4 lines · Patrik Hansson

Linux IKA 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
Not stable at all here, got 2 disconnects in 2 hours.
So it can't just be the kernel.

Didn't you say that you are running Hardy, but downgraded the kernel?

If so, maybe we should look at the user space.

The dvb-utils may be fairly old in Ubuntu.

Can the persons experiencing disconnects post:

Distro
distro version
kernel version (uname -a)
dvb-utils version

I'll start:

Ubuntu
Hardy (8.04)
Linux favia 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux
dvb-utils 1.1.1-3

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#32 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 32 lines · Nicolas Will
Quoted 4 lines · Patrik Hansson

Linux IKA 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
Not stable at all here, got 2 disconnects in 2 hours.
So it can't just be the kernel.

Didn't you say that you are running Hardy, but downgraded the kernel?

If so, maybe we should look at the user space.

The dvb-utils may be fairly old in Ubuntu.

Can the persons experiencing disconnects post:

Distro
distro version
kernel version (uname -a)
dvb-utils version

I'll start:

Ubuntu
Hardy (8.04)
Linux favia 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux
dvb-utils 1.1.1-3

Quoted 9 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Ubuntu
7.10
Linux IKA 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux dvb-utils ?

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#33 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

Quoted 7 lines · Nicolas Will

Can the persons experiencing disconnects post:

Distro
distro version
kernel version (uname -a)
dvb-utils version

Fedora Core
release 8 (Werewolf)
Linux chimera 2.6.24.3-34.fc8 #1 SMP Wed Mar 12 18:17:20 EDT 2008 i686 athlon i386 GNU/Linux
dvb-utils ?

Glen

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#35 lore raw

Re: [linux-dvb] Now with debug info - Nova-T-500 disconnects - They are back!

ah, ok.
I compiled it from linuxtv.org, how do i see what version ? But wy is that important ? I only got it so i could use femon.

Quoted 10 lines · Nicolas Will
Quoted 4 lines · Glen Robson
Quoted 4 lines

Distro
distro version
kernel version (uname -a)
dvb-utils version

dvb-utils are the tools like femon, tzap, etc... the package can be called dvb-apps too.

Quoted 8 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#36 lore raw
In reply to Nicolas Will
Quoted 2 lines · On Friday 21 March 2008 22:51:50 Nicolas Will wrote:

It may be very well linked to the remote, I was recording anything when this one struck, just using the remote.

I've been running a Nova-T500 for a week and more than 12 hours per day now on standard Debian Testing kernel 2.6.24-1-686 and Tobias Grimm's ctvdr 1.5.18-1ctvdr1 (thanks Tobias for all the vdr bits of yours I've been using over the last few years) and have seen 4 disconnects over that time.

3 of those disconnects have occurred while changing channels using the remote (mceusb2)

Andy

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#37 lore raw
In reply to Nicolas Will
Quoted 5 lines · Nicolas Will

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using 2.6.24, 64-bit.

Just thought I'd add, in case anyone was wondering, that I'm still not having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. MythTV multirec with eit scanning enabled.
One or two I2C read failed a day in the kernel log, and an occasional I2C write failed.

And no, haven't got around to going through the 2.6.22 vs 2.6.23 diffs yet.

Regards,
Ivor.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#38 lore raw
Quoted 6 lines · Ivor Hewitt
Quoted 3 lines · Nicolas Will

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using

2.6.24,

Quoted 8 lines
Quoted 2 lines

64-bit.

Just thought I'd add, in case anyone was wondering, that I'm still not
having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. MythTV multirec with eit scanning enabled.
One or two I2C read failed a day in the kernel log, and an occasional I2C write failed.

That was exactly my situation before upgrading my system, which brought the new kernel version.

Now, with 2.6.24, the disconnects are back with a vengeance, just as it was nearly a year ago.

I hope that the logs provided will help shed a light on this.

If not, I'm ready to turn debug on on all I can, even if it means generating gigs of logs.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#39 lore raw

A wild guess (bash me on the head if I'm wrong), but when you switched kernel, did you do 'make distclean' in your v4l-dvb directory? Unless you do, the code will keep compiling (and installing) for the previous kernel, and your new kernel will only use the stock drivers. That would explain why you're seeing disconnects again. I made that mistake once...

// J

Quoted 27 lines · Nicolas Will
Quoted 6 lines · Ivor Hewitt
Quoted 3 lines · Nicolas Will

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using

2.6.24,

Quoted 8 lines
Quoted 2 lines

64-bit.

Just thought I'd add, in case anyone was wondering, that I'm still not
having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. MythTV multirec with eit scanning enabled.
One or two I2C read failed a day in the kernel log, and an occasional I2C write failed.

That was exactly my situation before upgrading my system, which brought the new kernel version.

Now, with 2.6.24, the disconnects are back with a vengeance, just as it was nearly a year ago.

I hope that the logs provided will help shed a light on this.

If not, I'm ready to turn debug on on all I can, even if it means generating gigs of logs.

Quoted 7 lines

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#40 lore raw
Quoted 1 line · Jonas Anden

A wild guess (bash me on the head if I'm wrong),

Plonk! ;o)

Quoted 7 lines

but when you switched
kernel, did you do 'make distclean' in your v4l-dvb directory? Unless you do, the code will keep compiling (and installing) for the previous kernel, and your new kernel will only use the stock drivers. That would
explain why you're seeing disconnects again. I made that mistake once..

I did a distclean, as usual.

Then I did better, I put the whole tree on the side and got a brand new one.

And still...

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#41 lore raw
Quoted 4 lines · Nicolas Will
Quoted 1 line · Jonas Anden

A wild guess (bash me on the head if I'm wrong),

Plonk! ;o)

I'll take that back.

And apologise.

Deeply.

Quoted 11 lines
Quoted 3 lines

but when you switched
kernel, did you do 'make distclean' in your v4l-dvb directory?

Unless

Quoted 1 line

you do, the code will keep compiling (and installing) for the

previous

Quoted 4 lines

kernel, and your new kernel will only use the stock drivers. That would
explain why you're seeing disconnects again. I made that mistake once..

Quoted 5 lines

I did a distclean, as usual.

Then I did better, I put the whole tree on the side and got a brand new
one.

Because I'm desperate, I did a make distclean, a make and a sudo make install.

And I rebooted.

And the machine is still up with no breakage.

Ah...

I would have put my kids on the line about what I said I did.

But obviously...

And I did so many things on the box that the shell history does not go back long enough for me to check.

But obviously, there is no need to check.

To err is human, but, I was pretty certain. It is normally my usual process. Plus, for the weirdest reasons, I was eager to put myself in supposedly 2.6.24 problems.

So I hereby put myself in a position where you can bash me on the head, repeatedly.

But thanks all the same for showing me the light!

Nico
assumes the plonking position

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#42 lore raw
Quoted 11 lines · Nicolas Will
Quoted 4 lines · Nicolas Will
Quoted 1 line · Jonas Anden

A wild guess (bash me on the head if I'm wrong),

Plonk! ;o)

I'll take that back.

And apologise.

Deeply.

ah, no, I take that back as well.

Plonk!

Quoted 33 lines
Quoted 13 lines
Quoted 5 lines

but when you switched
kernel, did you do 'make distclean' in your v4l-dvb directory?

Unless

Quoted 1 line

you do, the code will keep compiling (and installing) for the

previous

Quoted 4 lines

kernel, and your new kernel will only use the stock drivers. That would
explain why you're seeing disconnects again. I made that mistake once..

Quoted 5 lines

I did a distclean, as usual.

Then I did better, I put the whole tree on the side and got a brand new
one.

Because I'm desperate, I did a make distclean, a make and a sudo make install.

And I rebooted.

And the machine is still up with no breakage.

Ah...

I would have put my kids on the line about what I said I did.

But obviously...

Quoted 8 lines

And I did so many things on the box that the shell history does not go back long enough for me to check.

But obviously, there is no need to check.

To err is human, but, I was pretty certain. It is normally my usual process. Plus, for the weirdest reasons, I was eager to put myself in supposedly 2.6.24 problems.

I got a disconnect, again.

So I did not forget to distclean originally.

Crap, I wish it had been so simple.

Back to 2.6.24 causing issues.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#43 lore raw
In reply to Ivor Hewitt
Quoted 19 lines · Ivor Hewitt
Quoted 5 lines · Nicolas Will

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using 2.6.24, 64-bit.

Just thought I'd add, in case anyone was wondering, that I'm still not having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. MythTV multirec with eit scanning enabled.
One or two I2C read failed a day in the kernel log, and an occasional I2C write failed.

And no, haven't got around to going through the 2.6.22 vs 2.6.23 diffs yet.

Regards,
Ivor.

Quoted 5 lines

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I downloaded the 2.6.22.19 from kernel.org (that is vanilla right?) and compiled it on my Ubuntu 7.10
Didn't help. So it can´t be just the kernel that does it.It must be something more than that.

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#44 lore raw
In reply to Ivor Hewitt
Quoted 5 lines · Ivor Hewitt
Quoted 3 lines · Nicolas Will

Guys,

I have upgraded my system to the new Ubuntu (8.04 Hardy), using

2.6.24,

Quoted 8 lines
Quoted 2 lines

64-bit.

Just thought I'd add, in case anyone was wondering, that I'm still not
having any problems with vanilla 2.6.22.19 and current v4l-dvb tree. MythTV multirec with eit scanning enabled.
One or two I2C read failed a day in the kernel log, and an occasional I2C write failed.

The more I look at logs, the more I believe that the i2c errors are not the root of the problem.

They are just a consequence of something failing somewhere else.

Nico

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb