On Tue, Nov 07, 2006 at 12:27:46PM +, Jo Shields wrote:
32-bit OSen have a theoretical limit of 4GiB addressable memory.
PAE gives you 64 GiB physical memory on 32-bit processors that support
it.
Gabor
--
-
MTA SZTAKI
On Tue, Nov 07, 2006 at 03:18:36PM +0100, Giacomo Mulas wrote:
I wish this were always true. I tried to get rid of the memory hole, but
then my nice 64 bit Linux kernel would crash (or better get in an infinite
loop) upon initialising the Yukon Gigabit Ethernet NIC (i.e. immediately
after
eFoxPay Co ofrfe Servizi di Gestione Finanziale Esterna.
Noi lavoriamo in tutto il mondo massimamente con stabilimenti Internet di
livello mezzo e piccolo che cercano
alta commodita ev elocita di trassazzioni monetarie.
Quelli sono, per essempio, Intrrnet shop, mercati, auzioni on-line, servizi
On Tue, 2006-11-07 at 18:39 +0100, Lubos Vrbka wrote:
hi,
Do 'apt-get install nvidia-kernel-source nvidia-kernel-common', then
run module assistant (m-a) as already suggest on this list.
I've done it several times, and it worked.
i tried to run m-a but the compilation ended with an
On Wed, 8 Nov 2006, Gabor Gombas wrote:
Try using the skge driver instead of sk98lin.
Thanks for the hint, I tried and indeed obtained a little improvement: it
does not hang as with sk98lin. However it still fails to initialise
properly, any trial to connect to anything via that NIC yields a
On Wed, Nov 08, 2006 at 12:15:41PM +0100, Giacomo Mulas wrote:
On Wed, 8 Nov 2006, Gabor Gombas wrote:
Try using the skge driver instead of sk98lin.
Thanks for the hint, I tried and indeed obtained a little improvement: it
does not hang as with sk98lin. However it still fails to initialise
(Please Cc: me on answers, as I am not subscribed to debian-adm64. Thanks.)
Hi.
I am currently struck by a _very_ weird bug of df on Sarge-AMD64 with
coreutils-5.2.1-2.
Note the randomly changing output:
[EMAIL PROTECTED]:~# while sleep 1; do BLOCK_SIZE= df --portability /; done
Filesystem
On Wed, 8 Nov 2006, Hamish Moffatt wrote:
Maybe there is nowhere to map the card's buffers into the bottom 4Gb of
RAM when you have 4Gb of real RAM available. (This would seem to be a
problem with all PCI cards plus AGP cards etc but maybe most systems
or cards have a workaround?)
Google has
On Wed, Nov 08, 2006 at 01:27:41PM +0100, Sven Hartge wrote:
I am currently struck by a _very_ weird bug of df on Sarge-AMD64 with
coreutils-5.2.1-2.
Note the randomly changing output:
[EMAIL PROTECTED]:~# while sleep 1; do BLOCK_SIZE= df --portability /; done
Interesting. Couldn't find
Um 23:36 Uhr am 08.11.06 schrieb Hamish Moffatt:
On Wed, Nov 08, 2006 at 01:27:41PM +0100, Sven Hartge wrote:
I am currently struck by a _very_ weird bug of df on Sarge-AMD64 with
coreutils-5.2.1-2.
Note the randomly changing output:
[EMAIL PROTECTED]:~# while sleep 1; do BLOCK_SIZE= df
On Wed, Nov 08, 2006 at 02:03:46PM +0100, Sven Hartge wrote:
Um 23:36 Uhr am 08.11.06 schrieb Hamish Moffatt:
Suggest backporting coreutils or upgrading to etch...
Upgrading to Etch is not an option right now, backporting coreutils might
work. An officially fixed package would be the best
On Tue, Nov 07, 2006 at 07:10:13PM -0500, Jim Crilly wrote:
-I already installed kernel headers and tried pointing the vmware-config
to many places without success.
Well I don't know what to say about that, I've installed VMWare on numerous
machines with custom and Debian kernels and the
On Wed, 8 Nov 2006, [EMAIL PROTECTED] wrote:
Hi. Have anybody heared about some mosix or open-mosix kernel for debian amd 64?
When I searched the package list on debian.org I have found only some mosix
kernel in oldstable dist (for i386 only).
Maby there is some unofficial one?
Or maby there
On Tue, Nov 07, 2006 at 11:07:56PM +0100, Daniel Tryba wrote:
Well, I personally have been trying debian kernels for a couple of
weeks. A machine that has been running Debian/unstable with custom
kernels for the last couple of years and always has been very stable,
now is not detecting the
On Wed, Nov 08, 2006 at 12:02:36AM +0100, Daniel Tryba wrote:
Thanks for the link, but:
-the machine having problems is not running a 64bit kernel
-I already installed kernel headers and tried pointing the vmware-config
to many places without success.
/usr/src/linux-headers-x.y.z-w/include
You will also want to install nvidia-glx after running module assistant.
but nvidia-glx is not available in etch. i had to use unstable version
when installing amd64 etch desktop.
any hints? what am i doing wrong?
This is caused by a stupid packaging error that remains to be fixed
Type cat
Gabor Gombas [EMAIL PROTECTED] writes:
On Tue, Nov 07, 2006 at 12:27:46PM +, Jo Shields wrote:
32-bit OSen have a theoretical limit of 4GiB addressable memory.
PAE gives you 64 GiB physical memory on 32-bit processors that support
it.
Yes, but a 32-bit OS still can't use it. Or can
On Wed, 8 Nov 2006, Matthias Julius wrote:
Yes, but a 32-bit OS still can't use it. Or can it?
Yes the OS can, but single apps will usually still see = 4Gbytes, unless
they do a lot of (slow) black magic. Therefore, if you need a lot of memory
overall because you need to run a huge number of
hi,
After installing an appropriate gcc package to match your running
kernel, the nvidia-kernel-source package can successfully create an
nvidia-kernel-$FOO package to match your system. nvidia-glx cannot
install without an appropriate nvidia-kernel package (which is what
module-assistant
On Wed, 2006-11-08 at 16:46 +0100, Lubos Vrbka wrote:
You will also want to install nvidia-glx after running module assistant.
but nvidia-glx is not available in etch. i had to use unstable version
when installing amd64 etch desktop.
any hints? what am i doing wrong?
This is caused
On Wed, 2006-11-08 at 17:38 +0100, Lubos Vrbka wrote:
hi,
After installing an appropriate gcc package to match your running
kernel, the nvidia-kernel-source package can successfully create an
nvidia-kernel-$FOO package to match your system. nvidia-glx cannot
install without an
On Wed, Nov 08, 2006 at 11:25:30AM -0500, Matthias Julius wrote:
Yes, but a 32-bit OS still can't use it. Or can it?
A 32bit OS with PAE support can use the ram, but you are still limited
to 32bit memory space per application.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Hi,
A bug seems to have crept in linux-image-2.6.18-1-amd64 so that purging
the package fails with the error:
dpkg: error processing linux-image-2.6.18-1-amd64 (--purge):
subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
On Wednesday 08 November 2006 01:08 am, Gabor Gombas wrote:
On Tue, Nov 07, 2006 at 12:27:46PM +, Jo Shields wrote:
32-bit OSen have a theoretical limit of 4GiB addressable memory.
PAE gives you 64 GiB physical memory on 32-bit processors that support
it.
Yes, but each process is still
Hi
I have had such problems several times and I have always resolved them by
editing /var/lib/dpkg/status by hand, setting the status of the corresponding
package to not-installed.
This has worked but it is not the preferred solution. If anyone knows a
better solution please tell.
Il Wed, 08 Nov 2006 15:26:00 +0100
[EMAIL PROTECTED] scrisse:
Hi. Have anybody heared about some mosix or open-mosix kernel for debian
amd 64? When I searched the package list on debian.org I have found only
some mosix kernel in oldstable dist (for i386 only).
Maby there is some unofficial
[Eek. Top-posting evil!]
On Wed, Nov 08, 2006 at 09:05:25PM +0100, Gudjon I. Gudjonsson wrote:
Þann Miðvikudagur 08 nóvember 2006 19:41 skrifaði Seb:
dpkg: error processing linux-image-2.6.18-1-amd64 (--purge):
subprocess post-removal script returned error exit status 128
Errors were
Hi,
On Wed, Nov 08, 2006 at 09:05:25PM +0100, Gudjon I. Gudjonsson wrote:
Hi
I have had such problems several times and I have always resolved them by
editing /var/lib/dpkg/status by hand, setting the status of the corresponding
package to not-installed.
This has worked but it is
Emmanuel Fleury wrote:
Couldn't it be kernel-space that would not be visible from user-space ?
No, because that is virtual and this is physical. The limitations on the two
are totally independent.
Thanks,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Christian Hammers wrote:
The is a kernel version called linux-image-2.6-amd64-k8-smp or so, try that. The
-generic has
maybe some options set that are not optimal for your system.
Impossible, as there aren't any options on x86_64 that control how much physical
memory you'll see (unlike IA-32).
Jo Shields wrote:
32-bit OSen have a theoretical limit of 4GiB addressable memory.
Wrong. IA-32 processors have had 36 address lines since PAE was added. That's
what CONFIG_HIGHMEM64G does for IA-32 kernels, BTW. It turns on PAE support.
However, there's an additional limitation as all
Freddie Cash fcash-ml at sd73.bc.ca writes:
On Wednesday 08 November 2006 01:08 am, Gabor Gombas wrote:
On Tue, Nov 07, 2006 at 12:27:46PM +, Jo Shields wrote:
32-bit OSen have a theoretical limit of 4GiB addressable memory.
PAE gives you 64 GiB physical memory on 32-bit
32 matches
Mail list logo
