From: Nicolas Will <nico@youplala.net>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Nova-T-500 disconnects - They are back!
Date: Fri, 21 Mar 2008 22:51:50 +0000 [thread overview]
Message-ID: <1206139910.12138.34.camel@youkaida> (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
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-03-21 22:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 22:51 Nicolas Will [this message]
2008-03-22 11:24 ` [linux-dvb] Nova-T-500 disconnects - They are back! Filippo Argiolas
2008-03-22 12:54 ` Nicolas Will
2008-03-23 11:13 ` Nicolas Will
2008-03-24 8:37 ` [linux-dvb] Now with debug info - " Nicolas Will
2008-03-24 8:47 ` Nicolas Will
2008-03-24 12:06 ` Patrik Hansson
2008-03-24 16:40 ` John Veness
2008-03-24 16:47 ` Nicolas Will
2008-03-26 15:53 ` Nicolas Will
2008-03-26 17:55 ` Patrik Hansson
2008-03-26 18:10 ` Markus Rechberger
2008-03-26 18:42 ` Henrik Beckman
2008-03-26 18:51 ` Henrik Beckman
2008-03-26 20:23 ` Nicolas Will
2008-03-26 20:52 ` Patrik Hansson
2008-03-26 21:17 ` Nicolas Will
2008-03-27 8:05 ` Nicolas Will
2008-03-27 17:44 ` Henrik Beckman
2008-03-27 21:38 ` Chris Simmons
2008-03-27 22:13 ` Nicolas Will
2008-03-28 15:46 ` Patrik Hansson
2008-03-28 15:47 ` Patrik Hansson
2008-03-28 15:56 ` Nicolas Will
2008-03-28 16:36 ` Patrik Hansson
2008-03-28 16:47 ` Nicolas Will
2008-03-28 16:51 ` Patrik Hansson
2008-03-30 0:56 ` Ian Cullinan
2008-03-31 19:44 ` Antti Luoma
2008-03-31 20:07 ` Andy Carter
2008-03-31 20:15 ` Eamonn Sullivan
2008-03-26 21:22 ` Nicolas Will
2008-03-26 21:43 ` Patrik Hansson
2008-03-26 22:28 ` Glen Robson
2008-03-27 6:58 ` Nicolas Will
2008-03-27 7:50 ` Patrik Hansson
2008-03-22 12:00 ` [linux-dvb] " Andy Carter
2008-03-24 9:47 ` Ivor Hewitt
2008-03-24 10:02 ` Nicolas Will
2008-03-24 12:49 ` Jonas Anden
2008-03-24 13:36 ` Nicolas Will
2008-03-25 7:54 ` Nicolas Will
2008-03-25 11:21 ` Nicolas Will
2008-03-24 12:09 ` Patrik Hansson
2008-03-24 12:20 ` Nicolas Will
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206139910.12138.34.camel@youkaida \
--to=nico@youplala.net \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox