From: Steven N. <st...@sn...> - 2001-06-29 10:36:13
|
I have recently upgraded my machine to a Athlon 1.2GHz+MSIK7Master (266DDR FSB) from a K6-2 I have kept the same video card G400MAX which has been working well in my old set up for some time. I seem to have found a problem I have been unable to track down as yet and was wondering if anyone else has found any idea what the problem is. I am using the current XFree86-cvs and all linux kernels that I have tested (2.4.x only) I am unable to reliably run Q3 1.27g. I am having to run the AGPGart driver with try_unsupported. If I select to start at the beginning of single player the game freezes within seconds. If I turn off the compiled vertex arrays then the game doesn't freeze but every few seconds the screen flashes what appears to be a heavily zoomed texture. It doesn't seem to matter what AGP settings I use or BIOS options I use. Strange thing is, it does seem to otherwise be stable. Q2 which also uses the compiled vertex array extension works fine as long as I have left it running, as do any other GL programs I have tried (XScreensaver etc). The whole machine doesn't lock up but the X process seems to get stuck in a loop or something (deadlock?). Running top on my Psion shows X using all CPU time, but killing the Q3 process does not make any difference, the only way of returning the system to a useful state is to kill the X process. There does not appear to be any telling messages in the log either. I have tried running with LIBGL_DEBUG enabled but it doesn't report anything out of the ordinary. I will next try a debug build of X and try to track this down, however I do not fully understand the full workings of the code yet... -- Steven Newbury st...@sn... |
From: Steven N. <st...@sn...> - 2001-06-29 10:36:30
|
I have recently upgraded my machine to a Athlon 1.2GHz+MSIK7Master (266DDR FSB) from a K6-2 I have kept the same video card G400MAX which has been working well in my old set up for some time. I seem to have found a problem I have been unable to track down as yet and was wondering if anyone else has found any idea what the problem is. I am using the current XFree86-cvs and all linux kernels that I have tested (2.4.x only) I am unable to reliably run Q3 1.27g. I am having to run the AGPGart driver with try_unsupported. If I select to start at the beginning of single player the game freezes within seconds. If I turn off the compiled vertex arrays then the game doesn't freeze but every few seconds the screen flashes what appears to be a heavily zoomed texture. It doesn't seem to matter what AGP settings I use or BIOS options I use. Strange thing is, it does seem to otherwise be stable. Q2 which also uses the compiled vertex array extension works fine as long as I have left it running, as do any other GL programs I have tried (XScreensaver etc). The whole machine doesn't lock up but the X process seems to get stuck in a loop or something (deadlock?). Running top on my Psion shows X using all CPU time, but killing the Q3 process does not make any difference, the only way of returning the system to a useful state is to kill the X process. There does not appear to be any telling messages in the log either. I have tried running with LIBGL_DEBUG enabled but it doesn't report anything out of the ordinary. I will next try a debug build of X and try to track this down, however I do not fully understand the full workings of the code yet... -- Steven Newbury st...@sn... |
From: Steven N. <st...@sn...> - 2001-06-29 10:37:28
|
I have recently upgraded my machine to a Athlon 1.2GHz+MSIK7Master (266DDR FSB) from a K6-2 I have kept the same video card G400MAX which has been working well in my old set up for some time. I seem to have found a problem I have been unable to track down as yet and was wondering if anyone else has found any idea what the problem is. I am using the current XFree86-cvs and all linux kernels that I have tested (2.4.x only) I am unable to reliably run Q3 1.27g. I am having to run the AGPGart driver with try_unsupported. If I select to start at the beginning of single player the game freezes within seconds. If I turn off the compiled vertex arrays then the game doesn't freeze but every few seconds the screen flashes what appears to be a heavily zoomed texture. It doesn't seem to matter what AGP settings I use or BIOS options I use. Strange thing is, it does seem to otherwise be stable. Q2 which also uses the compiled vertex array extension works fine as long as I have left it running, as do any other GL programs I have tried (XScreensaver etc). The whole machine doesn't lock up but the X process seems to get stuck in a loop or something (deadlock?). Running top on my Psion shows X using all CPU time, but killing the Q3 process does not make any difference, the only way of returning the system to a useful state is to kill the X process. There does not appear to be any telling messages in the log either. I have tried running with LIBGL_DEBUG enabled but it doesn't report anything out of the ordinary. I will next try a debug build of X and try to track this down, however I do not fully understand the full workings of the code yet... -- Steven Newbury st...@sn... |
From: Steven N. <st...@sn...> - 2001-06-29 10:37:58
|
I have recently upgraded my machine to a Athlon 1.2GHz+MSIK7Master (266DDR FSB) from a K6-2 I have kept the same video card G400MAX which has been working well in my old set up for some time. I seem to have found a problem I have been unable to track down as yet and was wondering if anyone else has found any idea what the problem is. I am using the current XFree86-cvs and all linux kernels that I have tested (2.4.x only) I am unable to reliably run Q3 1.27g. I am having to run the AGPGart driver with try_unsupported. If I select to start at the beginning of single player the game freezes within seconds. If I turn off the compiled vertex arrays then the game doesn't freeze but every few seconds the screen flashes what appears to be a heavily zoomed texture. It doesn't seem to matter what AGP settings I use or BIOS options I use. Strange thing is, it does seem to otherwise be stable. Q2 which also uses the compiled vertex array extension works fine as long as I have left it running, as do any other GL programs I have tried (XScreensaver etc). The whole machine doesn't lock up but the X process seems to get stuck in a loop or something (deadlock?). Running top on my Psion shows X using all CPU time, but killing the Q3 process does not make any difference, the only way of returning the system to a useful state is to kill the X process. There does not appear to be any telling messages in the log either. I have tried running with LIBGL_DEBUG enabled but it doesn't report anything out of the ordinary. I will next try a debug build of X and try to track this down, however I do not fully understand the full workings of the code yet... -- Steven Newbury st...@sn... |
From: Steven N. <st...@sn...> - 2001-06-29 10:44:12
|
I have recently upgraded my machine to a Athlon 1.2GHz+MSIK7Master (266DDR FSB) from a K6-2 I have kept the same video card G400MAX which has been working well in my old set up for some time. I seem to have found a problem I have been unable to track down as yet and was wondering if anyone else has found any idea what the problem is. I am using the current XFree86-cvs and all linux kernels that I have tested (2.4.x only) I am unable to reliably run Q3 1.27g. I am having to run the AGPGart driver with try_unsupported. If I select to start at the beginning of single player the game freezes within seconds. If I turn off the compiled vertex arrays then the game doesn't freeze but every few seconds the screen flashes what appears to be a heavily zoomed texture. It doesn't seem to matter what AGP settings I use or BIOS options I use. Strange thing is, it does seem to otherwise be stable. Q2 which also uses the compiled vertex array extension works fine as long as I have left it running, as do any other GL programs I have tried (XScreensaver etc). The whole machine doesn't lock up but the X process seems to get stuck in a loop or something (deadlock?). Running top on my Psion shows X using all CPU time, but killing the Q3 process does not make any difference, the only way of returning the system to a useful state is to kill the X process. There does not appear to be any telling messages in the log either. I have tried running with LIBGL_DEBUG enabled but it doesn't report anything out of the ordinary. I will next try a debug build of X and try to track this down, however I do not fully understand the full workings of the code yet... -- Steven Newbury st...@sn... |
From: <cs...@di...> - 2001-06-29 14:02:42
|
Hi! I have a Intel STL2 mainboard, with integrated Ati Rage 3D IIC video card. Card is not AGP slotted, it is PCI (integrated) card. The r128.o kernel modul shall to support PCI Ati cards in future ? I see the code, and i look some PCIgart requests, but the code not run without agpgart module. (many many unresolved symbols) This mainboard does not support agp slot (it is a server board with 2 cpu and dualchannel scsi, etc.) If somebody can help to me, please reply... |
From: Philip W. <pg...@do...> - 2001-06-29 14:43:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today, cs...@di... wrote: > >Hi! >I have a Intel STL2 mainboard, with integrated Ati Rage 3D IIC video card. >Card is not AGP slotted, it is PCI (integrated) card. > >The r128.o kernel modul shall to support PCI Ati cards in future ? I see >the code, and i look some PCIgart requests, but the code not run without >agpgart module. (many many unresolved symbols) > >This mainboard does not support agp slot (it is a server board with 2 cpu >and dualchannel scsi, etc.) > >If somebody can help to me, please reply... You can compile agpgart into a kernel with no agp slots just fine, this wil fix the unresolved symbols. Whether it will make your card work is another matter, but it's a start. Regards, Philip Willoughby - -- echo bz...@nf... | tr "bizndfohces" "pwgd9ociaku" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7PJQoTEXlrOaAVckRAnj6AKDZp1fbE9xJ8kaKV5zCkq7NkxkiHQCeJq+6 dik8YT9Kdt0HcNEccx0h+bc= =EQbY -----END PGP SIGNATURE----- |
From: <cs...@di...> - 2001-06-29 15:11:04
|
On Fri, 29 Jun 2001, Philip Willoughby wrote: > You can compile agpgart into a kernel with no agp slots just fine, this wil fix > the unresolved symbols. Whether it will make your card work is another matter, > but it's a start. > ??? It shall be work ? I try: :~# modprobe agpgart Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 203M agpgart: no supported devices found. :~# modprobe r128 [drm:r128_init] *ERROR* Cannot initialize agpgart module. :~# dmesg |tail -2 agpgart: no supported devices found. [drm:r128_init] *ERROR* Cannot initialize agpgart module. |
From: Malte C. <ma...@co...> - 2001-06-29 14:48:56
|
cs...@di... wrote: > I have a Intel STL2 mainboard, with integrated Ati Rage 3D IIC video card. > Card is not AGP slotted, it is PCI (integrated) card. IIRC, PCI is not the problem, but the Rage IIC is so old that it's not very useful as a 3D accelerator anyway and there never was and probably never will be a driver for it (except if you write it). The later models, Rage Pro, might be supported in the future and are already supported in Utah-GLX for Xfree 3.3.x. From Rage 128 upwards, there is excellent support in the DRI tree. I know this won't help you :-) -Malte #8-) |
From: <cs...@di...> - 2001-06-29 15:00:26
|
On Fri, 29 Jun 2001, Malte Cornils wrote: > IIRC, PCI is not the problem, but the Rage IIC is so old that it's > not very useful as a 3D accelerator anyway and there never was and > probably never will be a driver for it (except if you write it). The I dont want 3D acceleration support for may card, i enought for 2D accelerations (XVideo, YUVpacked,etc. support). If it is not supported yet, i can write it, if somedoby give to me some Ati Rage 3D IIC technical informations (for Xvideo support). |
From: Arpi <ar...@th...> - 2001-06-29 15:04:41
|
Hi, > > IIRC, PCI is not the problem, but the Rage IIC is so old that it's > > not very useful as a 3D accelerator anyway and there never was and > > probably never will be a driver for it (except if you write it). The > > I dont want 3D acceleration support for may card, i enought for 2D > accelerations (XVideo, YUVpacked,etc. support). If it is not supported > yet, i can write it, if somedoby give to me some Ati Rage 3D IIC technical > informations (for Xvideo support). > Then you need the GATOS Xv driver, not DRI. go to www.linuxvideo.org/gatos A'rpi / Astral & ESP-team -- mailto:ar...@th... http://esp-team.scene.hu |
From: Mike A. H. <mh...@re...> - 2001-06-29 20:00:04
|
On Fri, 29 Jun 2001 cs...@di... wrote: >Date: Fri, 29 Jun 2001 17:00:31 +0200 (CEST) >From: cs...@di... >To: Malte Cornils <ma...@co...> >Cc: dri...@li... >Content-Type: TEXT/PLAIN; charset=US-ASCII >List-Id: <dri-devel.lists.sourceforge.net> >Subject: Re: Ati Rage 3D IIC with PCI slot (integrated) > > > >On Fri, 29 Jun 2001, Malte Cornils wrote: > >> IIRC, PCI is not the problem, but the Rage IIC is so old that it's >> not very useful as a 3D accelerator anyway and there never was and >> probably never will be a driver for it (except if you write it). The > >I dont want 3D acceleration support for may card, i enought for 2D >accelerations (XVideo, YUVpacked,etc. support). If it is not supported >yet, i can write it, if somedoby give to me some Ati Rage 3D IIC technical >informations (for Xvideo support). I have a Compaq Proliant with an onboard Rage IIC, and it works fine in XFree86. No 3D accel, but 2D works fine. ---------------------------------------------------------------------- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, Red Hat Inc. Ontario, Canada, P6C 5B3 http://www.redhat.com Phone: (705)949-2136 ---------------------------------------------------------------------- Latest XFree86 test RPMS: ftp://people.redhat.com/mharris/testing |
From: Derrik P. <dp...@ds...> - 2001-06-29 15:58:44
|
On Fri, 29 Jun 2001, Malte Cornils wrote: > cs...@di... wrote: > > I have a Intel STL2 mainboard, with integrated Ati Rage 3D IIC video card. > > Card is not AGP slotted, it is PCI (integrated) card. > > IIRC, PCI is not the problem, but the Rage IIC is so old that it's > not very useful as a 3D accelerator anyway and there never was and > probably never will be a driver for it (except if you write it). Besides the ract that he was trying to load the Rage128 DRM, and the 3DRage IIC is a Mach64-based design - it's not even the right family. Derrik Pates | Sysadmin, Douglas School | #linuxOS on EFnet dp...@ds... | District (dsdk12.net) | #linuxOS on OPN |