Re: nvidiafb *almost* works

"John W. Cocula" <[email protected]>
Newsgroups gmane.comp.games.mame.advancemame.user
Message-ID <[email protected]>
I'm about to give up on using the new nvidiafb driver (and hence the card
or Linux), but I'm making one last plea for advice.

Like I said, the framebuffer driver works with fbset with no problem, but
advcfg and advv both exit with a Segmentation fault.

I built them with debugging support and run advcfg under gdb so I could
see the stack backtrace.  The trap occurs in the inline function
crtc_is_nvsync (crtc.h, line 149), when using the crtc pointer.  Obviously
the pointer is bad, but how does this happen?

I have already built a different system using the rivafb framebuffer
driver and it works wonderfully.

Any thoughts before I pack it in?

Thanks!!!

John


> I patched the nvidiafb framebuffer driver into a 2.6.11 kernel and it
> almost works.  fbset works.  When I run advcfg, it comes up, but as soon
> as it tests a low resolution, it exits with a Segmentation fault, leaving
> the display in the low resolution.  The same happens with advv.
>
> I'm surprised the failure doesn't show itself as a kernel Oops.  The
> rivafb does not work with this GeForce FX 5200 card.
>
> Anyone else have experience with the new nvidiafb driver and ideas about
> what can be done to make it work properly?  I'm using Mandrakelinux 10.1,
> but with 2.6.11 kernel built from their source RPM.
>
> Thanks,
> John
>
>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Unsubscribe at https://lists.sourceforge.net/lists/listinfo/advancemame-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.