I finally found some time to look at this again; after a re-recompile of the 
kernel, It now suddenly seems to have a /dev/fb, so probably some hick-up 
somewhere.

I have however run into a different problem. When I start the examples, I get 
an error. here is for instance the output of df_fire:

-----------------------------
       ---------------------- DirectFB v0.9.25 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2004  convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2007-03-24 12:05)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 24756)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 24757)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:853]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(!) Direct/Modules: Unable to dlopen 
`/usr/lib/directfb-0.9.25/gfxdrivers/libdirectfb_unichrome.so'!
    --> /usr/lib/directfb-0.9.25/gfxdrivers/libdirectfb_unichrome.so: undefined 
symbol: cos
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated 
media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
-----------------------------

See the "undefined symbol: cos" there ? that seems to come on every demo. The 
fire is actually showing on the display, but if I run df_dok, I get:

------------------------------
       ---------------------- DirectFB v0.9.25 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2004  convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2007-03-24 12:05)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 24769)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 24770)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:853]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(!) Direct/Modules: Unable to dlopen 
`/usr/lib/directfb-0.9.25/gfxdrivers/libdirectfb_unichrome.so'!
    --> /usr/lib/directfb-0.9.25/gfxdrivers/libdirectfb_unichrome.so: undefined 
symbol: cos
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated 
media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
(*) Direct/Interface: Loaded 'PNG' implementation of 'IDirectFBImageProvider'.
df_dok.c <1177>:
        (#) DirectFBError [dfb->CreateFont( dfb, fontfile, &desc, &bench_font 
)]: No (suitable) implementation found!
 (!!!)  *** WARNING [Application exited without deinitialization of DirectFB!] 
*** [core.c:741 in dfb_core_deinit_check()]
------------------------------


Which then stops. Also, "mplayer -vo directfb", which is my main goal, gives me:


-----------------------------
MPlayer 1.0rc1-4.1.1 (C) 2000-2006 MPlayer Team
CPU: VIA Esther processor 1200MHz (Family: 6, Model: 10, Stepping: 9)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2

Playing alexander.wmv.
ASF file format detected.
VIDEO:  [WMV1]  176x144  24bpp  1000.000 fps    0.0 kbps ( 0.0 kbyte/s)
Clip info:
 name: Untitled
 author:
 copyright: ©
 comments:
Error opening/initializing the selected video_out (-vo) device.


Exiting... (End of file)
-----------------------------


Any idea what is going wrong ?

TIA!

Harry

  ----- Original Message ----- 
  From: Mark Adams 
  To: Harry Mulder 
  Cc: [email protected] 
  Sent: Monday, March 12, 2007 15:11
  Subject: Re: [directfb-users] viafb not starting up


    Installation goes fine, but I don't get a /dev/fb device; the only thing
    dmesg states is the "viafb.. initializing" line, nothing more. I've tried 
    both in-kernel as well as module compilation. Both give the same results.

  Sounds like the driver isn't finding a device it recognises.  Others have 
used the driver for the CN700 I think so I'm slightly puzzled. 

  Assuming the driver will work with your hardware, it may just need an 
additional PCI ID adding to its table.  Or it may need to be extended.

  What do you get if you type:
  lspci -vns 1:0


  M.



------------------------------------------------------------------------------


  _______________________________________________
  directfb-users mailing list
  [email protected]
  http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to