sculpsit daenzerm:
FBIOPUT_VSCREENINFO should work on offb if you pass (a mode that can be
rounded up to) the exact same mode as offb is using.
surely default should do this?
Perhaps the routines to convert between XFree86 timings and fbdev timings
are not bijective?
Possible. These
dog wrote:
Perhaps the routines to convert between XFree86 timings and fbdev
timings 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:
sculpsit daenzer:
I notice that X tries to set a 32 bit mode while the console is apparently 8
bit (right?) - do you have DefaultDepth 32 in your XF86Config or something?
i had a default of 24. changing this to 8 has worked, whoo hoo :-)
thanks for the help. i had assumed it would be 24bit
On Wed, 29 Nov 2000, Michel [iso-8859-1] Dänzer wrote:
dog wrote:
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
Geert Uytterhoeven wrote:
On Wed, 29 Nov 2000, Michel [iso-8859-1] Dänzer wrote:
dog wrote:
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
fyi, the mkfontdir command got moved to the 'xutils' package.
Actually, I realize that; however, it is not in xutils-4.0.1-8.
apocalypse:/home/branden# dpkg -L xutils | grep mkfont
/usr/X11R6/bin/mkfontdir
/usr/X11R6/man/man1/mkfontdir.1x.gz
apocalypse:/home/branden# dpkg -l xutils
Actually, I realize that; however, it is not in xutils-4.0.1-8.
dpkg -L xutils | grep mkfont proves this, and yes I am sure
I do indeed have 4.0.1-8 installed.. am I the only one this has
happened to?
apocalypse:/home/branden# dpkg -L xutils | grep mkfont
/usr/X11R6/bin/mkfontdir
On Thu, Nov 30, 2000 at 04:22:55PM +0100, Michael Schmitz wrote:
Actually, I realize that; however, it is not in xutils-4.0.1-8.
dpkg -L xutils | grep mkfont proves this, and yes I am sure
I do indeed have 4.0.1-8 installed.. am I the only one this has
happened to?
And apocalypse is a PPC box?
I guess someone needs to make sure the *.powerpc files are appropriately in
sync with the *.i386 ones.
Hell, -8 won't even patch on my box ( the 001_something diff just barfs
with 23-odd rejects). The one I tried before (-6) I got to compile but
couldn't create
I'll continue trying xfree builds as I see new releases, but I can't spend
a whole lot of time to investigate build problems, sorry.
Okay, well, I just inherited my girlfriend's 7200/90, so once I get it
upgraded to woody I can give it a shot. I compiled 3.3.6-11 on it last
night just
On Tuesday 28 November 2000 7:52 pm, Matt Brubeck wrote:
I have a slot-loading iMac with Rage 128 video. All of the phase2 test
packages of XFree86 4 ran fine on this machine.
After upgrading xserver-xfree86 from phase2v27 to 4.0.1-8, the X server
dies on startup with the following error
Michael Flaig wrote:
In my case the Pismo restartet without shutdown. I think there was a kernel
panic, because of a bug ...
What are you referring to, the blanking or offb?
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux
Michael Schmitz wrote:
You've all heard Dan's answer: the upstream r128 driver code got borked.
He's working on it and gave you a 'sometime next week' estimate. I
seriously doubt it can be done faster (unless you're experts in xfree86
code).
For those who are desperate enough to build X
Yes. My pismo runs X4.0.1.
I grabbed 4.0.1 DRI binaries that Michel Danzer posted a month
back. They have worked fine for me.
jas.
Michael Flaig [EMAIL PROTECTED] writes:
On Wed, Nov 29, 2000 at 02:06:14PM +, Bertrand Sereno wrote:
This Driver is only for Mach64. So it won't run on my
I have a slot-loading iMac with Rage 128 video. All of the phase2 test
packages of XFree86 4 ran fine on this machine.
After upgrading xserver-xfree86 from phase2v27 to 4.0.1-8, the X server
dies on startup with the following error (full log attached):
(**) R128(0): Using framebuffer device
(II)
15 matches
Mail list logo