BookwormPup64 10.0.9

[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. (updated link).

See Bookwormpup64 fdrv, linked here:
https://www.mediafire.com/file/dzu43etl ... l.sfs/file

[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.

[Jasper]

Remember there is a difference between AUFS and Overlay based 'saves'

[JusGellin]

@JusGellin

You might try editing the xorg.conf and set de resolution to 1440x900

If you have no xorg.conf file, you can create one, and edit it. For ease of use you can just copy mine, alter it to your needs, save it and make it exicutable. Don't forget the latter!

Perhaps this does the trick.
Good luck!

Mine had the xorg.conf so I changed the resolution to 1440x900.
That looks really good.
Thanks

[JusGellin]

Remember there is a difference between AUFS and Overlay based 'saves'

How can I tell if one uses AUFS or Overlay based 'saves'?

Thanks

[fredx181]

Remember there is a difference between AUFS and Overlay based 'saves'

How can I tell if one uses AUFS or Overlay based 'saves'?

Thanks

Overlay 'saves' have "upper" and "work" directories inside, Aufs 'saves' not.

[JusGellin]

Overlay 'saves' have "upper" and "work" directories inside, Aufs 'saves' not.

I thought I read that Bookworm uses overlays. Is that something different than overlay saves?

Thanks

[Jasper]

@JusGellin

Kernel dependent

[radky]

BookwormPup64 10.0.9

• New release
• See first post to download and second post for changelog
• ibiblio downloads are available now
• nluug and aarnet download mirrors should sync within 24 hr

[ozsouth]

Instead of a basic CD version, with radky's permission I made a more compressed 10.0.9 remaster with kernel 6.10.14 (656mb).
See: viewtopic.php?p=137549#p137549

[keniv]

BookwormPup64 10.0.9

• New release
• See first post to download and second post for changelog
• ibiblio downloads are available now
• nluug and aarnet download mirrors should sync within 24 hr

Thanks for the new version 10.0.9 which I've just installed with a new clean save folder. I'm posting from it now. All seems to be working properly but I did have the same problem I had when I first installed 10.0.8. I'm multi-booting with Mint Linux, F96-CE v4 and 10.0.9 using the version of grub in Mint to boot the pups. On first booting 10.0.9 I have no problem and it boots to a desktop. I then make some initial setup changes, connected to wifi then close down including making a save folder. All of this seemed to go well. When I rebooted the boot process crashed with a lot of info in red text finishing with "Pausing 60 seconds". I remembered seeing this with 10.0.8 so I rebooted using F96-CE v4 and removed the file dpupdw64initmodules.txt that appeared in the 10.0.9 directory. I have rebooted now many times without further problem. I don't really understand why this problem occurs. I think this problem on the second boot would be disconcerting if you hadn't seen it before and it seems like a sort of a bug. Can I ask if there is a way to prevent this on the second boot. Can I also say that I do realise this is a minor irritation and I really like this OS.

Regards,

Ken.

[N97]

Tried S15... kernel too old for my new N97 cube 'puter. Void works, but I can't get to repo for a vlc add. So I'm here... kernel and browser excellent .
No mention of MM player, but one might be included. I have to buy DVD's- too large for CD. So a few more days to 1 week w/ void. 64bit ISO downloaded

Cheers

[bigpup]

There is a version of BookwormPup64 10.0.9 that will fit on a CD.
Get it from here:
viewtopic.php?t=13321

you should not need to burn the ISO image to a CD or DVD.

This N97 cube computer should be able to boot from a install of BookwormPup64 on a USB stick.

Do a live install of it on a USB stick and boot with it.

[Clarity]

SG2D

• Booted SG2D and launched the v1009 ISO file. Take the default boot menu stanza WITHOUT changes. v1009 finds the prior sessions folder automatically, captures the session I chose, and booted to desktop with all prior setups included. Works as expected and shutdown-save (persistence) behaves as expected.

Ventoy

• Booted Ventoy and launched the v1009 ISO file. Edited the default boot menu stanza. Added psave= pointing to the folder where sessions are saved. Chose a different prior session (I have 2 of these as they have different objectives) during boot and that, too, booted to desktop with all of its prior setups included. Works as expected and shutdown-save behaves as expected.

V1009 booted to desktop in each case. ALL is WELL!

The beauty of these "launchers" is no need to/for any efforts, plannings or thoughts beyond downloading the ISO file and booting immediately for the full capability of the distro.

Thanks @radky and those helping him

[Clarity]

This post is for users who might want to go back and forth between v1008 and v1009. If you are using either of the ISO file launchers, this is really simple.

I think that if you copy your v1008 save-session(s) as a backup, before running a v1009, the backup session will be available should you need to boot v1008 after a v1009 upgrade to the old session. In this case you will have both v1009 (new) session as well as the backup v1008 (old) session should you need to go back and forth for any reason.

For example, in my case:

1. copy /mnt/sdb3/Sessions/dpupbw64save-Radky_240926_nvidia_plus to "/mnt/sdb3/Sessions/dpupbw64save-Radky_240926_nvidia_plus (v1009)"

2. Booting the v1009 ISO file, when the BKWP64 stops awaiting your save-session choice, choose the copied file, ie "...(v1009)", and your PUP will be upgraded accordingly for you.

This way, if you ever need to revisit v1008, it will be there, unchanged, for you.

Hope this is helpful.

A similar approach could be used by non-ISO file users.

[Jasper]

Thats why Void 100924 selected. It took several threads here to put this together, along with Intel and Wiki, among others.

That's a shame you did so much research, slow down and you will be able to enunciate words instead of cube 'puter

[Clarity]

Helllo @radky and thanks for this issue.

Several members have posted here of issues and a resolution of v1009. Not sure if its relevant or important ... just mentioning.