(old)Puppy Linux Discussion Forum

The only non-pae version puppy I could find was tahrpup 6.0.5, looking for something latest with non-pae kernel?

There is slacko5.7-woofCE currently being tested that will work with non-pae (I have tested with atom n270 a 32-bit non-pae). Newer kernel to help with meltdown/spectre (k3.18.113). There is also the original slacko5.7 for all cpu's, and AtomicPup-18 for atom cpu's.

Its a start
8Geee

I have some non-pae kernels that are very recent and some pae that allow the forcepae boot option.

Xenial 7.5 will boot on nonpae machines by adding the forcepae boot option in the grub4dos menu.
the UUID is the USB stick I am using in this case....another version :

Xenial 7.06 loads OOTB in my ancient (2001) P4, 1.5 GB RAM, Dell desktop without needing any special boot commands.

It does take a tad longer than Tahr to initially load programs, but no noticeable lack of response in operating them once they're loaded.

Hi jss83,

We only know what you tell us. [Don't expect us to look for your prior posts, if any, in order to find out]. 8Geee, rockedge and a_salty_dog have provided good general advice. But to receive the best specific advice for your computer, we'd have to know the CPU it uses. Or baring that What Computer? --brand and model. [Knowing that, we can easily find its specs].

Rockedge has mentioned including the boot argument "forcepae". Using that argument, I have a Thinkpad T42, manufactured in 2003 which happily boots Sailor Enceladus' Slacko 5.7.1 and my updated Tahrpup 6.0.6. Both are only a couple months old. The T42's CPU is a Pentium M.

mikesLr

mikeslr wrote:Hi jss83,

We only know what you tell us. [Don't expect us to look for your prior posts, if any, in order to find out]. 8Geee, rockedge and a_salty_dog have provided good general advice. But to receive the best specific advice for your computer, we'd have to know the CPU it uses. Or baring that What Computer? --brand and model. [Knowing that, we can easily find its specs].

Rockedge has mentioned including the boot argument "forcepae". Using that argument, I have a Thinkpad T42, manufactured in 2003 which happily boots Sailor Enceladus' Slacko 5.7.1 and my updated Tahrpup 6.0.6. Both are only a couple months old. The T42's CPU is a Pentium M.

mikesLr

It's a P4 cpu with only 1 gb ram, I can install pae version on it but as salty dog mentioned, everything works slow.

I'll try 8Gee and rockedge's advice.

Thanks

mikeslr wrote: I have a Thinkpad T42, manufactured in 2003 which happily boots Sailor Enceladus' Slacko 5.7.1 and my updated Tahrpup 6.0.6. Both are only a couple months old. The T42's CPU is a Pentium M.

this is exactly the same machine I am using the forcepae on Xenialpup 7.5 and it runs better than expected.

I have some non-pae kernels that are very recent

Kindly provide those kernels please. The problem is somewhat solved, I installed xenial 7.5 and changed the kernel to nopae one that i found and the performance is somewhat improved.

Kindly provide those kernels please.

I am compiling a kernel 4.17 nopae (i686) right now....as soon as it is done I will upload it to a server for download access..... as well as some others. Name me a kernel you would like for Xenial nopae and perhaps I could compile one and upload it for access.

I currently changed it with this one http://distro.ibiblio.org/puppylinux/hu ... AE.tar.bz2 mainly because it has the wifi drivers needed for the dongle that I use, but it is old, I could use a newer/lighter one that has the the similar drivers in it and 32 bit nopae.

I installed xenial 7.5 and changed the kernel to nopae one that i found

The kernel that comes in Xenialpup 7.5 (32bit version) is already no-pae.

From release notes for Xenialpup 7.5:

Features include:

Kernel 4.4.95 noPAE

I have used it and never had to add anything to menu entry. PAE is definitely not being used.

Xenialpup64 7.5 (64 bit) is a completely different kernel and it does not need PAE to see more than 4GB of memory.
64 bit does not use PAE.

Here is a download link for a kernel 4.17 noPAE. try it out and let me know if it works and has your wifi drivers.
it is labeled upupbb I have run it with Xenialpup and tahr 6.0.6

https://drive.google.com/open?id=1cuJHB ... mPN2ZkeX-3

md5:
080195a8ec5db2b5a135ce4883251e78 huge-4.17.0-upupbb.tar.bz2

bigpup wrote:

I installed xenial 7.5 and changed the kernel to nopae one that i found

The kernel that comes in Xenialpup 7.5 (32bit version) is already no-pae.

But it does not have the drivers that I need for my wifi.

@rockedge, I'll let you know how it goes, thanks

Edit: It works perfectly, connected right away! Thanks so much!

Well, you got it working by using a different kernel.

For others trying to get WIFI working in the original Xenialpup 7.5 kernel.

You do not say what WIFI hardware you have.

There is a driver fix for Xenialpup 7.5 if you have an Atheros WIFI device.

There was some WIFI drivers left out of Xenialpup 7.5
They were for the Atheros hardware.
This pet package will install them.
http://distro.ibiblio.org/puppylinux/pu ... nial32.pet

Okay, I am having some trouble with the drivers, the wifi stopped working after the 2nd boot, I will roll it back and try the pet provided bigpup and report back how it goes.

If nothing works, I think I should just stick to huge-4.9.13-xenial_noPAE as it solves all the problem.

it worked then after a reboot the WiFi stopped working? what changed in between?

Never mind that, it's a bad device, not getting recognized now in previous kernel or windows machine.

ahhhhh....recently happened to me also...I kept trying to fix the software and it was the wifi card the whole time.....

jss83 wrote:Never mind that, it's a bad device, not getting recognized now in previous kernel or windows machine.

Occasionally the wifi card on my HP Elitebook gets 'lost' no matter what distribution I try to boot. First time it happened I thought it was damaged wifi, but turned out to be some software had somehow changed BIOS settings in some as yet undiscovered way. I don't even know what BIOS change occurred since everything looked the same... Anyway, whenever that happens on my machine a fix is to go into BIOS and reset to 'defaults' - no idea why that works, as I say, and can't say if that would work on any other machine, but worth a try... Certainly, I would have considered my machine a wireless 'brick' had I not stumbled upon that 'wifi reset' procedure. Doing all sorts of rfkill command, on the other hand, did not fix anything...

wiak

not that important but I got a 2005 IBM ThinkPad T-42 with these specs and no hard drive to run Bionic 18.05+8 and a kernel 4.17 from a cheap 4 gig Flash drive ...... and is actually running well