Savage3D crashes when switching to full screen in X (crash in 4.3.0 only!)
Hi, today I tried your experimental packages from deb experimental (4.3.0-0pre1v1). When I use my savage 3d (actually hercules terminator beast) graphics card and try to watch a movie using the current avifile from unstable (0.7.38.20030710-1) (+ icewm) it works ... well almost: when trying to switch to full screen mode, my computer hangs completely and can only be resetted (keyboard, etc. dead, monitor first issues a warning of the refresh rate being out of spec then shuts down, ...). I didn't find anything of interest in the log files (those that weren't corrupted during the crash ;-) ). However, when I plug in a matrox g200 graphics card the full screen mode works fine (well it seems to take longer that in 4.2.1. but I works). Note, that when I used xfree86 from unstable (4.2.1-9) + Tim Roberts's latest 4.2.x binary driver savage_drv.o (since the original savage_drv.o from 4.2.1-9 is not able to set a resolution/refresh rate that my monitor likes), my savage3d card had no problems with the full screen mode (i.e. it worked and did not crash my machine). Thus I tried Tim Roberts's 4.3.0 binary driver, but without success (full screen mode crashes, too). Hence I observe the problem in xfree86 4.3.0 only and not in the predecessor version (4.2.1). It seems that a change in the code that makes the switch to fullscreen mode makes my system go belly up with the savage3d graphics card/driver but not with another graphics card (matrox g200). Best regards and thanx for all your work, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86 4.3.0-pre1v1 sources ?
On Thu, Aug 07, 2003 at 01:34:56PM +0200, Sven Luther wrote: > On Thu, Aug 07, 2003 at 09:28:15PM +1000, Daniel Stone wrote: > > On Thu, Aug 07, 2003 at 12:48:45PM +0200, Sven Luther wrote: > > > BTW, is it to early to upload my gnome-randr-applet package, which > > > depends on 4.3.0 ? I have it ready for month, but couldn't upload it > > > previously. If i upload it to experimental, it should enter experimental > > > together with xfree86, but then, maybe i should wait to have an official > > > 4.3.0 package in unstable ? > > > > I don't see why you shouldn't upload it to experimental now. > > I just need a 4.3.0 package to build with. The -0ds4 would not be ok, > since it will not have the right dependencies. BTW, i have this problem with the packages : $ lintian gnome-randr-applet_0.2-0.1_i386.deb E: gnome-randr-applet: package-has-a-duplicate-relation xlibs (>> 4.1.0), xlibs (>> 4.3.0) Where is the first xlibs dependency comming from ? I suppose it causes no problem, since it is less strong than the first one, but it is not tidy. I have a shlibs.local for libRandR, but it changes nothing to have it or not. Anyway, i am uploading it to experimental now. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DRI performance on my Radeon 7500 with 4.3.0 pre1v1
On Mon, 2003-08-11 at 00:59, Moritz Muehlenhoff wrote: > Hi, > the update from 4.2.1-6 towards 4.3.0-pre1v1 was pretty smooth, > everything works as expected. I never really used 3D with my > Radeon 7500 QW (64 MB SDRAM) before, but I thought I'd give it > a try with 4.3.0. With the included drm-src package recompiled > for 2.4.21-bk30 (comparable to -rc1) and 2.6.0-test3 I get only > 330 to 440 fps (agp4, enablepageflip) in glxgears (normal size > on a 1024x768 screen on a Athlon 1700+), I hope you mean the size the window comes up in by 'normal size' ? > while someone on #dri told me that he had 1300-2500 on a Radeon > 7500 a year ago. Your numbers are low indeed. Does setting the RADEON_NO_USLEEPS and/or RADEON_NO_IRQS environment variable(s) make a difference? (See http://dri.sourceforge.net/doc/dri_driver_features.phtml for a list of other environment variable to tweak driver behaviour) -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question about patch 003a
On Mon, Aug 11, 2003 at 06:35:29AM -0500, Warren Turkal wrote: > Can I get a clue as to how to detect an error when I disable the patch? Sure. The /etc/X11/xdm/Xresources file will look all wrong. I.e. have less stuff in it than it does otherwise. -- G. Branden Robinson|The first thing the communists do Debian GNU/Linux |when they take over a country is to [EMAIL PROTECTED] |outlaw cockfighting. http://people.debian.org/~branden/ |-- Oklahoma State Senator John Monks pgp4FMGfCYpXD.pgp Description: PGP signature
XFree86 4.3 memory leak?
I was waiting for official prereleases to ask about this (again), but now that pre1 is out, somebody else out there has to be having the same problem as me and this can be caught before it hits sid: I recently upgraded from X 4.2 to X 4.3, and have noticed staggering memory problems. In a few hours of use, X will jump up to over 200 megs of memory before other processes start getting killed. I've gone back and forth between 4.2 and 4.3 a few times, and that's definately the pivot point in all my results. Matrox mil. G400DH 32Mb, Debian Sid. Section "ServerLayout" Identifier "Matrox PowerDesk configured." Screen "Display 1" RightOf "Display 2" Screen "Display 2" 0 0 InputDevice"Generic Keyboard" InputDevice"Configured Mouse" EndSection Section "Files" FontPath "/usr/lib/X11/fonts/misc/" FontPath "/usr/lib/X11/fonts/cyrillic/" FontPath "/usr/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/lib/X11/fonts/Type1/" FontPath "/usr/lib/X11/fonts/CID/" FontPath "/usr/lib/X11/fonts/Speedo/" FontPath "/usr/lib/X11/fonts/75dpi/" FontPath "/usr/lib/X11/fonts/100dpi/" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load "GLcore" Load "bitmap" Load "dbe" Load "ddc" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "record" Load "speedo" Load "type1" Load "vbe" Load "dri" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "aronkb" Option "XkbLayout" "dvorak" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ExplorerPS/2" Option "ZAxisMapping" "5 6" Option "Buttons" "6" EndSection Section "Monitor" Identifier "Display 1" HorizSync30.0 - 85.0 VertRefresh 50.0 - 130.0 Option "DPMS" EndSection Section "Monitor" Identifier "Display 2" HorizSync30.0 - 85.0 VertRefresh 50.0 - 130.0 EndSection Section "Device" Identifier "MATROX CARD 1" Driver "mga" VideoRam32768 BusID "PCI:1:0:0" Option "NoLogo" EndSection Section "Device" Identifier "MATROX CARD 2" Driver "mga" VideoRam32768 # Option "TV" "yes" # Option "CableType" "YC_COMPOSITE" # Option "TVStandard" "NTSC" BusID "PCI:1:0:0" Screen 1 Option "NoLogo" EndSection Section "Screen" Identifier "Display 1" Device "MATROX CARD 1" Monitor"Display 1" DefaultDepth 24 Option "XaaNoOffscreenPixmaps" SubSection "Display" Depth 1 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Display 2" Device "MATROX CARD 2" Monitor"Display 2" DefaultDepth 24 Option "XaaNoOffscreenPixmaps" SubSection "Display" Depth 1 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes"1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes"1280x1024" "1024x768" "800x600" "640
Re: patch numbers
On Tue, Aug 12, 2003 at 11:10:07AM +1000, Daniel Stone wrote: > On Mon, Aug 11, 2003 at 07:24:45AM -0500, Warren Turkal wrote: > > The patch numbers are not being properly followed. > > > > I have been submitting some patches upstream that are already fixed. They > > should be in a category not unlike patches from upstream so that we know > > that they can be deleted in the next version. I propose that 000 type > > patches should also include this class of patches such that 000 patches can > > just be deleted upon moving to a new upstream version. A patch of this type > > is 102, the sparc pci fix. I know that we may not know immediately when > > something like this is fixed, but when we know, it should be moved. > > > > Also, I have come across patches that are not labeled 900+ that are debian > > specific. I think that we need to promote these types of patches to the > > 900+ series patches. A couple patches of this type are 003 and 800, debian > > specific config patches. Please consider debian specificity when numbering > > patches. > > #003 should be merged upstream, so other people can build Debian packages; the > only part is where we do #define DebianMaintainer YES, or such - that's the > only > part we should keep as Debian-specific. Ditto #800. If you like, i can commit in some of the stuff. Especially the stuff like this which is mostly #ifdef protected could be a good candidate for a commit. I will see the opinion of upstream about this, and do the commits if it is ok, if you want that is. > As for #102 and the like, it's likely that the patch was developed by a > Debianite and sent to us, and we merged it and upstream later picked it up, so > the numbering became inaccurate (sort of) *after* the fact. Would be less if we sent more stuff upstream. Friendly, Sven Luther
Check out the facts on Herbal Health / rjo enqg ekokyx
90% of all sickness and disease begins in an unclean Colon! Since "Death begins in the colon," your nutritional program should begin with a good colon cleansing program. Toxins and waste build up in your colon just like they do in the pipes of your home. Both demand immediate attention or the results can be disastrous! No wonder Colon cancer is second only to lung cancer in terms of cancer deaths in the U.S., claiming the lives of nearly 50,000 men and women annually. Your colon is one of the largest muscles in your body and should be exercised regularly. Of course, physical exercise is beneficial for the colon, but water and fiber is even MORE important. Fiber is a bulking agent that gives the colon the resistance it needs in order to remain firm and active. If the colon is inactive, it will soon grow weak, just like any other muscle. Colon inactivity may hinder the movement of waste material along the intestinal track to be eliminated from the body. Eventually, this waste material builds up along the colon walls and prevents the absorption of water and electrolytes. At 98 degree's temperature, the waste material begins to rot and decay, sending toxins and poisons into the blood stream and throughout the body. Cleansing your colon is a 30-day process. Its also very economical at $51.50, for all three products US, and $96.20 Canadian. You may be very surprised at some of the benefits you will receive besides just losing 1-5 lbs of cr*p from your body and most of all, brightening your future health. Want more info? Click here and I'll send it to you, including instructions on how to take it. And yes, I have taken it myself. To receive no more mail, click here and send. Please do not reply to this email, as we will not see it. Click on the links above.
any chances to incorporate savage driver from S3
Hello, Since Tim Roberts stopped work on his savage driver (see below), is there any chances that S3 driver will be incorporated into XFree86? (either Debian or upstream ;-) It supports DRI (-ac kernels has it), but is for 4.2.0 only (ie. some work would be needed to use it on 4.3.x. It would be great to have DRI on my laptop, so I could play Neverwinter Nights ;-) *** From: Tim Roberts <[EMAIL PROTECTED]> Reply-To: Tim Roberts <[EMAIL PROTECTED]> To: savage40 <[EMAIL PROTECTED]> Subject: [Savage40] Better Driver Out There Date: Wed, 09 Jul 2003 11:32:34 -0700 Well, folks, it appears that my Savage driver is now a LONG ways from the state of the art. I am no longer "da man". Unbeknownst to me, VIA/S3 have been quietly bulking up their snapshot of the Savage driver. Recently, they were persuaded to release their driver to the world in source form: http://www.linux.org.uk/~alan/S3.zip I have not tried to compile this yet, but based on a quick perusal of the source code, it looks like it: * Supports all of the Savage chips * Supports video4linux for videoport/zoomvideo * Supports the Chrontel TV part on ProSavageDDR motherboards * Supports MPEG motion compensation acceleration (XvMC) and (drum roll, please): * Supports DRI and OpenGL They have made so many changes that it is almost impossible for me to determine whether all of my recent fixes are in their code, but given the thoroughness I see in other places, I suspect that they are. So, if you have the inclination and ability to build from source, it would be well worth your trouble to give this a try. If you do build binaries for either 4.2.0 or 4.3.0, let me know and I will announce it to this list. -- - Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc. -- Ondřej Surý <[EMAIL PROTECTED]>
Re: patch numbers
On Tue, 2003-08-12 at 03:54, Warren Turkal wrote: > > I am braving the world the the X inner sanctum. Does anyone here know > if the X people monitor the bugzilla dilligently, A number of people do, in particular Egbert, otherwise he wouldn't have recommended this. > or should I post a message to the x devel list upon submitting a number > of bug reports providing links and short descriptions. You can still do this after a while for patches which didn't get attention in bugzilla for some reason. > BTW, my goal is to get as many of the debian patches merged as possible > upstream so that they will not have to be ported when 4.4 comes out. Great, more power to you! :) -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
Bug#200699:
Here is an idea for /etc/logrotate.d/xdm:
# Logrotate file for xdm.log
# The log file is named in /etc/X11/xdm/xdm-config. How to extract it here?
# DisplayManager.errorLogFile: /var/log/xdm.log
#
# Better include a warning in a comment in /etc/X11/xdm/xdm-config that the log
# file name is assumed here.
# These defaults in /etc/logrotate.conf:
# weekly
# rotate 4
# create
/var/log/xdm.log {
notifempty
missingok
}
Re: XFree86 4.3 memory leak?
Em Ter, 2003-08-12 às 03:33, Jeremy Nickurak escreveu: > I was waiting for official prereleases to ask about this (again), but > now that pre1 is out, somebody else out there has to be having the same > problem as me and this can be caught before it hits sid: You got it! I'm having the same problem, but I didn't notice until you sent this message. The only difference is my version: I'm using 4.3.0-0ds4. Maybe this is a problem of a Debian patch applied during compilation, since others distribution (RedHat and Mandrake) don't have this problem. Cheers, Felipe Almeida Lessa.
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > severity 200699 serious Bug#200699: xdm: log rotating Severity set to `serious'. > tags 200699 +patch Bug#200699: xdm: log rotating There were no tags set. Tags added: patch > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: XFree86 4.3 memory leak?
On Tue, 2003-08-12 at 18:08, Felipe Almeida Lessa wrote: > Em Ter, 2003-08-12 às 03:33, Jeremy Nickurak escreveu: > > I was waiting for official prereleases to ask about this (again), but > > now that pre1 is out, somebody else out there has to be having the same > > problem as me and this can be caught before it hits sid: > > You got it! I'm having the same problem, but I didn't notice until you > sent this message. The only difference is my version: I'm using > 4.3.0-0ds4. Maybe this is a problem of a Debian patch applied during > compilation, since others distribution (RedHat and Mandrake) don't have > this problem. Interesting thought, as it doesn't seem to happen with xserver-xfree86-dri-trunk either, which only applies a few patches. Keep in mind though that the X server manages resources on behalf of clients, e.g. - check out FAQs and XFree86 bugs on the subject. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
Re: X restarts after switching from vt7 to console
Hi! Thomas E. Vaughan wrote (Thu 2003-Aug-07 06:52:34 -0600): > > When switching from X-Window to Console (Ctrl-Alt-F2) > > X-Server makes an automatic restart after a short time (5 > > to 20 seconds) and the kdm login screen appears again on > > vt7. > > That happens to me with debian sid. I have an i810 graphics > subsystem. This has happened for months. Looks like bugs.xfree86.org #103. I compiled the patch from Egbert Eich with Daniel Stones' current (4.3.0-0ds4) sources, which solved the problem. Daniel has promised to include the patch in 4.3.0-0pre1v1. Cheers, Marcus -- Marcus C. Gottwald · http://www.inf.fu-berlin.de/~gottwald/
Re: XFree86 4.3 memory leak?
On Tue, 2003-08-12 at 10:08, Felipe Almeida Lessa wrote: > You got it! I'm having the same problem, but I didn't notice until you > sent this message. The only difference is my version: I'm using > 4.3.0-0ds4. Maybe this is a problem of a Debian patch applied during > compilation, since others distribution (RedHat and Mandrake) don't have > this problem. I did have the same problem with 4.3.0-0ds4. Is there a straightforward way to try a patch-free build? I do have a tree here that's ready and able to compile the pre1v1 release... -- Jeremy Nickurak -= Email/Jabber: [EMAIL PROTECTED] =- "I do not know how World War III will be fought, but World War IV will be fought with sticks and stones." -- Einstein signature.asc Description: This is a digitally signed message part
Bug#205129: XFree86 and ATI Radeon 7500. (2)
Package: XFree86 Version 4.1.0.1 I use graphics card ATI RADEON 7500 built by ATI. After installation Debian 3.0 r1 and windowmaker I wrote in text mode "startx" and mistake appeared, (Fatal server error: no screens found) which content is in enclosure. I ask about help. Configuration: Iiyama HM 704 UTC MSI KT3 Ultra Aru AMI® BIOS ver. 5.7 AMD Duron 1300 Morgan DDR 512 Nanya Michael Best Regards [EMAIL PROTECTED]
Re: X restarts after switching from vt7 to console
On Tue, Aug 12, 2003 at 10:03:47PM +0200, Marcus C. Gottwald wrote: > Thomas E. Vaughan wrote (Thu 2003-Aug-07 06:52:34 -0600): > > > > When switching from X-Window to Console (Ctrl-Alt-F2) > > > X-Server makes an automatic restart after a short time (5 > > > to 20 seconds) and the kdm login screen appears again on > > > vt7. > > > > That happens to me with debian sid. I have an i810 graphics > > subsystem. This has happened for months. > > Looks like bugs.xfree86.org #103. I compiled the patch from > Egbert Eich with Daniel Stones' current (4.3.0-0ds4) sources, > which solved the problem. Daniel has promised to include the > patch in 4.3.0-0pre1v1. It's already included: deb http://debian.mirror/debian/ ../project/experimental/ main -- Daniel Stone <[EMAIL PROTECTED]> http://www.debian.org - http://www.kde.org - http://www.freedesktop.org "Configurability is always the best choice when it's pretty simple to implement" -- Havoc Pennington, gnome-list pgpjKTHMseyAI.pgp Description: PGP signature
Bug#178242: 4.2.1-9 works
It works for me too. Thanks, Norbert
