Re: [Dri-devel] Radeon problem
On Mon, 10 Nov 2003 09:05:07 +0100 Mark Baas [EMAIL PROTECTED] wrote: Hey, When running Scorched3d I get this error: drmCommandWrite: -22 drmRadeonCmdBuffer: -22 (exiting) I also got this error with a GameSkel of Soya3d http://oomadness.tuxfamily.org/en/soya/game_skel.html I just committed a fix for this (or a similar) problem. If you compile DRI from source please try a cvs update. Otherwise wait for the next snapshot. -- Mark Baas [EMAIL PROTECTED]) - Penguin Liberation Front - Best regards, Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
Joseph Carter [EMAIL PROTECTED] writes: I spoke too soon, it would seem. 22 March 2001 also dies, it just managed to remain functional overnight. It crashed, hard, as did later. It took the whole box down in the process. Thankfully this box uses reiserfs. It was converted immedately after I ended up with a corrupt filesystem one of the last times X did this to me.. ReiserFS is more prone to fs corruption than ext2. OTOH, you don't have to wait for a looong time to fsck big partitions. 2.4 itself has a few problems... just read the changelog for the latest ac kernels. Radeon support is not even pre-alpha quality right now IMO. =( It (well, yesterdays) works fine on Red Hat Linux Wolverine + rawhide updates, except for Descent 3. This has been a problem with all Radeon drivers I've tried, though. -- Trond Eivind Glomsrd Red Hat, Inc. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
Joseph Carter wrote: Radeon support is not even pre-alpha quality right now IMO. =( Mate, that's a pretty strong statement to be making. Yes, you are having problems. Lots of other people aren't (myself included). Let me guess -- you have an AMD chipset? An AMD 750 perhaps? -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
On Thu, Mar 29, 2001 at 02:20:53PM -0500, Trond Eivind Glomsr?d wrote: Thankfully this box uses reiserfs. It was converted immedately after I ended up with a corrupt filesystem one of the last times X did this to me.. ReiserFS is more prone to fs corruption than ext2. OTOH, you don't have to wait for a looong time to fsck big partitions. 2.4 itself has a few problems... just read the changelog for the latest ac kernels. Reiser is more prone to corruption in operation.. It seems to survive a crash better though. The last of the problems that kept me from running it have been fixed thankfully. Radeon support is not even pre-alpha quality right now IMO. =( It (well, yesterdays) works fine on Red Hat Linux Wolverine + rawhide updates, except for Descent 3. This has been a problem with all Radeon drivers I've tried, though. Current speculation is that it might be some issue with agpgart and my Abit KT-7A.. Of course, since it's crashing in 2D, I don't see how that can be the source of the problem. I'm going to see if there are BIOS updates for it and I may also try the Mesa 3.5 branch. I'm seriously regretting my choice of the Radeon at the moment, that's for sure. -- Joseph Carter [EMAIL PROTECTED]Free software developer == Signoff: Beregond (Klingon function calls do not have 'parameters' -- they have 'arguments' -- and they ALWAYS WIN THEM.) at 02:00PM PGP signature
Re: [Dri-devel] Radeon problem
Joseph Carter wrote: Current speculation is that it might be some issue with agpgart and my Abit KT-7A.. Of course, since it's crashing in 2D, I don't see how that can be the source of the problem. If the DRI is enabled (and I'm guessing that's the whole point, or you wouldn't be posting in this forum), 2D acceleration is done with bus mastering DMA via AGP. Hence, problems with your AGP support will be fatal. Have you tried running with the DRI disabled? -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
Joseph Carter wrote: Current speculation is that it might be some issue with agpgart and my Abit KT-7A.. Of course, since it's crashing in 2D, I don't see how that can be the source of the problem. It actually VERY unlikely that agpgart is your problem. VIA support has been pretty solid in agpgart since I originally wrote agpgart. In fact the first chipset that worked under agpgart was a VIA MVP3. If your enabling the DRI, its actually going to use the same DMA mechanism that 3D uses to get 2D commands to the card. Have you tried the driver without the dri enabled? (i.e., Have you tried 8bpp or not loading the dri/drm modules?) I'm going to see if there are BIOS updates for it and I may also try the Mesa 3.5 branch. I'm seriously regretting my choice of the Radeon at the moment, that's for sure. I personally would suggest narrowing the problem down first before you get experimental code. I also wouldn't suggest flashing the BIOS on a video card unless you know exactly what your doing. Its possible that you could render the card useless if you do it incorrectly. -Jeff ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
On Thu, 29 Mar 2001, Adam K Kirchhoff wrote: On Thu, 29 Mar 2001, Joseph Carter wrote: I'm going to see if there are BIOS updates for it and I may also try the Mesa 3.5 branch. I'm seriously regretting my choice of the Radeon at the moment, that's for sure. With all the negativity floating around, I'd like to say that I think the DRI developers have done an *awesome* job on all the drivers I've used (Voodoo3/4/5, Rage 128, G400, i810, and Radeon). Aside from a handful of problems (most due to configuration errors on my end) these drivers have worked nearly flawlessly for me. These driver have *never* caused me to regret buying the cards I did, and have, on more than one occaision, made me proud of the choices I made. Anytime the dri developers are in the Philadelphia area, dinner is on me :-) Same here. It seems like DRI rolls along swiftly and surely to greater, faster, and more stable code, despite what seems like a serious lack of bandwidth/hardware/docs/appreciation supplied to the developers. At some stages in time, some things are going to be broken, but nobody is forcing the user to run the latest and greatest. CVS has the ability to checkout arbitrary dates and revisions. Take advantage of that. -jwb ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
Jeff Hartmann [EMAIL PROTECTED] writes: Joseph Carter wrote: On Thu, Mar 29, 2001 at 01:36:40PM -0700, Jeff Hartmann wrote: I haven't, I'll comment the drm/dri modules out and see how that works. Just to be on the safe side, I will also make sure radeon/agpgart are not loaded in the kernel. It'll probably take a day or so to know if that works, but I suspect I'll know in a couple hours if it doesn't. Are you using the radeon module from the kernel? If you are this could possibly be a source of the problems. If you are using DRI CVS use the kernel modules from the CVS tree. The kernel modules that come with the kernel will only work properly with a release version of XFree86. Its very likely that we have changed things in the DRI CVS tree that require kernel module changes. I had the radeon module from the kernel, but was told that should not affect 2D. (Also was told agpgart wouldn't affect it, but seems that's not quite true..) CVS drm has its up()'s and down()'s (pun intended) still and that needs to change with more recent kernels. I just haven't had much time to do anything with it yet. Here is my recommendation: use 2.4.2 (don't use a pre patch unless you want to take all respondsibility for breakage.) 2.4.2 has known corruption issues. -- Trond Eivind Glomsrd Red Hat, Inc. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
Our policy is the following: We only submit kernel changes which will be compatible with the latest XFree86 release to the kernel. When there is a new XFree86 release, there will be updates. This does not include bugfixes which are backwards compatible, which we tend to send more frequently. But there has never been an official release for Radeon - hence, no such problems. 4.0.3 doesn't support Radeon, AFAIR. From XFree86.org's driver status page: 4.0.3: Accelerated support is provided for Mach64, Rage, Rage 128 and Radeon chips. AFAIK, Radeon 3D is at least marginally functional in 4.0.3 as well. I believe you said you were on a Via Apollo chipset? Could you narrow that down a bit? My advice/bugfixes vary wildly based on the chipset in question. For instance: The Apollo Pro 133A (6934) has severe AGP4X issues in some implementations, but the 6934X and 6934DP/6934XDP haven't shown evidence of the same issues. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Radeon problem
"AMD-760MP" [EMAIL PROTECTED] writes: Our policy is the following: We only submit kernel changes which will be compatible with the latest XFree86 release to the kernel. When there is a new XFree86 release, there will be updates. This does not include bugfixes which are backwards compatible, which we tend to send more frequently. But there has never been an official release for Radeon - hence, no such problems. 4.0.3 doesn't support Radeon, AFAIR. From XFree86.org's driver status page: 4.0.3: Accelerated support is provided for Mach64, Rage, Rage 128 and Radeon chips. That's 2D - no 3D support. I believe you said you were on a Via Apollo chipset? Wrong person - I'm running it successfully on an ASUS A7V133 - this would be a VIA KT133A. -- Trond Eivind Glomsrd Red Hat, Inc. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
