(Tiny)Core x86 : is there a reason not to enable PAE ?

[SeventhSin]

Hi SeventhSin
I wanted to boot Tinycore from a thumb drive on an HP Proliant ML150 G6 in 32 bit mode and still take advantage of the 6 Gig of
installed RAM. I started by installing Tinycore to the thumb drive. Next I fetched modules64.gz, rootfs.gz, and vmlinuz64:
http://tinycorelinux.net/10.x/x86/release/distribution_files/
and saved them where the 32 bit kernel and initrd are stored. Then create  core64.gz  like this:

Code: [Select]

cat rootfs.gz modules64.gz > core64.gz
I have grub on my thumb drive. My  menu.lst  looks like this:

Code: [Select]

default 1
timeout 10

title TC9_32bit
root (hd0,0)
kernel /tce/boot/vmlinuz quiet  waitusb=5:UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" tce=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" home=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" opt=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" printk.time=1 syslog enable_mtrr_cleanup
initrd /tce/boot/core.gz

title TC9_Core64
root (hd0,0)
kernel /tce/boot/vmlinuz64 quiet  waitusb=5:UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" tce=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" home=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" opt=UUID="1ad696eb-3913-4434-bb9e-25dd4b980c09" printk.time=1 syslog enable_mtrr_cleanup
initrd /tce/boot/core64.gzBoth  core  and  core64  share the same /home, /opt, and tce/optional directories as well as the same  onboot.lst  file:

Code: [Select]

firmware.tcz
aterm.tcz
fltk-1.3.tcz
flwm_topside.tcz
freetype.tcz
imlib2-bin.tcz
imlib2.tcz
libfontenc.tcz
libICE.tcz
libjpeg-turbo.tcz
libpng.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libxcb.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz
libXrender.tcz
libXt.tcz
libdrm.tcz
wbar.tcz
Xlibs.tcz
Xprogs.tcz
mc.tcz
pci-utils.tcz
curl.tcz
gzip.tcz
graphics-KERNEL.tcz
Xorg-7.7.tcz
alsa-config.tcz
alsa.tcz
alsamixergui.tcz
grabber.tcz
geany.tcz
wireshark.tcz
firefox-ESR.tcz
libavcodec.tcz
gnumeric.tcz
nfs-utils.tcz
pulseaudio.tcz
numlockx.tcz
gtk1.tcz
adwaita-icon-theme.tcz
util-linux.tcz
gparted.tcz
ntfsprogs.tcz
e2fsprogs.tcz
dosfstools.tcz
mtools.tcz
hfsprogs.tcz
tc-install-GUI.tcz
bind.tcz
usbutils.tcz
scsi-KERNEL.tcz
lsscsi.tcz
mdadm.tczYou'll note the 2 entries containing the word  KERNEL.  tce-load  will load the version (32 or 64 bit) that matches your running kernel.
My  tce/optional  directory contains both versions:

Code: [Select]

filesystems-4.14.10-tinycore.tcz
filesystems-4.14.10-tinycore64.tcz
graphics-4.14.10-tinycore.tcz
graphics-4.14.10-tinycore64.tcz
i2c-4.14.10-tinycore.tcz
i2c-4.14.10-tinycore64.tcz
mtd-4.14.10-tinycore.tcz
mtd-4.14.10-tinycore64.tcz
raid-dm-4.14.10-tinycore.tcz
raid-dm-4.14.10-tinycore64.tcz
scsi-4.14.10-tinycore.tcz
scsi-4.14.10-tinycore64.tcz
It's just a 32 bit install running  vmlinuz64  and 64 bit modules. That's all there is to it.

Hey Rich. Thanks for sharing your procedure. That should work very well for a custom install.

I can totally imagine the above on the Wiki. 

[SeventhSin]

@mods : please close this thread if you wish. From the creator's perspective (myself), its purpose (salient in the title) has been achieved. Other connected subjects such as the possibility of a Core64 ISO on the website are distinct topics, possibly subject(s) for future threads.

[Rich]

Hi SeventhSin

Hey Rich. Thanks for sharing your procedure. That should work very well for a custom install.

I can totally imagine the above on the Wiki. 

The Wiki content is contributed by forum members. You may log in to the Wiki using your forum credentials to add new content or
update/correct existing content if you wish.

@mods : please close this thread if you wish. From the creator's perspective (myself), its purpose (salient in the title) has been achieved. Other connected subjects such as the possibility of a Core64 ISO on the website are distinct topics, possibly subject(s) for future threads.

We typically leave all threads open. Someone may wish to comment, ask a question, or point out an error in the procedure I posted
at a later date.

[SeventhSin]

We typically leave all threads open. Someone may wish to comment, ask a question, or point out an error in the procedure I posted
at a later date.

That is perfectly alright.

[A Guy]

Not that it matters at this point but I thought that I would add that in the embedded market , having PAE disabled is handy for older CPUs still in use. Case in point, the AMD LX800 CPU will still be available until 2024.