Ernest jw ter Kuile <[EMAIL PROTECTED]> writes:
> On Tuesday 07 November 2006 07:10, vitko wrote:
>> > I only know of two (in my eyes) valid reasons to build your own kernel:
>>> ...
>> Two more reasons:
>> ...
>>
>
> One more: The debian stock kernel hangs on my system, while self built
> kerne
On Tuesday 07 November 2006 07:10, vitko wrote:
> > I only know of two (in my eyes) valid reasons to build your own kernel:
>> ...
> Two more reasons:
> ...
>
One more: The debian stock kernel hangs on my system, while self built kernels
don't. Since there are way too many drivers for not existi
On Mon, Nov 06, 2006 at 08:26:35PM +0100, Goswin von Brederlow wrote:
> > There is almost never a reason to not run one of debian's prebuilt
> > kernels. They work perfectly and optimally for probably 99% of users.
>
> I only know of two (in my eyes) valid reasons to build your own kernel:
>
>
On Wed, Nov 08, 2006 at 10:43:43AM -0500, Lennart Sorensen wrote:
> I also find initramfs handles LVM and software raid nicely, both of
> which I use, so I will stick with the modular kernels.
Debian initramfs tools used to use mdrun (maybe they still do) that is
horribly broken. There was a time
Freddie Cash 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 processor
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 exp
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-3
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". Tr
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 s
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]
wi
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
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. O
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
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 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
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 hi
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 init
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 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
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 Comp
On 11/08/06 12:02:36AM +0100, Daniel Tryba wrote:
> On Tue, Nov 07, 2006 at 05:38:50PM -0500, Jim Crilly wrote:
> > I've been using the pre-built kernels since I got this AMD64 box without
> > any hardware detection issues. If your soundcard disappears every couple of
> > reboots I would be more su
On Tue, Nov 07, 2006 at 05:38:50PM -0500, Jim Crilly wrote:
> I've been using the pre-built kernels since I got this AMD64 box without
> any hardware detection issues. If your soundcard disappears every couple of
> reboots I would be more suspicious of the hardware than the kernel.
This is contrad
On 11/07/06 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 soundcard ev
On Tue, Nov 07, 2006 at 04:39:00PM +0100, Goswin von Brederlow wrote:
> My system locks up when I run "ifconfig eth1 up" on the sk98lin module
> but I only have 1Gb of ram. Maybe I should play with the bios
> settings.
I'd guess that it could be related to IOMMU settings, but that does only
make s
On Tue, Nov 07, 2006 at 04:34:18PM +0100, Goswin von Brederlow wrote:
> > 1) I don't like seeing errors / misdetected hardware in kernel messages.
> > Far too many times I've seen loading drivers for hardware that was never
> > there. As for kernel, I want it to be clean and do its work for the
> >
On Tuesday 07 November 2006 10:32 am, John Hannfield wrote:
> Actually, Joost or others, do you know what difference the memCLK BIOS
> setting has?
>
> With "MTRR" set to discreet, and "Memhole Mapping" set to software
> control my system boots fine, and I can see 4GB RAM. However, I then
> install
Actually, Joost or others, do you know what difference the memCLK BIOS setting has?With "MTRR" set to discreet, and "Memhole Mapping" set to software controlmy system boots fine, and I can see 4GB RAM. However, I then install xen
then it won't boot. It fails activating the second core of the CPU.
Giacomo Mulas <[EMAIL PROTECTED]> writes:
> On Tue, 7 Nov 2006, Jo Shields wrote:
>
>> address. 64-bit OSen don't have that limitation, but many BIOSes assume
>> that there's only one OS on the market (32-bit XP) so keep the memory
>> configuration with a hole at 4GiB.
>
> I wish this were always
vitko <[EMAIL PROTECTED]> writes:
>> I only know of two (in my eyes) valid reasons to build your own kernel:
>>
>> 1. you hate initrd since it too often doesn't work
>> 2. you need/want some extra patch
>
> Two more reasons:
>
> 1) I don't like seeing errors / misdetected hardware in kernel messa
On Tue, 7 Nov 2006, Jo Shields wrote:
address. 64-bit OSen don't have that limitation, but many BIOSes assume
that there's only one OS on the market (32-bit XP) so keep the memory
configuration with a hole at 4GiB.
I wish this were always true. I tried to get rid of the memory hole, but
then m
On Mon, 2006-11-06 at 17:54 +0100, A J Stiles wrote:
> On Monday 06 November 2006 12:08, John Hannfield wrote:
> > I have a dual core Opteron 265 running in a Tyan K8WE (S2877) motherboard
> > with
> > 4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but using
> > a fresh install of t
Lennart Sorensen wrote:
> On Mon, Nov 06, 2006 at 05:54:00PM +0100, A J Stiles wrote:
>> There's your problem; you're still running the installer kernel. The
>> installer kernel is only supposed to work well enough and for long enough
>> for
>> you to build yourself a new one. Install kernel-p
Thanks Joost + JanIt was the Tyan BIOS memory mapping problem as you said.I had already turned the MTRR to discreet mapping, but it did notoccur to me to change the "Software Memory Hole" to software controlled,
rather than disabled. Once I did that, the system happily reports the 4GBof memory.Than
> I only know of two (in my eyes) valid reasons to build your own kernel:
>
> 1. you hate initrd since it too often doesn't work
> 2. you need/want some extra patch
Two more reasons:
1) I don't like seeing errors / misdetected hardware in kernel messages.
Far too many times I've seen loading dri
Lennart Sorensen <[EMAIL PROTECTED]> writes:
> On Mon, Nov 06, 2006 at 05:54:00PM +0100, A J Stiles wrote:
>> There's your problem; you're still running the installer kernel. The
>> installer kernel is only supposed to work well enough and for long enough
>> for
>> you to build yourself a new
On Mon, Nov 06, 2006 at 05:54:00PM +0100, A J Stiles wrote:
> There's your problem; you're still running the installer kernel. The
> installer kernel is only supposed to work well enough and for long enough for
> you to build yourself a new one. Install kernel-package, libncurses5-dev
> (menu
On Monday 06 November 2006 12:08, John Hannfield wrote:
> I have a dual core Opteron 265 running in a Tyan K8WE (S2877) motherboard
> with
> 4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but using
> a fresh install of testing/unstable from the AMD64 etch net-installer, I
> can stil
On Mon, 2006-11-06 at 12:08 +, John Hannfield wrote:
>
> I have a dual core Opteron 265 running in a Tyan K8WE (S2877)
> motherboard with
> 4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but
> using
> a fresh install of testing/unstable from the AMD64 etch net-installer,
> I ca
On 2006-11-06 John Hannfield wrote:
> I have a dual core Opteron 265 running in a Tyan K8WE (S2877) motherboard
> with
> 4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but using
> a fresh install of testing/unstable from the AMD64 etch net-installer, I can
> still only
> see 3.2 G
John Hannfield wrote:
>
> I have a dual core Opteron 265 running in a Tyan K8WE (S2877)
> motherboard with
> 4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but using
> a fresh install of testing/unstable from the AMD64 etch net-installer, I
> can still only
> see 3.2 GB out of the
I have a dual core Opteron 265 running in a Tyan K8WE (S2877) motherboard with4 x 1GB RAM DDR modules. The BIOS displays the RAM as 4094 MB, but usinga fresh install of testing/unstable from the AMD64 etch net-installer, I can still only
see 3.2 GB out of the 4GB RAM...I am using the amd64-generic
41 matches
Mail list logo
