Re: missing xinit & startx from XF4.0.1-11.deb

sculpsit salyari: > so far i havent been able to locate an xinit or startx in XF4.0.1-11.deb these are in xbase-clients, the current version of which is 4.0.1-10. -- dog

Re: Configuring XF4 for Lombard

server for Mach64 but it does not seem > to be available in the present woody ppc distribution. xvfb is the virtual framebuffer x server, isn't it? so it won't actually give you a display, just provide a software-addressable x server you can test x clients on. -- dog

Re: XFree 4.0.1-8 won't run on r128/ppc

24bit colour as that was what was being reported under os9 (pay attention 007). -- dog

Re: XFree 4.0.1-8 won't run on r128/ppc

imings > > are not bijective? > > Possible. These are the values he sent me from a debugging enabled fbdevhw: > > xfree init mode:10 1600 1616 1624 1640 1200 1216 1224 1240 > fbdev init mode:1 1600 16 8 16 1200 16 8 16 32 8:8:8 > FBIOPUT_VSCREENINF

Re: XFree 4.0.1-8 won't run on r128/ppc

r 4.0.1f, module version = 1.0.0 (--) Depth 24 pixmap format is 32 bpp FBIOPUT_VSCREENINFO: Invalid argument Fatal server error: AddScreen/ScreenInit failed for driver 0 the "FBIOPUT_VSCREENINFO: Invalid argument" is the same message i get when trying to use fbset to change resolution etc under offb. -- dog

Re: XFree 4.0.1-8 won't run on r128/ppc

e fbdev driver uses the "default" mode, it *still* queries the framebuffer and then sets it explicitly. if it just reused the existing settings, for instance, i could use offb (which is readonly and doesn't support being set explicitly) to run x. -- dog

Re: X and Woody

ared now. i imagine they will be published once they become a little more stable, although i personally am using them without any problems. -- dog zx750p5: rou "back to basics" - bmf#10572 nt#270825982g two#5