This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Supposedly the problem is not supposed to occur with a vanilla kernel,
but I get exactly the same issue when I run a vanilla 2.6.32.27 kernel,
compiled from kernel.org sources.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
... and for that matter, also on the 2.6.35-02063509-generic kernel from
the Maverick mainline builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/459523
Title:
regression: support for dvico dual
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I just did a test on the vanilla kernel
https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=showredirect=KernelMainlineBuilds
and the problem does not occur so the problem is in the ubuntu fixes
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You
I just tested on a mainline kernel from
https://wiki.ubuntu.com/Kernel/MainlineBuilds using v2.6.32.21.9-lucid/
and the problem does not occur so the problem is in the ubuntu fixes it
seems
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received
Hi Barry,
Indeed, the problem was fixed upstream a long time ago. I don't take
any responsibility for making sure the individual distributions
properly merge the patches, so if you have issues with some
distribution you really need to take it up with the distro maintainer.
Cheers,
Devin
On
This is the bug report is filed against the ubuntu kernel feel free to
unsubscribe from this bug and hopefully an ubuntu kernel maintainer will
take on the task of getting the fixes into the ubuntu kernel
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
I still get this problem when ubuntu updates its kernel however
recompiling v4l-dvb tree fixes it however this is frustrating to do
everytime a kernel upgrade happens should this fix be in the mainline
ubuntu kernel?
--
regression: support for dvico dual digital 4 card
I can confirm the problem is on lucid however fresh compile of v4l-dvb
tree fixes the problem
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I was having this problem on Karmic.
This morning I upgraded to the latest version of Karmic which fixed the
problem, then I upgraded to Lucid and it is back again.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification
Rob's fix went in to v4l as this commit:
http://git.linuxtv.org/v4l-
dvb.git?a=commit;h=0bc3518019f917a370935055f07698a4e9b3ea20
It was added to the karmic kernel git in January:
Yeah. I think this should be closed as fixed.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I see we have just got linux 2.6.31_16, but I cannot see the patch in
the changes list. Does anyone know if the patch made it? I don't have
reliable net access at my myth box, so I cannot easily try it to see.
--
regression: support for dvico dual digital 4 card
How are you going getting the patch into v4l, Robert? It would be good
to have these devices powered down when not required, because they are
hungry little fellows.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification
The patch has been merged into the v4l-dvb mercurial repository and has
also been merged into the kernel tree (for the upcoming 2.6.32 release).
I have also been notified that it is queued in the 2.6.31-stable tree,
not sure if a later karmic kernel will pick this up or whether we will
need to
I received notification that it was also merged into 2.6.31 stable, so
we should be good to go for Karmic.
Devin
On Tue, Dec 1, 2009 at 10:36 PM, Robert Lowery rglow...@exemail.com.au wrote:
The patch has been merged into the v4l-dvb mercurial repository and has
also been merged into the
Excellent thread. Comment 16 solved it for me - although I created
/etc/modprobe.d/mod_dvb.conf (instead of options).
using:
karmic 64 (2.6.31-14-generic #48-Ubuntu SMP)
firmware
latest v4l mercurial repository (as of 9-Nov-2009), commented
CONFIG_DVB_FIREDTV as above
Previously I had
Hi,
If it helps I can confirm that the workaround works fine for me. I meant to
post my dmesg outputs, but have taken so long to do so (apologies for that) it
seems that I missed the boat.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received
Barry,
What were you applying the patch to? The above patch was against the
current tip of the v4l-dvb mercurial repository. If it is against
something else (like the karmic kernel source?), you might need to apply
the patch by hand.
-Rob
--
regression: support for dvico dual digital 4 card
Robert,
I tried both and got the same error. It may have been something to do with the
way I was formatting the patch. However I just tried Devin's tree from the
mailing list and it doesn't fix my problem.
http://kernellabs.com/hg/~dheitmueller/misc-fixes-4
--
regression: support for dvico
djh - thanks to Vince and Robert for posting to the linux-media mailing
list. I know what the problem is (the zl10353 is wedging the i2c bus
because an i2c gate is not used on those boards) and will see about
committing a fix in the next couple of days.
--
regression: support for dvico dual
This is the proper fix that gets things going without workarounds. I'm
working on getting it merged upstream, but that will take a while to go
from the v4l-dvb tree - 2.6.31 stable kernel series. Hope you find it
useful until it makes its way into a karmic kernel.
-Rob
diff -r c57f47cfb0e8
i was wondering if anyone has a work around with karmic as the whole OS
become unusuable with this tuner and kernel 2.6.31 and compiling v4l-dvb
does not seem to fix it yet?
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug
This is a kernel bug, shifting to the right package.
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, I managed to bisect this issue being introduced by
http://linuxtv.org/hg/v4l-dvb/rev/7276a5854219 which puts the tuner into
sleep mode when no used.
At first glance, it looked like I would be able to use the no_poweroff=1
tuner-xc2028 kernel module parameter to workaround this issue, but the
Confirming that adding
options dvb-core dvb_powerdown_on_sleep=0
to /etc/modprobe.d/options.conf fixes it for me also.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which
The latest working kernel is the stock 2.6.28-15-generic one from
jaunty, although I had to symbolically line the old /dev entries to the
new ones expected by karmic.
I am attempting to bisect the v4l-dvb tree now to see when the issue was
introduced, but might take a while as it seems lots of
Also seen here with my v1 Dvico Dual digital 4. Works fine with my
Intrepid 2.6.27-15-generic kernel.
** Changed in: linux-meta (Ubuntu)
Status: New = Confirmed
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification
Logs from a working kernel:
[ 34.125372] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm
state.
[ 34.126593] dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
[ 34.156813] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual
Digital 4)
Hi Damien
are you using stock ubuntu or did you compile more recent v4l-dvb
drivers yourself?
Could you post dmesg output from booting up the working version?
It would be particularly helpful if you could boot, then try to tune the
receiver with dvbscan or equivalently try to watch live tv in
I was able to get 2.6.31-14-generic to boot. I did not try tuning with this, I
doubt it will make any difference.
I tried building the v4l tree:
$ cd v4l-dvb
$ make update; make ;
The build dies on the FiredTV driver for some reason, so turn it off.
$ sed -ie
** Attachment added: strace of dvbscan, with 2.6.31-14-generic + v4l tip
drivers
http://launchpadlibrarian.net/34749121/log.dvbscan.20091031
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a
I too have experienced this issue. I run 2.6.27-11-generic with no
dramas, but karmic beta was no good- same error as is described above.
Dvico dual digital 4.
lsusb:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
I have exactly the same issue on 9.10 (karmic) with my dvico dual
digital 4 cards. Previously working perfectly on 9.04 (jaunty)
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Hi Bob
it would probably help people processing this report quite a bit to have the
output of a working Jaunty system.
Could you post 'dmesg' from the following sequence of events:
* disable mythtv if you have it installed (rename the /etc/init.d scripts)
* shut down, pull the power.
* boot
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34302610/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34302611/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/34302612/ArecordDevices.txt
and kept the syslog of what occured then (syslog.dvbscan).
it stops when I typed 'halt'.
** Attachment added: syslog.dvbscan
http://launchpadlibrarian.net/34306522/syslog.dvbscan
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this
I tried stracing the dvbscan, see attached (log.dvbscan)
** Attachment added: log.dvbscan
http://launchpadlibrarian.net/34306455/log.dvbscan
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a
details of the working system:
it's the same hardware, with an earlier version of ubuntu installed on a
separate hard disk.
$ uname -a
Linux wellington 2.6.24-23-rt #1 SMP PREEMPT RT Wed Apr 1 23:40:34 UTC 2009
i686 GNU/Linux
The kernel I am using is linux-image-2.6.24-23-rt, package version
regarding the rmmod/modprobe experiment I described. The module is of
course dvb_usb_cxusb, not 'cxusb'.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/etc/lsb-release for working system:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu 8.04.3 LTS
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of
42 matches
Mail list logo
