Re: [gentoo-user] Re: Speed up GoogleEarth on an ATI RV370 5B60 [Radeon X300 (PCIE)]?

Re: [gentoo-user] Re: Speed up GoogleEarth on an ATI RV370 5B60 [Radeon X300 (PCIE)]?

[Walter Dnes]

Reply-To 
In-Reply-To: <200703100155.58144.bss03@volumehost.net>

On Sat, Mar 10, 2007 at 01:55:57AM -0600, Boyd Stephen Smith Jr. wrote

> Well, then you have DRI working.
> 
> You might enable/disable some driver options and/or server extensions to 
> get the best speed out of your DRI.
> 
> > server glx vendor string: SGI
> 
> However, it looks like you might be using the wrong driver or glx library; 
> I've fairly sure this is supposed to be 'ATI' when using fglrx.  Anything 
> interesting in grep -E '\((EE|WW)\)' /var/log/Xorg.0.log ?

  A few items of interest.  I actually ran
grep -A5 -B5 -E '\((EE|WW)\)' /var/log/Xorg.0.log
and then trimmed down a bit.

1)
1609-(**) Extension "XVideo" is enabled
1644:(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
1718-(II) No APM support in BIOS or kernel
1756-(II) Module ABI versions:
1782-   X.Org ANSI C Emulation: 0.3

  I assume that this means no screensaver.


2)
21946-(II) ATI Proprietary Linux Driver Build Date: Dec 12 2006 17:18:27
22013-(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.32.2.1.2.3-driver-lnx-x86-x86_64-313294
22125-(--) Assigning device section with no busID to primary device
22187:(WW) fglrx: No matching Device section for instance (BusID PCI:5:0:1) found
22263-(--) Chipset RADEON X300/X550 Series (RV370 5B60) found

  lspci shows 2 entries for the video card...
05:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
05:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]

  What is the second entry dupposed to be for?

3)
(II) fglrx(0): Acceleration enabled
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(==) fglrx(0): Using hardware cursor
(**) fglrx(0): Video overlay enabled on CRTC1

  Does this matter at all?

4)
drmOpenByBusid: Searching for BusID PCI:5:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports PCI:5:0:0
(EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX: reverting to software rendering

  "reverting to software rendering" ouch.  This is probably it.  Now
what?

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Forget about it already

[Walter Dnes]

  I've just unmerged ati-drivers and gone back to regular mode.

  1) Windows emulation is all and good, but I can do without the hard
lockups, thank you.

  2) In addition to random lockups, I lost the ability to run X at
lower resolutions like 640x480, 512x384, and 400x300.  This is both via
xrandr and via custom modelines.  I prefer to run videos at these lower
resolutions, rather than take the cpu hit for software scaling to get
the videos to a reasonable size.

  3) Firefox fonts suck in fglrx mode versus regular mode.  Since I used
the old xorg.conf, I don't see why that should happen.

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
-- 
gentoo-user@gentoo.org mailing list