no i386 kernels but switch to force i386 install if on 64 bit host exists

[darylkuchay]

Saw and implemented the switch for a i386 kernel within this script but watched a i686-pae kernel get downloaded. While this fits the description of a non 64 bit kernel it is not really i386 compatible. Tried to manually enter the debian i586 kernel:

linux-image-586_4.9+80+deb9u2_i386.deb

but script errors and fails. linux-image-586 also causes script to fail. My project requires a 586 kernel and I wanted to use debian dog for the base. Is there a recommended way to substitute a 586 compatible kernel in to this script?

Or, since I am basically trying to build a 586 compatible of Trinity Dog, is there a way to swap kernels in that image? Trinity Dog is only pae based in current links....

Either way there is no way to build a i386 compatible version with this script as the only kernel linked in this is the i686-pae kernel. Please update and preferably in a way that can support other kernels.

[fredx181]

That would be very complicated, to make choice for pae or non-pae.
Mostly because aufs should be supported (and is not included by default in Debian kernel)
Does it work for you booting with the pae kernel and add to kernel boot commanline?:

forcepae   

Fred

[darylkuchay]

No, I get message that kernel is not correct for hardware. I understand that recompiling a new non pae kernel not in direct goals as current project works for most. I am using tablet from webdt.org and trying to update a newer build but this is strictly a 586 cpu with no pae. I can offer to build kernel in non pae form. I think this would open audience to old puppy users too that have older hardware. Please let me know if you have any guides on how to build kernel for this project. If non pae kernel was in the custom repository script would work for me, no? In past I have done the same with Porteus with recompiling a custom kernel aimed towards the ancient geode hardware that this tablet has. Daryl

…

On Thu, Nov 16, 2017 at 7:22 AM, fredx181 ***@***.***> wrote: That would be very complicated, to make choice for pae or non-pae. Mostly because aufs should be supported (and is not included by default in Debian kernel) Does it work for you booting with the pae kernel and add to kernel boot commanline?: forcepae Fred — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AExnBpl-d2CoNFXWtzX9oL9qVwd_7Vowks5s3CkIgaJpZM4Qf2UV> .

[fredx181]

Before considering building kernel or modifying mklive-stretch script, maybe the best (and easiest) is that I make a .tar.gz including:

• .squashfs module from Debian non-pae kernel 4.9 (with aufs included)
• initrd1.xz (non-pae)
• initrd.img (non-pae)
• vmlinuz1 (non-pae)
  Would that work for you? (by adding (and replacing) those in frugal install 'live' folder)

EDIT: From one thing came the other, made a .tar.gz including above
(this can be used for TrinityDog-Stretch or Stretchdog)
https://debiandog.github.io/MakeLive/kernel-nopae/kernel-4.9.0-4-686-nopae.tar.gz
and modified mklive-stretch script to have choice for pae or no-pae, see more info and download here:
http://murga-linux.com/puppy/viewtopic.php?p=974507#974507

Fred