VoidPup32 and VoidPup64 Discussion

[Marv]

Updated the 240907 version on the S761 2nd gen i5 laptop to the 240919 version. Seems fine on first boot, dmesg clean, idle resource use good, all portables working etc. BUT it now has the same failure on suspend/resume that BW64 does on this hardware and has had since 10.0.4.

Unless I remove psmouse prior to suspend, modprobe it on resume, wait 8 seconds and reload the synaptics touchpad properties the touchpad button mapping on resume is completely wrong. -closing a window opens a duplicate instead etc.- Voidpup64 240907 was an intermediate case, there I could get away with just reloading the touchpad properties.

As of now, I either freeze Voidpup64 at 240803 on these machines or just not use it on them. One by one, puppies Built on Woof-CE Github have fallen prey to this. non Github builds like LxPupSc64 and the fossapup64 series, and so far JammyPup64 and NoblePup64 have avoided it.

In BW64, it was between 10.0.3 and 10.0.4, in VoidPup64 it was between the 240803 build and the 240825 build. I can't isolate it further except that it is in the main SFS and is kernel independent.

Alas,

[Jasper]

@Xanegon

components.png

Devx - contains the developer tools for compiling applications
Docx - contain the documentation/help files
Nlsx - contains the 'Native Language Support' for non-English users
Kernel_sources - contains the code to enable you to compile device drivers eg Nvidia graphics drivers
LXDE - is an alternative Window Manager (the default one is JWM - Joe's Window Manager)

[peebee]

There is a problem with VoidPup-241006

mesa has a new dependency - mesa-gallium - which is huge.....

The build boots OK on my Nvidia desktop but @Marv has reported it fails on his Intel laptop.

Not sure what to do as yet.

Use with caution.

[rcrsn51]

You should also check the functionality of the yassm 4.8 that you dropped into the ISO. It would make more sense to get the PET instead of the DEB. Also, it would be nice to participate in the testing.

[Clarity]

Boot status is reported in a table, here

[Jasper]

I am using the latest build of VoidPup64-241006 and have no issues on two Intel devices i915 & Gemini Lake.

[rcrsn51]

@Jasper I notice that you did this with the intel Xorg driver. It definitely does NOT work with the default (modesetting?) driver.

[Jasper]

This is on the i915 hardware with no 'Fdrv' included just the

• vmlinux

• zdrv

[Jasper]

@rcrsn51 ........... yes it does work with the default 'modesetting'

I did edit the xorg.conf file and changed it from modesetting to Intel only on the i915.

[Jasper]

Also, changed the setting on the Gemini Lake from 'modesetting' to 'Intel'

As you can see this does include the Fdrv from the ISO.

[peebee]

Version 241009 is uploaded - with added mesa-libgallium & libv3 - seems to fix the xorgwizard modesetting issue.

[Jasper]

install-va-info.png

va-info.png

[peebee]

Version 241009 seems to fix the xorgwizard modesetting issue on my laptop.

[Clarity]

VoidPup64 v241009 tested: Notice the change in launches. In a KVM: SG2D and Ventoy, now, land in the same spot without starting the desktop; namely the distro's console. Xorgwizard is no help,either.

Edit: Bare Metal boots to desktop as shown in the table.

[rcrsn51]

I just tested 241009 on several machines with ISObooter and it now works fine.

[Jasper]

@peebee

Hi there, can you explain to me the build number for these releases?

VoidPup64-22.02-241009

Does the highlighted number refer to when the initial release was created?

The reason why I am asking is that the current live image for Void Linux is 14 March 2024 ie

void-live-x86_64-20240314.base.iso

So, is this the foundation for new releases? Or are you using a previous build release back in February 2022?

[peebee]

@peebee

Hi there, can you explain to me the build number for these releases?

VoidPup64-22.02-241009

Does the highlighted number refer to when the initial release was created?

The reason why I am asking is that the current live image for Void Linux is 14 March 2024 ie

void-live-x86_64-20240314.base.iso

So, is this the foundation for new releases? Or are you using a previous build release back in February 2022?

22.02 is when VoidPup first arrived. This doesn't change between builds and is part of the sfs naming.

241009 is when the latest Github build was done.

VoidPup builds use the latest Void components available at the time of the build - they have nothing to do with the Void-live isos..... I have no idea how or when the isos are built. I would assume that the first thing you'd do with a 240314 iso would be to do a big vpm update as it is quite out of date.

[Jasper]

@peebee

From my limited understanding is that are base ISO's available .... basic & XFCE.

Then 'rolling' releases are simply the 'base' and the 'new' updated application packages.

I might be wrong in my thinking.

[Fredk6]

VoidPup32-22.02-241009.
"Chromium_129.0.6668.58_lxsc_spot.sfs " is ok with default profile only, but if another profile is added, the profile menu doesn't open on startup.

[peebee]

VoidPup32-22.02-241009.
"Chromium_129.0.6668.58_lxsc_spot.sfs " is ok with default profile only, but if another profile is added, the profile menu doesn't open on startup.

Sorry - don't understand what the problem is! Which "profile menu"?

How did the 2nd invocation of /opt/chromium/chromium with very different switches occur?? with 46% cpu?

tracker-miner-fs-3 ??? with 42% cpu? why is this running?

It is in fact a process of tracker, GNOME's file indexer. It is used to index the names and contents of your files in order to easily search and access them in Nautilus

[Fredk6]

Thanks,
You may try to add a profile to your chromium, if it open, then my computer is the problem and you may delete my posts.

Sorry - don't understand what the problem is! Which "profile menu"?

Screenshot.jpg (40.48 KiB) Viewed 1786 times

It open when there are more then 1 profile. Here, with more than 1 profile, it is an empty window (see below).
[

Screenshot(1).jpg (21.93 KiB) Viewed 1786 times

How did the 2nd invocation of /opt/chromium/chromium with very different switches occur?? with 46% cpu?

Don't know, it stay like this indefinitely.

tracker-miner-fs-3 ??? with 42% cpu? why is this running?

Have tried with no save file (no tracker).

Screenshot(2).jpg (154.63 KiB) Viewed 1786 times

[peebee]

VoidPup32-22.02-241009.
"Chromium_129.0.6668.58_lxsc_spot.sfs " is ok with default profile only, but if another profile is added, the profile menu doesn't open on startup.

32-bit Chromium is becoming an increasing problem.
There does seem to be a serious issue with the 32-bit Chromium .sfs from Void.
Can you move to a 64-bit build rather than 32-bit? That would be better long-term.
If you have to stick with 32-bit, I suggest trying the chromium-ungoogled from Alien-Bob - that runs on VoidPup32 and seems to do profiles OK:
https://sourceforge.net/projects/lxpup/ ... /browsers/
https://sourceforge.net/projects/lxpup/ ... s/download
chromium_ungoogled_129.0.6668.70 RUNS-AS-SPOT :2cf7f6797c1c0d8213afdb0fcc1b23ea

[Marv]

Updated my frugal install to SSD on the all intel Fujitsu S761 (2nd gen i5, Sandylake) from the 241009 version to the 241101 version.
Using my @peebee derived LXDE ydrive plus customizations so no JWM checks unless requested. Adrive not used as usual. Running AUFS at the moment.
Booted both with the supplied 6.1.x kernel and with the 6.6.53 from the 241009 version.. Currently running with that (as I understand that should be prior to the latest AUFS dustuo) as the suspend on this hardware is cleaner with the 6.6.x kernel and newer. Clean dmesg, excellent idle resource use, all portables and lidsuspend continue to work normally., intel video driver used at boot with no intervention required. Posting from the portable Brave, updated to the current version, now.

Just my looksee but seems all good here. I'll use as my daily -had been running pretty much in @ozsouths' NoblePup64-low- for a bit and do some multimedia checks etc.

Thanks,

[N97]

There is a bug or 2 in VoidPup 20241009

1.) Grub NOT installed, drag n drop CD--> devsave fixed. But redo from start!
2.) in grub cfg insmod fat32 must be added

MHO, using msFAT a bad idea, make these installers accept ext3... i see exfat, ext2, and f2fs allowed... i guess whats needed is isolinux 64-bit.
BTW no more of this single partition kitch... a boot partition of say 4Gb should suffice, with remainder for storage.

Installed FF128.5.1 esr in ~ and transferred bookmarks and added extensions.

This N97 flies! Using it now.

Regards N97 formerly Opi5b.
Its good to be a Puppian again

[Jasper]

@peebee

Just an observation really ........... my previous build/s of VoidPup64 on a USB flash drive installation created a 'save folder'. Created using StickPup.

With the latest iteration Dec 2024, this has now reverted back to a 'save file'; same device.

I only realised this when my previous 'save folder' was not recognised.

Was this a bug previously allowing me to use PupSave66 instead of PupSave13? ...... hope I have got that right

[Jasper]

This a handy application to use.

For some reason it does not copy files to this location, but required me to choose /root as a new location.

[Marv]

Updated my frugal VoidPup64 install to SSD on one of the new-to-me all intel Fujitsu U747 (6nd gen i5, Sandylake) from the 241201 version to the 250101 version. No CD/DVD drives on any of my new kids so no checks there. I do have several of the 2nd gen S761s still alive so if necessary they can drive CD/DVD.

Using my @peebee derived LXDE ydrive plus customizations so no JWM checks unless requested. Adrive not used as usual. Running overlayfs at the moment.

Booted both with the supplied 6.6.68 kernel and with the 6.12.3. Currently running with that though the 6th gen i5 (skylake) laptops seem to have no lidsuspend bugs (although a completely different intel_pstate governor paradigm on these laptops , still learning there). Still fiddling with the new touchpad settings also.

Clean dmesg with NO fails or warnings. Excellent idle resource use, all portables and lidsuspend continue to work normally., Modesetting video driver used as the default on first boot, haven't fiddled with that, performance 'feels' snappy.

Posting in that install from the portable Brave, updated to the current version, now.

Happy new year indeed

[N97]

Voidpup64-22.02 has some bugs and omissions that need fixing...

1.) the grub cfg file needs 'insmod fat32'

2.) using BOOT FLASH --> Create UEFI USB
a.) the grub cfg file NOT installed
b.) the Boot directory NOT installed

3.) There MUST be some file that loads/installs a microcode update,
NOT in fdrv, or in /lib/firmware. dmesg | grep microcode indicates a properly placed microcode update NO install.
What is the name of this installer?, and where can i get a copy for this os? and where do i put it?

N97

[peebee]

Voidpup64-22.02 has some bugs and omissions that need fixing...

1.) the grub cfg file needs 'insmod fat32'

Woof-CE issue applies to all builds:
https://github.com/puppylinux-woof-CE/w ... iso.sh#L27

[Marv]

3.) There MUST be some file that loads/installs a microcode update,
NOT in fdrv, or in /lib/firmware. dmesg | grep microcode indicates a properly placed microcode update NO install.
What is the name of this installer?, and where can i get a copy for this os? and where do i put it?

N97

I, like ozsouth, use the 'old school' method of early loading -in my 'old school' installs. I place the current microcode, ucode.cpio in my case, in a directory 'microcode', in the same partition and at the same level as my other puppy boot directories. I share whatever is the most recent cpio amongst all of my pups. I pass the following as a kernel parameter: /microcode/ucode.cpio in all the pup items in my menu.list. An example item is:

title NoblePup64 version 241124, peebee LXDE drive plus my configs and synaptics drivers in adrive, trialing ozsouth 6.11.6 kernel
uuid 2685-7828
kernel /NoblePup64/vmlinuz punionfs=overlay net.ifnames=0 pmedia=ataflash psubdir=NoblePup64 pfix=copy,fsck,fsckp ipv6.disable=1
initrd /microcode/ucode.cpio /NoblePup64/initrd.gz

Works in all my pups from fossapup64 9.5 up through the current NoblePup64 and VoidPup64. All of the kernels I'm using are version 6.6.x or 6.12.x but I've used it with much older kernels and with very similar adds to the grub configuration file in a grub2config install. Also with the dated microcode files such microcode-update-20241121-64.cpio.

grepping for microcode in dmesg will show if the load occurs. One thing I ran into on a new-to-me Lenovo X1 carbon was that the early load didn't occur. The reason was that I had just updated the UEFI/BIOS and the code version therein was newer than the ucode version. The kernel didn't squawk, just didn't perform the early load.

I've briefly looked for the magic fdrive installer but didn't see it, could just be me...