From: Michael M. <Michael@Meding.net> - 2000-08-15 23:36:24
|
Hi everybody, is there ongoing effort to get 32bpp working on the G400 ? The second warp engine / warp improvements / multitexturing (if not included already :-)) ? What about 3DNOW/3DNOWEXT for MESA / the MGA driver ? What about the second head of the G400DH, or the video out. I heard that PI was on contract doing this work and that it should be released as binary at first, later to be released with source if possible. I heard also that this is in a usable state as of know. Hopefully I am not congesting this list with too off topic questions (and I am not asking too stupid questions). With best regards Michael Meding |
From: mike l. <mc...@es...> - 2000-08-16 07:56:43
|
What is this about it not working in 32bpp, I may well be living on the edge here, but I'm using 32bpp with a G400 (using XF3.3.6). I seems to work ok! Are you talking about XF4, if so I'd also be interested to see what the issue is with 32bpp. (that may well be a stupid question). Anyway, I fear this is off topic. Sorry I'all go away now 8). Mike Michael Meding wrote: > > Hi everybody, > > is there ongoing effort to get 32bpp working on the G400 ? The second > warp engine / warp improvements / multitexturing (if not included > already :-)) ? > What about 3DNOW/3DNOWEXT for MESA / the MGA driver ? > What about the second head of the G400DH, or the video out. > I heard that PI was on contract doing this work and that it should be > released as binary at first, > later to be released with source if possible. I heard also that this is > in a usable state as of know. > > Hopefully I am not congesting this list with too off topic questions > (and I am not asking too stupid questions). > > With best regards > > Michael Meding > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel |
From: Michael M. <Michael@Meding.net> - 2000-08-16 09:31:17
|
Hi Mike, yes this is about XF4.x. To my knowledge DRI is only working with 16bpp as of now. Regards Michael |
From: Andreas E. <eh...@ly...> - 2000-08-16 10:10:41
|
On Wed, Aug 16, 2000 at 12:42:51AM +0200, Michael Meding wrote: > Hi everybody, > > is there ongoing effort to get 32bpp working on the G400 ? The second > warp engine / warp improvements / multitexturing (if not included > already :-)) ? * 32bpp shouldn't be too hard to add but I don't know if anyone is working on it. I might take a look at this myself after the exam tomorrow. * The second warp engine should be working as of day 0. (There was never anything magical about the second warp pipe, you might not even be able to use only one warp pipe on the G400 with the microcode we have.) * No idea wether any warp improvements are planned. * multitexturing was enabled at one point but was disabled later on because it was unstable. > What about 3DNOW/3DNOWEXT for MESA / the MGA driver ? No idea. > What about the second head of the G400DH, or the video out. No idea, I assume you know of the fbdev driver for it in the later linux kernels though? regards Andreas Ehliar |
From: FT R. <ma...@mu...> - 2000-08-16 14:48:15
|
Hi DRI on mga is very unstable even on 16bpp, there would not be any use making it work with 32bpp. FT On Wed, 16 Aug 2000, Andreas Ehliar wrote: > On Wed, Aug 16, 2000 at 12:42:51AM +0200, Michael Meding wrote: > > Hi everybody, > > > > is there ongoing effort to get 32bpp working on the G400 ? The second > > warp engine / warp improvements / multitexturing (if not included > > already :-)) ? > > * 32bpp shouldn't be too hard to add but I don't know if anyone is > working on it. I might take a look at this myself after the exam > tomorrow. > > * The second warp engine should be working as of day 0. (There was never > anything magical about the second warp pipe, you might not even be able > to use only one warp pipe on the G400 with the microcode we have.) > > * No idea wether any warp improvements are planned. > > * multitexturing was enabled at one point but was disabled later on > because it was unstable. > > > What about 3DNOW/3DNOWEXT for MESA / the MGA driver ? > No idea. > > What about the second head of the G400DH, or the video out. > No idea, I assume you know of the fbdev driver for it in the later > linux kernels though? > > regards > Andreas Ehliar > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel > |
From: Michael M. <Michael@Meding.net> - 2000-08-16 15:17:15
|
FT Rathore schrieb: > > Hi > DRI on mga is very unstable even on 16bpp, there would not be any use > making it work with 32bpp. > FT Excuse me unstable ? Who told you this crap ? I don't want to offend you, but despite some pixel corruptions, which are not due to dri but rather the mga driver, DRI seems pretty stable to me (my wild guesses). Hours of intensive testing I have spend on this not one crash in the last days. So what gives ? Maybe your system is misconfigured. How does the unstability you see materialize ? Can you tell me what happened on your system, what do you have running which codeversion on which distri with which compiler ? Maybe the people here on the list can help you stabilize this thing.... Just, and it pretty obvious, my 2c. Regards Michael |
From: <pk...@ed...> - 2000-08-16 15:41:16
|
On Wed, 16 Aug 2000, Michael Meding wrote: > FT Rathore schrieb: > > > > Hi > > DRI on mga is very unstable even on 16bpp, there would not be any use > > making it work with 32bpp. > > FT > Excuse me unstable ? Who told you this crap ? I don't want to offend > you, but despite some pixel corruptions, which are not due to dri but > rather the mga driver, DRI seems pretty stable to me (my wild guesses). > Hours of intensive testing I have spend on this not one crash in the > last days. So what gives ? > I have at least 2 programs that cause full system crash (powercycle needed) when using MGA DRI with G400 on a PIII (BX-motherboard). I've posted a bug report but nobody seems to be interested.. or people have more important things to hack. - Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. |
From: Nathan H. <na...@ma...> - 2000-08-16 16:16:17
|
On Wed, Aug 16, 2000 at 06:41:12PM +0300, Pasi Kärkkäinen wrote: > > I have at least 2 programs that cause full system crash (powercycle > needed) when using MGA DRI with G400 on a PIII (BX-motherboard). > > I've posted a bug report but nobody seems to be interested.. or people > have more important things to hack. People are definitely interested. It's just sometimes hard to replicate these bugs and people stay quiet until they've at least managed to make some progress on replicating and fixing the bug. Don't take the silence badly: it means people are busy looking first then talking later. One good thing to do is put these bug reports on dri.sourceforge.net in the bug tracker. Bugs in there eventually get fixed. On email they will sometimes get lost. -- Microsoft Windows 2000. Now with more than 63000 known innovations. |
From: <pk...@ed...> - 2000-08-17 11:41:03
|
On Thu, 17 Aug 2000, Nathan Hand wrote: > On Wed, Aug 16, 2000 at 06:41:12PM +0300, Pasi Kärkkäinen wrote: > > > > I have at least 2 programs that cause full system crash (powercycle > > needed) when using MGA DRI with G400 on a PIII (BX-motherboard). > > > > I've posted a bug report but nobody seems to be interested.. or people > > have more important things to hack. > > People are definitely interested. It's just sometimes hard to replicate > these bugs and people stay quiet until they've at least managed to make > some progress on replicating and fixing the bug. Don't take the silence > badly: it means people are busy looking first then talking later. > > One good thing to do is put these bug reports on dri.sourceforge.net in > the bug tracker. Bugs in there eventually get fixed. On email they will > sometimes get lost. > Yes, I have submitted a bugreport to the dri's bug tracker. I'm also trying to get the sources for those demos to find out what's causing the crashes. - Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. |
From: Michael H. <mdh...@ho...> - 2000-08-16 16:20:53
|
If the stuff that's crashing will build on FreeBSD I would be happy to try it here. The only things I've run are the demos that come with Mesa and glclock. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... Make everything as simple as possible, but not simpler. -- Einstein |
From: Jeff H. <jha...@va...> - 2000-08-16 17:05:25
|
Okay here is the skinny: We know there is a serious bug(s) with the mga driver that causes some peoples systems to crash. It happens on some systems, and doesn't happen on others. We did all of our testing on 2.3.99-pre5 when we did the driver development. It seems that 2.4.0-test? doesn't seem to work very well. That is what I'm working on at the moment. As many of you know multitexture is broken. This particular bug is where most of my time has been spent. We are working closely with Matrox to identify the problem. Something with the way we are interacting with the card causes the cards texturing unit to crash when in multitexture mode. This has proven to be a very difficult problem to track down, but has been our highest priority. I think that Matrox just released a binary beta 4.0.1 module which replaces the mga_drv.o file. It does require a binary component to build correctly so it is only usable as a binary at this time. You can get this at www.matroxusers.com. With multihead only the first screen has accelerated opengl rendering. At this time accelerated opengl on the second head is not planned. 32 bpp is a feature that we plan to add. However fixing the multitexture and crash bugs are our first priority. Until these are fixed, it will not be added. I will be checking in a fix for font corruption later today from Mark V. It had to do with the way planemasks were handled. We do not have documentation for the WARP microcode, so any improvements to the WARP are not planned by us directly. Matrox would have to do these improvements for their own drivers before we got them. We are currently running their latest microcode for the g200/g400. Hope this answers everyones questions. If I missed one please forgive me ;) -Jeff |
From: Damon L. <dlo...@se...> - 2000-08-16 19:34:01
|
On Wed, 16 Aug 2000, Jeff Hartmann wrote: > > Okay here is the skinny: > > We know there is a serious bug(s) with the mga driver that causes some > peoples systems to crash. It happens on some systems, and doesn't > happen on others. We did all of our testing on 2.3.99-pre5 when we did > the driver development. It seems that 2.4.0-test? doesn't seem to work > very well. That is what I'm working on at the moment. Ok.. now I am interested.. I am running 2.4-test5 with a earlier CVS version of the XFree86-DRI tree and haven't come across any problems.. yet. Q3 runs smooth, DVD playback is cool, and the video editing suites I am trying out seem to run quite nippy. You want to point me to some test kits that I can stress my configuration as it is now? Not that I am complaining, just if I can help narrow down a problem it'll be better for all of us, no? <SNIP> -- === "If you can keep your head when all about you are losing theirs... you're missing something IMPORTANT!" Rob. (prolly teefed tho') |
From: FT R. <ma...@mu...> - 2000-08-16 19:52:48
|
Hi UnrealTournament does seem to crash it often FT On Wed, 16 Aug 2000, Damon LoCascio wrote: > On Wed, 16 Aug 2000, Jeff Hartmann wrote: > > > > > Okay here is the skinny: > > > > We know there is a serious bug(s) with the mga driver that causes some > > peoples systems to crash. It happens on some systems, and doesn't > > happen on others. We did all of our testing on 2.3.99-pre5 when we did > > the driver development. It seems that 2.4.0-test? doesn't seem to work > > very well. That is what I'm working on at the moment. > > > Ok.. now I am interested.. I am running 2.4-test5 with a earlier CVS > version of the XFree86-DRI tree and haven't come across any problems.. > yet. Q3 runs smooth, DVD playback is cool, and the video editing suites I > am trying out seem to run quite nippy. > > You want to point me to some test kits that I can stress my > configuration as it is now? Not that I am complaining, just if I can help > narrow down a problem it'll be better for all of us, no? > > <SNIP> > > > -- > === > > "If you can keep your head when all about you are losing theirs... you're > missing something IMPORTANT!" > Rob. (prolly teefed tho') > |
From: <pk...@ed...> - 2000-08-17 11:39:48
|
On 16 Aug 2000, Michael Harnois wrote: > If the stuff that's crashing will build on FreeBSD I would be happy to > try it here. The only things I've run are the demos that come with > Mesa and glclock. > Sorry, the demos that are crashing my box are binary-only demos. Maybe you could try using linux-binary emulation or something? Those demos use glut. ftp://ftp.nl.scene.org/pub/scene.org/parties/1999/tp99/demo/accel/ast-a2.zip (file called demo-lnx.elf) and the other: ftp://ftp.dutchfun.de/pub/asm00/demo/haugyjob.zip - Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. |
From: Michael H. <mdh...@ho...> - 2000-08-17 06:31:56
|
On Wed, 16 Aug 2000 10:03:24 -0600, Jeff Hartmann <jha...@va...> said: > I will be checking in a fix for font corruption later today from > Mark V. It had to do with the way planemasks were handled. I wasn't experiencing the problem with font corruption until I updated my tree and built about half an hour ago. Now I am ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... God shows his contempt for wealth by the kind of person He selects to receive it. -- Austin O'Malley |
From: FT R. <ma...@mu...> - 2000-08-17 20:14:36
|
Same here I started seeing the pixel corruption afterupdating from CVS last night, and it goes away if DRI is not being used. BTW the binary driver from martox does not do DRI, Ill try to compile it myself. FT On 17 Aug 2000, Michael Harnois wrote: > On Wed, 16 Aug 2000 10:03:24 -0600, Jeff Hartmann <jha...@va...> said: > > > I will be checking in a fix for font corruption later today from > > Mark V. It had to do with the way planemasks were handled. > > I wasn't experiencing the problem with font corruption until I updated > my tree and built about half an hour ago. Now I am ... > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdh...@ho... aa...@aa... > God shows his contempt for wealth by the kind of person > He selects to receive it. -- Austin O'Malley > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel > |
From: <pk...@ed...> - 2000-08-17 21:00:16
|
On Thu, 17 Aug 2000, FT Rathore wrote: > Same here I started seeing the pixel corruption afterupdating from CVS > last night, and it goes away if DRI is not being used. > > BTW the binary driver from martox does not do DRI, Ill try to compile it > myself. > FT > I can confirm the corruption also. I updated my DRI-tree from the CVS couple of hours ago. - Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. |
From: Michael H. <mdh...@ho...> - 2000-08-19 17:46:01
|
The font corruption seems to be fixed here, as of updating and rebuilding last night. Thanks to whoever found the problem. Now if someone could suggest where I'm going wrong here. When I run a DRI-enabled app as root, it does not use direct rendering. When I run it as an ordinary user, X stops. The mouse continues to move, but does nothing. The keyboard has no effect. However I can telnet in to the machine from another and kill the offending process, and then X returns to normal. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... "Times are bad. Children no longer obey their parents, and everyone is writing a book." -- Marcus Tullius Cicero |
From: Michael H. <mdh...@ho...> - 2000-08-26 01:48:13
|
Sigh ... every time something changes in the tree, I rebuild with excitement and anticipation. Still no luck. Any app linked with libGL hangs the xserver until killed from the outside ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdh...@ho... aa...@aa... "He who will not reason is a bigot; he who cannot is a fool; and he who dares not, is a slave." -- William Drummond |
From: FT R. <ma...@mu...> - 2000-08-16 15:41:20
|
Hi Man are you lucky, (no offecne taken) maybe we can get to the bottom of this. Please look at my bug report at: http://sourceforge.net/bugs/?func=detailbug&group_id=387&bug_id=109001 And also look at my previous posts Most of the posts ive seen on this list about mga confirm the problem, and a lot of people have sent me emails confirming this problem. Can you please tell me the configuration you are running. Like motheboard chipset and other stuff, I have been trying to debug this problem and have even switched my motherboard from 400BX to VIA. On Wed, 16 Aug 2000, Michael Meding wrote: > FT Rathore schrieb: > > > > Hi > > DRI on mga is very unstable even on 16bpp, there would not be any use > > making it work with 32bpp. > > FT > Excuse me unstable ? Who told you this crap ? I don't want to offend > you, but despite some pixel corruptions, which are not due to dri but > rather the mga driver, DRI seems pretty stable to me (my wild guesses). > Hours of intensive testing I have spend on this not one crash in the > last days. So what gives ? > > Maybe your system is misconfigured. How does the unstability you see > materialize ? Can you tell me what happened on your system, what do you > have running which codeversion on which distri with which compiler ? > Maybe the people here on the list can help you stabilize this thing.... > > Just, and it pretty obvious, my 2c. > > Regards > > Michael > |