Re: savage-20050205-linux snapshot - problems
Am Mittwoch, den 16.02.2005, 00:14 -0500 schrieb Alex Deucher: On Wed, 16 Feb 2005 05:51:25 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Sunday 13 February 2005 16:30, Felix K=FChling wrote: I took another look at your lspci-output. It's a PCI card, right? I saw vertex corruption with PCI-DMA on my Savage4 once. Maybe this isn't working reliably. Does it help to set enable_vdma to false (in driconf or the environment)? Performance will be worse though. The chip is connected to a PCI bus on the notebooks main board. Haven't tried enable_vdma as solution to problem is below. Have you overclocked your front-side bus? In that case, does it help if you don't overclock? No overclocking by me, All I do is underclock the LCD clock=20 to 40MHz in the hope of less heat under the keyboard :-) Did you override the VideoRam size in xorg.conf? Maybe you made it believe that it has more memory than is actually available. Yes, that was it, memory size was set to 16384, it =20 apparently got only 8192 according to Xorg log. Dunno why the machine is advertised with 16M and used this setting wo DRI for 3 years. the DDX never used more than a couple megs probably. Now it does work with tuxkart and tuxracer. fgfs will not load anymore, perhaps not enough video memory? Maybe fgfs needs a certain minimum texture size that is not available with 8MB memory. You could try to reduce the resolution in order to make more texture memory available. This may also improve performance with other applications due to reduced texture swapping. Is there a savage IX chip with 16M? There were some, but I don't think they ever left S3's testing labs. No commercial vendors that I know of used them. FWIW, 16MB is the theoretical limit you can get with this chip because of the layout of the PCI address mapping. Alex -- | Felix Kühling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Sunday 13 February 2005 16:30, Felix K=FChling wrote: I took another look at your lspci-output. It's a PCI card, right? I saw vertex corruption with PCI-DMA on my Savage4 once. Maybe this isn't working reliably. Does it help to set enable_vdma to false (in driconf or the environment)? Performance will be worse though. The chip is connected to a PCI bus on the notebooks main board. Haven't tried enable_vdma as solution to problem is below. Have you overclocked your front-side bus? In that case, does it help if you don't overclock? No overclocking by me, All I do is underclock the LCD clock=20 to 40MHz in the hope of less heat under the keyboard :-) Did you override the VideoRam size in xorg.conf? Maybe you made it believe that it has more memory than is actually available. Yes, that was it, memory size was set to 16384, it =20 apparently got only 8192 according to Xorg log. Dunno why the machine is advertised with 16M and used this setting wo DRI for 3 years. Now it does work with tuxkart and tuxracer. fgfs will not load anymore, perhaps not enough video memory? Is there a savage IX chip with 16M? I'll continue to test further snapshots. Thank you and Regards Michael --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Wed, 16 Feb 2005 05:51:25 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Sunday 13 February 2005 16:30, Felix K=FChling wrote: I took another look at your lspci-output. It's a PCI card, right? I saw vertex corruption with PCI-DMA on my Savage4 once. Maybe this isn't working reliably. Does it help to set enable_vdma to false (in driconf or the environment)? Performance will be worse though. The chip is connected to a PCI bus on the notebooks main board. Haven't tried enable_vdma as solution to problem is below. Have you overclocked your front-side bus? In that case, does it help if you don't overclock? No overclocking by me, All I do is underclock the LCD clock=20 to 40MHz in the hope of less heat under the keyboard :-) Did you override the VideoRam size in xorg.conf? Maybe you made it believe that it has more memory than is actually available. Yes, that was it, memory size was set to 16384, it =20 apparently got only 8192 according to Xorg log. Dunno why the machine is advertised with 16M and used this setting wo DRI for 3 years. the DDX never used more than a couple megs probably. Now it does work with tuxkart and tuxracer. fgfs will not load anymore, perhaps not enough video memory? Is there a savage IX chip with 16M? There were some, but I don't think they ever left S3's testing labs. No commercial vendors that I know of used them. Alex --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Sunday 13 February 2005 11:03, [EMAIL PROTECTED] wrote: On Saturday 12 February 2005 16:33, Felix K=FChling wrote: I can't reproduce this on my Savage/IX. Someone else reported problems with 2.6.11-rc3, something like it wouldn't even load the DRM modules. Maybe something's broken with current DRM on Linux 2.6.11-rc3. If this problem persists with the latest snapshot (tomorrow's should have my latest fixes) could you try if it works with a stock 2.6.10 kernel (you'd have to recompile the DRM for it)? OK, I will try with 2.6.10. 2.6.10 behaves the same. Regards Michael --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Thursday 10 February 2005 14:58, Felix K=FChling wrote: Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20 [EMAIL PROTECTED]: On Monday 07 February 2005 15:33, Felix K=3DFChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=3D20 [EMAIL PROTECTED]: Hardware: Toshiba Libretto L2 Tm5600 with: :00:04.0 VGA compatible controller: S3 Inc. 86C270-294=3D3D20 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-=3D3D Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3D3D3Dmedium TAbort- =3D3D 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 e000 (32-bit, non-prefetchable) [size=3D3D3D128=3D3D M] Expansion ROM at 000c [disabled] [size=3D3D3D64K] Capabilities: available only to root Software: Gentoo current with Gentoo supplied X Window System Version 6.8.1.903 (6.8.=3D3D 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]=3D3D20 Current Operating System: Linux mhfl4 2.4.29-rc3-mhf239 #2 Tue Jan 18 17:43=3D3D :33 CET 2005 i686 Build Date: 05 February 2005 Installed snapshot from savage-20050205-linux.i386.tar.bz2. On starting X: [snip] 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.=3D20 Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=3D20 painting occurs outside of games window. Parts of the image=3D20 appear (sometime mirrored) outside game window or random=3D20 patterns appear. Cursor and numeric display in game window=3D20 appear as random patterns. The garbage patters could be that it's getting the texture tiling wrong. I messed with that code recently. Could be that I broke it on Savage/IX. Also please try if the latest snapshot fixes this. Sometimes above games mess up the screen but restart Game a=3D20 few times fixes it. =3D46lighgear messes up the entire screen and would never work. Weird. I haven't had this kind of problems in a while. Though I haven't tested on my Savage/IX recently. Looks like it's time to swap cards again. Tried 0211 snapshot and it behaves similar.=20 [snip] Are there any test programs available to systematically test=3D20 DRM/GL functionality? For example mesa/progs/demos and Glean (http://glean.sourceforge.net/). For reference you can always run with indirect software rendering. Set LIBGL_ALWAYS_INDIRECT in the environment. I got hold of glean and will try it later today.=20 Regards Michael --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Saturday 12 February 2005 16:33, Felix K=FChling wrote: Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20 [EMAIL PROTECTED]: On Monday 07 February 2005 15:33, Felix K=3DFChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=3D20 [EMAIL PROTECTED]: [snip] Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=3D20 painting occurs outside of games window. Parts of the image=3D20 appear (sometime mirrored) outside game window or random=3D20 patterns appear. I can't reproduce this on my Savage/IX. Someone else reported problems with 2.6.11-rc3, something like it wouldn't even load the DRM modules. Maybe something's broken with current DRM on Linux 2.6.11-rc3. If this problem persists with the latest snapshot (tomorrow's should have my latest fixes) could you try if it works with a stock 2.6.10 kernel (you'd have to recompile the DRM for it)? OK, I will try with 2.6.10. Cursor and numeric display in game window=3D20 appear as random patterns. I just fixed another bug in texture tiling on Savage/IX. Though it only affected the road-texture in Tuxkart for me. Most textures were looking correctly. If you still get broken textures with tomorrow's snapshot then it might be a difference between our chip revisions (sigh). Sometimes above games mess up the screen but restart Game a=3D20 few times fixes it. Can't reproduce this either. Every time starting tuxkart or tuxracer different textures get messed up. For example, in tuxracer sometime trees and=20 herrings show as randomly colored rectangles/shapes only,=20 and herring counter and speed indicator OK; restart and=20 tress and herrings OK but indicators show (some) digits as=20 rectangles. Ground in tuxracer seems to go partially wrong as well,=20 seems that some textures do not belong there Seems to go wrong already during initialization as behavior afterward seems consistent. By what I see about wrong texture patterns, just wondering,=20 could pointers to some texture buffers be invalid and it=20 then paints with crap data? =3D46lighgear messes up the entire screen and would never work. BTW, the games work on i810 HW with 2.6.11-rc3. Since Linux 2.4 is no longer=3D20 open for new features there is not much point back-porting it to Linux 2.4.=3D20 See=3D20 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. Sorry, have not found any reference to 2.4 being unsupported=3D20 on that page.=3D20 Are there any test programs available to systematically test=3D20 DRM/GL functionality? Regards Michael --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
Am Sonntag, den 13.02.2005, 11:03 +0100 schrieb [EMAIL PROTECTED]: On Saturday 12 February 2005 16:33, Felix K=FChling wrote: Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb=20 [EMAIL PROTECTED]: On Monday 07 February 2005 15:33, Felix K=3DFChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=3D20 [EMAIL PROTECTED]: [snip] Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=3D20 painting occurs outside of games window. Parts of the image=3D20 appear (sometime mirrored) outside game window or random=3D20 patterns appear. I can't reproduce this on my Savage/IX. Someone else reported problems with 2.6.11-rc3, something like it wouldn't even load the DRM modules. Maybe something's broken with current DRM on Linux 2.6.11-rc3. If this problem persists with the latest snapshot (tomorrow's should have my latest fixes) could you try if it works with a stock 2.6.10 kernel (you'd have to recompile the DRM for it)? OK, I will try with 2.6.10. Cursor and numeric display in game window=3D20 appear as random patterns. I just fixed another bug in texture tiling on Savage/IX. Though it only affected the road-texture in Tuxkart for me. Most textures were looking correctly. If you still get broken textures with tomorrow's snapshot then it might be a difference between our chip revisions (sigh). Sometimes above games mess up the screen but restart Game a=3D20 few times fixes it. Can't reproduce this either. I took another look at your lspci-output. It's a PCI card, right? I saw vertex corruption with PCI-DMA on my Savage4 once. Maybe this isn't working reliably. Does it help to set enable_vdma to false (in driconf or the environment)? Performance will be worse though. Have you overclocked your front-side bus? In that case, does it help if you don't overclock? Every time starting tuxkart or tuxracer different textures get messed up. For example, in tuxracer sometime trees and=20 herrings show as randomly colored rectangles/shapes only,=20 and herring counter and speed indicator OK; restart and=20 tress and herrings OK but indicators show (some) digits as=20 rectangles. Ground in tuxracer seems to go partially wrong as well,=20 seems that some textures do not belong there Seems to go wrong already during initialization as behavior afterward seems consistent. By what I see about wrong texture patterns, just wondering,=20 could pointers to some texture buffers be invalid and it=20 then paints with crap data? Did you override the VideoRam size in xorg.conf? Maybe you made it believe that it has more memory than is actually available. =3D46lighgear messes up the entire screen and would never work. BTW, the games work on i810 HW with 2.6.11-rc3. Since Linux 2.4 is no longer=3D20 open for new features there is not much point back-porting it to Linux 2.4.=3D20 See=3D20 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. Sorry, have not found any reference to 2.4 being unsupported=3D20 on that page.=3D20 Are there any test programs available to systematically test=3D20 DRM/GL functionality? Regards Michael -- | Felix Kühling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb [EMAIL PROTECTED]: On Monday 07 February 2005 15:33, Felix K=FChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=20 [EMAIL PROTECTED]: Hardware: Toshiba Libretto L2 Tm5600 with: :00:04.0 VGA compatible controller: S3 Inc. 86C270-294=3D20 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-=3D Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3D3Dmedium TAbort- =3D 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 e000 (32-bit, non-prefetchable) [size=3D3D128=3D M] Expansion ROM at 000c [disabled] [size=3D3D64K] Capabilities: available only to root Software: Gentoo current with Gentoo supplied X Window System Version 6.8.1.903 (6.8.=3D 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]=3D20 Current Operating System: Linux mhfl4 2.4.29-rc3-mhf239 #2 Tue Jan 18 17:43=3D :33 CET 2005 i686 Build Date: 05 February 2005 Installed snapshot from savage-20050205-linux.i386.tar.bz2. On starting X: [snip] 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.=20 Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=20 painting occurs outside of games window. Parts of the image=20 appear (sometime mirrored) outside game window or random=20 patterns appear. I can't reproduce this on my Savage/IX. Someone else reported problems with 2.6.11-rc3, something like it wouldn't even load the DRM modules. Maybe something's broken with current DRM on Linux 2.6.11-rc3. If this problem persists with the latest snapshot (tomorrow's should have my latest fixes) could you try if it works with a stock 2.6.10 kernel (you'd have to recompile the DRM for it)? Cursor and numeric display in game window=20 appear as random patterns. I just fixed another bug in texture tiling on Savage/IX. Though it only affected the road-texture in Tuxkart for me. Most textures were looking correctly. If you still get broken textures with tomorrow's snapshot then it might be a difference between our chip revisions (sigh). Sometimes above games mess up the screen but restart Game a=20 few times fixes it. Can't reproduce this either. =46lighgear messes up the entire screen and would never work. BTW, the games work on i810 HW with 2.6.11-rc3. Since Linux 2.4 is no longer=20 open for new features there is not much point back-porting it to Linux 2.4.=20 See=20 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. Sorry, have not found any reference to 2.4 being unsupported=20 on that page.=20 Are there any test programs available to systematically test=20 DRM/GL functionality? Regards Michael -- | Felix Kühling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
Am Donnerstag, den 10.02.2005, 07:21 +0100 schrieb [EMAIL PROTECTED]: On Monday 07 February 2005 15:33, Felix K=FChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=20 [EMAIL PROTECTED]: Hardware: Toshiba Libretto L2 Tm5600 with: :00:04.0 VGA compatible controller: S3 Inc. 86C270-294=3D20 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-=3D Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3D3Dmedium TAbort- =3D 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 e000 (32-bit, non-prefetchable) [size=3D3D128=3D M] Expansion ROM at 000c [disabled] [size=3D3D64K] Capabilities: available only to root Software: Gentoo current with Gentoo supplied X Window System Version 6.8.1.903 (6.8.=3D 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]=3D20 Current Operating System: Linux mhfl4 2.4.29-rc3-mhf239 #2 Tue Jan 18 17:43=3D :33 CET 2005 i686 Build Date: 05 February 2005 Installed snapshot from savage-20050205-linux.i386.tar.bz2. On starting X: [snip] 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.=20 Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=20 painting occurs outside of games window. Parts of the image=20 appear (sometime mirrored) outside game window or random=20 patterns appear. Cursor and numeric display in game window=20 appear as random patterns. The garbage patters could be that it's getting the texture tiling wrong. I messed with that code recently. Could be that I broke it on Savage/IX. Also please try if the latest snapshot fixes this. Sometimes above games mess up the screen but restart Game a=20 few times fixes it. =46lighgear messes up the entire screen and would never work. Weird. I haven't had this kind of problems in a while. Though I haven't tested on my Savage/IX recently. Looks like it's time to swap cards again. BTW, the games work on i810 HW with 2.6.11-rc3. Since Linux 2.4 is no longer=20 open for new features there is not much point back-porting it to Linux 2.4.=20 See=20 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. Sorry, have not found any reference to 2.4 being unsupported=20 on that page.=20 Err, I probably pushed Preview instead of Save. :-/ Are there any test programs available to systematically test=20 DRM/GL functionality? For example mesa/progs/demos and Glean (http://glean.sourceforge.net/). For reference you can always run with indirect software rendering. Set LIBGL_ALWAYS_INDIRECT in the environment. Regards Michael -- | Felix Kühling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
On Monday 07 February 2005 15:33, Felix K=FChling wrote: Am Montag, den 07.02.2005, 15:12 +0100 schrieb=20 [EMAIL PROTECTED]: Hardware: Toshiba Libretto L2 Tm5600 with: :00:04.0 VGA compatible controller: S3 Inc. 86C270-294=3D20 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-=3D Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3D3Dmedium TAbort- =3D 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 e000 (32-bit, non-prefetchable) [size=3D3D128=3D M] Expansion ROM at 000c [disabled] [size=3D3D64K] Capabilities: available only to root Software: Gentoo current with Gentoo supplied X Window System Version 6.8.1.903 (6.8.=3D 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]=3D20 Current Operating System: Linux mhfl4 2.4.29-rc3-mhf239 #2 Tue Jan 18 17:43=3D :33 CET 2005 i686 Build Date: 05 February 2005 Installed snapshot from savage-20050205-linux.i386.tar.bz2. On starting X: [snip] 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.=20 Tested with 2.6.11-rc3. DRM functional with glxgears. tuxkart and tuxracer work most the time but sometimes=20 painting occurs outside of games window. Parts of the image=20 appear (sometime mirrored) outside game window or random=20 patterns appear. Cursor and numeric display in game window=20 appear as random patterns. Sometimes above games mess up the screen but restart Game a=20 few times fixes it. =46lighgear messes up the entire screen and would never work. BTW, the games work on i810 HW with 2.6.11-rc3. Since Linux 2.4 is no longer=20 open for new features there is not much point back-porting it to Linux 2.4.=20 See=20 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. Sorry, have not found any reference to 2.4 being unsupported=20 on that page.=20 Are there any test programs available to systematically test=20 DRM/GL functionality? Regards Michael --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: savage-20050205-linux snapshot - problems
Am Montag, den 07.02.2005, 15:12 +0100 schrieb [EMAIL PROTECTED]: Hardware: Toshiba Libretto L2 Tm5600 with: :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 e000 (32-bit, non-prefetchable) [size=3D128= M] Expansion ROM at 000c [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 @ 0xe000 with size 0x100 (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::00:04.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci::00:04.0 (II) SAVAGE(0): [drm] DRM interface version 1.2 (II) SAVAGE(0): [drm] created savage driver at busid pci::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 0xe000 (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 @ 0xe000 with size 0x100 (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
