Re: Tracking sarge

2005-02-05 Thread Goswin von Brederlow
Sven Mueller <[EMAIL PROTECTED]> writes: > Or in other words: With a 64bit (amd64) kernel, where are the actual > limits for: > 32bit Apps ~4 GiB > 64bit Apps 17179869184 GiB theoretically ~262144 GiB on current CPUs (- a few GiB the kernel reserves) > > Thanks, > Sven MfG Goswin -

Re: libxf86config.a can't be used by shared libraries

2005-02-05 Thread Goswin von Brederlow
Sebastian Kügler <[EMAIL PROTECTED]> writes: > On Sunday 06 February 2005 00:29, Goswin von Brederlow wrote: >> Sebastian Kügler <[EMAIL PROTECTED]> writes: >> > These are exactly identical files, hence the error from linking to either >> > one is the same. >> > >> > miro.sebas(~): md5sum /usr/X11

Re: compiling custom kernel with gcc-3.4

2005-02-05 Thread David Liontooth
On Sat, 5 Feb 2005, Jonathan Marchand wrote: > Hi, > > I'am running an amd64 laptop and I would like to build a kernel with > gcc-.34 like the kernel images avaible on the internet. Therefore, it > seems I can only build kernel with gcc-3.3. I did change some > variables in the kernel-source's Ma

Fwd: Re: address space (was Re: Tracking sarge)

2005-02-05 Thread Kurt Roeckx
I guess other people might be interested in this too. Kurt --- Begin Message --- On Sun, Feb 06, 2005 at 01:24:26AM +0100, Sven Mueller wrote: > Kurt Roeckx wrote on 03/02/2005 18:24: > > > >Actually, you can use 4GB of address space for userspace. > > For 32bit userspace or also for 64bit user

K8 Mainboard Compatibility Update

2005-02-05 Thread Shawn D'Alimonte
The Gigabyte GA-K8VNXP has a VIA rhine LAN adapter as well as the r8169 shown in the table (2 ports). Also it has via82xx audio that isn't shown in the table. -- Shawn D'Alimonte [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [E

Re: Tracking sarge

2005-02-05 Thread Sven Mueller
Kurt Roeckx wrote on 03/02/2005 18:24: >> On Thu, Feb 03, 2005 at 05:54:35PM +0100, Goswin von Brederlow wrote: >> > >From what I heart you won't feel the difference. The advantage of a 64bit kernel lies in having more than 3GB address space (more than 4GB for 64bit) programs and the po

Re: Re: Installing Nvidia 1.0.6629 Driver

2005-02-05 Thread SpikeyGG
Actually, I got it figured out, you were right those messages are normal.  Apparently, changing the S20xprint to non-executable causes XFree86 to bomb without an error in XFree86.0.log or syslog... it drops an error into .xsession-errors.  I didn't want a print server running so I took off t

Re: compiling custom kernel with gcc-3.4

2005-02-05 Thread Ed Tomlinson
On Saturday 05 February 2005 13:52, Jonathan Marchand wrote: > Hi, > > I'am running an amd64 laptop and I would like to build a kernel with > gcc-.34 like the kernel images avaible on the internet. Therefore, it > seems I can only build kernel with gcc-3.3. I did change some > variables in the ker

Re: libxf86config.a can't be used by shared libraries

2005-02-05 Thread Sebastian Kügler
On Sunday 06 February 2005 00:29, Goswin von Brederlow wrote: > Sebastian Kügler <[EMAIL PROTECTED]> writes: > > These are exactly identical files, hence the error from linking to either > > one is the same. > > > > miro.sebas(~): md5sum /usr/X11R6/lib/libxf86config*.a > > 27db885b4c292588c6c55ae95

Re: libxf86config.a can't be used by shared libraries

2005-02-05 Thread Goswin von Brederlow
Sebastian Kügler <[EMAIL PROTECTED]> writes: > These are exactly identical files, hence the error from linking to either one > is the same. > > miro.sebas(~): md5sum /usr/X11R6/lib/libxf86config*.a > 27db885b4c292588c6c55ae951c85132 /usr/X11R6/lib/libxf86config.a > 27db885b4c292588c6c55ae951c851

Re: libxf86config.a can't be used by shared libraries

2005-02-05 Thread Sebastian Kügler
On Saturday 05 February 2005 23:03, Goswin von Brederlow wrote: > Sebastian Kügler <[EMAIL PROTECTED]> writes: > > On Wednesday 02 February 2005 21:22, Simon Edwards wrote: > >> It appears that libxf86config.a can't be used by shared libraries. It > >> doesn't appear to have been compiled correctly

Re: libxf86config.a can't be used by shared libraries

2005-02-05 Thread Goswin von Brederlow
Sebastian Kügler <[EMAIL PROTECTED]> writes: > On Wednesday 02 February 2005 21:22, Simon Edwards wrote: >> It appears that libxf86config.a can't be used by shared libraries. It >> doesn't appear to have been compiled correctly using the -fPIC compile >> option. >> >> I'm currently developing a ut

libxf86config.a can't be used by shared libraries

2005-02-05 Thread Sebastian Kügler
On Wednesday 02 February 2005 21:22, Simon Edwards wrote: > It appears that libxf86config.a can't be used by shared libraries. It > doesn't appear to have been compiled correctly using the -fPIC compile > option. > > I'm currently developing a util in Python that uses has a C extension which > uses

Re: compiling custom kernel with gcc-3.4

2005-02-05 Thread Goswin von Brederlow
Jonathan Marchand <[EMAIL PROTECTED]> writes: > Hi, > > I'am running an amd64 laptop and I would like to build a kernel with > gcc-.34 like the kernel images avaible on the internet. Therefore, it > seems I can only build kernel with gcc-3.3. I did change some > variables in the kernel-source's Ma

compiling custom kernel with gcc-3.4

2005-02-05 Thread Jonathan Marchand
Hi, I'am running an amd64 laptop and I would like to build a kernel with gcc-.34 like the kernel images avaible on the internet. Therefore, it seems I can only build kernel with gcc-3.3. I did change some variables in the kernel-source's Makefile and the environment variables, but the resulting ke

Re: Kernel panic on boot with 2.6.10 Kernel

2005-02-05 Thread Gordon Ball
Unfortunately this doesn't seem to make any difference. Are the kernel options (root, real_root) unchanged in this version? On Sat, 5 Feb 2005 17:20:54 +, Gordon Ball <[EMAIL PROTECTED]> wrote: > On Sat, 5 Feb 2005 17:01:30 +0100, Filippo Carone > <[EMAIL PROTECTED]> wrote: > > * Gordon Ball

Re: Kernel panic on boot with 2.6.10 Kernel

2005-02-05 Thread Gordon Ball
On Sat, 5 Feb 2005 17:01:30 +0100, Filippo Carone <[EMAIL PROTECTED]> wrote: > * Gordon Ball ([EMAIL PROTECTED]) ha scritto: > > Having until recently been using the stock 2.6.8-1-amd64-k8 kernel > > (without problems), I decided to try and compile a new one myself. > > > > Using the package for ke

Re: Installing Nvidia 1.0.6629 Driver

2005-02-05 Thread Theodore Kisner
On Friday 04 February 2005 23:23, SpikeyGG wrote: > I tried what you suggested about making the symbolic link and it appears to > have half-way worked. Now when I kick off X it shows me the Nvidia logo > for a little while but then jumps back out (without reporting any errors to > standard output)

Re: Kernel panic on boot with 2.6.10 Kernel

2005-02-05 Thread Filippo Carone
* Gordon Ball ([EMAIL PROTECTED]) ha scritto: > Having until recently been using the stock 2.6.8-1-amd64-k8 kernel > (without problems), I decided to try and compile a new one myself. > > Using the package for kernel-source-2.6.10 I compiled a monolithic > kernel with (I think) everything essentia

Kernel panic on boot with 2.6.10 Kernel

2005-02-05 Thread Gordon Ball
Having until recently been using the stock 2.6.8-1-amd64-k8 kernel (without problems), I decided to try and compile a new one myself. Using the package for kernel-source-2.6.10 I compiled a monolithic kernel with (I think) everything essential for boot compiled into the kernel. In this configurat

Re: Installing Nvidia 1.0.6629 Driver

2005-02-05 Thread Paul Brook
On Saturday 05 February 2005 07:23, SpikeyGG wrote: > Theodore, > > I tried what you suggested about making the symbolic link and it appears to > have half-way worked. Now when I kick off X it shows me the Nvidia logo > for a little while but then jumps back out (without reporting any errors to >

Bug#293722: grub: simulated stack not marked PROT_EXEC, causes segfaults on new hardware

2005-02-05 Thread Colin Watson
Package: grub Version: 0.95+cvs20040624-12 Severity: important When using Linux 2.6.10, grub's 'install' command segfaults on new hardware that has the NX bit available (e.g. AMD64, and I think also new Pentium 4 systems). This turns out to be because: * grub's Unix shell allocates a region of