amd64 and video card experiences?
Hi, Ever since I got close to the stage where I wanted to upgrade my Matrox P650 with a Sledgehammer (pun intended) I am looking for experiences by others with ATI or nVidia cards, especially with the OSS-drivers (especially since ATI has stil not delivered an AMD64-enabled Linux-driver). Unfortunately posts about them are a bit rare it seems, especially for Debian. So I would like to hear some experiences from you people. I am mostly looking at an ATI 9200 card, but I would not mind about hearing experiences with 9600 series or nVidias 5200/5900XT series. thanx, Thomas
Re: 2.6.8 based installer?
On Sun, Aug 15, 2004 at 11:04:59AM +0100, Martin A. Brooks wrote: Hi Are any of the currently available installers based on 2.6.8? Not yet. There currently isn't a kernel image with 2.6.8 available yet but work is in progress. (A better question would perhaps be How can I find out if any of the currently available installers are based on 2.6.8? :) In the debian-installer dir there is a stats file (stats.txt) that's made each day with all udebs that are on the image including the kernels. It currently tells the last ones are still with 2.6.7-5. Kurt
Re: Bug#260747: removing --enable-final allows successful compilation of arts-1.3.0
the version you cite is not made by the gcc-3.4 package in unstable nor do I see that --enable-final is passed at configure time. Matthias David Dumas writes: I experienced the segfault in mcopidl when compiling arts-1.3.0 with gcc 3.4.1 under debian unstable (amd64). I looked at debian/rules and found that --enable-final is passed to configure; this option has the following description in the configure usage message: --enable-final build size optimized apps (experimental - needs lots of memory) Why would the debian package optimize for size? Anyway, removing this option allowed a successful build, i.e. no segfault in mcopidl. -David $ gcc -v Reading specs from /usr/lib/gcc/x86_64-linux/3.4.1/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug --disable-werror x86_64-linux Thread model: posix gcc version 3.4.1 (Debian 3.4.1-5.0.0.2.amd64) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#260747: removing --enable-final allows successful compilation of arts-1.3.0
I was referring to the rules for arts-1.3.0-1, specifically, lines 73-76: # run configure with build tree $(objdir) cd $(objdir) \ CC=gcc-3.3 CXX=g++-3.3 ../configure $(configkde) --enable-final \ --with-alsa However, as you point out, gcc/g++ 3.3 is used to build the package by default. I removed the CC and CXX settings and rebuilt with the default version on my system (3.4.1), and experienced the segfault in mcopidl. I then removed the suspicious --enable-final option and the package compiled successfully with 3.4.1. Thus in the end I replaced the rules quoted above with: # run configure with build tree $(objdir) cd $(objdir) \ ../configure $(configkde) \ --with-alsa -David On Sun, 15 Aug 2004 21:56:08 +0200, Matthias Klose [EMAIL PROTECTED] wrote: the version you cite is not made by the gcc-3.4 package in unstable nor do I see that --enable-final is passed at configure time. Matthias David Dumas writes: I experienced the segfault in mcopidl when compiling arts-1.3.0 with gcc 3.4.1 under debian unstable (amd64). I looked at debian/rules and found that --enable-final is passed to configure; this option has the following description in the configure usage message: --enable-final build size optimized apps (experimental - needs lots of memory) Why would the debian package optimize for size? Anyway, removing this option allowed a successful build, i.e. no segfault in mcopidl. -David $ gcc -v Reading specs from /usr/lib/gcc/x86_64-linux/3.4.1/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug --disable-werror x86_64-linux Thread model: posix gcc version 3.4.1 (Debian 3.4.1-5.0.0.2.amd64)
Re: amd64 and video card experiences?
On Sun, Aug 15, 2004 at 11:29:36AM +0200, Thomas J. Zeeman wrote: Hi, Ever since I got close to the stage where I wanted to upgrade my Matrox P650 with a Sledgehammer (pun intended) I am looking for experiences by others with ATI or nVidia cards, especially with the OSS-drivers (especially since ATI has stil not delivered an AMD64-enabled Linux-driver). Unfortunately posts about them are a bit rare it seems, especially for Debian. So I would like to hear some experiences from you people. I am mostly looking at an ATI 9200 card, but I would not mind about hearing experiences with 9600 series or nVidias 5200/5900XT series. I have an ATi Radeon 9600 Pro. It works (in the sense that I can get X running acceptably). 2D works; 3D is unsupported. There are no 64-bit capable drivers for the 3D parts of the card for linux yet. ATi are being completely uncommunicative on the subject, and I'm starting to regret buying the card, after having been a happy ATi customer for many years. Just my experience, Hugo. -- === Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- If you're not part of the solution, you're part --- of the precipiate. signature.asc Description: Digital signature
