Change kernel program is already in Bionicpup64 8.0
Quickpet->Info->Change kernel
I did already run Quickpet->Info->Bionicpup updates
Worked OK for me.
you did click on OK?
Got a message that change was made and backups of changed files?
Can you post an image of what is in the location of all the Bionicpup64 8.0 files.
Change kernels GUI in recent woof-ce puppies
I clicked OK and did get messages before rebooting. Hope attached is the correct folder. thanksbigpup wrote:Change kernel program is already in Bionicpup64 8.0
Quickpet->Info->Change kernel
I did already run Quickpet->Info->Bionicpup updates
Worked OK for me.
you did click on OK?
Got a message that change was made and backups of changed files?
Can you post an image of what is in the location of all the Bionicpup64 8.0 files.
- Attachments
-
- kernel.png
- (105.25 KiB) Downloaded 102 times
---
trying to learn puppylinux... :D
---
trying to learn puppylinux... :D
---
try the simple manual method of changing the Bionic 4.19.23 kernel with the Tahr kernel. First ensure you are using the correct 64 or 32 bit version.
in the Bionic directory rename the vmlinuz and zdrv_upupbb_18.05.sfs to something like vmlinuz-4.19.23 and zdrv_upupbb_18.05.sfs-4.19.23
then copy the vmlinz and zdrv_upupbb_18.05.sfs from the Tahr directory or from the Tahr ISO and paste them into the Bionic directory then reboot into Bionic
This should work ok
in the Bionic directory rename the vmlinuz and zdrv_upupbb_18.05.sfs to something like vmlinuz-4.19.23 and zdrv_upupbb_18.05.sfs-4.19.23
then copy the vmlinz and zdrv_upupbb_18.05.sfs from the Tahr directory or from the Tahr ISO and paste them into the Bionic directory then reboot into Bionic
This should work ok
my mistake
I have found I was not able to change the kernel since my PC was not installed to HD, only had sav folder on a HD partition. I was booting from a USB stick.
I appreciate the help but I will take it from here to get my internal SD reader working by changing the kernel. Sorry about my mistake.
I appreciate the help but I will take it from here to get my internal SD reader working by changing the kernel. Sorry about my mistake.
---
trying to learn puppylinux... :D
---
trying to learn puppylinux... :D
---
It still should have worked as long as vmlinuz and the zdrv are on the USB stick.I was booting from a USB stick.
The image you posted shows no vmlinuz on the location of the zdrv.
Also, I see no backups that should have been made.
Is that image what is on the USB stick?
I assume there is free space on the USB stick that will hold changes and added files?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
image is wrong, not the USB stick. I was able to change the kernel per your and rockedge suggestions but ran into nvidia driver issue..., giving it all up for now...bigpup wrote:It still should have worked as long as vmlinuz and the zdrv are on the USB stick.I was booting from a USB stick.
The image you posted shows no vmlinuz on the location of the zdrv.
Also, I see no backups that should have been made.
Is that image what is on the USB stick?
I assume there is free space on the USB stick that will hold changes and added files?
---
trying to learn puppylinux... :D
---
trying to learn puppylinux... :D
---
01micko,
This is a very good program, but there is some confusion, with the information on the programs, main window.
It is not clear, to a lot of people, that only stuff from the new kernel package, goes into the input slots.
The info for the bottom input slot is confusing.
Could you change it to just say:
New kernels zdrv sfs or kernel modules sfs if built with kernel-kit.
Maybe a statement at the top, that all inputs are from the new replacement kernel package.
This is a very good program, but there is some confusion, with the information on the programs, main window.
It is not clear, to a lot of people, that only stuff from the new kernel package, goes into the input slots.
The info for the bottom input slot is confusing.
Could you change it to just say:
New kernels zdrv sfs or kernel modules sfs if built with kernel-kit.
Maybe a statement at the top, that all inputs are from the new replacement kernel package.
- Attachments
-
- Screenshot(3).jpg
- (31.32 KiB) Downloaded 172 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Yes I was just thinking that yesterday when I used it in fossapup.
I'll fix it in woof something like zdrv_xxx_xxx.sfs maybe?
Ok, done in woof.
Here is the file https://raw.githubusercontent.com/puppy ... ge_kernels
I'll fix it in woof something like zdrv_xxx_xxx.sfs maybe?
Ok, done in woof.
Here is the file https://raw.githubusercontent.com/puppy ... ge_kernels
- Attachments
-
- ck.png
- (17.57 KiB) Downloaded 112 times
Puppy Linux Blog - contact me for access
01micko,
Thanks for the change.
I know I am being a pain in the a@#s.
You would not believe how many times I had to tell someone this:
That all inputs are from the new replacement kernel package.
Maybe add as a statement at the top.
I have been working on a Chromebook I have. Turning it into a Puppy laptop.
This change kernel GUI is getting well used, trying out different kernels.
Thanks!
Thanks for the change.
I know I am being a pain in the a@#s.
You would not believe how many times I had to tell someone this:
That all inputs are from the new replacement kernel package.
Maybe add as a statement at the top.
I have been working on a Chromebook I have. Turning it into a Puppy laptop.
This change kernel GUI is getting well used, trying out different kernels.
Thanks!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Yes an oversight. While Slacko64 is quite happy with the aufs libs in /usr/lib I can see a problem with the real directory overlaying the symlink in debian/arch based pups.ozsouth wrote:One other issue with change kernels - 64bit libau kernel kit files in slacko derivatives go in /usr/lib64, whereas those for ubuntu derivatives go in /usr/lib with /usr/lib64 as a symlink. That's why I specify which flavour each kernel is.
I will have to write a routine which mounts the zdrv before changing and moves /usr/lib64 to /usr/lib then resquashing the new zdrv if this situation is detected.
Puppy Linux Blog - contact me for access
I've said this before. But no one was listening. 64-bit "Ubuntu/debian" based Puppies can find /usr/lib64 folders. What they can't find are /x86_64-linux-gnu folders. Woof & PPM should automatically change the files in debs to use /lib64.
For further info, see this post. http://murga-linux.com/puppy/viewtopic. ... 945#960945. FYI, FWIW, the pet at the bottom of the thread didn't work. PaDS 1.1.4 did work, but obviously you have to use it and IIRC it also just moved 64 bit libs into the "lib" folders shared with 32-bit libs. And, recently, with bionicpup64 I've had some problems using PaDS.
For further info, see this post. http://murga-linux.com/puppy/viewtopic. ... 945#960945. FYI, FWIW, the pet at the bottom of the thread didn't work. PaDS 1.1.4 did work, but obviously you have to use it and IIRC it also just moved 64 bit libs into the "lib" folders shared with 32-bit libs. And, recently, with bionicpup64 I've had some problems using PaDS.