[mythtv-users] Newest KDE & Geforce 4 mmx 440 tv-out

[Joseph A. Caputo]

On Thursday 08 April 2004 12:22, RJM Bardoel wrote:
> <-----Original Message-----
> <From: Joseph A. Caputo [mailto:jcaputo1 at comcast.net]
> <Sent: donderdag 8 april 2004 15:42
> <To: Discussion about mythtv
> <Subject: Re: [mythtv-users] Newest KDE & Geforce 4 mmx 440 tv-out
> <
> <On Thursday 08 April 2004 08:14, RJM Bardoel wrote:
> <> I have mythtv 0.14 and fedora I running on a PIII 550 Mhz, 512
> SDRAM, <> PVR 350 and a Geforce 4 mmx 440. I know there have been
> some issues <> about this in the past, but i can't find the right
> solutions <> anywhere. When i run my pvr through my tv, everything
> goes perfect, <> but when X starts KDE hangs en doesn't start kicker.
> I have done <> everything, but i can't solve the problem. I heard
> that a lot of <> users use this card, so i hope that someone has got
> the right <> solution!
> <
> <I used to have the same problem on RH8; KDE would hang trying to
> start <kicker.  The workaround is to get a shell and kill kicker (or
> the <kdeinit process responsible for starting kicker); then KDE
> startup <continues normally.  You could then start kicker manually
> from a <terminal and it would come up fine.
> <
> <The odd thing was this was only a problem when I was running on a
> remote <XDMCP terminal, so wasn't the Nvidia card or driver at fault
> (the <remote display was a PowerMac)
> <
> <I never did solve the problem, and I've since upgraded my Myth box
> to <FC1.  I also now have a separate file, web & mail server, so no
> need to <run KDE on my Myth box.  A previous post I read suggested
> the problem <might have been related to a missing X-extension on the
> display. <Sounds plausible, at least.
> <
> <-JAC


> I have done that, but now he stops at the end. Kicker starts fine and
> at the end I can see the desktop etc. perfect, but I can only move my
> mouse and kde hangs. When I look through ssh too my processes, X is
> having 99% of the proc. capacity (PIII 550 Mhz). I've waited a long
> time, but the situation doesn't stop. Could this problem be related
> too the nvidia driver (nvidia-graphics4363) ?
>


Beats me.  This is getting way off-topic, though.  This sounds like a 
problem for the KDE list.

-JAC