Dave Airlie wrote:
Hmm.. thought I had.. hadn't.. I've just picked it up from git and put it
in CVS.. hopefully it works .. I've got to reboot to test it properly ..
Dave.
Now it's ok, thanx.
Bye, Dario.
--
Laera Dario
Undergraduate student at Computer Science
University of Bologna
ICQ# 203
> > is loaded before the radeon kernel module.
> >
> > I get this error with linux-2.6.13 and 2.6.9 both with agpgart and
> > uninorth driver built in. The drm module is from cvs, and I've tried
> > with xorg-6.8.99.15 and cvs. I'm running on a powebook5,2 with r300
> > card. You can find some logs
On Thu, 2005-09-29 at 13:56 +0200, Dario Laera wrote:
> Hi all,
> since some week I'm no more able to load DRI, this is the error:
>
> (II) RADEON(0): [agp] 8192 kB allocated with handle 0x0001
> (EE) RADEON(0): [agp] Could not add ring mapping
> (EE) RADEON(0): [agp] AGP failed to initialize.
Hi all,
since some week I'm no more able to load DRI, this is the error:
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x0001
(EE) RADEON(0): [agp] Could not add ring mapping
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make su
On Thu, 2005-08-25 at 23:42 +0200, Jerome Glisse wrote:
> IIRC there have been a patch to xorg for that and to DRM
> too. Give it a try :)
For whatever reason, I can't seem to build xorg right now. I'll have a
try another time, but thanks for the heads-up.
johannes
signature.asc
Description: T
On Thu, 2005-08-25 at 23:26 +0200, Johannes Berg wrote:
> On Wed, 2005-06-22 at 18:36 +1000, Benjamin Herrenschmidt wrote:
>
> > The problem is simple: when setting up the AGP aperture, it's putting it
> > after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy,
> > CONFIG_APER_SIZE
On 8/25/05, Johannes Berg <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-06-22 at 18:36 +1000, Benjamin Herrenschmidt wrote:
>
> > The problem is simple: when setting up the AGP aperture, it's putting it
> > after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy,
> > CONFIG_APER_SIZE mig
On Wed, 2005-06-22 at 18:36 +1000, Benjamin Herrenschmidt wrote:
> The problem is simple: when setting up the AGP aperture, it's putting it
> after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy,
> CONFIG_APER_SIZE might only be _half_ of the mapped vram space (as the
> card can b
On Tue, 2005-06-21 at 16:44 +0200, Johannes Berg wrote:
> Jerome Glisse wrote:
>
> >I can remember from the top of my head but there is maybe some patch
> >that could be revealent for ppc not included in this snapshot. Thus i think
> >you should consider trying building xorg from cvs. Anyway with
Jerome Glisse wrote:
I can remember from the top of my head but there is maybe some patch
that could be revealent for ppc not included in this snapshot. Thus i think
you should consider trying building xorg from cvs. Anyway with a g4 it will
compiles a lot faster than on dumb x86 ;)
Ok, I'll
On 6/21/05, Nicolai Haehnle <[EMAIL PROTECTED]> wrote:
> On Tuesday 21 June 2005 10:54, Jerome Glisse wrote:
> > On 6/21/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > > On Sat, 18 Jun 2005, Johannes Berg wrote:
> > > > Any idea where I should start looking for the source of the lockups or
>
Hi,
I mainly used r300 on ppc so far thus yes it works.
Good to know.
I am using it on x86 for
the 9800 lockup. But as i used a g5 i don't know if there is an issue with the
agp of g4, don't think so... And IIRC someone told me that it worked on a
powerbook which is, i presume, what Johannes
On 6/21/05, Johannes Berg <[EMAIL PROTECTED]> wrote:
> Hi,
>
> >I mainly used r300 on ppc so far thus yes it works.
> >
> Good to know.
>
> >I am using it on x86 for
> >the 9800 lockup. But as i used a g5 i don't know if there is an issue with
> >the
> >agp of g4, don't think so... And IIRC some
On Tuesday 21 June 2005 10:54, Jerome Glisse wrote:
> On 6/21/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > On Sat, 18 Jun 2005, Johannes Berg wrote:
> > > Any idea where I should start looking for the source of the lockups or
what else to do?
> >
> > The problem is likely either due to t
On 6/21/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> On Sat, 18 Jun 2005, Johannes Berg wrote:
> > Any idea where I should start looking for the source of the lockups or what
> > else to do?
>
> The problem is likely either due to the radeon memory controller - in
> particular registers li
On Sat, 18 Jun 2005, Johannes Berg wrote:
Hi,
I just tried the latest r300 cvs code (with current mesa cvs, latest
Xorg snapshot) but all I get is a lockup as soon as the X server starts.
If I have debugging enabled, I get a loop of radeon_do_cp_idle calls.
Hardware is:
:00:10.0 VGA comp
Hi,
I just tried the latest r300 cvs code (with current mesa cvs, latest
Xorg snapshot) but all I get is a lockup as soon as the X server starts.
If I have debugging enabled, I get a loop of radeon_do_cp_idle calls.
Hardware is:
:00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [
Jerome Glisse wrote:
I think it's related to r300 driver because i get something
with the r300 demo. I get the depth buffer with r300 demo
but not the color one. I think this is due to radeon base address
or to the R300_RB3D_COLOROFFSET0 setup, moreover there
is a need for some endian swapping with
Hi,
Finally i find my bug in AGP but r300 still not work.
You will see below revelant part of my xorg log.
I think it's related to r300 driver because i get something
with the r300 demo. I get the depth buffer with r300 demo
but not the color one. I think this is due to radeon base address
or to th
19 matches
Mail list logo
