Does your kernel support the type 50?
tuner: tuner type not set
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
tuner: tuner type not set
This usually means that your v4l module doesn't recognize the type 50.
On Sun, 19 Dec 2004 23:34:29 -0500, Daniel Milani
ivtv: version 0.1.10 (0.1.10-48.4_pre2_ck100zz.rhfc2.at) loading
No, his doesn't, he has to read this:
http://www.gossamer-threads.com/lists/ivtv/devel/16035 , we're still
working out the kinks
On Mon, 20 Dec 2004 07:09:37 -0500, Alan Gonzalez
[EMAIL PROTECTED] wrote:
Does your kernel
What does dmesg say about the lirc detection?
did you try running lircd specifying the device manually?
On Sat, 18 Dec 2004 23:21:37 -0500, Marc Spencer [EMAIL PROTECTED] wrote:
Doubt it, I checked. And the obvious things: using locate to find the
kernel modules, irw, etc. turns up only one
hey,
i did a little more research about the mpeg1 issue.
we have to make some changes to the driver to support mpeg1.
(1) at the moment the video decoder resolution is always the same as the
resolution of the mpeg-encoder. for mpeg1 we need to (a) limit the vertical
resolution to 240 ( 288 )
Nicholas Gibson wrote:
All,
I have been setting up MythTv and have thoroughly gone
through the troubleshooting procedure. I have run
into some usability problems that from what I can see
may not be solvable and I would like to find out if
these are just things people deal with or if I should
Sorry, fixed it. Started throwing different ID's at it. On a wild
guess I tried 2:10:0 and that worked. Is this a small bug? PCI probing
shows the busid in hex, putting it in hex in xorg.conf doesn't work
but gives an error in decimal for the correct busid.
On Mon, 20 Dec 2004 20:42:15 +0100,
Ignore what I said completely. I misread the error message and it wasn't
what I was thinking it was.
I'll try to read and digest stuff properly before replying next time.
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:ivtv-devel-
[EMAIL PROTECTED] On Behalf Of Tim Fenn
On Mon, Dec 20, 2004 at 08:19:54PM -, John Harvey wrote:
kernel: ivtv: OSD: DMA xfer from 0xf6f2a2f8 of
262144 bytes failed with (-512) offset = 0x000eb2f0,
total 1225456
Is scattered throughout the logs, may have something
to do with that..
Also which version of the X
Oops, didn't realize before that my configuration was broken; but then
again, I'm just a poor guy with only 1 350 ;-)
Any idea where these are coming from? Don't tknow if they are related
to the X-driver as well. They don't seem to cause any problems but
fill up my message-buffers:
ivtv: OSD:
No that's the way it works.
This is X server code doing the work not our driver.
It did actually list it correctly for you in the line :-
(WW) ivtvdev: No matching Device section for instance (BusID PCI:2:10:0)
found
What was happening before is that it was ignoring your busid because it was
10 matches
Mail list logo
