Page 1 of 1

can't change_kernels via LICK (Solved)

Posted: Mon Mar 07, 2022 7:31 pm
by BobW

From Win10, I used LICK to boot into Fossa. I started up change_kernels, which says it found kernel /initrd/fossapup64-9.5

I dragged the replacement kernel tarball (downloaded from LxPuppy, btw) into the change_kernels form, from a Win10 directory. But in the end I got the error:

cannot stat '/initrd/fossapup64-9.5/vmlinuz': No such file or directory

Just for the heck of it, I next tried using the two files instead of the tarball, and got the same error.

While now back in Windows, I look at where LICK had created C:\fossapup64-9.5\ and I can see that vmlinuz is indeed there.

Is the problem that my Fossa isn't installed, per se? My Fossa isn't detected in /mnt so that's why it's not found? How do I overcome this and make change_kernels work? Or else how can I manually change the kernel in C:\fossapup64-9.5 ?

Thanks.

P.S. (I expected that the LxPup kernel might not work, but I wanted to try it and see. But could it possibly work?)


Re: can't change_kernels via LICK

Posted: Mon Mar 07, 2022 11:06 pm
by mikeslr

@ rockedge. After posting it occurred to me that neither Bobw's post nor my reply should be in this Section.
@ BobW --Edited after this post was moved -- this Section The Kernel Section is for posts by those providing kernels or seeking advice regarding how to create them. Each Puppy and each application have their own Section for reporting problems; and here's a 'bug' Section as well. But if you're unsure of where to post, the User's Section, viewforum.php?f=4 purpose is sufficiently broad: "Issues and / or general discussion relating to Puppy".

LICK has nothing to do with it. LICK is just a boot-loader. Once it boots an operating system its function is complete and it no has effect on whatever operating system you booted into.

Because a Win10 directory was the download location of the kernel package, my guess is that you downloaded it using a browser running under Windows into space controlled by Windows and Windows screwed things up.

As I don't use the 'Change Kernel' application I can't speak of any problems it may have. I also can't examine the specific kernel package you tried to work with as you did not provide its download link.

The only thing that the 'Change Kernel' application does is automate the renaming discussed below.

I often update the kernels my Puppys use; but I do it manually:

(1) Boot into Puppy.
(2) Create a folder into which you will copy the current versions of the specified files [vmlinuz and zdrv_fossapup64_9.5] just in case you have, or want to, revert.
(3) Download a 'Kernel package'.
(4) Right-Click it and from the pop-up menu select UExtract.
(5) The Extraction folder will contain two files: one named vmlinuz-IDENTIFYING-CHARACTERISTICS; the other named kernel-modules-IDENTIFYING-CHARACTERISTICS.sfs.
Fossapup64's initrd.gz determines what files it will use.
The kernel group of fossapup64 consists of vmlinuz and zdrv_fossapup64_9.5.sfs. vmlinuz is actually 'the kernel'; a zdrv....sfs is the drivers of hardware compiled for that kernel.
(6) Rename the vmlinuz-IDENTIFYING-CHARACTERISTICS to just vmlinuz.
(7) Rename kernel-modules--IDENTIFYING-CHARACTERISTICS.sfs to zdrv_fossapup64_9.5.

The following may also be necessary. Both drivers and firmware are required for the kernel to communicate with a computer's hardware. Drivers are kernel specific. Firmware is not. Some devs package firmware in what is or will become the zdrv.sfs. Some don't because once you have the necessary firmware it can be used with any kernel in any Puppy. When you use their kernel-modules--IDENTIFYING-CHARACTERISTICS.sfs you'll also have to download an fdrv.sfs. The link from which you downloaded the 'Hugh-Kernel' should tell you whether an fdrv.sfs is needed. If per that post you need one and there was an fdrv.sfs in fossapup64's ISO, that will suffice. If you have to download an fdrv.sfs you have to rename it fdrv_fossapup64_9.5 for fossapup's initrd.gz to use it.

Having renamed the package contents to work with fossapup64's initrd, you can reboot.


Re: firmware SFS links --when you need it

Posted: Tue Mar 08, 2022 12:14 am
by mikeslr

I don't know about you, but often when swapping kernels I find that I need to download (then rename) a fdrv.sfs and end up spending an inordinate amount of time searching for one. I thought I previously provided a post with links, but can't find it. This Section seemed a logical location for such a post and thread as those most interested in alternate kernels may also need a firmware sfs. Suggest this post be made a 'sticky'.

peebee provides two here, https://sourceforge.net/projects/lxpup/ ... e-kernels/. I know somewhere there's an even more comprehensive version. I'll see if I can find it. Don't hesitate to add your own links.


Re: can't change_kernels via LICK

Posted: Tue Mar 08, 2022 12:26 am
by ozsouth

Re: can't change_kernels via LICK

Posted: Tue Mar 08, 2022 12:36 am
by mikewalsh

@mikeslr :-

Yep, good advice, mate...

After posting it occurred to me that neither Bobw's post nor my reply should be in this Section.
@ BobW --this Section is for posts by those providing kernels or seeking advice regarding how to create them. Each Puppy and each application have their own Section for reporting problems; and here's a 'bug' Section as well. But if you're unsure of where to post, the User's Section, viewforum.php?f=4 purpose is sufficiently broad: "Issues and / or general discussion relating to Puppy".

------------------------------------------------------

Moved thread to 'Users'. Will leave 'shadow copy' for the short-term, so it can be found easily....

Mike. ;)


Re: can't change_kernels via LICK

Posted: Tue Mar 08, 2022 9:31 am
by bigpup

Give us the download link to the kernel package you tried to use.


Re: can't change_kernels via LICK (Solved)

Posted: Mon Mar 14, 2022 12:35 pm
by BobW

Solved: change_kernels won't do it until you create a Save file. Then it works as expected. That fits with what I'd initially reported: that change_kernels had complained that it can't find the kernel-to-be-changed under /mnt/

[I'd said "via LICK" in the title to emphasize that this was something equivalent to a LIVE instance. Apparently, that's called a frugal install.]

P.S. It was a stroke of good fortune that I had posted under the Kernels subforum, because ozsouth commented that he had a kernel which allowed me to finally use wifi with Fossa (the common Realtek problem). Without that ability, I would have abandoned Fossa. But since wifi finally now works, I will likely be recommending Puppy all over the internet - to people who are thinking of a way to dabble in Linux and eventually switch away from M$oft.