While I'm no expert on PAE, I believe PAE support is controlled by
this kernel config option:
chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
Modify that to "#CONFIG_X86_PAE is not set" and run the normal tools
inside a chroot to build an x86-generic image/package/etc. See below
for some suggestions.
This really begs the question of why though....Mandeep Baines
explained that PAE has been available since Pentium Pro. Hugh Dickens
pointed out that disabling PAE also disables "NX" (no execute) support
- ie code pushed on the stack could be executed. This is a security
feature. Just FYI - not trying to stop you from making use of
older/less capable HW.
Some detailed steps to do what I'm suggesting (NOT TESTED):
cd /usr/local/src/chromiumos/x86-generic/src/scripts/
./enter_chroot.sh
./cros_workon start chromeos-base/kernel # create local copy of
kernel source
cd ../third_party/kernel/files
fgrep -R PAE chromeos/config/
chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
vi chromeos/config/i386/config.common.i386 # modify X86_PAE config option
# rebuild everything - there are ways to rebuild just the
kernel...msb promised he'd add a FAQ entry to do that :)
cd ../../../scripts
B="x86-generic"
./build_packages --board=$B --oldchromebinary && ./build_image
--board=$B --noenable_rootfs_verification && ./mod_image_for_test.sh
--board=$B -y && ./image_to_usb.sh --board=$B --to=/dev/sdc -y
hth,
grant
On Thu, Dec 9, 2010 at 4:29 AM, Alexei Humeniy <ahum...@gmail.com> wrote:While I'm no expert on PAE, I believe PAE support is controlled by
> Is there a way to build Chromium OS for processors without PAE? How?
this kernel config option:
chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
Modify that to "#CONFIG_X86_PAE is not set" and run the normal tools
inside a chroot to build an x86-generic image/package/etc. See below
for some suggestions.
I'm not sure we should support non-PAE processors. Without PAE we don't get
NX. We are hoping to rely more and more on NX for security so PAE would
become a minimum requirement. Other than the first generation Pentium M
(Banias) and some second generation Pentium M (Dothan), I don't believe
Intel has released any x86 CPUs without PAE after the 2000.
But nothing should break if we don't have PAE. You'll just have a less
secure system which I wouldn't recommend but it'll work.
Might be reasonable to add something to the ebuild to disable PAE via
a USE flag. I think such a patch might be acceptable.
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
But I though cloud computing was all about no third-party applications
running against the machine CPU -excep the browser- so my computer in
theory shouldn't even need to be "secure".
Chromium OS Developers mailing list: chromiu...@chromium.org
Try removing the march and mcpu lines from:
/usr/local/portage/chromiumos//chromeos/config/make.conf.x86-target
@Mandeep: There wasn't a MARCH or MCPU line in that file, but there
was a MARCH_TUNE line and I blanked out the string and rebuilt.
Unfortunately, I'm still getting the same Kernel Panic as I was
getting before.
Chromium OS Developers mailing list: chromiu...@chromium.org
Well, I removed the "-march=atom -mtune=atom" part of MARCH_TUNE then
just re-ran the build_package and build_image. I don't think I want
to re-build everything from source otherwise the changes I made to
remove PAE won't be there. Did I need to re-setup_board first to make
the changes have effect?
Chromium OS Developers mailing list: chromiu...@chromium.org
Can you open a bug and paste a photo of the panic.
> > > > > > > On Dec 9, 11:12�am, Grant Grundler <grund...@chromium.org>
> > > wrote:
> > > > > > > > On Thu, Dec 9, 2010 at 4:29 AM, Alexei Humeniy <
> > > ahume...@gmail.com>
> > > > > wrote:
> > > > > > > > > Is there a way to build Chromium OS for processors without PAE?
> > > > > How?
> >
> > > > > > > > While I'm no expert on PAE, I believe PAE support is controlled
> > > by
> > > > > > > > this kernel config option:
> > > > > > > > � � chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
> >
> > > > > > > > Modify that to "#CONFIG_X86_PAE is not set" and run the normal
> > > tools
> > > > > > > > inside a chroot to build an x86-generic image/package/etc. See
> > > below
> > > > > > > > for some suggestions.
> >
> > > > > > > > This really begs the question of why though....Mandeep Baines
> > > > > > > > explained that PAE has been available since Pentium Pro. Hugh
> > > Dickens
> > > > > > > > pointed out that disabling PAE also disables "NX" (no execute)
> > > > > support
> > > > > > > > - ie code pushed on the stack could be executed. This is a
> > > security
> > > > > > > > feature. Just FYI - not trying to stop you from making use of
> > > > > > > > older/less capable HW.
> >
> > > > > > > > Some detailed steps to do what I'm suggesting (NOT TESTED):
> > > > > > > > � � cd /usr/local/src/chromiumos/x86-generic/src/scripts/
> > > > > > > > � � ./enter_chroot.sh
> > > > > > > > � � ./cros_workon start chromeos-base/kernel � �# create
> > > > > local copy of
> > > > > > > > kernel source
> > > > > > > > � � cd ../third_party/kernel/files
> > > > > > > > � � fgrep -R PAE chromeos/config/
> > > > > > > > � � chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
> > > > > > > > � � vi chromeos/config/i386/config.common.i386 � �#
> > > modify
> > > > > X86_PAE config option
> >
> > > > > > > > � �# rebuild everything - there are ways to rebuild just the
> > > > > > > > kernel...msb promised he'd add a FAQ entry to do that :)
> > > > > > > > � � cd ../../../scripts
> > > > > > > > � � �B="x86-generic"
> > > > > > > > � � ./build_packages --board=$B --oldchromebinary &&
> > > > > ./build_image
> > > > > > > > --board=$B --noenable_rootfs_verification &&
> > > ./mod_image_for_test.sh
> > > > > > > > --board=$B -y && ./image_to_usb.sh --board=$B --to=/dev/sdc -y
> >
> > > > > > > > hth,
> > > > > > > > grant
> >
> > > > > > > --
> > > > > > > Chromium OS Developers mailing list: chromium-os-...@chromium.org
> > > > > > > View archives, change email options, or unsubscribe:
> > > > > > >http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
> >
> > > > > --
> > > > > Chromium OS Developers mailing list: chromium-os-...@chromium.org
> > > > > View archives, change email options, or unsubscribe:
> > > > >http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
> >
> > > --
> > > Chromium OS Developers mailing list: chromium-os-...@chromium.org
> > > View archives, change email options, or unsubscribe:
> > >http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
that is a diff issue from what you are describing
-mike
--
Alexei Humeniy (ahum...@gmail.com) wrote:
> Any news about that re-split?
>
I'm not sure we should support non-PAE processors. Without PAE we don't get
NX. We are hoping to rely more and more on NX for security so PAE would
become a minimum requirement. Other than the first generation Pentium M
(Banias) and some second generation Pentium M (Dothan), I don't believe
Intel has released any x86 CPUs without PAE after the 2000.
But nothing should break if we don't have PAE. You'll just have a less
secure system which I wouldn't recommend but it'll work.
Might be reasonable to add something to the ebuild to disable PAE via
a USE flag. I think such a patch might be acceptable.
> ~Alexei
>
> On Dec 9, 2:40�pm, Olof Johansson <ol...@chromium.org> wrote:
> > On Thu, Dec 9, 2010 at 9:12 AM, Grant Grundler <grund...@chromium.org>wrote:
> >
> > > On Thu, Dec 9, 2010 at 4:29 AM, Alexei Humeniy <ahume...@gmail.com> wrote:
> > > > Is there a way to build Chromium OS for processors without PAE? How?
> >
> > > While I'm no expert on PAE, I believe PAE support is controlled by
> > > this kernel config option:
> > > � �chromeos/config/i386/config.common.i386:CONFIG_X86_PAE=y
1. Operation with Pentium M / Celeron M CPU
I also make it work on PC with Pentium M or Celeron M installed in CPU. There is also a track record of running on a CPU that is not compatible with PAE. For now it is running on each of the following Pentium M / Celeron M models.
However, the performance is as it is. Particularly, since CF - W2 has less memory, it can not be said that response is good. Also, originally Chromium OS does not support enough support for older devices (rather it is truncating more and more). For models not listed here, there is a high possibility that they will not move. I do not expect much, I think if you can try it with a light feeling like money if you move.