Philip Armstrong wrote: > On Thu, Mar 06, 2008 at 07:47:20PM +0100, Tanja wrote: >> thanks for your offered help. At the moment I am back to the matroxfb >> setting that we were using successfully over the last years. I broke our >> freevo machine completly by all this experimenting >> with directfb (to much upgrades of to many packages, finally I lost myself >> somewhere). >> >> But when I have freevo running again more or less reliable I will return to >> the directfb problem. >> At the moment fixing the recordserver has a slightly higher priority ;-) > > :) > >> I would appreciate, if you can post your current settings. Which >> directfb-version are you running? >> Which kernel? Which kernel modules are needed? As I said, I can not >> find i2c-matroxfb. Do I need it? > > > >> Should it be in the kernel source or is it an extra package? Do you have >> any bootscripts, any special settings for mplayer or freevo? What >> resolution (modes) are you using? Are you running freevo as root or is >> there a way to run it as user? > > I think root is required. You might be able to tie things down, but it > would at the very least require some udev hackery to give the user in > question access to the relevant i2c device nodes. > >> You see, I am totaly confused with the whole subject and actually the >> documentation is very rare, very old and not always helpful. So any hint >> you can give would be great! > > OK. Here's my current setup. > > Hardware first: Biostar IDEQ 210V, 1GHz Duron, 256Mb memory, 16Mb Dual > Head G400, Microsoft Media Centre remote control, PCI Technotrend DVB > tuner card. > > The machine is running Debian stable, with a stock kernel. (well, a > backported stock kernel to be precise...) > > Following modules are loaded at boot time: > > usbcore > rtc > rtc-cmos > > fusion > i2c-dev > i2c-matroxfb > matroxfb_crtc2 > lirc_mceusb2 > > The second half are freevo/directfb related > > fusion is directfb related, but isn't strictly necessary. > > I'm using the stock Debian stable directfb release, which is old now > (0.9.25), but means I don't have to faff about recompiling mplayer and > libSDL. The only small bug is that on power-on, freevo has to be > started twice for it to work correctly -- it always fails to > initialised the directfb layer correctly the first time (this is a bug > in directfb rather than freevo: I can start any directfb app first, > watch it die & then run freevo subsequently. Weird I know...) > > mplayer and other media-related stuff is installed from > http://www.debian-multimedia.org/ > > freevo is hand installed into /usr/local, with a startup script from > an old debianised version which I installed yonks ago back in the > 1.5.x days IIRC. > > Directfb settings: /etc/directfbrc > > matrox-crtc2 > matrox-tv-standard=pal > matrox-sgram > mode=720x576 > memcpy=MMXEXT > primary-layer=02 > #matrox-cable-type=scart-composite > disable-module=ps2mouse > mouse-source=/dev/input/mice > disable-module=linux_input > disable-module=joystick > #disable-module=keyboard > mouse-source=/dev/input/mice > no-cursor > agp=2 > dma > videoram-limit=16384 > #videoram-limit=8192 > #linux-input-ir-only > no-vt-switch > pixelformat=RGB32 > #pixelformat=ARGB > bg-color=00FF00FF > graphics-vt
Does matrox-sgram work, IIRC it used to work on my machine but now when I run df_dok the "Fill Rectangle", "Fill Triangles" doesn't work any more. But that could be only when running it on the primary layer 0. Thanks for the information it is very good to have. Duncan BTW there are two mouse-source lines. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
