Michelle Konzack wrote:
Am 2006-10-02 17:29:46, schrieb Johannes Wiedersich:
By the way, 'unstable woody' doesn't exist anymore. woody became stable
years ago and now is obsolete.
Not realy right. - Currently it is ONLY Old-Stable. ;-)
Obsolete it would be if Etch is released as Stable.
Am 2006-10-02 17:29:46, schrieb Johannes Wiedersich:
> By the way, 'unstable woody' doesn't exist anymore. woody became stable
> years ago and now is obsolete.
Not realy right. - Currently it is ONLY Old-Stable. ;-)
Obsolete it would be if Etch is released as Stable.
Thanks, Greetings and ni
fraz wrote:
Don't wanna get flamed, but am running unstable 2.4.27 woody right now
and don't want to reinstall if I don't need to. Just want to get this
memory recognized.
[...]
Thanks, you are correct. Guess I'll make the move to a new kernel
image.
Why don't you just 'aptitude update' a
Ron,
Thanks, you are correct. Guess I'll make the move to a new kernel
image.
Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/28/06 09:39, fraz wrote:
> > Just switched a processor on a system, went fine, but added an
> > additional gig of ram and debian doesn't see
fraz wrote:
Just switched a processor on a system, went fine, but added an
additional gig of ram and debian doesn't seem to see it.
It shows up in the BIOS. Googled a bit and added "mem=2048M" to the
kernal
line in /boot/grub/grub.conf. Didn't work. Still just shows a gig (the
original memory).
On Thu, Sep 28, 2006 at 07:39:48AM -0700, fraz wrote:
> Just switched a processor on a system, went fine, but added an
> additional gig of ram and debian doesn't seem to see it.
>
> It shows up in the BIOS. Googled a bit and added "mem=2048M" to the
> kernal
> line in /boot/grub/grub.conf. Didn't
On Thu, Sep 28, 2006 at 05:53:48PM +0200, Florian Kulzer wrote:
>
> I am not sure about the amd64 kernels in Etch; you can run
>
> grep HIGHMEM /boot/config-$(uname -r)
>
> to see if your kernel has been compiled with HIGHMEM support.
>
Which does no good on a 64 bit kernel. HIGHMEM support on
On Thursday 28 September 2006 12:53, Florian Kulzer wrote:
> On Thu, Sep 28, 2006 at 17:54:03 +0200, Andreas Rönnquist wrote:
> > Ron Johnson wrote:
> > >Your kernel probably is not configured to recognize more than 1GB.
> > >
> > >- --
> >
> > (Somewhat on topic anyway) - I've just ordered an upgr
On Thu, Sep 28, 2006 at 17:54:03 +0200, Andreas Rönnquist wrote:
> Ron Johnson wrote:
> >
> >Your kernel probably is not configured to recognize more than 1GB.
> >
> >- --
>
> (Somewhat on topic anyway) - I've just ordered an upgrade for my box - 1
> Gb of RAM included and an amd64 processor - wi
Ron Johnson wrote:
Your kernel probably is not configured to recognize more than 1GB.
- --
(Somewhat on topic anyway) - I've just ordered an upgrade for my box - 1
Gb of RAM included and an amd64 processor - will I need to recompile the
kernel to get support for all RAM? The debian version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/06 09:39, fraz wrote:
> Just switched a processor on a system, went fine, but added an
> additional gig of ram and debian doesn't seem to see it.
>
> It shows up in the BIOS. Googled a bit and added "mem=2048M" to the
> kernal
> line in /boot
11 matches
Mail list logo