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 j
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
--
Mark Baas <[EMAIL PROTECTED])
- Penguin Liberation Front -
---
On Thu, Mar 29, 2001 at 06:02:03PM -0500, AMD-760MP wrote:
> 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.
Not him, me..
Kernel identified it as being an Apollo, it never crossed my mind t
On Thu, Mar 29, 2001 at 02:00:40PM -0700, Jeff Hartmann wrote:
> > 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
On Thu, Mar 29, 2001 at 12:41:15PM -0800, Jeffrey W. Baker wrote:
> 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.
FWIW, I have
Gareth Hughes wrote:
>
> Sorry, been terribly busy this week. I'll reply today, I promoise :-)
And one day I'll learn to spell. Or ensure I have a cup of coffee
before replying to any email...
-- Gareth
___
Dri-devel mailing list
[EMAIL PROTECTED]
AMD-760MP wrote:
>
> > Anytime the dri developers are in the Philadelphia area, dinner is on me
> > :-)
> >
> > Adam
>
> Only if I don't get to them first. :)
>
> Gareth - You never answered my last mail... What kind of microbrews do you
> like? I've got a box and peanuts and the UPS label read
On Thu, 29 Mar 2001, Keith Whitwell wrote:
> AMD-760MP wrote:
> >
> > > Anytime the dri developers are in the Philadelphia area, dinner is on me
> > > :-)
> > >
> > > Adam
> >
> > Only if I don't get to them first. :)
> >
> > Gareth - You never answered my last mail... What kind of microbrews d
AMD-760MP wrote:
>
> > Anytime the dri developers are in the Philadelphia area, dinner is on me
> > :-)
> >
> > Adam
>
> Only if I don't get to them first. :)
>
> Gareth - You never answered my last mail... What kind of microbrews do you
> like? I've got a box and peanuts and the UPS label read
"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
> > 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
> Anytime the dri developers are in the Philadelphia area, dinner is on me
> :-)
>
> Adam
Only if I don't get to them first. :)
Gareth - You never answered my last mail... What kind of microbrews do you
like? I've got a box and peanuts and the UPS label ready to print.
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
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 o
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
> > wo
Jeff Hartmann <[EMAIL PROTECTED]> writes:
> Trond Eivind Glomsrød wrote:
>
> > Jeff Hartmann <[EMAIL PROTECTED]> writes:
> >
> >> 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 modul
Trond Eivind Glomsrød wrote:
> Jeff Hartmann <[EMAIL PROTECTED]> writes:
>
>> 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 w
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 t
Jeff Hartmann <[EMAIL PROTECTED]> writes:
> 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
On Thu, Mar 29, 2001 at 01:11:07PM -0700, Jeff Hartmann 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.
> >
> I personally would suggest narrowing the pro
Joseph Carter wrote:
> On Fri, Mar 30, 2001 at 06:07:19AM +1000, Gareth Hughes 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
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 th
On Fri, Mar 30, 2001 at 06:07:19AM +1000, Gareth Hughes 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
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 so
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 postin
On Fri, Mar 30, 2001 at 05:23:27AM +1000, Gareth Hughes 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
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
Joseph Carter wrote:
>
> Radeon support is not even pre-alpha quality right now IMO. =(
And just because it's 5:30am and I'm nearing the end of yet another 18+
hour day working on the DRI drivers, I think I have the right to say
that this kind of thing is not going to motivate any of the core
d
On Thu, 29 Mar 2001, Joseph Carter wrote:
> On Wed, Mar 28, 2001 at 11:07:44PM -0800, Joseph Carter wrote:
> > > I have a 32 meg DDR radeon on an athlon slot A box. I have got DRI-CVS to
> > > install and all the modules are loaded corectaly, but when I startx i get
> > > a white screen with a
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
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 immedat
On Wed, Mar 28, 2001 at 11:07:44PM -0800, Joseph Carter wrote:
> > I have a 32 meg DDR radeon on an athlon slot A box. I have got DRI-CVS to
> > install and all the modules are loaded corectaly, but when I startx i get
> > a white screen with an outline of console and a block as the curser.
>
On 29 Mar 2001, mgestudios wrote:
> I have a 32 meg DDR radeon on an athlon slot A box. I have got DRI-CVS to
> install and all the modules are loaded corectaly, but when I startx i get
> a white screen with an outline of console and a block as the curser.
I had the same problem on a Slot A s
On Thu, Mar 29, 2001 at 05:06:01AM -, mgestudios wrote:
> I have a 32 meg DDR radeon on an athlon slot A box. I have got DRI-CVS to
> install and all the modules are loaded corectaly, but when I startx i get
> a white screen with an outline of console and a block as the curser.
Just a wild
I have a 32 meg DDR radeon on an athlon slot A box. I have got DRI-CVS to
install and all the modules are loaded corectaly, but when I startx i get
a white screen with an outline of console and a block as the curser.
Become a BN3 affiliate, $2 per lead, $65 per sale, http://es.bn3.com/aff.jx
35 matches
Mail list logo