Re: rivafb + NV17

David Liontooth <[email protected]>
Newsgroups gmane.linux.fbdev.user
Message-ID <[email protected]>
Hi Tony,

The directfb works great -- I can now play movies in the framebuffer
and the quality is as good as in x-windows (even though my fb.mode
has a depth of 8). CPU usage is below 50% (and that is running the
CPU at half speed using cpufreq), while in X it's around 75%. Very
cool actually.

A quirk in the framebuffer: if I touch the mouse while playing a movie
with mplayer, everything freezes and I have to hardboot. I can't even
ssh into the machine. I wanted the mousewheel as a way of fast
forwarding in the movie.

I'm also wondering if it's possible to tell the rivafb module to use
the right mode when loading -- at the moment it loads into 640x480
and then I use fbset to change it to 1280x854. Here's the first
entry in my /etc/fb.modes:

    #
    #   Sample video modes
    #

    #  Generated using modeline2fb, 1280x854, 85.266 MHz dotclock

    mode "fullscreen"
      geometry   1280 854   1280 26201   8
      timings    11728   240 16   31 0   256 7
      hsync low
      vsync low
    endmode

The module doesn't seem to accept mode parameters, however.

>>The main remaining annoyance is that you can't remove the rivafb module,
>>    
>>
>You can actually, as long as you don't enable the framebuffer console. This
>sequence should work:
>
>modprobe rivafb
>mplayer -vo directfb
>rmmod rivafb
>
>Of course you will only have a vga console.
>  
>
Not sure I understand -- you don't mean I can insert rivafb while
the nvidia module is still inserted? In that case I get this:


       ---------------------- DirectFB v0.9.20 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2003  convergence GmbH
        -----------------------------------------------------------

(*) Single Application Core. (with MMX support) (2004-01-20 10:18)
(*) DirectFB/misc/memcpy: using MMXEXT optimized memcpy()
(!) DirectFB/core/fbdev: Error opening `/dev/fb0'!
    --> No such device
(!) DirectFB/Core: Could not initialize 'system' core!
    --> Not supported!
(!) DirectFB/Core: Error during initialization (Not supported!)
vo_directfb2.c <315>:
        (#) DirectFBError [DirectFBCreate (&dfb)]: Not supported!

Not surprising, right? The framebuffer device /dev/fb0 is not created.
So what does it mean to use directfb without enabling the framebuffer
console?

>The rivafb driver and nv should nicely coexist.  The nvidia driver is still
>not compatible with rivafb.
>  
>
Good point, I'll try that.

Cheers,
Dave




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
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.