Re: [debian-x] Hardware GL with a G400
* Gordon Heydon [EMAIL PROTECTED] [001013 20:20]: but what about the libGLU and libGL libraries? don't you need those. At the moment I have the Utah ones is that enough. Well, yes, you do. XF86 4.0.1 currently provides libGL. Shortly they will begin providing libGLU. (It is a technical issue -- it is the only file in their distribution that uses C++.)
Re: [debian-x] Hardware GL with a G400
Hello, Thanks, but what about the libGLU and libGL libraries? don't you need those. At the moment I have the Utah ones is that enough. Gordon. * Seth Arnold ([EMAIL PROTECTED]) wrote: Gordon, you are in luck, this was my situation exactly. Go to matrox.com, find their drivers section, and download their linux driver. It should be one file. Be sure to take a look at their readme, it is good enough to get you installed. (except for the bit about groups and DRI don't bother with setting a group for DRI.) You will need a recent kernel. I use 2.4.0-test7. I built my kernel with agpgart and mga modules available. They may or may not be needed. I'd bet agpgart is required, mga isn't. shrug There are two ways of getting Matrox's mga_drv.o into use -- replace XFree86's version in /usr/X11R6/lib/modules/drivers/ with matrox's (clunky, will get overwritten with each new xf86 upgrade unless you use dpkg diversions...) -or- (the recommended way) is to use a direct path in your /etc/X11/XF86Config-4 file to load the new module. I haven't gone this route (lazy) but suggest you do. Sadly, I don't know the syntax for this, so I suggest you look for all of Branden's postings in the archives for more information about this. (Perhaps he mentioned it in a thread with someone from nvidia...) Once things are in place, modprobe agpgart, modprobe mga, and startx. I have attached my XF86Config file for reference... * Gordon Heydon [EMAIL PROTECTED] [001013 00:14]: Hello, This is a simple question, can anyone tell me how to or better point me in the direction of some documentation on how to get hardware 3gl going with my dual head g400 (I am only using 1 head at the moment) with the Xfree 4.0.1 debs found here. Thanks in advance Gordon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Section ServerLayout Identifier Dual Screen Screen0 RightOf Screen1 Screen Screen1 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option Xinerama EndSection Section ServerLayout Identifier Single Screen Screen0 InputDevice Mouse0 CorePointer InputDevice Keyboard0 CoreKeyboard EndSection Section Files FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/PEX/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:noscale FontPath /usr/X11R6/lib/X11/fonts/misc/:noscale EndSection Section Module Load GLcore Load dbe Load dri Load extmod Load glx Load pex5 Load record Load xie Load freetype Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol IMPS/2 Option Device /dev/mouse Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Mitsubishi VendorName MEL ModelName42c0 HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option DPMS #ModeLine 640x480 45.8 640 672 768 864 480 488 494 530 -HSync -VSync EndSection Section Monitor Identifier Sony HorizSync60.5 - 82.0 VertRefresh 65.0 - 100.0 Option DPMS EndSection Section Device Identifier G400_0 Driver mga VendorName Matrox BoardName MGA G400 AGP BusID PCI:1:0:0 Screen 0 EndSection Section Device Identifier G400_1 Driver mga VendorName Matrox BoardName MGA G400 AGP BusID PCI:1:0:0 Screen 1 EndSection Section Screen Identifier Screen0 Device G400_0 MonitorMitsubishi DefaultDepth 16 SubSection Display Depth 1 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Section Screen
Re: [debian-x] Hardware GL with a G400
* Michael Epting ([EMAIL PROTECTED]) wrote: On Fri, Oct 13, 2000 at 08:06:45AM -0500, Thomas E. Vaughan wrote: On Fri, Oct 13, 2000 at 06:11:47PM +1100, Gordon Heydon wrote: This is a simple question, can anyone tell me how to or better point me in the direction of some documentation on how to get hardware 3gl going with my dual head g400 (I am only using 1 head at the moment) with the Xfree 4.0.1 debs found here. If you haven't done so already, then get the source code to kernel 2.4.0-test9. I compiled support for my AGP chipset directly into the kernel, and I recommend compiling the matrox DRI support as a module. I may be wrong, but it seems that, at least in the past, the X server liked to load the kernel module itself. After installing the new kernel and DRI module, remember to reboot. Dexter, the X configuration program that ran when I installed the most recent debs, made a fairly good approximation of an XF86Config-4 file for me. Make sure that you add the following lines: Section DRI Mode 0666 EndSection I have had an off-list exchange with Thomas that clarified but did not resolve a problem I have with DRI. I get hardware 3d acceleration, as he does, with 2.4.0-test9, which resolved the version mismatch of earlier kernel 2.4 releases. However, while X is running, my virtual consoles are not usable. It turns out that the major difference between our installations is hardware -- I have an ASUS P5A motherboard with the ALI chipset. Does anybody have DRI working with the G400/P5A combination? (or any other ALI-based motherboard?) Hello, I have a ALI based board and it does the some thing, but when I try to get run the evas test with hardware I get [EMAIL PROTECTED]:~/src/evas/test$ ./evas_test @@Created GLX Context.. X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 145 () Serial number of failed request: 894 Current serial number in output stream: 894 [EMAIL PROTECTED]:~/src/evas/test$ and the evas_test_old onlu gets about 8.6 frames per second. I must have missed something or it is in the libraries, I have a funny feeling I need different ones to the utah ones that I triied to use when I first go the G400. Gordon.
