Re: Opinion question (Core2 Duo)
Lennart Sorensen wrote: On Tue, Sep 18, 2007 at 09:45:42AM -0400, Zaq Rizer wrote: Thank you both for the advice. I am compiling a new preempt/cfs kernel with Intel/core2-specific instructions, and will stick with my -amd64 installation. Don't fix it if it ain't broke, right? Regards, Zaq Why would you bother compiling your own kernel? The AMD64 instruction set is pretty much the same on all the CPUs and debian's kernel works and you get security fixes without having to do all the work and research yourself. You are very unlikely to gain any performance by compiling your own kernel. -- Len Sorensen First, apologies for sending in HTML only ... My current kernel is custom so I can try out the new scheduler (CFS), and increase the tickrate, and enable preemption. None of which, afaik, can I do with any Debian packaged kernels. So since I was doing all that, I figured I'd go ahead and re-config it for Intel c2d. It's purely a desktop machine ... ~Zaq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Opinion question (Core2 Duo)
Lennart Sorensen wrote: On Tue, Sep 18, 2007 at 02:18:34PM +0200, Helge Hafting wrote: My experimental sudoku solving program is 3x faster on a 1.8GHz 64-bit opteron, than on a 2.4GHz 32-bit pentium. In this case, a slow 64-bit processor beats a faster 32-bit processor 3x. And an athlon64 3500+ (2.2GHz) runs bzip2 5x faster than a 2.8GHz Pentium 4. The pentium 4 HATES branch heavy code when the branch prediction fails to work (which essentially by definition it has to on compression and other optimizing/solving problems). It might have been a good design for multimedia streaming operations, but it really sucks at many general purpose tasks. I never did like the pentium 4 even from day 1. -- Len Sorensen Thank you both for the advice. I am compiling a new preempt/cfs kernel with Intel/core2-specific instructions, and will stick with my -amd64 installation. Don't fix it if it ain't broke, right? Regards, Zaq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Opinion question (Core2 Duo)
I have an Intel Core2 Duo arriving in the mail in a couple of days, and I read online that these processors can run in either 32bit or 64bit mode (just like Athlons can). Thing is, the 32bit chroot and ia32-compatibility libraries, are, imo, a total mess and a real pain in the rear to deal with on a daily basis. I'm looking for people's opinions on whether I should stick with debian-amd64, or do a reinstall of debian from the main branch (32bit)? What, truly, are the real performance differences? Simply support for 4+G of ram, or something else? My /home is a seperate partition, as are my mp3s, etc etc, so data retention is not a huge concern. Thanks, Zaq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiz + AIGLX + Nvidia HOWTO
Jack Malmostoso wrote: Hi list, I'm posting it here for future reference. Sorry if someone isn't interested at all. Nice writeup, but I don't believe compiz is in unstable . . . what does your sources.list look like? ~Zaq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Quake 4
On Sat, 2005-10-22 at 15:23 -0500, Levi Bard wrote: On 10/21/05, Zaq Rizer <[EMAIL PROTECTED]> wrote: > The linux client came out yesterday. Has anyone gotten in it working in > debian-amd64? Mine is segfaulting and I can't figure out why for the life > of me. Works fine for me (not in chroot). I didn't do anything special, though - just ran the linux installer, copied over the pak*pk4 and the english pak from the dvd, and voila! If there's any info I can provide, I will do so... 5900XT and AMD64 3000+ here, running on sid. Are you on sid or sarge? ~Zaq -- I got this powdered water -- now I don't know what to add. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: Quake 4
On Sat, 2005-10-22 at 04:31 +0200, Marcin Dębicki wrote: For me looks like known problem with libs. Maybe you haven't properly created libs cache for 32bit libs. Sometimes after upgrading main system or chroot you have to run ldconfig to update libs cache and with Doom it usually was helpful. Q4 uses the same engine so it may help here I've tried that, of course. And no other OpenGL game has an issue now; it's specific to Quake 4. BTW ID should compile 64bit Q4 and Doom version Why? The 32bit runs natively in amd64 environment. I'm just glad there's a client at all. ~Zaq -- I poured spot remover on my dog. Now he's gone. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: Quake 4
On Sat, 2005-10-22 at 01:05 +0200, Marcin Dębicki wrote: --snip Doom 3 is also 32bit and works fine is 32bit chroot is configured. On what step is segfaults? -- Registered Linux User 369908 [EMAIL PROTECTED] It shows the loading page for about a second, then immediately crashes with a segfault. Information regarding the crash from the console is as follows: ++ found DLL in pak file: /Shared/Games/quake4/q4base/game100.pk4/gamex86.so copy gamex86.so to /home/epoch/.quake4/q4base/gamex86.so signal caught: Segmentation fault si_code 2 Trying to exit gracefully.. --- BSE Shutdown - WARNING: rvServerScanGUI::Clear() - invalid scanGUI Shutting down sound hardware --- Alsa Shutdown close pcm dlclose -- idRenderSystem::Shutdown() Shutting down SDL subsystem /usr/local/bin/quake4: line 6: 9543 Segmentation fault ./quake4.x86 $* ++ The 'invalid scanGUI' and 'si_code 2' are both items common to other individuals (debian-amd64 and others). I've filed a bug report to id software, as have other people, but, from what I'm told, there are no commonalities between all of us. At least, not at first glance. I assume they're working on it...? As I've told someone else on the list, though, I've spoken to a couple other people who do run debian-amd64 (in this native amd64 fashion) that have success. ~Zaq -- It's a small world, but I wouldn't want to have to paint it. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: Quake 4
Yes, but it runs natively in amd64, just like a lot of other applications. Besides, it segfaults in the 32bit chroot, as well. This is not architecture-related. Zaq On Sat, 2005-10-22 at 08:50 +1000, Dean Hamstead wrote: you realise its a 32 bit binary? Dean Zaq Rizer wrote: > The linux client came out yesterday. Has anyone gotten in it working in > debian-amd64? Mine is segfaulting and I can't figure out why for the > life of me. > > Thanks! > ~Zaq > > -- > My friend has a baby. I'm writing down all the noises he makes so later > I can ask him what he meant. -- Steven Wright > > -- WWW: http://dean.bong.com.au LAN: http://www.bong.com.au EMAIL: [EMAIL PROTECTED] or [EMAIL PROTECTED] ICQ: 16867613 ~Zaq -- I look at life as being cruise director on the Titanic. I may not get there, but I'm going first class. -- Art Buchwald signature.asc Description: This is a digitally signed message part
Quake 4
The linux client came out yesterday. Has anyone gotten in it working in debian-amd64? Mine is segfaulting and I can't figure out why for the life of me. Thanks! ~Zaq -- My friend has a baby. I'm writing down all the noises he makes so later I can ask him what he meant. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: libc6 & ia32-libs
Funny how timing is, sometimes. Immediately after sending the prior email, I came across the solution. The symlink in /lib which points to your 32bit linker must point to your /var/chroot/foo/lib/ld-linux.so.2, NOT /emul/lib... Remove the bogus symlink, create the proper, rerun ldconfig, and voila. Now to get this Quake4 segfault fixed. Zaq On Thu, 2005-10-20 at 23:23 -0400, Zaq Rizer wrote: I have the same issue; I cannot get games like this to run in native amd64. Did you ever find a solution? Zaq On Sat, 2005-09-03 at 03:14 +0200, Sergi Vidal wrote: Hello, i've recently upgrade my debian sid and one of the upgraded packets was libc6... after this I get the follow errors with programs that uses ia32-libs. [EMAIL PROTECTED]:~$ quake3 ./quake3.x86: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference [EMAIL PROTECTED]:~$ cedega /home/benit/TransGaming_Drive/Program\ Files/GUILD\ WARS/Gw.exe /usr/lib/transgaming_cedega//winex/bin/pthreads_stack_test: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference /usr/bin/cedega: line 144: [: -gt: unary operator expected /usr/lib/transgaming_cedega//winex/bin/wine: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference my /etc/ld.so.conf is: /usr/X11R6/lib /emul/ia32-linux/lib /emul/ia32-linux/usr/lib /emul/ia32-linux/usr/X11R6/lib versions of the libraries: ii libc6 2.3.5-6GNU C Library: Shared libraries and Timezone data ii libc6-dev 2.3.5-6GNU C Library: Development Libraries and Header F ii ia32-libs1.4 ia32 shared libraries for use on amd64 and ia64 systems ii ia32-libs-dev1.4 ia32 development libraries and headers for use on ia32/ia64 systems [EMAIL PROTECTED]:~$ ls -l /emul/ia32-linux/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 2005-09-01 19:25 /emul/ia32-linux/lib/tls/libc.so.6 -> libc-2.3.2.so Anyone have any idea howto solve this? ~Zaq -- Why is the alphabet in that order? Is it because of that song? -- Steven Wright ~Zaq -- Is it weird in here, or is it just me? -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: libc6 & ia32-libs
I have the same issue; I cannot get games like this to run in native amd64. Did you ever find a solution? Zaq On Sat, 2005-09-03 at 03:14 +0200, Sergi Vidal wrote: Hello, i've recently upgrade my debian sid and one of the upgraded packets was libc6... after this I get the follow errors with programs that uses ia32-libs. [EMAIL PROTECTED]:~$ quake3 ./quake3.x86: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference [EMAIL PROTECTED]:~$ cedega /home/benit/TransGaming_Drive/Program\ Files/GUILD\ WARS/Gw.exe /usr/lib/transgaming_cedega//winex/bin/pthreads_stack_test: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference /usr/bin/cedega: line 144: [: -gt: unary operator expected /usr/lib/transgaming_cedega//winex/bin/wine: relocation error: /emul/ia32-linux/lib/tls/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference my /etc/ld.so.conf is: /usr/X11R6/lib /emul/ia32-linux/lib /emul/ia32-linux/usr/lib /emul/ia32-linux/usr/X11R6/lib versions of the libraries: ii libc6 2.3.5-6GNU C Library: Shared libraries and Timezone data ii libc6-dev 2.3.5-6GNU C Library: Development Libraries and Header F ii ia32-libs1.4 ia32 shared libraries for use on amd64 and ia64 systems ii ia32-libs-dev1.4 ia32 development libraries and headers for use on ia32/ia64 systems [EMAIL PROTECTED]:~$ ls -l /emul/ia32-linux/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 2005-09-01 19:25 /emul/ia32-linux/lib/tls/libc.so.6 -> libc-2.3.2.so Anyone have any idea howto solve this? ~Zaq -- Why is the alphabet in that order? Is it because of that song? -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: Kernel Headers for 2.6.11
On Wed, 2005-09-21 at 08:30 -0400, Lennart Sorensen wrote: On Tue, Sep 20, 2005 at 10:51:57PM -0400, Zaq Rizer wrote: - snip for brevity - Well for me compiling has worked just fine when I use module assistant (and have gcc-4.0 installed since that is what the debian 2.6.12 kernels use and hence require, unless you rebuilt it with 3.4 or someone else did). apt-get install gcc-4.0 (just in case you didn't already) m-a -t prepare (sets up kernel headers and build essentials and such) m-a a-i -t nvidia (builds and installs the module and it's dependancies) Len Sorensen Wow ... I don't understand why that worked, but it worked. I'll look into the how and why later. Thanks so much, Len! Should I follow a similar method to update my nvidia-glx package in my 32bit chroot or can I just install the experimental i386 debs for this? Thanks again, ~Zaq -- Things will get better despite our efforts to improve them. -- Will Rogers signature.asc Description: This is a digitally signed message part
Re: Kernel Headers for 2.6.11
On Wed, 2005-09-21 at 01:10 -0500, Aethon wrote: On 9/20/05, Zaq Rizer <[EMAIL PROTECTED]> wrote: Sorry to sort of butt in here, but I've been trying to get my nvidia drivers fixed for some time now and am stuck at a certain point. Hoping you can point me in the same direction you took, since you recently got your setup working. To be honest I'm not completely sure what you are doing. I just followed the directions from http://home.comcast.net/~andrex/Debian-nVidia/ going "the Debian way" using module-assistant. I used the stock 2.6.12 debian kernel and it all worked without a hitch. So you're running the 7174 version of the nvidia module? I was under the impression you were running the most recent. Anyone else out there got the recent drivers working with a debian-provided 2.6.12-amd64-k8? Aethon Thanks anyway, Aethon. ~Zaq -- In like a dimwit, out like a light. -- Pogo signature.asc Description: This is a digitally signed message part
Re: Kernel Headers for 2.6.11
On Sun, 2005-09-18 at 01:07 +, Aethon wrote: On 9/17/05, Frank <[EMAIL PROTECTED]> wrote: As a followup to my other message: Now I understand. "kernel-headers" as well as "kernel-image" are obsoleted, because the new kernel package now creates "linux-image" as well as "linux-headers" packages. And the newest of these is linux-headers-2.6.12-1. That answers quite a few things. I've now got 2.6.12 running with the nvidia drivers. Now to figure out the sound... Thanks Aethon Sorry to sort of butt in here, but I've been trying to get my nvidia drivers fixed for some time now and am stuck at a certain point. Hoping you can point me in the same direction you took, since you recently got your setup working. Steps I have taken thus far: Following Adam Majer's instructions, which are roughly 1) Get the latest nvidia-graphics-drivers package files from experimental 2) dpkg-source -x nvidia-graphics-drivers_1.0.7667-3.dsc cd nvidia-graphics-drivers* fakeroot dpkg-buildpackage 3) [This part I might have mucked up] -- Use the old instructions for building the custom nvidia-kernel module as per the AMD64 HOWTO available at [https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id272586] But it's during this step #3, which Adam also recommended, applying [MAKEFLAGS="CC=gcc-3.4" make-kpkg --append-to-version -1-amd64-k8 modules_image (from within /usr/src/linux-headers-2.6.12-1-amd64-k8] that I get the following error: make[1]: Entering directory `/usr/src/linux-headers-2.6.12-1-amd64-k8' scripts/Makefile.build:13: scripts/basic/Makefile: No such file or directory make[2]: *** No rule to make target `scripts/basic/Makefile'. Stop. make[1]: *** [scripts_basic] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-1-amd64-k8' make: *** [stamp-kernel-configure] Error 2 Naturally, attempting to install the nvidia-glx, et al, packages fails because I need nvidia-kernel-1.0.7676. Any help you or Adam Majer can provide is greatly appreciated. ~Zaq -- I just got out of the hospital after a speed reading accident. I hit a bookmark. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: X.org enters in Sid
On Fri, 2005-07-15 at 21:47 +0200, Goswin von Brederlow wrote: Zaq Rizer <[EMAIL PROTECTED]> writes: > I can't get X.org installed ... possibly someone has encountered this? > dist-upgrade gives: > libx11-6: Depends: x11-common (> 4.3.0) but it is not installed > So I try apt-get install x11-common, which reports: > Unpacking x11-common (from .../x11-common_6.8.2.dfsg.1-2_all.deb) ... > dpkg: error processing > /var/cache/apt/archives/x11-common_6.8.2.dfsg.1-2_all.deb (--unpack): > trying to overwrite `/etc/X11/Xsession', which is also in package xorg-common > Seems to me I have the wrong packages installed ... thoughts? > On Wed, 2005-07-13 at 11:59 +0200, v0n0 wrote: > > Since yesterday night, X.org 6.8.2 is in Debian unstable. Be aware if > you dist-upgrade you will get X.org installed over Xfree. Did you have xorg from ubuntu installed or from somewhere else? Debian has no package called xorg-common so that must be something you screwed up. MfG Goswin Yes, I had some packages from Ubuntu ... I suppose I could manually uninstall the offending package(s)? ~Zaq -- In like a dimwit, out like a light. -- Pogo signature.asc Description: This is a digitally signed message part
Re: X.org enters in Sid
I can't get X.org installed ... possibly someone has encountered this? dist-upgrade gives: libx11-6: Depends: x11-common (> 4.3.0) but it is not installed So I try apt-get install x11-common, which reports: Unpacking x11-common (from .../x11-common_6.8.2.dfsg.1-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/x11-common_6.8.2.dfsg.1-2_all.deb (--unpack): trying to overwrite `/etc/X11/Xsession', which is also in package xorg-common Seems to me I have the wrong packages installed ... thoughts? On Wed, 2005-07-13 at 11:59 +0200, v0n0 wrote: Since yesterday night, X.org 6.8.2 is in Debian unstable. Be aware if you dist-upgrade you will get X.org installed over Xfree. ~Zaq -- What is comedy? Comedy is the art of making people laugh without making them puke. -- Steve Martin signature.asc Description: This is a digitally signed message part
Re: Re : Flash kills Firefox (ia32)
On Sun, 2005-07-10 at 16:12 +, Jean-Luc Coulon (f5ibh) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 10.07.2005 17:58:16, Zaq Rizer a écrit : > Any page containing flash kills Firefox within the 32bit chroot. The > only debug information it gives is the following: > > [EMAIL PROTECTED] dchroot -c ia32 -d firefox > (ia32) firefox > > (firefox-bin:26200): Gtk-WARNING **: Locale not supported by C > library. > Using the fallback 'C' locale. > > (firefox-bin:26200): Gdk-WARNING **: gdk_property_get(): length value > has wrapped in calculation (did you pass G_MAXLONG?) > > -!-!-!- > The previous lines are all printed upon first draw of the window, what > follows below is what occurs after visiting a page with flash on it, > e.g. http://www.macromedia.com/shockwave/welcome/ > -!-!-!- > > NP_Initialize > New > SetWindow > Destroy > The program 'Gecko' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadShmSeg (invalid shared segment parameter)'. > (Details: serial 31 error_code 172 request_code 149 minor_code 2) > (Note to programmers: normally, X errors are reported > asynchronously; >that is, you will receive the error a while after causing it. >To debug your program, run it with the --sync command line >option to change this behavior. You can then get a meaningful >backtrace from your debugger if you break on the gdk_x_error() > function.) > dchroot: Child exited non-zero. > dchroot: Operation failed. The free flash plugin kills mozilla, firefox, galeon, epiphany and everything based on the Gecko engine. From you chroot, after removing the libflash-mozplugin and its dependancies do: apt-get install flashplugin-nonfree And you will get an non-free (according to Debian policy) but workable package. > > --End. > > Thoughts? I've tried the following, to no avail: > > agi --reinstall libflash-dev libflash-mozplugin libflash-swfplayer > libflash0 flashplayer-mozilla flashplugin-nonfree > [agi is my apt-get install alias] > > Do one of those packages interfere with another or something? > > > Thanks, > ~Zaq > > -- > Life is wasted on the living. -- The Restaurant at the Edge of the > Universe. > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC0Uj+Xit3lz9m7V4RAqvPAKC4iCSh54m+N1/FKsJSoZqI6AnkDwCeI8Nd Gr2WkuBS7ipvDUh1LH+QQz4= =cYWe -END PGP SIGNATURE- Perfect, that worked great. Thanks! ~Zaq -- Romeo wasn't bilked in a day. -- Walt Kelly, "Ten Ever-Lovin' Blue-Eyed Years With Pogo" signature.asc Description: This is a digitally signed message part
Flash kills Firefox (ia32)
Any page containing flash kills Firefox within the 32bit chroot. The only debug information it gives is the following: [EMAIL PROTECTED] dchroot -c ia32 -d firefox (ia32) firefox (firefox-bin:26200): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (firefox-bin:26200): Gdk-WARNING **: gdk_property_get(): length value has wrapped in calculation (did you pass G_MAXLONG?) -!-!-!- The previous lines are all printed upon first draw of the window, what follows below is what occurs after visiting a page with flash on it, e.g. http://www.macromedia.com/shockwave/welcome/ -!-!-!- NP_Initialize New SetWindow Destroy The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadShmSeg (invalid shared segment parameter)'. (Details: serial 31 error_code 172 request_code 149 minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) dchroot: Child exited non-zero. dchroot: Operation failed. --End. Thoughts? I've tried the following, to no avail: agi --reinstall libflash-dev libflash-mozplugin libflash-swfplayer libflash0 flashplayer-mozilla flashplugin-nonfree [agi is my apt-get install alias] Do one of those packages interfere with another or something? Thanks, ~Zaq -- Life is wasted on the living. -- The Restaurant at the Edge of the Universe. signature.asc Description: This is a digitally signed message part
Re: Servers inside the chroot
On Fri, 2005-07-08 at 09:40 -0400, Lennart Sorensen wrote: On Fri, Jul 08, 2005 at 06:30:30AM -0700, Zachary Rizer wrote: > Oh my, a forehead slapper. At some point, I had > commented out all my 32bit libs from ld.so.conf. I > removed the comments, reran ldconfig, checked ldd > bin/* in my NX directory, and it works! Quite likely at some point when amd64 had a new libc, since the libc package seems to be very upset if it finds the 32bit libc in the ld.so.conf paths while upgrading. > Thanks so much! > > I'll put together a write-up at some point for other > debian-amd64 users interested in using FreeNX. > > p.s. - It lives up to the hype, and even after using > it for just 5 minutes, I'd say it's worth the 50 > (pound) license. Len Sorensen Yep, that was it. As far as making a write-up, is there a preferred place to put it (i.e., the wiki) or just host it somewhere and hope people google for it? Suggestions? ~Zaq -- I got this powdered water -- now I don't know what to add. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: Servers inside the chroot
On Thu, 2005-07-07 at 20:13 -0600, Bob Proulx wrote: Zachary Rizer wrote: > --- Thomas Steffen <[EMAIL PROTECTED]> wrote: > > Yes, you can. The chroot may have a different file > > system, but it sees exactly the same network. Agreed. This works fine. > The server doesn't seem to want to run in the chroot, > or if it's running, I can't get to it from outside... > see below. The only below I see is: > > > I'd like to run the FreeNX server, but it won't work > > > in amd64 "mode" because of a missing > > > libstdc++-libc6.2-2.so.3, which is present in the > > > sid-ia32 chroot. Since as you say it is present in the sid-ia32 chroot that says to me that it is working for you. Right? If it is not working then what are the details? When you say ``amd64 "mode"'' do you mean native amd64 64-bit code? In which case it would not be using a 32-bit library but would instead be using a 64-bit library. Or do you mean running the 32-bit program outside the chroot? Bob The package contains statically-compiled 32bit binaries. It runs (the server process, I mean) in native amd64 code, except that when a client tries to connect, after it authenticates via SSH, it bails because it cannot find the aforementioned libstdc file, since it expects this common 32bit library. I tried moving the directory into my 32bit chroot, and running it from there, but that seems to cause an entire 'nother set of issues. (e.g., the server process won't even start). I'll look into it more today, I'd love to get it working and write up a howto for other debian-amd64 folks. ~Zaq -- I got this powdered water -- now I don't know what to add. -- Steven Wright signature.asc Description: This is a digitally signed message part
Re: 32bit chrooted apps can't use OpenGL .
Javier Kohen wrote: El lun, 28-03-2005 a las 00:29 -0500, Zaq Rizer escribiÃ: OpenGL games (e.g. Quake3 and Enemy Territory -- but *not* Doom3 [??]) run like total crap now. They run, but at about half what they should -- almost as if it's using the CPU instead of the GPU. Maybe some direct rendering option was disabled when you updated your kernel config? I recommend you use "make oldconfig" instead of "make menuconfig"/save/quit. I used to do the latter, but it's really difficult to see what changed (and sometimes options are renamed or replaced), while the former asks you about every new question (usually, not too many between stable releases). However, you should check the obvious places... dmesg, game logs, video driver logs, video driver forums, etc. This isn't a vanilla kernel - 2.6.11-9 is in sid/amd64 now. I simply used that. All log files are clean (I checked them first), it's just bad performance...I guess I should be happy the games run at all now, and maybe it will pan out in the coming days. -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit chrooted apps can't use OpenGL .
Zaq Rizer wrote: tony mancill wrote: If you don't mind building a package or using the stock kernel, you should be able to get the 7167 drivers going without too much issue. In summary: * start with a stock source tree of 2.6.11, configured for your box * install the nvidia-kernel-source package with apt * build and install the binary modules package * install the nvidia-glx package with apt At this point, your 64-bit setup should run fine. To use GL inside the 32-bit chroot, you need to install the nvidia-glx package there as well, but you're going to run into a dependency problem (or you're going to have to build the nvidia-kernel-2.6.11 package inside the chroot, which is what you've run into). A quick fix to this is, inside the chroot: cd /tmp apt-get source nvidia-glx cd nvidia-graphics-drivers-1.0.7167 vi debian/control (remove "nvidia-kernel-#VERSION#" from the Depends: line for nvidia-glx) dpkg-buildpackage -rfakeroot -us -uc sudo dpkg --install nvidia-glx_1.0.7167-1_i386.deb I think the process raises an interesting question about support for chroots in general. It seems like it would be helpful to differentiate between Depends and something like Kernel-Depends, since in general you'll never be able to actually satisfy Kernel-Depends for packages inside of the chroot (which is to say, since you're not running those modules, you're just using up disk space). A fairly simple work-around would be to have packages like nvidia-graphics-drivers build a dummy nvidia-kernel-chroot package that provided the nvidia-kernel-#VERSION# package, but I don't know if that would be palatable to the non-chrooting community at large. Cheers, tony Zaq Rizer wrote: There's a lot of unfortunate back story to this, but I'll spare you all and give you the current-day situation, as it stands, after a fresh complete reinstall: Because I cannot install the latest (7167) nvidia drivers via the method listed in the HOWTO on alioth, I've attempted installing them via nvidia's own installer. It worked just fine, although it warned me that I should be running 2.6.11+. Then about two hours later, I found out as X crashed in a flaming ball of death. So, I rolled back to 6629 (using nvidia's own drivers). These work perfectly, as they did before. However. In the 32bit chroot, I have installed 7167 via apt-get install, because, as far as I can tell, there is no way to install 6629 from nvidia's own installer (because it complains that it's an amd64 system, even while in the chroot) and the only version available in my unstable 32bit chroot is 7167. So in lieu of installing 2.6.11 (which I'll probably end up doing, but I've gotten rather happy with debian-provided kernels) what other options do I have? Any idea when 2.6.11.X will be available in sid/amd64? Thanks, Zaq Hmm... So 2.6.11-9 found its way into sid sometime tonight. I was surprised, but I don't know why. Still won't build here: /usr/bin/make EXTRAVERSION=-9-amd64-k8 \ ARCH=x86_64 oldconfig make[1]: Entering directory `/usr/src/kernel-headers-2.6.11-9-amd64-k8' HOSTCC scripts/kconfig/mconf.o scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu' follows non-static declaration scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu' was here make[2]: *** [scripts/kconfig/mconf.o] Error 1 make[1]: *** [oldconfig] Error 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.11-9-amd64-k8' make: *** [stamp-kernel-configure] Error 2 Note to everyone: As I was writing out this email, I removed gcc-4.0 and then re-tried the compilation, and that worked fine. I was using the following command, from the howto: CC=gcc-3.4 make-kpkg --append-to-version -9-amd64-k8 modules_image Apparently "CC=gcc-3.4" did not suffice in this case (or something else was going awry) but I had downgrade to 3.4 fully to get the .deb to build. Regards, Zaq Quick follow up: OpenGL games (e.g. Quake3 and Enemy Territory -- but *not* Doom3 [??]) run like total crap now. They run, but at about half what they should -- almost as if it's using the CPU instead of the GPU. -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit chrooted apps can't use OpenGL .
tony mancill wrote: If you don't mind building a package or using the stock kernel, you should be able to get the 7167 drivers going without too much issue. In summary: * start with a stock source tree of 2.6.11, configured for your box * install the nvidia-kernel-source package with apt * build and install the binary modules package * install the nvidia-glx package with apt At this point, your 64-bit setup should run fine. To use GL inside the 32-bit chroot, you need to install the nvidia-glx package there as well, but you're going to run into a dependency problem (or you're going to have to build the nvidia-kernel-2.6.11 package inside the chroot, which is what you've run into). A quick fix to this is, inside the chroot: cd /tmp apt-get source nvidia-glx cd nvidia-graphics-drivers-1.0.7167 vi debian/control (remove "nvidia-kernel-#VERSION#" from the Depends: line for nvidia-glx) dpkg-buildpackage -rfakeroot -us -uc sudo dpkg --install nvidia-glx_1.0.7167-1_i386.deb I think the process raises an interesting question about support for chroots in general. It seems like it would be helpful to differentiate between Depends and something like Kernel-Depends, since in general you'll never be able to actually satisfy Kernel-Depends for packages inside of the chroot (which is to say, since you're not running those modules, you're just using up disk space). A fairly simple work-around would be to have packages like nvidia-graphics-drivers build a dummy nvidia-kernel-chroot package that provided the nvidia-kernel-#VERSION# package, but I don't know if that would be palatable to the non-chrooting community at large. Cheers, tony Zaq Rizer wrote: There's a lot of unfortunate back story to this, but I'll spare you all and give you the current-day situation, as it stands, after a fresh complete reinstall: Because I cannot install the latest (7167) nvidia drivers via the method listed in the HOWTO on alioth, I've attempted installing them via nvidia's own installer. It worked just fine, although it warned me that I should be running 2.6.11+. Then about two hours later, I found out as X crashed in a flaming ball of death. So, I rolled back to 6629 (using nvidia's own drivers). These work perfectly, as they did before. However. In the 32bit chroot, I have installed 7167 via apt-get install, because, as far as I can tell, there is no way to install 6629 from nvidia's own installer (because it complains that it's an amd64 system, even while in the chroot) and the only version available in my unstable 32bit chroot is 7167. So in lieu of installing 2.6.11 (which I'll probably end up doing, but I've gotten rather happy with debian-provided kernels) what other options do I have? Any idea when 2.6.11.X will be available in sid/amd64? Thanks, Zaq Hmm... So 2.6.11-9 found its way into sid sometime tonight. I was surprised, but I don't know why. Still won't build here: /usr/bin/make EXTRAVERSION=-9-amd64-k8 \ ARCH=x86_64 oldconfig make[1]: Entering directory `/usr/src/kernel-headers-2.6.11-9-amd64-k8' HOSTCC scripts/kconfig/mconf.o scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu' follows non-static declaration scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu' was here make[2]: *** [scripts/kconfig/mconf.o] Error 1 make[1]: *** [oldconfig] Error 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.11-9-amd64-k8' make: *** [stamp-kernel-configure] Error 2 Note to everyone: As I was writing out this email, I removed gcc-4.0 and then re-tried the compilation, and that worked fine. I was using the following command, from the howto: CC=gcc-3.4 make-kpkg --append-to-version -9-amd64-k8 modules_image Apparently "CC=gcc-3.4" did not suffice in this case (or something else was going awry) but I had downgrade to 3.4 fully to get the .deb to build. Regards, Zaq -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [AGAIN] kde 3.4 packages anybody?
Rafael Rodríguez wrote: From wiki.debian.net: KDE 3.4.0 will not enter sid until sarge is released. Now i _DO_ worry for having an alternative repository.. anyone with 64-bit packages? Regards, Rafael Rodríguez Have you tried installing from source? -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 32bit chrooted apps can't use OpenGL .
Frederik Schueler wrote: Hello, On Sat, Mar 26, 2005 at 10:25:51PM -0500, Zaq Rizer wrote: Any idea when 2.6.11.X will be available in sid/amd64? kernel-source-2.6.11 entered sid today, so expect kernel-image-2.6.11-amd64 within a day or two. Kind regards Frederik Schueler Oh, excellent, I see that now. Thanks Frederik! -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
32bit chrooted apps can't use OpenGL .
There's a lot of unfortunate back story to this, but I'll spare you all and give you the current-day situation, as it stands, after a fresh complete reinstall: Because I cannot install the latest (7167) nvidia drivers via the method listed in the HOWTO on alioth, I've attempted installing them via nvidia's own installer. It worked just fine, although it warned me that I should be running 2.6.11+. Then about two hours later, I found out as X crashed in a flaming ball of death. So, I rolled back to 6629 (using nvidia's own drivers). These work perfectly, as they did before. However. In the 32bit chroot, I have installed 7167 via apt-get install, because, as far as I can tell, there is no way to install 6629 from nvidia's own installer (because it complains that it's an amd64 system, even while in the chroot) and the only version available in my unstable 32bit chroot is 7167. So in lieu of installing 2.6.11 (which I'll probably end up doing, but I've gotten rather happy with debian-provided kernels) what other options do I have? Any idea when 2.6.11.X will be available in sid/amd64? Thanks, Zaq -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: powernowd / stock kernels
Javier, I wouldn't say I "prefer" powernowd, per se, but I know that powernowd is made for AMD, whereas cpudynd is more generic (afaik). That being said, I use cpudynd in my thinkpad (X40) and it works very well. YMMV, Zaq Javier Kohen wrote: Hi guys, is there any reason why you prefer powernowd to cpudyn? I was wondering because I'm using the later on my notebook. I barely use it on batteries, but I like the noise reduction that comes with the reduced speed. Zachary Rizer wrote: Aha! You're right. Works like a charm here as well. Thank you Thomas! --- "T.J. Zeeman" <[EMAIL PROTECTED]> wrote: Hi, On Fri, 2005-03-04 at 11:06 -0800, Zachary Rizer wrote: Please disregard previous email -- I just realized powernowd is only on XP-M processors, and that what I'm looking for is "Cool 'n Quiet". My mistake! Actually, no mistake at all. I have an AMD64 and run powernowd to have cpu-scaling (as provided by the CnQ-feature in the cpu). I got it to run on a Debian kernel-image after I put powernowd-k8 and cpufreq-userspace in /etc/modules. It was apparently necessary to have these loaded forcedly to get the powernowd daemon to run. regards, Thomas -- "Firefox is both more secure and more modern than IE [Internet Explorer], and it comes packed with user-friendly features the Microsoft browser can't touch." -- Walt Mossberg, The Wall Street Journal. Find out what all the fuss is about: Get Mozilla Firefox. http://www.getfirefox.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
