withdrawn
5.4.170 64bit kernel withdrawn
Moderator: Forum moderators
Re: 5.4.170 64bit kernel
I have not messed with kernels before now . I;d like to learn with this.
I am running xenialpup64-7.5 atm. Can you list the steps I need to take to change kernels to yours please. I guess there will be others that will want to follow along and change too so your time will not be wasted .
The Australian State Governments have all enacted laws to steal your assets on your death. All legal paperwork is binned and all assets seized on one disgruntled child's complaint.Move them well before you die or go into a home.
-
- Posts: 1569
- Joined: Sun Jul 12, 2020 2:38 am
- Location: S.E. Australia
- Has thanked: 241 times
- Been thanked: 704 times
Re: 5.4.170 64bit kernel
@April - The first post includes:
"Once downloaded, expand in an empty folder with tar -jxvf, & rename kernel-modules.sfs-5.4.170-64oz to zdrv ... (same as one to be replaced) & rename vmlinuz-5.4.170-64oz to vmlinuz & then substitute for originals."
For Xenialpup64, you will need the Ubuntu derivative kernel.
Hence you would download huge-5.4.170-ubun64oz.tar.bz2 , copy it to an empty folder, cd /(that folder)
then run tar -jxvf huge-5.4.170-ubun64oz.tar.bz2
When done, rename kernel-modules.sfs-5.4.170-64oz to zdrv_xenialpup64_7.5.sfs
and rename vmlinuz-5.4.170-64oz to vmlinuz . Then copy the 2 new files over the originals, as below:
If you are running a frugal, without a save file/folder, mount the drive containing all the boot .sfs
files (adrv, fdrv, puppy, zdrv etc - possibly in a subfolder) and copy new file(s) over original one(s).
If you have a save file/folder, all the .sfs boot files will be in /mnt/home (possibly under a subfolder).
If you have a boot partition, mount it & copy vmlinuz over original there (possibly under a subfolder).
Unmount & upon reboot, new kernel will be running. (uname -r in a terminal will confirm this).
If you have a save file/folder & added any new drivers after original install, as these are kernel-specific
you will need to remove them & replace with versions for the new kernel.
Suggest you try this on a non mission-critical usb stick first. Use at own risk. Hope this helps.
(Also, you could try the change_kernels option in the first post of this subforum).