F96_3-CE a 3rd Development Test of Fossapup64-9.6-CE

[rockedge]

This is the latest version of F96-CE and is called F96_3-CE

This version is an extension of F96_2-CE with further small fixes and adjustments. Dunst is repaired and seems to work but not tested thoroughly. Inkscapelite is not working because of an old version looking for old libraries. Anyone else experiencing this?

For now I don't want to confuse the process of finding a Distrowatch entry so we will need to contemplate how to move forward or put F96 into hibernation.

@bigpup If we go forward with F96 at some point, I would include all of the documentation. We have room.

[Sofiya]

wallpaper selection problem
wallpaper selection missing in desktop settings
also after reboot you can't select wallpaper in JWMdesk ___ happens after selecting " Fossapup updates "
I had to put together a package.
Edit: file Changing_wallpaper.pet was replaced in the previous build there was an error

[Sofiya]

if I'm catching the moment correctly it happens after selecting " Fossapup updates "

[radky]

Sofiya,

The most recent Quickpet updates for FossaPup64 9.5 are now two years old and the included files will overwrite and break current applications in FP 9.6.

It may be time to disable some or all of the options in the Quickpet module.

[Sofiya]

Sofiya,

The most recent Quickpet updates for FossaPup64 9.5 are now two years old and the included files will overwrite and break current applications in FP 9.6.

It may be time to disable some or all of the options in the Quickpet module.

Thanks
@radky
but still wallpaper selection missing in desktop settings. until I install the package
This is of course not so important if it does not disappear from JWMdesk
all the same, when there is a package, it’s somehow calmer

[radky]

@Sofiya

I'll test F96 a bit more. Maybe we can help rockedge fix a few bugs.

Thanks for your report.

[rockedge]

I have removed inkscapelite and replaced it with inkscape which is in the adrv_fossapup64-9,6.sfs now at 90 MiB. This has increased the overall ISO size slightly. So far it's loading and working

The missing wallpaper config option in Desktop Setup needs repair

[wizard]

Working my way through f96-3. Here's the spreadsheet I use to log what I found so far. Let me know if you need extra info

f963.xls

(11.5 KiB) Downloaded 150 times

Thanks
wizard

[wanderer]

hi rockedge

trying your F96_RC3

wow looks really nice

tons of goodies
i like palemoon

posting from it now

this looks like a winner

no problems to report yet
will keep testing

thanks for all your work

wanderer

[radky]

@rockedge

Attached is a spin of FP96 which addresses several issues such as the broken quickpet and wallpaper applications. The Picom, Conky and Dunst configuration applications are adjusted and working. Duplicated applications in the adrv and main sfs have been consolidated to one sfs.

Phil's most recent fossapup updates from quickpup are applied, but not those that break FP96. The quickpup GUI is also updated and the broken modules are removed. Several applications are updated such as Palemoon, PupSysInfo, etc. The broken Inkscapelite application is removed but I did not add the full Inkscape application since some users may prefer large applications in sfs format.

As true for Phil's original FP95, this spin of FP96 has JWMdesk as the lone desktop manager.

I'll leave the iso link for a day or two, then remove it to avoid confusion as you continue development.

Thanks

Edit: iso removed

[wizard]

@radky

Tried to download from your link, but got a 403 error. Did you limit the access?

Thanks
wizard

[radky]

Tried to download from your link, but got a 403 error. Did you limit the access?

wizard

Sorry, the permissions at smokey01.com are now reset and the iso should be accessible.

Thanks

[rockedge]

@radky Fantastic! I have been pushing forward finding the problems but not actually fixing many. The elimination of duplicate packages between the rootfs and adrv is an important step.

Looking at the list of fixes and adjustments I think this version you've produced should be the new base to work from. It is already going in the same direction I was aiming for. Thanks for the good work and the effort.

I also like the wallpaper.

I will set it up on bare metal and try it out on virtual machines. I a pretty convinced this Pup is almost ready to come out of training school and get out in the field. Perhaps a few additions but I think the default version of the distro should remain relatively basic with the user making the choices what to add and what method to use, portable, SFS, PET or from the Ubuntu repos as deb packages.

Again thank you for pitching in and making short order of the few nagging problems floating around the Fossapup64-CE model.

[TerryH]

Very excited to see @radky's spin of the FPup96, makes a really true collaborative Community Edition.

Unfortunately it fails to boot on my Asus laptop AMD Ryzen 7 5800H (S15Pup won't bot either, but possibly different failure). This was a manual frugal install to an existing USB Flash with multiple puppy/dog installs. The image shows how far the boot proceed.

Note: I left the image I originally posted to the forum, after uploading to hosting site. This frequently happens when trying to post images.

[radky]

TerryH

I also have a new Ryzen 7 5800 laptop (configured with RTW89 WIFI). I can boot recent iterations of Vanilla Dpup which has significant firmware support, but only after a couple of changes.

1 - Support for the RTW89 chipset requires kernel >= 5.18.x and the kernel must be configured specifically to support RTW89. At the moment, FP96 is using Peebee's 6.0.5 kernel which does indeed support the RTW89 chipset.

2 - Additionally, the RTW89 chipset requires RTW89_8852 firmware not currently included in FP96. You can add the firmware manually, but the fdrv of FP96 should be updated to support recent hardware. Also the community will need to decide on the final kernel version so rockedge can generate proper devx and kernel_source packages.

I hope this helps.

[radky]

@dimkr

While booting FossaPup64 9.6 I see multiple error messages pertaining to udev, and dmesg shows the following:

[ 20.667975] udevd[1634]: starting version 3.2.9
[ 20.698328] udevd[1634]: specified group 'input' unknown
[ 20.699671] udevd[1634]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /etc/udev/rules.d/55-cups.rules:5
[ 20.727465] udevd[1634]: unknown key 'DEVTYPE' in /etc/udev/rules.d/88-puppy-autodetect.rules:6
[ 20.727518] udevd[1634]: invalid rule '/etc/udev/rules.d/88-puppy-autodetect.rules:6'
[ 20.727559] udevd[1634]: unknown key 'DEVTYPE' in /etc/udev/rules.d/88-puppy-autodetect.rules:10
[ 20.727597] udevd[1634]: invalid rule '/etc/udev/rules.d/88-puppy-autodetect.rules:10'
[ 20.732539] udevd[1635]: starting eudev-3.2.9
[ 20.734325] aufs may_rename_srcdir:561:udevd[1635]: renaming dir who has child(ren) on multiple branches, is not supported
[ 20.734411] udevd[1635]: unable to move watches dir /run/udev/watch; old watches will not be restored: Invalid cross-device link

Are the above error messages important?

Concerning udev, in recent Vanilla Dpup the /etc/udev/hwdb.d folder is empty. However, in FossaPup64 9.6 this folder contains multiple udev files (timestamp Nov 2019) as follows:

/etc/udev/hwdb.d/20-acpi-vendor.hwdb
/etc/udev/hwdb.d/20-bluetooth-vendor-product.hwdb
/etc/udev/hwdb.d/20-net-ifname.hwdb
/etc/udev/hwdb.d/20-OUI.hwdb
/etc/udev/hwdb.d/20-pci-classes.hwdb
/etc/udev/hwdb.d/20-pci-vendor-model.hwdb
/etc/udev/hwdb.d/20-sdio-classes.hwdb
/etc/udev/hwdb.d/20-sdio-vendor-model.hwdb
/etc/udev/hwdb.d/20-usb-classes.hwdb
/etc/udev/hwdb.d/20-usb-vendor-model.hwdb
/etc/udev/hwdb.d/20-vmbus-class.hwdb
/etc/udev/hwdb.d/60-evdev.hwdb
/etc/udev/hwdb.d/60-keyboard.hwdb
/etc/udev/hwdb.d/60-sensor.hwdb
/etc/udev/hwdb.d/70-mouse.hwdb
/etc/udev/hwdb.d/70-pointingstick.hwdb
/etc/udev/hwdb.d/70-touchpad.hwdb

Are the files of the /etc/udev/hwdb.d folder important for FossaPup64, or is OK to remove them as true for Vanilla Dpup?

---

Additionally, in Fossapup64 9.6, dmesg shows multiple error messages concerning Bluetooth:

[ 46.927321] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[ 46.928838] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq failed with error -2
[ 46.928854] Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq (-2)
[ 46.929003] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2
[ 46.929009] Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.7.bseq

I don't use Bluetooth devices, but are the errors above a simple matter of missing firmware?

Thanks

[Sofiya]

Very excited to see @radky's spin of the FPup96, makes a really true collaborative Community Edition.

Unfortunately it fails to boot on my Asus laptop AMD Ryzen 7 5800H (S15Pup won't bot either, but possibly different failure). This was a manual frugal install to an existing USB Flash with multiple puppy/dog installs. The image shows how far the boot proceed.

Note: I left the image I originally posted to the forum, after uploading to hosting site. This frequently happens when trying to post images.

HP Pavilion AMD A10-4600M APU with Radeon(tm) HD Graphics
It also shows me when loading.
Luckily it's loading

[TerryH]

Additionally, in Fossapup64 9.6, dmesg shows multiple error messages concerning Bluetooth:

[ 46.927321] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[ 46.928838] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq failed with error -2
[ 46.928854] Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq (-2)
[ 46.929003] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2
[ 46.929009] Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.7.bseq

I don't use Bluetooth devices, but are the errors above a simple matter of missing firmware?

Thanks

In regards to the bluetooth errors, providing the relevant firmware corrects the -2 errors in my experience.

[TerryH]

TerryH

I also have a new Ryzen 7 5800 laptop (configured with RTW89 WIFI). I can boot recent iterations of Vanilla Dpup which has significant firmware support, but only after a couple of changes.

1 - Support for the RTW89 chipset requires kernel >= 5.18.x and the kernel must be configured specifically to support RTW89. At the moment, FP96 is using Peebee's 6.0.5 kernel which does indeed support the RTW89 chipset.

2 - Additionally, the RTW89 chipset requires RTW89_8852 firmware not currently included in FP96. You can add the firmware manually, but the fdrv of FP96 should be updated to support recent hardware. Also the community will need to decide on the final kernel version so rockedge can generate proper devx and kernel_source packages.

I hope this helps.

Unfortunately not an issue for me. Asus luckily used intel iwl865 wifi in this laptop, so one less problem for me. I'm currently in an older Vanilla DPup. rockedge's KLV's are usually OK also.

[wizard]

@rockedge

Here's day two test of f96-3

f963.xls

(15 KiB) Downloaded 107 times

Thanks
wizard

[wizard]

@rockedge
@radky

Here's a little .pet to add "mdview", which is already installed, to the menu.

viewtopic.php?p=73100#p73100

wizard

[dimkr]

Concerning udev, in recent Vanilla Dpup the /etc/udev/hwdb.d folder is empty.

/usr/lib/udev/hwdb.d

(And, AFAIK, hwdb.d is unused in every Puppy built before https://github.com/puppylinux-woof-CE/woof-CE/pull/3520, but I could be wrong)

[mikeslr]

@ wizard, rockedge &c. Wizard, regarding your notation about the capabilities missing from rox's Right-Click Menu, see my post here, posting.php?mode=edit&p=73094. The pet I provided here, https://www.forum.puppylinux.com/viewto ... 0d5#p69513 will implement most of what's missing. But note what I wrote: "I never did get "Create a pet package" right so took the easy way out substituting "Make pet". And while sfs-load works there must be a better way which will display a nice icon."

I've been exploring woof on my own. It creates a folder (or more accurately a folder with a symbolic link to it) under woof-out named packages-pet. In context with the other folders under woof-out, I suspect that 'pets' put into the packages-pet folder would be incorporated into the build*. It's an initial reconnoiter: I don't yet know if pets, themselves could be used, or would have to be decompressed. Will have to study the code: Even if I can't write code, I usually can read it sufficiently to 'get the gist'.

F96_3-CE worked OOTB on my desktop. But this is also just an initial reconnoiter. It's fast. But with RAM usage @ 394 Mbs on boot-up, that's more than twice the amount required by my recent Tahrpup64 updated. On the other hand, unlike that Tahrpup64, F96_3-CE ran every AppImage and portable web-browser and recent video editor I threw at it. 394 Mbs isn't significant on today's computers.

Osmo doesn't sport a Contact module. Osmo from EasyOS can be installed and does.

@ dimkr: I like conman. It's fast and efficient. I have only two 'petty annoyances'. (a) There should be a way to 'un-hide' the password being typed. Not everyone's fingers always do what their brains tell them. It would be good to know when a scribner's error occurred. (b) Between my router and my computer is a wifi-extender which enhances the router's wifi signal** before relaying it. The router's signal is encrypted and all wifi applications show it as such requiring input of the password. The relay from the extender shows up as a separate signal 'unencrypted'. But it really isn't. It requires that the same password as the direct signal. Both SNS and frisbee's GUI enable recording that. As far as I know, Conman doesn't.

-=-=-=-=-=-
* Even if a Puppy were to be built @ github, one of these possibilities should exist: (a) woof's code could download an application from wherever its online location is; (b) a folder @ github could hold the application; or both.

** There are actually 2 signals, one of which is 5G, but weaker. My desktop's adapter doesn't 'see' 5G signals. My laptop --closer to the router-- 'sees' 4 networks; and often the 5G as enhanced by the extender is the strongest.

[wizard]

@mikeslr

Interesting observation about ram usage. Here are 3 images of TOP in terminal for F95, F96, and F96radky. The 96's are taking more than 95.
wizard

f95-bootram.png (302.75 KiB) Viewed 2555 times

f96-3-bootram.png (51.03 KiB) Viewed 2555 times

f96-3radky-bootram.png (58.21 KiB) Viewed 2561 times

[wizard]

@rockedge
@radky

Third pass on F96-3. Added a status column to sheet to show resolutions. Doing cursory test on F96_3-radkyCE.iso and find some issues from F96-3 are OK. Going forward, should we wait for another release to resume testing?

Thanks
wizard

f963.xls

(16.5 KiB) Downloaded 106 times

[radky]

Concerning udev, in recent Vanilla Dpup the /etc/udev/hwdb.d folder is empty.

/usr/lib/udev/hwdb.d

(And, AFAIK, hwdb.d is unused in every Puppy built before https://github.com/puppylinux-woof-CE/woof-CE/pull/3520, but I could be wrong)

Thank you dimkr !

[radky]

@wizard questions:

1 - Quicksetup dropdown boxes have no scroll bars

Response: The legacy gtk combobox widget provides the scrollbars for the Quicksetup drop-down lists in older Pups. However, the combobox widget is now deprecated and replaced by comboboxtext and comboboxentry widgets in new Woof-CE Pups. Certainly, using the mouse scroll wheel or arrow keys to view long lists can be tedious, but you can move relatively quickly through the list by using the PgUp and PgDn keys.

2 - Conky does not show ip address

Response: Conky displays my IP address correctly, but I don't actually use this application. Maybe more experienced users will provide a better response.

3 - Default app-chooser needs default settings

Response: Fixed in next release

4 - Redshift does not start

Response: Fixed in next release

5 - Bluetooth pairs with speaker, does not show up in Pulse Audio devices

Response: I have no experience with bluetooth. Maybe other users will help.

6a - Input wizard has no mouse settings
6b - No internet connection wizard other than default connman application

Response: FP96 has the new input-wizard of woof-CE, and Connman is the new internet connection manager. Both utilities are now standard in recent Dpups by dimkr.

Maybe dimkr will answer any specific questions you may have about current or future development of these applications.

7 - Rox right click menu missing many items

Response: Fixed in next release

9 - Help opens Abiword

Response: For me, the menu Help option correctly opens file:///usr/share/doc/index.html

10 - Access to markdown language in FP96

Response: The next release will have a convenient ROX right-click option to view markdown files.

[fr-ke]

Hi,

conky does not show ip address:

My ethernet interface is enp1s0. When I swap eth0 for enp1s0 in conkyrc it shows the IP.
I don't have wifi, so I can't comment on that.

Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
Ethernet device [0200] Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
• Kernel Driver igb
-- --
Ethernet device [0200] Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
• Kernel Driver igb
• Memory Used 180.00 KB
• Path /lib/modules/6.0.5-lxpup64/kernel/drivers/net/ethernet/intel/igb/igb.ko
• Description Intel(R) Gigabit Ethernet Network Driver

IP-Info: Interface enp1s0

regards
fr-ke

[dimkr]

7 - Rox right click menu missing many items

If these right-click menu items are added https://github.com/puppylinux-woof-CE/w ... /rox-filer, they will appear in any Puppy built using woof-CE that uses the ROX-Filer petbuild instead of some old prebuilt package.

This is not the first time I see this complaint, so let's just fix it?

[fr-ke]

iptables rules wrong order

I need port 54925,UDP open for my scanners and 22000,TCP for syncthing. If I add the appropriate rules to the firewall setup under Extras, port 22000,TCP can be reached. But not the UDP port 54925.
If I understand correctly, Firewall Setup creates the file /etc/init.d/rc.firewall.
In rc.firewall, the additional rules, Custom Extras, for TCP come before the RETURN rule, but the additional UDP rules come after the corresponding RETURN rule.

I'm not a programmer and I hope I got this right.

/etc/init.d/rc.firewall, partially:

Line 565 bis 596
# Not matched, so return for logging
$IPT -A udp_inbound -p UDP -j RETURN
$IP6T -A udp_inbound -p UDP -j RETURN

# udp_outbound chain
#
# This chain is used with a private network to prevent forwarding for
# UDP requests on specific protocols. Applied to the FORWARD rule from
# the internal network. Ends with an ACCEPT

# No match, so ACCEPT
$IPT -A udp_outbound -p UDP -s 0/0 -j ACCEPT

# tcp_inbound chain
#
# This chain is used to allow inbound connections to the
# system/gateway. Use with care. It defaults to none.
# It's applied on INPUT from the external or Internet interface.

############################### Custom Extras #################################

# Custom entry for port 22000
$IPT -A tcp_inbound -p TCP -s 0/0 --destination-port 22000 -j ACCEPT
# Custom entry for port 54925
$IPT -A udp_inbound -p UDP -s 0/0 --destination-port 54925 -j ACCEPT

############################## END Custom Extras ##############################

# Not matched, so return so it will be logged
$IPT -A tcp_inbound -p TCP -j RETURN

Output from iptables -v -L partially:

Chain tcp_inbound (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT tcp -- any any anywhere anywhere tcp dpt:22000
0 0 RETURN tcp -- any any anywhere anywhere

Chain udp_inbound (1 references)
pkts bytes target prot opt in out source destination
0 0 DROP udp -- any any anywhere anywhere udp dpt:netbios-ns
0 0 DROP udp -- any any anywhere anywhere udp dpt:netbios-dgm
0 0 ACCEPT udp -- any any anywhere anywhere udp spt:bootps dpt:bootpc
10 1442 RETURN udp -- any any anywhere anywhere
0 0 ACCEPT udp -- any any anywhere anywhere udp dpt:54925

F96_3-radkyCE pristine frugal install