Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Mar 2014 07:33:31 +0000
From:      Alexey Dokuchaev <danfe@FreeBSD.org>
To:        Justin Hibbits <chmeeedalf@gmail.com>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: PowerMac G4 graphics issue
Message-ID:  <20140330073331.GB30090@FreeBSD.org>
In-Reply-To: <20140329100217.505671e8@zhabar.att.net>
References:  <20081108120019.440D2106570D@hub.freebsd.org> <762295.44650.qm@web33105.mail.mud.yahoo.com> <20140329105152.GA73812@FreeBSD.org> <20140329124227.GA22005@FreeBSD.org> <CAHSQbTAy89HtJHfq1CmDGyygNwOVSh_19NnESgjvX1WhpdMDDQ@mail.gmail.com> <20140329164046.GA7227@FreeBSD.org> <20140329100217.505671e8@zhabar.att.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 29, 2014 at 10:02:17AM -0700, Justin Hibbits wrote:
> On Sat, 29 Mar 2014 16:40:46 +0000 Alexey Dokuchaev wrote:
> > HW accel seems to work: X11 overall feels quite fast; glxinfo reports:
> > 
> >   direct rendering: Yes
> >   server glx vendor string: SGI
> >   server glx version string: 1.4

I guess I spoke too soon; something is not quite right here, running Quake2
in GL mode clearly indicated that hw accel does not work.  I've also found
these lines in the Xorg.0.log:

  [  1679.643] (EE) AIGLX error: dlopen of /usr/local/lib/dri/r200_dri.so failed (Cannot open "/usr/local/lib/dri/r200_dri.so")
  [  1679.643] (EE) AIGLX: reverting to software rendering
  [  1680.188] (II) AIGLX: Loaded and initialized swrast
  [  1680.188] (II) GLX: Initialized DRISWRAST GL provider for screen 0

That's true, I don't have r200_dri.so there, but I do have radeon_dri.so;
why X is trying to load r200 one?

> > glxgears spin at ~53 FPS.  I haven't benchmarked Quake yet. ;-)
> 
> Awesome!  I've never had success with DRI on PowerPC.

I wish I had! ;-)  I've tried glxgears on my laptop (2.26GHz Dothan with
GMA900 video) -- it yielded almost 900 FPS.  Now that's closer to really
being hardware accelerated.

> I think X is just setting it to a square that's big enough to hold the
> current screen.  That's not always the case, though, as on my G5 I see:

There are a bunch of lines like these in the log:

  [  1678.663] (II) RADEON(0): Not using default mode "416x312" (vrefresh out of range)
  [  1678.663] (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range)

And then:

  [  1678.663] (II) RADEON(0): Printing probed modes for output DVI-1
  [  1678.663] (II) RADEON(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
  [  1678.663] (II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz d)
  [  1678.663] (II) RADEON(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
  [  1678.663] (II) RADEON(0): Modeline "512x384"x60.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
  [  1678.663] (II) RADEON(0): Modeline "400x300"x60.3   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
  [  1678.664] (II) RADEON(0): Modeline "320x240"x60.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)

I'll see if I can force the correct resolution via xorg.conf or something...

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140330073331.GB30090>