On Wed August 31 2005 1:36 am, Thorsten Leemhuis wrote: > Am Dienstag, den 30.08.2005, 11:48 -0400 schrieb Claude Jones: > > [...] > > I still can't tell if they're active because of the anomalies > > I reported in my previous posts. > > Look at your /var/log/Xorg.0.log -- you should see there if the driver > and DRI are active. > I looked, but I can't say I know what I was looking at. There's definitely fglrx activity, but there appear numerous error messages. It's a huge section of that log, so I am not sure whether I should post it. A sample: (II) Loading /usr/X11R6/lib/modules/drivers/fglrx_drv.o (II) Module fglrx: vendor="FireGL - ATI Technologies Inc." compiled for 6.8.0, module version = 8.16.20 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 It would seem that the driver is being loaded, though all sorts of error messages follow later on: II) ATI Proprietary Linux Driver Version Identifier:8.16.20 (II) ATI Proprietary Linux Driver Release Identifier: @@UNRELEASED_AND_UNSUPPORTED_DRIVER@@ (II) ATI Proprietary Linux Driver Build Date: Aug 16 2005 00:15:14 (II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.16.1-driver-lnx-206829 (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found Then later, regarding DRI: (II) fglrx(0): doing DRIScreenInit drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID PCI:1:0:0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) But then, later: (II) fglrx(0): [drm] register handle = 0xfe9f0000 (II) fglrx(0): [agp] Mode=0x1f004a1b bridge: 0x8086/0x2570 (II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000000 (II) fglrx(0): [agp] AGP v3 disable mask 0x00000000 (II) fglrx(0): [agp] enabling AGP with mode=0x1f004b1a (II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f004312) (II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode) (II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes (II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 28672 (II) fglrx(0): [drm] texture shared area handle = 0xf8f81000 (II) fglrx(0): shared FSAAScale=1 (II) fglrx(0): DRI initialization successfull! So, it would appear that DRI is up. These samples probably represent less than 10% of the lines containing ATI or fgrlx - I can post the whole thing if necessary. > I'll look into your "anomalies", but I did not find the time yet. > Ok- thanks -- Claude Jones Bluemont, VA, USA
