[vdr] Re: always restarting

[Nicolas Huillard <nhuillard@ghs.fr>]

Cedric.Picard@esial.uhp-nancy.fr a écrit :
> Selon Nicolas Huillard <nhuillard@ghs.fr>:
>
> > Main Menu > Console drivers > Frame-buffer support > Support for frame
> > buffer devices (EXPERIMENTAL) > Virtual Frame Buffer support (ONLY FOR
> > TESTING!) (EXPERIMENTAL) (NEW)
> >
> > 1) select Experimental first  : Main Menu > Code maturity level options
> > > Prompt for development and/or incomplete code/drivers
> >
> > 2) this is for 2.4.27 : I hope the mentionned (NEW) is not so new and
> > you will have this in 2.4.26
> >
> > 3) doing this will activate software MPEG decoding for any channel
> > selected for live view ; this very MPEG output deing discarded in a fake
> >  frame-buffer (the same applied to the FF case before, but you were'nt
> > aware of it, because the FF did what it's meant to do, without
> > performance impact on the server). You can add a "Pause live view"
> > option in softdevice to avoid the CPU hog (many people ask for such an
> > option).
>
> ok
> i've done that
>
> but when i do fbset -i it still do :
>
> open /dev/fb0: No such device
According to the menuconfig help page :

│ CONFIG_FB_VIRTUAL: 
                                       │ 
         │ This is a `virtual' frame buffer device. It operates on a 
chunk of                                           │ unswappable kernel 
memory instead of on the memory of a graphics 
                  │ board. This means you cannot see any output sent to 
this frame                                               │ buffer 
device, while it does consume precious memory. The main use 
                              │ of this frame buffer device is testing 
and debugging the frame                                               │ 
buffer subsystem. Do NOT enable it for normal systems! To protect 
                                     │ the innocent, it has to be 
enabled explicitly at boot time using the 
          │ kernel option `video=vfb:'. 
                                                │ 
                 │ This driver is also available as a module ( = code 
which can be                                              │ inserted and 
removed from the running kernel whenever you want). The 
                        │ module will be called vfb.o. If you want to 
compile it as a module,                                          │ say M 
here and read Documentation/modules.txt. 

Thus modify lilo.conf or the grub config to add the required kernel 
option video=vfb:
And alos load the module once booted, for the double fresh effect : 
modprobe vfb

--
NH