On Mon, 5 Sep 2022, Andy Smith wrote:
Hello,
On Sun, Sep 04, 2022 at 01:54:16PM +0100, Tim Woodall wrote:
and remove pvshim=1
I think this was your issue. pvshim is PV-inside-PVH. So the
hypervisor that starts your guest kernel is in PV mode, which as
mentioned is not supported for 32-bit in
Hello,
On Sun, Sep 04, 2022 at 01:54:16PM +0100, Tim Woodall wrote:
> and remove pvshim=1
I think this was your issue. pvshim is PV-inside-PVH. So the
hypervisor that starts your guest kernel is in PV mode, which as
mentioned is not supported for 32-bit in newer Linux kernels.
Modern Linux kerne
On Sun, 4 Sep 2022, Andy Smith wrote:
Hello,
On Sun, Sep 04, 2022 at 11:07:35AM +0100, Tim Woodall wrote:
Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
but bookworm fails too)
The Linux kernel removed PV mode 32-bit Xen domU support at version
5.9. What type of
Hello,
On Sun, Sep 04, 2022 at 11:07:35AM +0100, Tim Woodall wrote:
> Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
> but bookworm fails too)
The Linux kernel removed PV mode 32-bit Xen domU support at version
5.9. What type of virtualisation are you using? (s
Hi,
Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
but bookworm fails too)
(XEN) d46v0 Unhandled page fault fault/trap [#14, ec=0010]
(XEN) Pagetable walk from 0100:
(XEN) L4[0x000] = 09790027 1f90
(XEN) L3[0x000] = 097a4027
lou wrote:
> Thanks, i've just installed linux-image-686, result is same
you understand that in most cases if you use a 32bit OS with 4GB of memory
you may not utilize 1GB, because the overhead of utilizing this memory
consumes much of this memory with the registers to overcome the 3GB
barrier.
S
On 10/16/21 10:32 AM, Stefan Monnier wrote:
Any particular reason why you must use pae rather than
the standard 32 bit kernel?
Hmm... isn't "the standard 32 bit kernel" `linux-image-686-pae` ?
At least the `linux-image-686` package seems to describe itself as for use
only on
> Any particular reason why you must use pae rather than
> the standard 32 bit kernel?
Hmm... isn't "the standard 32 bit kernel" `linux-image-686-pae` ?
At least the `linux-image-686` package seems to describe itself as for use
only on those machines where `linux-image-
> David.
>
Upgrade to Buster (following the release notes and hints given in this group)
then to Bullseye. Any particular reason why you must use pae rather than
the standard 32 bit kernel?
Checking, it looks as if the N280 is 32 bit only.
It's a nice, small thin client drawing low power but don't expect
superb performance at this class of hardware.
All the very best, as ever,
Andy Cater
On Fri 15 Oct 2021 at 07:48:06 (-0400), lou wrote:
> https://support.hp.com/us-en/product/hp-t5740e-thin-client/4282707/manuals
>
> from hp's QuickSpecs: Note: Minimum of 1GB and a maximum of 4GB* (2 X
> 2GB) can be supported (*Up to 1 GB may not be available with 32-bit
> operating systems due t
Thank Likonen and piorunz!
https://support.hp.com/us-en/product/hp-t5740e-thin-client/4282707/manuals
from hp's QuickSpecs: Note: Minimum of 1GB and a maximum of 4GB* (2 X
2GB) can be supported (*Up to 1 GB may not be available with 32-bit
operating systems due to system resource requirements.
I am wrong, but how I understand it is this:
Your computer can address 32 bits of memory,
2^32 bits = 4096MB, that's all you can install. PAE will not help.
Doesn't matter if CPU can run 64bit, your memory support is only up to
32bit. Some old computers have 36 or more bits for memory, that
* 2021-10-15 08:57:02+, Andy Smith wrote:
> If your CPU capable of running 64-bit then you could just install an
> amd64 kernel. What does
>
> cat /proc/cpuinfo
>
> say?
I suggest using command "lscpu". It gives clearer answer:
$ lscpu |head -n2
Architecture:x
0
siblings: 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx
Hello,
On Fri, Oct 15, 2021 at 04:27:10AM -0400, lou wrote:
> i have stretch, it use 3G memory, 1G memory can't be used
[…]
> i think pae kernel can use 4G memory
It can be a restriction of your motherboard. Has it ever seen more
than 3G in any operating system?
If your CPU capable
i have stretch, it use 3G memory, 1G memory can't be used
top: KiB Mem : 3038696 total, 2221904 free, 400628 used, 416164
buff/cache
uname: Linux debian 4.9.0-13-686-pae #1 SMP Debian 4.9.228-1
(2020-07-05) i686 GNU/Linux
i think pae kernel can use 4G memory
do i have to upgra
Reiner Buehl schreef op 2018-07-25 19:51:
Many thanks, Floris! With your expression I now see the other options:
bilbo:~# awk -F"'" '/menuentry/ {print $2}' /boot/grub/grub.cfg
Debian GNU/Linux
Advanced options for Debian GNU/Linux
Debian GNU/Linux, with Linux 4.
Hello,
On Wed, Jul 25, 2018 at 07:51:11PM +0200, Reiner Buehl wrote:
> bilbo:~# awk -F"'" '/menuentry/ {print $2}' /boot/grub/grub.cfg
>
> Debian GNU/Linux
>
> Advanced options for Debian GNU/Linux
[…]
> Debian GNU/Linux, with Linux 4.9.0-7-amd64
>
> Debian GNU/Linux, with Linux 4.9.0-7-amd64
Many thanks, Floris! With your expression I now see the other options:
bilbo:~# awk -F"'" '/menuentry/ {print $2}' /boot/grub/grub.cfg
Debian GNU/Linux
Advanced options for Debian GNU/Linux
Debian GNU/Linux, with Linux 4.9.0-7-686-pae
Debian GNU/Linux, with Linux
Reiner Bühl schreef op 2018-07-25 13:02:
I have installed both the 32-bit 686-pae and the 64-bit amd64 kernel
on my system. Grub Update recognizes all of them:
bilbo:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.9.0-7-686-pae
Found initrd image: /boot
I have installed both the 32-bit 686-pae and the 64-bit amd64 kernel
on my system. Grub Update recognizes all of them:
bilbo:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.9.0-7-686-pae
Found initrd image: /boot/initrd.img-4.9.0-7-686-pae
Found linux
On Mon, 12 Mar 2018, Neo wrote:
> No PAE.
>
> For 2GB of RAM it makes no sense. You just need this on 32bit machines with
> more than 4GB of RAM.
You need PAE to get the NX (non-execute) protection, and also KPTI (aka
Meltdown defense). Note that KPTI for i686 is a work in progr
Le 13/03/2018 à 04:57, Joe Pfeiffer a écrit :
Gene Heskett writes:
Both pae and hyperthreading take time, hyperthreading quite a bit more
than pae. With hyperthreading, to switch to the 2nd task, takes a
complete processor state stored on the stack, the stack pointer reloaded
to point at the
> I will agree that it increases the unpredictability of execution time,
> and if I wanted to guarantee I could meet deadlines I'd turn it off.
Turning it off may indeed improve predictability of execution time in
some cases. Especially if the various active threads have different
real-time prior
Gene Heskett writes:
> On Monday 12 March 2018 15:27:23 Hans wrote:
>
>> > Note that the non PAE kernel in older Debian versions up to Jessie
>> > lacked multi-processor (including multi-core and hyper-threading)
>> > support.
>>
>> Yes, I read t
On Monday 12 March 2018 15:27:23 Hans wrote:
> > Note that the non PAE kernel in older Debian versions up to Jessie
> > lacked multi-processor (including multi-core and hyper-threading)
> > support.
>
> Yes, I read this, too. The N280 is a single core, but mith
> hyper
Le 12/03/2018 à 20:27, Hans a écrit :
Note that the non PAE kernel in older Debian versions up to Jessie
lacked multi-processor (including multi-core and hyper-threading) support.
Yes, I read this, too. The N280 is a single core, but mith hyperthreading, I
have two cores.
Is this still so
but I have seen machines remapping 1
GiB or even 2 GiB, leaving only 2 or 3 GiB of usable RAM with a non
PAE kernel.
Note that the non PAE kernel in older Debian versions up to Jessie
lacked multi-processor (including multi-core and hyper-threading)
support.
Thx for the clarification.
the 4-GiB boundary due to the "PCI hole". Usually the remapped memory
amount is about 500 MB, but I have seen machines remapping 1 GiB or even
2 GiB, leaving only 2 or 3 GiB of usable RAM with a non PAE kernel.
Note that the non PAE kernel in older Debian versions up to Jessie
la
> Note that the non PAE kernel in older Debian versions up to Jessie
> lacked multi-processor (including multi-core and hyper-threading) support.
Yes, I read this, too. The N280 is a single core, but mith hyperthreading, I
have two cores.
Is this still so, that the non-pae-kernel lacks
Le 12/03/2018 à 12:31, Neo a écrit :
No PAE.
For 2GB of RAM it makes no sense.
Indeed.
You just need this on 32bit machines with more than 4GB of RAM.
No, you also need it on machines with 4 GiB of RAM and remapping
capability, in order to use the part of the RAM which is remapped beyond
No PAE.
For 2GB of RAM it makes no sense. You just need this on 32bit machines
with more than 4GB of RAM.
HTH
Tom
Am 12.03.2018 um 12:11 schrieb Hans:
Hi folks,
as I have still trouble with restore after suspend-to-disk, I read,
that this issue was gone with a kernel with non pae
Hi folks,
as I have still trouble with restore after suspend-to-disk, I read, that this
issue was gone
with a kernel with non pae.
This brings the following question:
MUST I use (or is it RECOMMENDED?) a kernel with PAE in my system?
My system:
CPU N280 (with PAE usable)
2 GB RAM
32-Bit
present.
So it looks like you're right. The NX feature can be used only when
running a 32-bit kernel in PAE mode on a 64-bit processor. When running
a 32-bit kernel in PAE mode on a 32-bit processor, the NX bit is not
available. So I'm back to my original question. For a system with a
3
On Mon, Aug 24, 2015 at 08:44:44PM -0400, Stephen Powell wrote:
> PAE may be a necessary condition for NX, but it is not a sufficient condition.
> I am presently using three 32-bit computers: one is a Pentium M (2G), one is
> a Pentium 4 (2G), and one is a Xeon (4G). All three are PA
On Mon, 2015-08-24 at 20:44 -0400, Stephen Powell wrote:
> On Mon, 24 Aug 2015 13:52:30 -0400 (EDT), Mirko Parthey wrote:
> > One such benefit is that the NX bit (non-executable memory pages)
> > is only available with 64 bit page table entries, which in turn depend on
> > PAE
On Mon, 24 Aug 2015 13:52:30 -0400 (EDT), Mirko Parthey wrote:
>
> On Mon, Aug 24, 2015 at 06:45:10AM -0400, Stephen Powell wrote:
>> Furtherfore, a non-PAE kernel is
>> useful even on PAE-capable hardware. The main purpose of PAE is to
>> address memory above 4G. But
On Mon, Aug 24, 2015 at 06:45:10AM -0400, Stephen Powell wrote:
> Furtherfore, a non-PAE kernel is
> useful even on PAE-capable hardware. The main purpose of PAE is to
> address memory above 4G. But if the machine has less than 4G of
> memory, what does a PAE-capable kernel buy you?
prompt, and debian boots just fine
Usually I only have to reload the module once, but occasionally I need
to do it two or three times.
At this point, I think that this is a kernel bug. This behavior never
happened in the 3.2.0-4-686-pae kernel in wheezy.
I am not sure whom to contact or what
On Wed, 2015-05-20 at 10:03 +0530, rajiv chavan wrote:
> Aufs support dropped in linux-image-4.0.0-1-686-pae? Or in all 4.0
> debian-kernels
> Any way to add module?
Hi,
It was dropped in 3.18 in favour of overlayfs:
https://lists.debian.org/debian-live/2014/12/msg00041.html
There doe
Aufs support dropped in linux-image-4.0.0-1-686-pae? Or in all 4.0
debian-kernels
Any way to add module?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debia
ogram is
going to use more than 3G. Therefore, say, in an 8G ram system no
single program can thrash the 8G system memory. It may cause other
programs pages to be remapped out but after having done so then the
large 3G program would usually stay mapped.
Of course if you were running two or more la
Bob Proulx a écrit :
> Sharon Kimble wrote:
>> This setup is currently running a "3.16.0-4-686-pae" kernel. Is it a
>> good idea to convert to a 64bit kernel, specifically
>> "3.16.0-4-amd64"?
>
> How much memory do you have in your system?
&g
If you are starting with a clean disk, do not use the installer's partitioning
scheme. Problematic at best.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2555858.G
Bob Proulx writes:
> Sharon Kimble wrote:
>> This setup is currently running a "3.16.0-4-686-pae" kernel. Is it a
>> good idea to convert to a 64bit kernel, specifically
>> "3.16.0-4-amd64"?
>
> How much memory do you have in your system?
4G act
Thank you I will use the 64 bit one. Thanks again.
Moe
On 02/28/2015 05:51 PM, Bob Proulx wrote:
Linux-Fan wrote:
Maureen L Thomas wrote:
My new toshiba is a 64 bit amd system. It has 6G of memory and 750G
hard drive. Is the 64 bit system better or should I install the 32
bit. I am using w
I did exactly that several years ago with no problem.
I installed an amd64 kernel at which point grub knew about both.
Changed default boot to the new kernel and ran for a while. Once all
was well I uninstalled the pae kernel.
I did it mostly because I expect that amd64 is the dominant kernel
Linux-Fan wrote:
> Maureen L Thomas wrote:
> > My new toshiba is a 64 bit amd system. It has 6G of memory and 750G
> > hard drive. Is the 64 bit system better or should I install the 32
> > bit. I am using weezy.
>
> I recommend you to install the 64 bit version so that a single process
> is ab
On 02/28/2015 11:25 PM, Maureen L Thomas wrote:
> My new toshiba is a 64 bit amd system. It has 6G of memory and 750G
> hard drive. Is the 64 bit system better or should I install the 32
> bit. I am using weezy.
> Moe
I recommend you to install the 64 bit version so that a single process
is abl
My new toshiba is a 64 bit amd system. It has 6G of memory and 750G
hard drive. Is the 64 bit system better or should I install the 32
bit. I am using weezy.
Moe
On 02/28/2015 05:05 PM, Bob Proulx wrote:
Sharon Kimble wrote:
This setup is currently running a "3.16.0-4-686-pae"
tup is currently running a "3.16.0-4-686-pae" kernel. Is it a
> good idea to convert to a 64bit kernel, specifically
> "3.16.0-4-amd64"? And if it is a good idea,
It is not.
> how do I do it? Is it as
> simple as downloading the "3.16.0-4-amd64" kernel, reboo
Sharon Kimble wrote:
> This setup is currently running a "3.16.0-4-686-pae" kernel. Is it a
> good idea to convert to a 64bit kernel, specifically
> "3.16.0-4-amd64"?
How much memory do you have in your system?
If the answer is 4G or less then there is no advantage.
Sorry, I meant that I installed this "jessie" setup on 10/02/15! Got
the year wrong! Ooops!
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.6, emacs 24.4.1.0
signature.asc
D
I installed this "jessie" setup on 10/02/14 from an old "wheezy"
net-install disc dated 28/05/13! I'm in the process of downloading a
jessie net-install for future installation.
This setup is currently running a "3.16.0-4-686-pae" kernel. Is it a
goo
On Wed, 6 Nov 2013 10:00:34 +0100 (CET), Pierre Frenkiel
wrote:
>What remains unexplained is that I had the 3.10-3-686-pae kernel
>on my old install, and I never enabled multiarch (At that time, I even
> ignored
>this possibility).Is there an other explanation th
Pierre Frenkiel:
> On Fri, 25 Oct 2013, Jochen Spieker wrote:
>
> What remains unexplained is that I had the 3.10-3-686-pae kernel
> on my old install, and I never enabled multiarch (At that time, I even ignored
> this possibility).Is there an other explanation than Alzheimer?
On Fri, 25 Oct 2013, Jochen Spieker wrote:
You do not need PAE with an AMD64 installation and your 64 Bit system
will not boot using a 32 Bit kernel. If you really, really want to have
a 686-PAE kernel then you need to enable multiarch.
hi Jochan,
thanks for your comments. I wanted to
Pierre Frenkiel:
>
> I had on my laptop the kernel 3.10-3-686-pae. After re-installing wheezy,
> all pae kernels became invisible, i.e I only get, with
>aptitude search linux-image.
>
> p linux-image-2.6-amd64 p linux-image-3.10-0.bpo.2-amd64 p
> linux-image-3.1
Pierre Frenkiel wrote:
> I had on my laptop the kernel 3.10-3-686-pae. After re-installing wheezy,
> all pae kernels became invisible, i.e I only get, with
>aptitude search linux-image.
> p linux-image-2.6-amd64 p linux-image-3.10-0.bpo.2-amd64 p
> ...
You appear to hav
hi,
I had on my laptop the kernel 3.10-3-686-pae. After re-installing wheezy,
all pae kernels became invisible, i.e I only get, with
aptitude search linux-image.
p linux-image-2.6-amd64
p linux-image-3.10-0.bpo.2-amd64
p linux-image-3.10-0.bpo.2-amd64-dbg
p linux-image-3.10-0.bpo.2
tely, Debian does not offer a 686 non-PAE kernel in wheezy as
> a stock kernel image package, as it did for squeeze.
I think I read that the rationale for this is that optimizations for 686
on a non PAE capable CPU are likely to provide very limited improvements.
--
To UNSUBS
Ok, many thanks.
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/91B5CF2767ED4DACB45AE7598E5EBD5B@rx
On Mon, 26 Aug 2013 05:32:36 -0400 (EDT), antispammbox-debian wrote:
>
> Kernel 486 is very old 1999?, for my laptop, :-), I would like to install
> a kernel 686, as with Squeeze.
Unfortunately, Debian does not offer a 686 non-PAE kernel in wheezy as
a stock kernel image package,
Can create an initrd to install Wheezy, that not control if the CPU is
with PAE option?
May I ask why ?
Why my laptop cpu do not support PAE.
Then the installer should propose to install only the non-PAE (i.e.
-486) kernel, so what is the problem ?
Kernel 486 is very old 1999?, for
Antispammbox-debian a écrit :
>
> Antispammbox-debian a écrit :
>> Can create an initrd to install Wheezy, that not control if the CPU is
>> with PAE option?
>
>> May I ask why ?
>
> Why my laptop cpu do not support PAE.
Then the installer should propose
Hello,
Antispammbox-debian a écrit :
Can create an initrd to install Wheezy, that not control if the CPU is
with
PAE option?
May I ask why ?
Why my laptop cpu do not support PAE.
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Hello,
Antispammbox-debian a écrit :
>
> Can create an initrd to install Wheezy, that not control if the CPU is with
> PAE option?
May I ask why ?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
Hi all
Can create an initrd to install Wheezy, that not control if the CPU is with
PAE option?
Thanks
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arc
Rob McMurray wrote:
> I want to run ownCloud on a small server using a mini-itx
> motherboard. Unfortunately the CPU, a 1GHz VIA C3 Eden Nehemiah,
> doesn't support pae so I haven't yet found anything current that
> supports it. CentOS 5.9 works but not the latest 6.x ver
Andrei POPESCU gmail.com> writes:
>
> On Ma, 26 feb 13, 09:03:55, Tixy wrote:
> >
> > Unfortunately, the top hits for me when searching for "pentium m pae" in
> > Google is Wikipedia, which is at best misleading if not wrong.
>
> It's a wiki
On Ma, 26 feb 13, 09:03:55, Tixy wrote:
>
> Unfortunately, the top hits for me when searching for "pentium m pae" in
> Google is Wikipedia, which is at best misleading if not wrong.
It's a wiki :p
(SCNR)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianU
On Mon, 2013-02-25 at 22:26 -0600, Stan Hoeppner wrote:
> On 2/24/2013 7:41 AM, Tixy wrote:
>
> > Actually, I just double checked, and my CPU [1] does have PAE after all.
>
> PAE is in every AMD/Intel chip manufactured post 1998. You'd have to be
> using a Pentium MM
On 2/24/2013 7:41 AM, Tixy wrote:
> Actually, I just double checked, and my CPU [1] does have PAE after all.
PAE is in every AMD/Intel chip manufactured post 1998. You'd have to be
using a Pentium MMX, AMD K6-2, or older chip, to lack PAE support.
The general rule here: if the chip
On Sun, 24 Feb 2013, Tixy wrote:
> Actually, I just double checked, and my CPU [1] does have PAE after all.
> I was confused because it only has 32-bit physical address size (and so
> doesn't benefit from any 'Extension' to the physical address).
The Pentium-M does indeed
; >
> > This system (Dell D505) has a Pentium M processor. My understanding is
> > that the Pentium M's are just about the only modern(ish) processor
> > without pae, and thus kernels with pae compiled in can't run on it. (pae
> > doesn't show up in th
On Sat, 2013-02-23 at 19:15 +, Dom wrote:
> I think the pae bit will only be used by CPUs that support it, otherwise
> it will be ignored and run normally. Only some "really old" CPUs (like
> some others I do run) won't be supported.
>
> My laptop shows:
&g
y understanding is
> that the Pentium M's are just about the only modern(ish) processor
> without pae, and thus kernels with pae compiled in can't run on it. (pae
> doesn't show up in the cpu flags)
>
> During the upgrade I did get warnings about it not supporting pa
As previously posted, I am definitely running a PAE kernel on a system which
does not benefit from it. Boots no problem.
The CPU probably does support it. The BIOS, however, does not.
On 02/23/2013 02:15 PM, Dom wrote:
> On 23/02/13 18:36, deb...@paulscrap.com wrote:
>
> I think the pae bit will only be used by CPUs that support it, otherwise
> it will be ignored and run normally. Only some "really old" CPUs (like
> some others I do run) won't
s are just about the only modern(ish) processor
without pae, and thus kernels with pae compiled in can't run on it. (pae
doesn't show up in the cpu flags)
During the upgrade I did get warnings about it not supporting pae, so I
did make sure to install the 486 image, but forgot to
thout pae, and thus kernels with pae compiled in can't run on it. (pae
doesn't show up in the cpu flags)
During the upgrade I did get warnings about it not supporting pae, so I
did make sure to install the 486 image, but forgot to remove the 686-pae
(removed 686, though). That&#
David Baron wrote:
> Here 'tis:
> [0.00] BIOS-e820: - 0009f400 (usable)
> [0.00] BIOS-e820: 0009f400 - 000a (reserved)
> [0.00] BIOS-e820: 000f - 0010 (reserved)
> [0.00] BIOS-e820: 00
On Thursday 17 January 2013 17:48:24 debian-user-digest-
requ...@lists.debian.org wrote:
> >> This is apparently not at all a rare problem. I put 4gig in my
> >> computer but it only recognizes 3gig.
> >
> > Please post the output of
> >
> > dmesg | grep BIOS-e820
> >
> > This will show the memor
Sven Hartge wrote:
> David Baron wrote:
>> This is apparently not at all a rare problem. I put 4gig in my
>> computer but it only recognizes 3gig.
> Please post the output of
> dmesg | grep BIOS-e820
> This will show the memory map provided by the BIOS.
I forgot to provide an example. Here
cases beyond the 4GiB limit. If and only if this is possible, you are
able to use PAE to access this memory region.
Many older boards lack this function inside the BIOS or are even unable
because of hardware constraints, either by design or by choice of the
manufacturer.
Grüße,
Sven.
--
This is apparently not at all a rare problem. I put 4gig in my computer but it
only recognizes 3gig.
Is there any way for the kernel to bypass/override BIOS and see all the
memory?
I have a strange MB (it has ISA!!) so finding and flashing a new BIOS may not
be possible or desirable. ALL the d
On Fri 06 Jul 2012 at 03:23:33 -0700, John Magolske wrote:
> I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
> to boot with it. As transcribed from my phone-camera "screenshot"
> (there are 10 more lines of output I can transcribe if that'd help):
>
Hi,
I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
to boot with it. As transcribed from my phone-camera "screenshot"
(there are 10 more lines of output I can transcribe if that'd help):
[ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root
fault behaviour, I guess.
It would be nice though, that Squeeze installer could detect the CPU
capabilities and gives the user the possibility to install all the
available kernels for the 32-bits flavour: "-486" (non PAE, non-SMP),
"-686" (SMP, non-PAE) and "-big
On Saturday 14 April 2012 12:20:18 pm Camaleón wrote:
> On Fri, 13 Apr 2012 18:34:03 -0430, German Eduardo Jaber De Lima wrote:
> > What was the first stable Debian release that enabled PAE support
> > (bigmem kernel option)?
>
> The first?
>
> If we take we time-m
On Fri, 13 Apr 2012 18:34:03 -0430, German Eduardo Jaber De Lima wrote:
> What was the first stable Debian release that enabled PAE support
> (bigmem kernel option)?
The first?
If we take we time-machine and according to the snapshot archive¹, there
was a "-bigmem" kernel sin
On Vi, 13 apr 12, 18:34:03, German Eduardo Jaber De Lima wrote:
> What was the first stable Debian release that enabled PAE support (bigmem
> kernel option)? Is it enabled by default in Debian6?
Squeeze (6.0) has a -bigmem kernel flavour, so it is available, but not
default.
I don't
What was the first stable Debian release that enabled PAE support (bigmem
kernel option)? Is it enabled by default in Debian6?
On 06/03/12 05:06 PM, Jari Fredriksson wrote:
6.3.2012 23:28, Weaver kirjoitti:
The 3.0 series PAE kernels won't run on this machine...
Yes they do.
I'm currently running 686 PAE 3.2.7-1 on a Pentium 4, 2.8 GHz machine -
this one - on a separate install.
Qualifying remark - n
McCormick wrote:
The latest upgrade to Sid has apparently borked creation of
initrd.img.
This is what was upgraded:
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.38-2-686
Why are you running such an old kernel?
The 3.0 series PAE kernels
6.3.2012 23:28, Weaver kirjoitti:
>>>>> The 3.0 series PAE kernels won't run on this machine...
>
> Yes they do.
> I'm currently running 686 PAE 3.2.7-1 on a Pentium 4, 2.8 GHz machine -
> this one - on a separate install.
> Qualifying remark - no gu
>>>>>
>>>>>> Processing triggers for initramfs-tools ...
>>>>>> update-initramfs: Generating /boot/initrd.img-2.6.38-2-686
>>>>>
>>>>>
>>>>> Why are you running such an old kernel?
>>>>
>
has apparently borked creation of initrd.img.
This is what was upgraded:
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.38-2-686
Why are you running such an old kernel?
The 3.0 series PAE kernels won't run on this machine...
B
On Sat, 20 Aug 2011 12:42:52 -0500, Stan Hoeppner wrote:
> On 8/20/2011 4:36 AM, Camaleón wrote:
>> PAE kernel is not only convenient for more than 4 GiB of ram but is
>> also enables SMP (multi-processing) and NX bit (a security measure). In
>> brief, just keep it as is :-)
On 8/20/2011 4:36 AM, Camaleón wrote:
> PAE kernel is not only convenient for more than 4 GiB of ram but
> is also enables SMP (multi-processing) and NX bit (a security measure).
> In brief, just keep it as is :-)
To clarify, the *Debian* PAE kernel package in question was built w
1 - 100 of 166 matches
Mail list logo
