Am Montag, den 07.02.2005, 15:12 +0100 schrieb [EMAIL PROTECTED]: > Hardware: > > Toshiba Libretto L2 Tm5600 with: > > 0000:00:04.0 VGA compatible controller: S3 Inc. 86C270-294=20 > Savage/IX-MV (rev 13) (prog-if 00 [VGA]) > Subsystem: Toshiba America Info Systems: Unknown device 0001 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-= > Stepping- SERR- FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium >TAbort- = > <TAbort- <MAbort- >SERR- <PERR- > Latency: 248 (1000ns min, 63750ns max), cache line size 08 > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=3D128= > M] > Expansion ROM at 000c0000 [disabled] [size=3D64K] > Capabilities: <available only to root> > > Software: > > Gentoo current with Gentoo supplied X Window System Version 6.8.1.903 (6.8.= > 2 RC 3) > Release Date: 25 January 2005 > X Protocol Version 11, Revision 0, Release 6.8.1.903 > Build Operating System: Linux 2.4.29-rc3-mhf239 i686 [ELF]=20 > Current Operating System: Linux mhfl4 2.4.29-rc3-mhf239 #2 Tue Jan 18 17:43= > :33 CET 2005 i686 > Build Date: 05 February 2005 > > Installed snapshot from savage-20050205-linux.i386.tar.bz2. On starting X: > > =46rom dmesg: > > [drm] Initialized savage 1.0.0 20011023 on minor 0: S3 Inc. 86C270-294 Sava= > ge/IX-MV > [drm:savage_unlock] *ERROR* Process 5736 using kernel context 0 > > =46rom Xorg.0.log: > > (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000 > (II) SAVAGE(0): VESA BIOS detected > (II) SAVAGE(0): VESA VBE Version 2.0 > (II) SAVAGE(0): VESA VBE Total Mem: 8192 kB > (II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. M7 BIOS > (II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0 > (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated. > (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0 > (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.1 > (--) SAVAGE(0): mapping framebuffer @ 0xe0000000 with size 0x1000000 > (II) SAVAGE(0): map aperture:0x413cc000 > (II) SAVAGE(0): 4692 kB of Videoram needed for 3D; 16384 kB of Videoram ava= > ilable > (II) SAVAGE(0): Sufficient Videoram available for 3D > (II) SAVAGE(0): [drm] bpp: 16 depth: 16 > (II) SAVAGE(0): [drm] Sarea 2200+284: 2484 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenByBusid: Searching for BusID pci:0000:00:04.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenByBusid: drmOpenMinor returns 7 > drmOpenByBusid: drmGetBusid reports pci:0000:00:04.0 > (II) SAVAGE(0): [drm] DRM interface version 1.2 > (II) SAVAGE(0): [drm] created "savage" driver at busid "pci:0000:00:04.0" > (II) SAVAGE(0): [drm] added 8192 byte SAREA at 0xcfa3a000 > (II) SAVAGE(0): [drm] mapped SAREA 0xcfa3a000 to 0x40024000 > (II) SAVAGE(0): [drm] framebuffer handle =3D 0xe0000000 > (II) SAVAGE(0): [drm] added 1 reserved context for kernel > (EE) SAVAGE(0): [dri] SAVAGEDRIScreenInit failed because of a version misma= > tch. > [dri] savage.o kernel module version is 1.0.0 but version 2.0.x is needed. > [dri] Disabling DRI. > (II) SAVAGE(0): [drm] removed 1 reserved context for kernel > (II) SAVAGE(0): [drm] unmapping 8192 bytes of SAREA 0xcfa3a000 at 0x40024000 > (EE) SAVAGE(0): DRI isn't enabled > > So, driver in snapshot still reports 1.0. Seems to be quite old (2001).
The new Savage DRM 2.0.0 (in fact 2.2.0 by now) is only available for Linux 2.6. Since Linux 2.4 is no longer open for new features there is not much point back-porting it to Linux 2.4. See http://dri.freedesktop.org/wiki/S3Savage for more information about the savage driver status. I just added a note about Linux 2.4 to that page. > > Changed that to 2.0, rebuild on starting X: Don't do that. You're pretending an interface version that this DRM doesn't provide. There are good reasons for checking interface versions as you found out below. ;-) > > =46rom dmesg: > > [drm] Initialized savage 2.0.0 20011023 on minor 0: S3 Inc. 86C270-294 Sava= > ge/IX-MV > [drm:savage_unlock] *ERROR* Process 9671 using kernel context 0 > [drm:savage_unlock] *ERROR* Process 11025 using kernel context 0 > > =46rom Xorg.0.log: > > (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000 > (II) SAVAGE(0): VESA BIOS detected > (II) SAVAGE(0): VESA VBE Version 2.0 > (II) SAVAGE(0): VESA VBE Total Mem: 8192 kB > (II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. M7 BIOS > (II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0 > (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated. > (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0 > (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.1 > (--) SAVAGE(0): mapping framebuffer @ 0xe0000000 with size 0x1000000 > (II) SAVAGE(0): map aperture:0x413cc000 > (II) SAVAGE(0): 4692 kB of Videoram needed for 3D; 16384 kB of Videoram ava= > ilable > (II) SAVAGE(0): Sufficient Videoram available for 3D > (II) SAVAGE(0): [drm] bpp: 16 depth: 16 > (II) SAVAGE(0): [drm] Sarea 2200+284: 2484 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenByBusid: Searching for BusID pci:0000:00:04.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > drmOpenByBusid: drmOpenMinor returns 7 > drmOpenByBusid: drmGetBusid reports pci:0000:00:04.0 > (II) SAVAGE(0): [drm] DRM interface version 1.2 > (II) SAVAGE(0): [drm] created "savage" driver at busid "pci:0000:00:04.0" > (II) SAVAGE(0): [drm] added 8192 byte SAREA at 0xcfa3a000 > (II) SAVAGE(0): [drm] mapped SAREA 0xcfa3a000 to 0x40024000 > (II) SAVAGE(0): [drm] framebuffer handle =3D 0xe0000000 > (II) SAVAGE(0): [drm] added 1 reserved context for kernel > (II) SAVAGE(0): [drm] aperture handle =3D 0xe2000000 > > (II) SAVAGE(0): [drm] failure adding 32 65536 byte DMA buffers (-1007)=20 > > ^^^^^ It failed to add DMA buffers > > (II) SAVAGE(0): [drm] removed 1 reserved context for kernel > (II) SAVAGE(0): [drm] unmapping 8192 bytes of SAREA 0xcfa3a000 at 0x40024000 > (EE) SAVAGE(0): DRI isn't enabled > > What's the reason for the failure? > > DRI never worked for me on this hardware. > > Anything I can help to fix/test please let me know. > > Michael > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > -- > _______________________________________________ > Dri-devel mailing list > Dri-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dri-devel > -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
