On Sun, Jul 17, 2005 at 05:10:33PM -0500, Joe Henley wrote:
>
> I did have MythTV working pretty well. Then I did a big update to
> ivtv 0.3.6w, to FC3 version 2.6.11-1.35_FC3, to lirc 0.7.1-46, to
> mplayer 1.0-45. I'm running MythTV 0.18.1.
>
> After a couple of problems I could noodle
I just received my PVR 500 today, and I jumped right in with 0.3.2z.
It works *almost* flawlessly, with the following exception: when I try
to select the svideo/composite inputs, the video comes through fine,
but the audio is muted. If I try to switch back to the tuner, I get
both audio and video
On Sat, Jan 15, 2005 at 08:25:16PM -, John Harvey wrote:
> That all looks ok other than the virtual terminal has been switched away
> from the one that X is using (I think)
>
right. I'm a moron - my fluxbox configuration was b0rked. Never
mind.
-Tim
--
Morals? I eat communism and $h!t A
For reasons I haven't figured out, X.org no longer starts up using the
tv-out on the pvr350 and version 0.8 of ivtvdev_drv.o. At some point
last night, the screen locked up and can't be brought back to life,
even after a cold boot. I've attached the xorg.0.log, but it seems
the culprit is:
(EE)
On Mon, Jan 10, 2005 at 11:38:58PM +, Oliver Gorwits wrote:
> On Wed, 5 Jan 2005 21:33:48 -
> "John Harvey" <[EMAIL PROTECTED]> wrote:
>
> > Attached is a pre-compiled version of the v0.8 driver. (See previous mail
> > for description of fix)
>
> Hi John,
>
> Please could you just confir
I've attached the relevent dmesg output after loading ivtv from 0.3.2b
running on FC3 (kernel 2.6.9-1.724). No problems using ivtv 0.3.2a,
however (which works rather well so far).
Let me know if higher debugging levels/etc. would help.
Regards,
Tim
--
Morals? I eat communism and $h!t America
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 whi
I was able to figure out a workaround for the console being taken over
by ivtv-fb, thanks to a pointer from David Smith.
Just adding vga=792 to the kernel options (in FC3, I also removed the
rhgb option) forces ivtv-fb to use fb1, and leaves fb0 alone.
Hope this saves people some headaches.
Rega
On Wed, Dec 08, 2004 at 09:00:09AM +, John Harvey wrote:
> Have you tried adding vide:vc:0-0 to your boot
> configuration? There are some notes in the top of
> ivtv-osd.c under the heading A note on unloading the
> fb driver.
Sorry it took me awhile to get to this, but I did try this with no
l
On Tue, Dec 07, 2004 at 08:24:14PM -, John Harvey wrote:
> Attached is a patch for people to try.
>
tried it out against 0.3.1z, and didn't get the oops, but the console
still locks up and attempts to remove ivtv-fb from the running kernel
yield the "module is in use" message. I've attached
On Tue, Dec 07, 2004 at 08:59:18AM +, John Harvey wrote:
> Just a quick update. I think i understand the problem
> though i couldn't reproduce it with my 2.6.9 or 2.6.10
> kernels but that is probably down to kernel
> configuration.
> Anyway looking at the stack trace there are call being
> ma
On Thu, Dec 02, 2004 at 01:58:51PM -0600, Clay Fandre wrote:
> Anyone know why I get a kernel oops when I load ivtv-fb?
>
> I'm running Fedora Core3 and it's a fresh install.
FWIW, I've had the same problem under FC3 - I've been using the ATrpms
packages, and tried both 0.1.10pre2 (ck100zz, from
12 matches
Mail list logo
