Peter Andersson wrote:
>>Peter Andersson wrote:
>>>Hi! I am running a umax Apus 3000, with suse linux ppc 7.1 and two
>>>Voodoo 3 Banshee Cards. I have just compiled and installed the cvs (
>>>7th mars 2003) version of DRI and have a couple of questions i have
>>>been trying to solve without success.
>>>1.) I haven=ABt been able to locate either the sourcecode or any pre
>>>compiled libraries of libglide for linux ppc. Does anyone know where i
>>>can find either of them (preferably the pre compilde ones)...
>>http://sourceforge.net/projects/glide/ is the sf-page for glide. I don'=
>> know if anyone is still maintaining this code (probably not), and I
>>don't know if it will even compile on ppc. Actually, compiling glide ha=
>> often been reported to be a real pain in the ass anyway. I don't know
>>of any precompiled libraries either, but I've never searched for those.
> Thanks, according to the cvs repository there haven't been any change i=
> the files on libglide in at least two years... Also i didn't get the
> compilation to run through without errors, so you are also right about =
> being a pain in the ass...
Hmm, http://dri.sourceforge.net/doc/dri_driver_features.phtml states=20
glide-support for ppc as "untested". google'ing around for "linux ppc=20
glide" didn't provide any useful results either, so I can't really say=20
any more about this topic. The best I could find was dead links to some=20
Glide-rpm's for ppc :(
>>>2.) I have an old card which is attatched to the motherboard and
>>>therefore when ever i boot up linux that card is set as the default
>>>graphics card. That means that the monitor attatched to the voodoo
>>>card doesn't come on until Xf86 is loaded. Any ideas on how to auto
>>>load the tdfx drivers instead of the framebuffer drivers at bootup?
>>Usually you can completely disable onboard graphics hardware by either
>>setting a jumper on the mainboard or switching it off in the BIOS. That
>>might do the trick.
> Managed to do this by recompiling the kernel.The documentation on macs =
> really poor and i didn=B4t manage to find any jumper. Also macs doesn=B4=
> easily configurable bios the way pc:s does...
sorry, didn't think about that (I'm not really familiar with macs)
>>>3.) Also since i have two identical voodoo cards i also attatched two
>>>monitors (exactly the same brand) to the computer so that i could use
>>>dual screens. The problem is that i can't start X with both monitors,
>>>one at a time works fine but when i try using both X doesn't start.
>>>Has anyone heard of similar problems? Is this something that has to do
>>>with the tdfx driver that comes with DRI? I don=ABt think i have done
>>>something wrong in my configuration file since configuration was
>>>pretty straight forward. I have exausted every last idea trying to fix
>>What are you trying to do? Do you want Xinerama, or two independent
>>X-displays? In theory both should work, I suppose. What does
>>/var/log/XFree86.0.log say when X doesn't start? Maybe there's a clue i=
> I had been thinking of switching between a two displays and xinerama
> depending if i need accelerated open-GL or not.
> I am not very good at interpreting the log file, so i don't really know
> what to look for. But there are no explicit error messages, except for =
> entry in the end of the log, and that didn't tell me anything i didn=B4=
> already know.
> Fatal server error:
> Caught signal 11. Server aborting
> The very last entry is:
> (II) Screen 0 shares mem & io resources
> (II) Screen 1 shares mem & io resources
> Resetting FIFO
> Do you have any idea what to make of this???
Nope, but it doesn't look like an error to me, at least, more like a=20
status information. I guess only a developer can help you out here. You=20
could try posting at dri-devel, but I don't know if any of the=20
developers are still maintaining voodoo-drivers (I doubt it).
> The behaviour when i try to start both displays are
> somewhat similar to when you try to operate a monitor with the wrong
> vertical/horizontal sync (i hope you have seen this some time since i
> don't exactly know how to describe it).=20
I think I know what you mean.
> The monitor connected to the
> screen first listed in the XF86config file always manage to get
> started but it is the second that keep "crashing".
> Section "ServerLayout"
> Identifier "Simple Layout"
> Screen "Screen 0"
> Screen "Screen 1" RightOf "Screen 0"
> InputDevice "Mouse1" "CorePointer"
> InputDevice "Keyboard1" "CoreKeyboard"
Looks sane to me, so I really suppose it's a driver issue.
> In this configuration "Screen 0" seems to start correctly while "Screen=
> is the one that is crashing all the time.
> Thanks for the help!