From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org, debian-amd64@lists.debian.org,
dancer@netfort.gr.jp
Subject: Re: [x86_64] bttv: linux 2.6.16-rc1 mplayer fails to record ALSA audio and fails tune TV.
Date: Fri, 03 Feb 2006 08:04:30 +0900 [thread overview]
Message-ID: <87ek2lmkg1.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <43E20ED5.3000401@gmail.com>
Hi,
> Junichi Uekawa wrote:
> > Hi,
> >
> > status update, it's still like this; I probably don't have much time
> > to sit around debugging this problem myself, but if anyone else has
> > met this problem and fixed it, I'd be delighted to know about it.
> >
> > Linux dancer64 2.6.16-rc1dancer-ga6df590d-dirty #1 Wed Feb 1 18:36:00 JST 2006 x86_64 GNU/Linux
> >
> >
>
> Are you referring to bugzilla 5895 ? I just closed that ticket.
>
> http://linuxtv.org/hg/v4l-dvb?cmd=changeset;node=dc3ce5a86001;style=gitweb
That sounds like a different module; I'm using 'bttv' module.
I've tried
rmmod bttv
rmmod tuner
rmmod compat_ioctl32
rmmod v4l2-common
rmmod tveeprom
rmmod videodev
rmmod ir-common
insmod v4l2-common.ko
insmod tveeprom.ko
insmod videodev.ko
insmod compat_ioctl32.ko
insmod tuner.ko
insmod ir-common.ko
insmod bttv.ko
on
$ hg log|head
changeset: 3295:02699cfc26d5
tag: tip
user: Manu Abraham <manu@linuxtv.org>
date: Thu Feb 2 07:59:47 2006 +0400
summary: bugfix [5895], return an error value
and I can reproduce the situation.
The current situation being that no images come through mencoder,
which probably means it's not
1. tuning the tuner (If there has been a i2c breakage, sounds possible)
2. getting the images
or both.
I am able to see TV through xawtv, and I am assuming that means it's
working with v4l1 compatibility layer of some sort.
regards,
junichi
--
dancer@{debian.org,netfort.gr.jp} Debian Project
prev parent reply other threads:[~2006-02-02 23:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 4:26 mencoder fails with Linux kernel from linus's git tree (2 Nov 2005) Junichi Uekawa
2005-11-10 21:40 ` [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 " Junichi Uekawa
2005-11-10 22:58 ` Mike Krufky
2005-11-11 0:05 ` Junichi Uekawa
2005-11-11 3:24 ` Michael Krufky
2005-11-11 12:06 ` Junichi Uekawa
2005-11-11 13:11 ` Michael Krufky
2005-11-11 13:29 ` Junichi Uekawa
2005-11-11 14:06 ` Hugh Dickins
2005-11-12 22:22 ` Nickolay V. Shmyrev
2005-11-13 2:54 ` Matti Aarnio
2005-11-13 4:24 ` Junichi Uekawa
2005-11-16 12:50 ` Nickolay V. Shmyrev
2005-11-16 17:47 ` Hugh Dickins
2005-12-01 0:09 ` Junichi Uekawa
2005-11-17 0:07 ` Junichi Uekawa
2005-11-11 14:21 ` Junichi Uekawa
2005-11-12 21:11 ` Ricardo Cerqueira
[not found] ` <87mzj4uoys.dancerj%dancer@netfort.gr.jp>
2005-12-19 23:10 ` [x86_64] linux 2.6.15-rc6 mplayer fails to record ALSA audio Junichi Uekawa
2006-01-14 7:33 ` Junichi Uekawa
2006-01-19 23:11 ` [x86_64] bttv: linux 2.6.16-rc1 mplayer fails to record ALSA audio and fails tune TV Junichi Uekawa
2006-02-02 9:13 ` Junichi Uekawa
2006-02-02 13:53 ` Manu Abraham
2006-02-02 23:04 ` Junichi Uekawa [this message]
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=87ek2lmkg1.dancerj%dancer@netfort.gr.jp \
--to=dancer@netfort.gr.jp \
--cc=abraham.manu@gmail.com \
--cc=debian-amd64@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=video4linux-list@redhat.com \
/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
all inboxes | Powered by JetHome®