F96_4-CE 4th Gen Dev Tester with a New Kernel 6.0.9 Made for F96

[fr-ke]

@rockedge Thanks for the quick reply.

As far as I understand, adrv_xxx_.sfs is the top layer, which is only overwritten by changes in the savefile.
So that e.g. changes in /root/concyrc can be made persistent (conkyrc is in adrv_xxx_.sfs) adrv_xxx_.sfs must be merged into e.g. ydrv or bdrv or a remastering must take place so that the content of the save file is then copied into adrv is at the top and in adrv there is only the content of the save file (not mixed with the original adrv).
That's no problem, I do it that way too. A possible downside to doing this is that the original structure of puppy is modified, which sometimes makes debugging difficult.

[wizard]

@radky
@rockedge

Here is the updated issue list.

f96-4.xls

(22.5 KiB) Downloaded 45 times

Thanks
wizard

[amethyst]

@rockedge Thanks for the quick reply.

As far as I understand, adrv_xxx_.sfs is the top layer, which is only overwritten by changes in the savefile.
So that e.g. changes in /root/concyrc can be made persistent (conkyrc is in adrv_xxx_.sfs) adrv_xxx_.sfs must be merged into e.g. ydrv or bdrv or a remastering must take place so that the content of the save file is then copied into adrv is at the top and in adrv there is only the content of the save file (not mixed with the original adrv).
That's no problem, I do it that way too. A possible downside to doing this is that the original structure of puppy is modified, which sometimes makes debugging difficult.

Rename the existing adrv of the distribution as a bdrv and use my utility to save your system changes to an adrv.

[wizard]

@radky
@rockedge

One of the under promoted advantges of using Puppy Linux is the number of applications it offers OOTB. A new user browsing the Menu is confronted with names like Osmo, uGet, or my favorite, DeaDBeef, and yes there are short "hover" descriptions, but it's not really easy to find what you want in the menus (almost 150 items). I suggest we make it easier by including a "Programs Installed" list and place an icon on the desktop. A kind of "One stop shopping" list. This would help both new users and reviewers alike.

I've attached such a list, in spreadsheet format, for F96-4. If used it would need a final edit before release.

Programs_Installed-F96.xls

(23.5 KiB) Downloaded 51 times

Desktop-F96.png (355.47 KiB) Viewed 1479 times

Thanks
wizard

[radky]

New F96_4-radky3 iso

Edit: outdated iso removed

Changelog:

• Add rockedge's 6.0.9 kernel

AUFS6 and Overlayfs built in
SMP PREEMPT DYNAMIC
KVM virtualization support
NTFS and FAT32 read and write support
Lz4 and zstd compression support enabled

• Add dimkr's comprehensive firmware which provides improved wifi and bluetooth support (fdrv_fossapup64_9.6.sfs)
• Add ConnMan network manager (originally removed, now restored). ConnMan is the default connection manager for FossaPup64 CE. See Note-1 below.
• Add Internet Connection Switcher (enables switching to/from ConnMan and Connect Wizard tools (sns, frisbee, network wizard). Go to Menu -> Setup -> Internet connection switcher. Use of this GUI requires a Save File/Folder and Rebooting to initialize the selected connection manager.
• Adjust functionality of pmount and pupswap in the FP96 environment
• Adjust eventmanager spacing of the ROX pinboard drive icons (prevent icon overlap when the user selects fine, medium or coarse grid steps in ROX options)
• Adjust contrast of network and speaker icons of the main tray, and move conky toggle from main tray to the utilities menu (right side of main tray).
• Adjust Conky-GTK and companion start/stop scripts to support wallpaper names with spaces. See Note-2 below.
• Update Puppy help resources in /usr/share/doc
• Update base files for compliance with recent changes in Woof-CE
• And many more adjustments to hopefully improve the desktop experience
• Again, JWMdesk is the lone desktop manager as true for the original FP95

Note-1: The ConnMan default configuration is effective but additional options are available in /etc/connman/main.conf. In the default configuration ConnMan may register an inactive network interface that is currently disabled (with no IP data). Consequently, the Conky information monitor will also show the inactive network interface. To completely disable this inactive connection, simply right-click the ConnMan (tray) network icon and toggle the interface button to OFF.

Note-2: The conky start scripts reset the Rox desktop background after a short delay of 2-5 seconds. This synchronizes the conky background with the current desktop background. In some scenarios (ex: delayed internet connection) the conky display does not appear until after the desktop background is set, in which case the conky background may fail to synchronize properly. If this happens, reset your internet connection if necessary and click the Conky toggle in the utilities menu (right side of main tray) to stop/start the conky display.

PupMates
https://www.smokey01.com/radky/PupMates.html

[wizard]

@radky
@rockedge

Here is the updated issue list.
Testing - F96_4-radky3 iso
Runs really well on my hardware.
Also tested on a low spec Toshiba A135 laptop cpu=Celeron M, 1.7ghz single core, 2gb ram. F96-4rad3 found all hardware.
Was able to run @mikewalsh Firefox Portable v107, single tab, and view Youtube video in a window. Note that on low spec computers web browsing is greatly enhanced by installing the Ublock Origin extension which blocks the ad streaming content. Also note that this Toshiba's cpu is well below what should be considered the minimum hardware requirement of dual core.

f96-4issues.xls

(23 KiB) Downloaded 51 times

Thanks
wizard

[fr-ke]

qemu_gui error message

1. After installing qemu-7.0.50-fossapup-x86_64.pet:

2. error message modprobe kvm (this disappears when I delete the entry gs in /etc/modprobe.d/cdrecord.conf)

3. Error message qemu_gui

4. However, when I start an .iso in the console, it boots normally and the virtualization runs at almost the same speed as the host system

[rockedge]

That's why I use aqemu installed with PPM instead of qemu-gui on F96. This message about enabling virtualization is incorrect on the DELL blade server I see it on. Since I know 100% that Intel virtualization support is enabled in the machine's BIOS.
The PowerEdge R210 II has either BIOS or UEFI that can be selected and I have enabled full virtualization support, but still see that error using qemu-gui. Aqemu runs well and is a bit heavier but I like being able to generate a startup script for a virtual machine with a menu selection.

I use qemu-gui on several different Bionic64's, and using those on this machine, I have not seen the message at all. Some kernels do not have builtin KVM support but use modules and for some reason as modules are not always loaded.

To fix the modprobe KVM ERROR open the file /etc/modprobe.d/cdrecord.conf and delete the line with "sg" in it and save. Redo the modprobe KVM command

I wonder if qemu-gui works correctly in Bionic but not so well in Fossapup. Come to think of it, I have not gotten qemu-gui to work fully or at all on any Fossapup.

[fr-ke]

In Bionic64 and Fossa64-9.5 qemu_gui works as expected.

With lsmod the modules are also displayed correctly.

Not in fossa 64-9.6.

[Clarity]

It appears @gyrog is a forum's "go-to" for init knowledge and some WoofCE maintenance. The INIT ideas could be raised on WoofCE GIT for consideration in Puppyland.

[Clarity]

I have had problems with qemu_gui over the past couple years. Seems the script may not be maintained with the changes that have occurred in Pups. Further the problems are differed depending which of the PUPs used as well as which of the versions are used.

I recommend that, if possible, all future WoofCE and PUP PETs use QEMU v7+ as it offers plenty for our needs with hardware over the past decade.

Further the Google document that exist for PUPs that covers VMs, QEMU, KVM needs updating...but that should not be done until the forum adopts QEMU v7+ such that the doc would be accurate for our modern times.

Just a thought

[fr-ke]

The bug in qemu_gui might be kernel dependent.

In Fossa64_9.6 with kernel 4.19.23 from Bionic64_8.0 both, qemu_gui and lsmod works fine

[rockedge]

@fr-ke I agree, I am cycling through kernels on F96_4-radky2 and both 6.0.9-rock and 6.0.9-redge report KVM module is builtin but don't grep it with lsmod, but work and I am also seeing some work with qemu-gui and some do not.

Odd that those 2 kernels do not show results for lsmod | grep kvm

WIth many huge kernels I am testing out modprobe kvm_intel --first-time is required. At some point I will review the kernel 6.0.9-rock's configuration. Possibly rebuild it tonight.

[radky]

New F96_4-radky4 iso

Edit: outdated iso removed

Changelog:

• Replace 6.0.9 with 6.0.12 kernel to address issues with qemu and network shares
• Continue dimkr's comprehensive firmware (fdrv_fossapup64_9.6.sfs)
• Adjust Conky toggle -- now two separate options (Conky restart and Conky stop) in tray utilities menu (right side of tray)
• Add shinobars's grub2config and zigbert's pburn
• Add help for the Pupswap utility (Menu -> Document)
• And many more adjustments to hopefully improve the desktop experience

PupMates
https://www.smokey01.com/radky/PupMates.html

[retiredt00]

New F96_4-radky4 iso

This a very nicely build puppy!
I need the broadcom-sta driver for my wifi though.
I can find the kernel source but not a devx file. Is there one?
Better yet is there a compiled broadcom wl module for the used kernel?
Thank you.

[Sofiya]

New F96_4-radky4 iso

https://www.smokey01.com/radky/Testing/ ... radky4.iso

Hi @radky
Touchpad won't start

[wizard]

@radky
@rockedge

Here is the updated issue list.
Testing - F96_4-radky4 iso

f96-4issues.xls

(23.5 KiB) Downloaded 66 times

Thanks
wizard

[rockedge]

I can find the kernel source but not a devx file. Is there one?

Yes this is the devx_fossapup64-9.6.sfs that is an artifact of the original build of F96-CE from woof-CE.

devx_fossapup64_9.6.sfs.md5.txt

https://rockedge.org/kernels ---- Devx->F96-CE-devx

[retiredt00]

I can find the kernel source but not a devx file. Is there one?

Yes this is the devx_fossapup64-9.6.sfs that is an artifact of the original build of F96-CE from woof-CE.

Thank you!

BTW your original link had/has a small typo (is corrected it in the quotation here)

[mikeslr]

I have not yet explored F96_4CE 4th. So I don't know to what extent the Right-Click options previously customarily found in Puppys --discussed on this thread, https://www.forum.puppylinux.com/viewto ... 513#p69513-- may still be absent.

[rockedge]

So I don't know to what extent the Right-Click options previously customarily found in Puppy's

The team is working on those step by step. It's the goal to have again a comprehensive set of useful right-click menu options

[Clarity]

Hello @radky Does your version have KVM built into its OOTB kernel?

Hello @rockedge Does your version have KVM built into its OOTB kernel?

Would like visit the KVM detection problem using one of forum's distros with the kernel support built in the OOTB distro. It appears that this module is very lightweight and does NOT affect system performance in any way when it is NOT used.

[wizard]

@mikeslr

Here are the right click menus from Rox in F96:
FILE

fileRC.png (25.61 KiB) Viewed 1420 times

DIR

dirRC.png (63.44 KiB) Viewed 1420 times

Thanks
wizard

[geo_c]

@rockedge I do miss these right click actions in KLV! I learned that a lot of things I assumed were Rox features are actually puppy features.

[rockedge]

The one I miss the most is "Run in a Terminal"!

All the configurations to achieve these right click actions could be made into a PET that can be applied and will install all the components for these to be available

@Clarity The kernels I built for testing with F96 have KVM modules built in but something doesn't seem 100% with them when querying the system with lsmod | grep kvm the result output is blank.
The team switched to the kernel 6.0.12 from @peebee's workshop.

[wizard]

@rockedge
@geo_c

I think @mikeslr has already made a pet for the right click menus that would probably work in KLV

Thanks
wizard

[rockedge]

@wizard Already added it I believe. Will need to look into that it made it through the radky factory stages. But it's not as fully featured as we are planning on.

[geo_c]

The one I miss the most is "Run in a Terminal"!

The one I miss the most is "duplicate"

[rockedge]

@geo_c More right click actions will be also added to KLV, borrowing from the Puppy Linux philosophy.
Both of those we mentioned are used by me alot!

@fredx181 already has made a .xbps that I used to add the few that exist now. His ideas will be expanded on soon.

[radky]

@rockedge

A comprehensive ROX right-click context menu (including Run in Terminal) is included in FP96 (radky4 and the upcoming radky5). What is missing?