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 thru
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 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
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
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.
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
luck
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
maded