On Fri, 09 Jul 2004 16:30:16 -0700, Nifty Hat Mitch wrote:
> On Fri, Jul 09, 2004 at 09:42:28AM -0500, Marc Williams wrote:
>> On Thu, 08 Jul 2004 16:15:04 -0700, Nifty Hat Mitch wrote:
>>
>> > On Fri, Jul 02, 2004 at 09:52:09PM -0500, Marc Williams wrote:
>> >> On Fri, 02 Jul 2004 17:59:08 -0700, Ioan Podoleanu wrote:
>> >> > You're right, the combination nvidia-1.0-6106 with xawtv is a
>> >> > killer. For xawtv, if you use "-remote" which disables overlay
>> >> > mode, it should work. I also use -noxv which reduces the procesor
>> >> > use even further. It's not perfect, but it works for me. My line
>> >> > now is: xawtv -c /dev/video0 -remote -noxv .
>> >>
>> >> Thanks for the tip. Adding -remote -noxv does indeed provide an
>> >> acceptable workaround. I hope I can eventually get overlay mode back
>> >> though.
>> >
>> > I wonder if xawtv is making a gfx call that causes rivafb.ko to load.
>> > What if rivafb.ko was moved ...?
>>
>> Since that would be an easy test and since I am in no position to argue
>> otherwise, I tried it. It didn't work. Had the exact same freeze up as
>> previously. But thanks for the resolution attempt.
>>
>> I think I'll leave my rivafb.ko permanently renamed since it doesn't
>> seem to hurt anything...
>
> Just in case the kernel loads objects in ways that ignore the file name
> move it out of the normal dir. I have left mine in place and do not see
> lockups. I think that rivafb.ko is a distraction at this point.
[much helpful debugging tools and info clipped...]
> And lastly a kernel version check since things are stable here, mine is:
> # uname -r
> 2.6.6-1.435.2.3
Wow, talk about being overwhelmed by helpful information!
Quite frankly, I don't think I'm up to such sleuthing and debugging. The
FC2 nv driver is working adequately and I don't play any 3D so I'm ok for
now without Nvidia. I've posted my problems in the Nvidia forums, the
Redhat v4l forum and this one. I think I'll let the Nvidia, xawtv, and
xorg guys sort this one out. Thanks anyway!
