Created attachment 24733 [details] xorg.conf Server ~ # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) Server ~ # uname -a Linux Server 2.6.27-gentoo-r8 #12 SMP Sun Apr 12 20:35:46 CEST 2009 i686 Intel(R) Pentium(R) D CPU 3.00GHz GenuineIntel GNU/Linux Server ~ # grep drm /var/log/Xorg.0.log drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenByBusid: drmOpenMinor returns 10 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 (II) [drm] DRM interface version 1.3 (II) [drm] DRM open master succeeded. (II) intel(0): [drm] Using the DRM lock SAREA also for drawables. (II) intel(0): [drm] framebuffer mapped by ddx driver (II) intel(0): [drm] added 1 reserved context for kernel (II) intel(0): [drm] installed DRM signal handler (II) intel(0): [drm] Registers = 0xfe980000 (II) intel(0): [drm] ring buffer = 0xd0000000 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8835000 at 0xb796a000 (II) intel(0): [drm] Closed DRM master. Server ~ # grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (EE) intel(0): I830 Dma Initialization Failed Server ~ # dmesg | grep drm [drm] Initialized drm 1.1.0 20060810 [drm] Initialized i915 1.6.0 20060119 on minor 0 [drm:i915_getparam] *ERROR* Unknown parameter 5 [drm:i915_initialize] *ERROR* can not ioremap virtual address for ring buffer
Created attachment 24734 [details] Xorg.0.log
Created attachment 24735 [details] dmesg
xorg-server-1.5.3 libdrm-2.4.5 xf86-video-intel-2.6.3
Server ~ # lspci -vv ... 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device 2772 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fe980000 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at bc00 [size=8] Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 3: Memory at fe940000 (32-bit, non-prefetchable) [size=256K] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable- Address: 00000000 Data: 0000 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510769 drm:i915_getparam *ERROR* Unknown parameter 5 "... this message is emitted if you're using xf86-video-intel >= 2.5 on a kernel < 2.6.28, because the driver is poking for GEM support; the message is harmless, and can be safely ignored ..."
Server ~ # glxgears 1352 frames in 5.0 seconds = 269.276 FPS 1356 frames in 5.0 seconds = 271.033 FPS
mesa-7.3
so what's your problem, other than the "ERROR" message?
HW acceleration (DRI) does not work. glxgears reports ~270 FPS. Isn't it too slow for G945? Is it caused by "old" kernel 2.6.27 with no GEM support?
(**) intel(0): Tiling enabled (==) intel(0): VideoRam: 262144 KB (II) intel(0): Attempting memory allocation with tiled buffers. (II) intel(0): Tiled allocation successful. (II) intel(0): [drm] Registers = 0xfe980000 (II) intel(0): [drm] ring buffer = 0xd0000000 (EE) intel(0): I830 Dma Initialization Failed Is it related to tiling problem (http://bugs.freedesktop.org/show_bug.cgi?id=16835)?
Created attachment 24793 [details] Xorg.0.log with ModeDebug
Ping? DRI should be working if using compatible kernels and userspace...
The code paths indicated here, UMS and EXA, have been removed from the driver. Please file a new bug if the current kernel, ddx or mesa fail on your hardware.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.