it auto-loads swrast_dri.so instead of mach64_dri.so
I would like to ask some questions about X.Org and DRI and Mesa amd hope maybe someone knows:
1. is it possible to build X.Org directly with DRI, without Mesa ?
2. where is the most complete documentation of all the X.Org extensions ? and all the XCB extensions ? how do I know which ones I should compile and which not, the X.Org manuals weren't very helpful in that regard
3. where are the most complete instructions of building a Modular X.Org 1.5.0, I have made some progress but am having some problems, specifically aiglx loads swrast_dri.so even if mach64_dri.so is present
4. why does AIGLX load even if DRI is working ? and how to prevent it ? because --disable-aiglx has no effect, and that module still gets compiled and loaded
previously I wasn't able to start X at all, but that appears to have been either due to following incorrect build instructions or due to the driver for my hardware (mach64) being too new (building the latest .tar.bz2 source and overwriting with make install allowed to start the server)
and before that I had some other errors such as "shmget: function not implemented" which apparently disappeared after compiling System V IPC support into the kernel
and then there was another error in the mach64 driver which says "linear aperture not available" which was also fixed by using the non-git version of the driver (latest bz2 release)
there were additional errors: such as:
cannot open virtual console 7 (permission denied)
undefined symbol xf86getpcivideoinfo
xf860OpenConsole: Cannot open/dev/tty0 (Permission denied)
some agp error, which was fixed by setting a higher agp aperture size in the BIOS
and another error from MACH64 which was fixed by enabling VM86 in the kernel
what an eventful week, wouldn't you agree ? and it's not over yet!
specs of the target and build system:
P3 Katmai 500/100 384MB
Ati Rage Pro Turbo AGP 2X 8MB
I am currently trying to figure out what I can from:
mesa3d.org
but I have yet to know exactly what I need to do or how, every guide suggest different ./configure options for different packages and uses different installation methods
the good news is that MACH64 driver itself does not have any (EE) during it's loading, so currently I am trying to build xorg-server-1.5.0.tar.bz2 with ./configure --enable-dri --enable-dri2 but apparently that does not go so well, because I found on the forum someone suggests that to disable aiglx need DRI2
I would appreciate some pointers in the right directions.
I have tried to use DirectFB and XDirectFB as a preferred method of hardware acceleration, and that mission was only partially successful, DirectFB did build, but the patch of XDirectFB for xorg did not work at all.
for your consideration, I am currently open for any suggestions anyone may have for the best hardware acceleration performance achieveable on Linux, if there is something other than the two above mentioned methods you think I should know about and try to use instead, I would like to know about it.
I would like to ask some questions about X.Org and DRI and Mesa amd hope maybe someone knows:
1. is it possible to build X.Org directly with DRI, without Mesa ?
2. where is the most complete documentation of all the X.Org extensions ? and all the XCB extensions ? how do I know which ones I should compile and which not, the X.Org manuals weren't very helpful in that regard
3. where are the most complete instructions of building a Modular X.Org 1.5.0, I have made some progress but am having some problems, specifically aiglx loads swrast_dri.so even if mach64_dri.so is present
4. why does AIGLX load even if DRI is working ? and how to prevent it ? because --disable-aiglx has no effect, and that module still gets compiled and loaded
previously I wasn't able to start X at all, but that appears to have been either due to following incorrect build instructions or due to the driver for my hardware (mach64) being too new (building the latest .tar.bz2 source and overwriting with make install allowed to start the server)
and before that I had some other errors such as "shmget: function not implemented" which apparently disappeared after compiling System V IPC support into the kernel
and then there was another error in the mach64 driver which says "linear aperture not available" which was also fixed by using the non-git version of the driver (latest bz2 release)
there were additional errors: such as:
cannot open virtual console 7 (permission denied)
undefined symbol xf86getpcivideoinfo
xf860OpenConsole: Cannot open/dev/tty0 (Permission denied)
some agp error, which was fixed by setting a higher agp aperture size in the BIOS
and another error from MACH64 which was fixed by enabling VM86 in the kernel
what an eventful week, wouldn't you agree ? and it's not over yet!
specs of the target and build system:
P3 Katmai 500/100 384MB
Ati Rage Pro Turbo AGP 2X 8MB
I am currently trying to figure out what I can from:
mesa3d.org
but I have yet to know exactly what I need to do or how, every guide suggest different ./configure options for different packages and uses different installation methods
the good news is that MACH64 driver itself does not have any (EE) during it's loading, so currently I am trying to build xorg-server-1.5.0.tar.bz2 with ./configure --enable-dri --enable-dri2 but apparently that does not go so well, because I found on the forum someone suggests that to disable aiglx need DRI2
I would appreciate some pointers in the right directions.
I have tried to use DirectFB and XDirectFB as a preferred method of hardware acceleration, and that mission was only partially successful, DirectFB did build, but the patch of XDirectFB for xorg did not work at all.
for your consideration, I am currently open for any suggestions anyone may have for the best hardware acceleration performance achieveable on Linux, if there is something other than the two above mentioned methods you think I should know about and try to use instead, I would like to know about it.
Comment