BookwormPup64 10.0.8

[JusGellin]

@JusGellin - this is getting crazier by the day. The link I posted 2 posts up has all the firmware you need, including pnvm files (and all I need too). Interesting that the 6.11 kernel you used tried to fallback. Would you please post the config? If not in /boot, should be in /proc (as config.gz).

Here's the one found in /boot.

Let me know whatever you need.

Thanks

[ozsouth]

@JusGellin - thanks. Tried a few combos (still refused fallback) & finally used all your config. Sadly, was extremely large (kernel-modules.sfs was over 1Gb - usually about 40mb) & still didn't fallback. Will have use my config with a 'no-fallback' warning. Suggest other folk use woof-ce derived kernels for 6.11 on.

[dimkr]

@ozsouth It's large because it includes debugging symbols and you're probably not stripping them or not doing this correctly. My Debian based kernels at https://github.com/vanilla-dpup/woof-CE/actions are about 150 MB in total (modules, source) and that's with erofs and zstd (squashfs with xz would be much smaller).

[JusGellin]

@ozsouth
I loaded kernel 6.10.14 on this to make my new laptop work properly for graphics and wifi.

I loaded it using the command: change_kernels
When I look to what the kernel is, using uname -r, it gives 6.10.14-64ox-hf-umovx
But it tries loading iwlwifi-so-A0-gf-a0-89 through iwlwifi-so-A0-gf-a0-59 and fails
The graphics works properly.

What should I do next? I wanted to follow what you and @dimkr indicated below:
Re: Kernel 6.11 firmware rolldown (fallback) issue
https://www.forum.puppylinux.com/viewto ... 16#p137116

@JusGellin - the last USRMERGE kernel I made without this issue was 6.10.14 - I made it specifically because of this. Is suited to Bookwormpup64, with it's fdrv.
That said, as dimkr says, mismatches are generally not a good idea.

Thanks

[JusGellin]

@ozsouth
fyi
I also ran this from a usb stick on two other 2021 laptops which failed as well.
But I noticed both of these were trying to use the iwlwifi driver as well unless that driver is just a generic driver.

I'm getting a bit confused.

Thanks

[ozsouth]

@JusGellin - did you use Bookwormpup64-10.0.8's original fdrv? That has
/usr/lib/firmware iwlwifi-so-a0-gf-a0.72.ucode
/usr/lib/firmware iwlwifi-so-a0-gf-a0.pnvm
Which should be found on bootup. The reason for using that fdrv is that it also runs microcode security, which would need to be run manually with a plain fdrv.
If you did use Bookworm's fdrv when wifi failed, you could try my latest bwp64 fdrv to see if it works (99mb, has extra iwlwifi files):
https://www.mediafire.com/file/6wq0kcey ... l.sfs/file
Must rename file to fdrv_dpupbw64_10.0.8.sfs before use.

[JusGellin]

@JusGellin - did you use Bookwormpup64-10.0.8's original fdrv? That has
/usr/lib/firmware iwlwifi-so-a0-gf-a0.72.ucode
/usr/lib/firmware iwlwifi-so-a0-gf-a0.pnvm
Which should be found on bootup. The reason for using that fdrv is that it also runs microcode security, which would need to be run manually with a plain fdrv.
If you did use Bookworm's fdrv when wifi failed, you could try my latest bwp64 fdrv to see if it works (99mb, has extra iwlwifi files):
https://www.mediafire.com/file/6wq0kcey ... l.sfs/file
Must rename file to fdrv_dpupbw64_10.0.8.sfs before use.

Once I figured how change_kernels works, all my laptops work properly with the new kernel.
The problems I had before was not using the app right.

Also, I found I could use the original fdrv and all would work. So then my new computer would use wilwifi .72 driver.
But if I use the fdrv you made, it would use wilwifi .83 driver

So is using the change_kernels script the only way to load a different kernel?

Is there any good way to try different kernels easily if I just wanted to test things out?

Thanks to you @ozsouth , @dimkr and puppy linux for all of this.

[ozsouth]

@JusGellin - all you need to do to basically change kernels is to replace vmlinuz & zdrv with those from kernels in the forum Kernels section (or some other sources). Must ensure it is a compatible kernel (i.e is usrmerge for Bookwormpup64) & that you have aufs or overlayfs compatibility (i.e is overlayfs capable for Bookwormpup64), renaming them to the same as those replaced.

Extra considerations: with Bookwormpup64 you must disable kbuild....sfs (is kernel-specific, I add .no to end). Also if an ....initmodules.txt file is in same folder as puppy...sfs, must delete it before booting into new kernel. Any extra drivers added (i.e. wl) are kernel specific & should be removed before change. If you have a savefile/folder, once booted up must remove ..../lib/modules/(kernel name) subfolder pertaining to old kernel. I suggest testing new kernel out on a non-mission-critical install first.