Hello, some trouble trying to make dri works with my card. It is a S3 savage 4 card with 16384 k video memory. I include logs here (I follow dri.freedesktop.org steps on troubleshooting): > lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 44) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 21) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) 00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 0d) 00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 30) 00:0a.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08) 00:0d.0 Communication controller: Rockwell International HSF 56k Data/Fax/Voice/Spkp (w/Handset) Modem (rev 01) 01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04) > dmesg | grep agp Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA Apollo Pro 133 chipset agpgart: AGP aperture is 64M @ 0xd8000000 agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode > dmesg | grep drm [drm] Initialized drm 1.0.1 20051102 [drm] Initialized savage 2.4.1 20050313 on minor 0 > cat /var/log/Xorg.0.log | grep "Direct rendering" (II) SAVAGE(0): Direct rendering enabled ..in Xorg.0.log there is also: (II) SAVAGE: driver (version 2.0.2) for S3 Savage chipsets: Savage4, Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, Twister PN133, Twister KN133, SuperSavage/MX 128, SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128, SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64, SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR, ProSavage DDR-K (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset Savage4 found > xdriinfo Screen 0: savage > glxinfo | grep "direct rendering" direct rendering: Yes lsmod lists these modules : savage, drm, via_agp, agpart, i2c_savage4, i2c_algo_bit, i2c_viapro, i2c_core All these with: - Slackware 11.0, kernel 2.6.17.13, X.org 6.9.0, savage_dri.so driver downloaded from snapshots (savage-20060403-linux.i386.tar.bz2), OpenGL renderer string: Mesa DRI Savage4 20050829 AGP 1x x86/MMX/SSE the computer hangs with glxgears after a little movement of mechanics. I tried also with: - Foresight 1.0, kernel 2.6.19.2, X.org 7.1.1 glxinfo complains : "libGL warning: 3D driver claims to not support visual 0x4B", so does glxgears but then hangs. and: - Zenwalk, kernel 2.6.18.6, X.org 7.1.1 launching glxgears appears a black window (but no hangs). - Ubuntu 7.04 beta I try with these options: set DmaMode to "None", BusType and DmaType to "PCI", ShadowStatus to "on". Launching glxgears 6-7 times seems to works for a little (about the time to print 10 FPS report), then stops (seems to hang), and then print "wait event returned -16". However, continue to run glxgears occurs a time when it hangs the pc. When it works it prints a FPS of about 80. Bye, Gaetano
The locking is broken with that version of the savage driver. You need either the latest version from git, or this patch: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-savage.git;a=commit;h=baa74b10d7a1c304dba2d658e4d1336b7ee7e70e
I think the above patch is included in version 2.1.2 which is on the Ubuntu 7.04 Beta (xserver-xorg-video-savage 1:2.1.2-1).
You might also try the savage drm from the drm git tree.
Created attachment 9416 [details] xorg log
Created attachment 9418 [details] xorg log
Created attachment 9419 [details] /etc/X11/xorg.conf
Created attachment 9420 [details] log
I think the drm (at least the savage part) is pretty much up to date on Ubuntu 7.04 Beta as well, AFAICS its kernel drm was synced with 2.6.21-rc4, and there haven't been many savage changes the last months. BTW, why isn't the savage_drv.h DRIVER_DATE updated since "20050313"? It makes it hard to tell from dmesg output how up-to-date the savage module is.
Not savage per se... http://bugzilla.kernel.org/show_bug.cgi?id=7767 (In reply to comment #8) > I think the drm (at least the savage part) is pretty much up to date on Ubuntu > 7.04 Beta as well, AFAICS its kernel drm was synced with 2.6.21-rc4, and there > haven't been many savage changes the last months. > > BTW, why isn't the savage_drv.h DRIVER_DATE updated since "20050313"? It makes > it hard to tell from dmesg output how up-to-date the savage module is. >
Not sure why this was moved to XIT, so moving back and closing as per comment #9 and 9 years of silence after that.
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.