> > Go on http://patcher2k.012webpages.com/ and download the patch that > will add the menuconfig option and the kernel module in the kernel > source (I think). > Or go on the DirectFB CVS tree (linux-fb, IIRC) and download the > nearly same kernel module source. > I don't know yet what is the best one. I got mine from epiawiki.org, a > long time ago, but it's time to update, and I think it came from > http://patcher2k.012webpages.com/ before that. Andre Kriehn signed > both DirectFB CVS and the patcher2k site. > Well, a lot of thanks. Now I have: vdr:/usr/src/VDR# fbset -i mode "720x576-74" # D: 41.475 MHz, H: 44.693 kHz, V: 74.488 Hz geometry 720 576 720 1152 32 timings 24111 88 32 16 4 88 4 rgba 8/16,8/8,8/0,8/24 endmode Frame buffer device information: Name : UNICHROME Address : 0xd8000000 Size : 33288192 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 1 YWrapStep : 0 LineLength : 2880 MMIO Address: 0xdc000000 MMIO Size : 16777216 Accelerator : Unknown (77) And when starts vdr I get: vdr:/usr/src/VDR# ./vdr -P"softdevice -vo dfb:" [softdevice] processing args [softdevice] argv [0] = softdevice [softdevice] initializing Plugin [softdevice] Initializing Video Out [softdevice] ffmpeg version(cvs) build(4752) [dfb] init ---------------------- DirectFB v0.9.22 --------------------- (c) 2000-2002 convergence integrated media GmbH (c) 2002-2004 convergence GmbH ----------------------------------------------------------- (*) DirectFB/Core: Single Application Core. (2005-05-27 21:18) (*) Direct/Memcpy: Using SSE optimized memcpy() (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 3323)... (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 3334)... (!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802] (*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH) (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 3335)... (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH) (*) DirectFB/Genefx: MMX detected and enabled (*) DirectFB/Graphics: VIA/S3G UniChrome 0.4 (-) (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH) [dfb] Supported video Modes are: 640x480@8 640x480@8 640x480@8 640x480@8 640x480@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8 800x600@8 1024x768@8 1024x768@8 1024x768@8 1024x768@8 1024x768@8 1024x768@8 1024x768@8 1152x864@8 1152x864@8 1152x864@8 1152x864@8 1152x864@8 1152x864@8 1280x960@8 1280x960@16 1280x960@32 1280x1024@8 1280x1024@8 1280x1024@8 1280x1024@8 1280x1024@8 1600x1200@8 1600x1200@8 1600x1200@8 [dfb] Enumeratig display Layers Layer 0 FBDev Primary Layer Type: graphics Caps: brightness contrast saturation surface Layer 1 VIA Unichrome Video Type: graphics picture video Caps: deinterlacing dst_colorkey opacity screen_location surface uc_overlay: color-keying is disabled [surface capabilities] scrSurface: primary videoonly double-buffered flipping [dfb] width = 640, height = 480 [dfb] got fmt = 0x00418c04 bpp = 32 [dfb] Using this layer for OSD: (FBDev Primary Layer - [640x480]) [surface capabilities] osdSurface: videoonly double-buffered flipping (!!!) *** WARNING [letting unprivileged IDirectFBDisplayLayer::GetSurface() call pass until cooperative level handling is finished] *** [idirectfbdisplaylayer.c:170 in IDirectFBDisplayLayer_GetSurface()] [surface capabilities] videoSurface: videoonly [dfb] Configuring CooperativeLevel for Overlay [dfb] Configuring CooperativeLevel for OSD [dfb] Using this layer for OSD: FBDev Primary Layer [dfb] Using this layer for Video out: VIA Unichrome Video [dfb] (re)configuring Videolayer to 720 x 576 (720x576) Caught: action=IDirectFBDisplayLayer::SetLevel(int), result=Not supported! Failed: SetLevel() uc_overlay: color-keying is enabled uc_overlay: color-keying is enabled uc_overlay: color-keying is enabled uc_overlay: color-keying is enabled [surface capabilities] videoSurface: videoonly double-buffered flipping [dfb] (re)configured 0x08100609 Subplugin successfully opend [softdevice] Video Out seems to be OK [softdevice] Initializing Audio Out [softdevice] Audio out seems to be OK [softdevice] A/V devices initialized, now initializing MPEG2 Decoder But I don't see anything in my monitor. all black I'm not asked to learn the remote keys. I'm using lirc with the /dev/lirc0 device The syslog says: Jun 2 22:53:02 localhost kernel: setmode x:640 y:480 bpp:32 Jun 2 22:53:02 localhost vdr[3336]: DFB remote control thread started (pid=3336) Jun 2 22:53:02 localhost vdr[3310]: [softdevice] videoOut OK ! Jun 2 22:53:02 localhost vdr[3310]: [softdevice-audio] Opening alsa device default Jun 2 22:53:02 localhost vdr[3310]: [softdevice-audio] Device opened! Ready to play Jun 2 22:53:02 localhost vdr[3310]: setting primary device to 2 Jun 2 22:53:02 localhost vdr[3310]: SVDRP listening on port 2001 Jun 2 22:53:02 localhost vdr[3310]: loading /video/themes/sttng-default.theme Jun 2 22:53:02 localhost vdr[3310]: starting plugin: softdevice Jun 2 22:53:02 localhost vdr[3310]: loading /video/themes/sttng-default.theme Jun 2 22:53:02 localhost vdr[3310]: ERROR: /dev/lircd: S'ha refusat la connexi? Jun 2 22:53:02 localhost vdr[3310]: remote control softdevice-dfb - learning keys Jun 2 22:53:02 localhost vdr[3337]: KBD remote control thread started (pid=3337, tid=163851) Jun 2 22:53:12 localhost vdr[3310]: ERROR: remote control LIRC not ready! Jun 2 22:53:12 localhost vdr[3310]: remote control KBD - learning keys Jun 2 22:53:22 localhost vdr[3310]: switching to channel 1 Jun 2 22:53:27 localhost vdr[3310]: ERROR: device 1 has no lock, can't attach receiver! Jun 2 22:53:27 localhost vdr[3338]: transfer thread started (pid=3338, tid=180236) There is a way to set the lirc device that VDR uses? Perhaps it try to use /dev/lirc and I have /dev/lirc0 Thanks again Leo