KLV-Airedale-beta20.2 is Available.

[rockedge]

KLV-Airedale-beta20.2
https://klv-airedale.rockedge.org/

Only changes are a routine system update and the addition of gxmessage in the default rootfs.

save2flash has been expanded to handle persistence on FAT32 and NTFS partitions.
The mksplash GUI utility to create splash notification banners.

has the latest FirstRib skeleton initrd v6.0-rc1 supplying the initrd.gz
and is currently equipped with the kernel 5.16.14-KLV (no AUFS5 support).
00modules-5.16.14-KLV-b19.sfs has the file structure -> /usr/lib/modules

The latest initrd.gz brings vFat and NTFS formatted partition support to KLV, allowing persistence on NTFS/vFat systems as well as the usual /ext2/ext3/ext4 /swap support.

• Beta20.2 has wiak's FirstRib skeleton initrd v6.0-rc1 and w_init_6.0-rc1
• the kernel's 00Module SFS file structure has been modified by moving /lib/modules to /usr/lib/modules
• included htop
• created a symlink /root/spot with the target /home/spot
• Auto login cleaned up.
• includes also the logout logic provided by fredx181 gives true mulit-user support.
• replaced loop.cfg to the most recent modifications.
• updated (latest 27/3/2022)save2flash to compliment initrd_v504-rc2.gz now initrd_v505-rc1.gz
• kernel 5.16.14-KLV (overlayfs built in and no aufs5) is used.
• added gtkhash

Plus the other important improvements contributed by the KLV team.


Added @fredx181's save2flash utility that can be used when KLV is started in RAM2 mode to perform session saves on demand for persistence.
This is similar to PUPMODE13 in Puppy Linux.

fredx181's swap partition enable script includes the latest revisions and also added are the packages

• mime-add-1.0_0.noarch.xbps
• edit-sfs-1.0_0.noarch.xbps

KLV-Airedale-beta4 is able to load squash SFS packages on the fly or during the boot sequence.
Squash files and ISO images can be opened from the file manager and the read the contents.

• can run with rootfs, 01fimware and 00module SFS files as uncompressed directories.
• Also able to load compressed and/or decompressed directories,
  once a 2 digit prefix is added to the file name.
• It is possible to mix using compressed squash files and uncompressed directories.

Also can be downloaded from https://rockedge.org/kernels in ISO->Kennel_Linux->Airedale

[Clarity]

Downloaded its ISO file to SG2D folder and booted directly to desktop. Total time to download 1.5 minutes and to boot the USB's ISO file was 1 min. Total time to desktop is 3 minutes included BIOS start on PC.

Performance is outstanding. All is well.

Edit: Tested ISO file booting. also, with QEMU-KVM. Again, performance is outstanding.

[Clarity]

Can we have/run BTOP on KLV without issues in the terminal? Reason: MUCH more useful information in a single terminal screen than HTOP. BTOP covers the spectrum of today's home LAN-WiFi system at a glance. And is consistent with info seen in Conky screens of today's PUPs who present them OOTB. In other words, it present complete details of one's PC activity more so than HTOP. (THIS IS NOT a request to abandon HTOP!!!)

Just a thought as others may have seen such, too.

Edit: I cant remember exactly, but there seemed to have been some issues with KLV's terminal from BTOP before. (true/not???)

[rockedge]

I run have run Btop using uxterm in KLV-Airedale

[user1234]

Hey @rockedge! I am totally new to KLV-Airedale and am trying to install it (version=beta20.2) on sda7 partition from Fossapup64. Runninng KLV from QEMU is totally fine, but I am not able to run it by installing it.

What have I done so far? -
This is my device's partition structure (unallocated space is there because of so many bad-blocks present mainly in that space)-

screenshot_2022-10-11_1366x768.png (116.08 KiB) Viewed 962 times

I mounted the .iso file and copied all the files over to sda7. Then I installed grub2 to sda1 (boot partition at front of sda). The grub.cfg looks like this-

Code: Select all

# grub.cfg produced by grub2config 2.0.1
set default=0
set timeout=10
set menu_color_normal=white/blue
set menu_color_highlight=black/yellow

loadfont $prefix/fonts/DejaVuSansMono18.pf2
set gfxmode=auto
insmod all_video
insmod gfxterm
terminal_output gfxterm

# Puppy Linux

menuentry 'Main Fossa'{
  search --no-floppy --set=root --fs-uuid f29bf877-5d71-4f7a-a7a5-ffbbd622aabf
  linux /vmlinuz     pmedia=atahd pfix=fsck
  initrd /initrd.gz
}

menuentry 'Main Fossa RAM mode'{
  search --no-floppy --set=root --fs-uuid f29bf877-5d71-4f7a-a7a5-ffbbd622aabf
  linux /vmlinuz     pfix=ram
  initrd /initrd.gz
}

menuentry 'Other Fossa'{
  search --no-floppy --set=root --fs-uuid 0f55dad4-d26b-4184-9279-84a5d9c8a8c2
  linux /vmlinuz     pmedia=atahd pfix=fsck
  initrd /initrd.gz
}

# Other Linux

menuentry 'KLV-Airedale'{
  search --no-floppy --set=root --fs-uuid eb279000-9497-49fb-a461-68a3551a4908
  configfile /boot/grub/grub.cfg
#  linux /vmlinuz/initrd.gz root=UUID=eb279000-9497-49fb-a461-68a3551a4908 quiet splash
#  initrd /initrd.gz
}

if [ $grub_platform = "efi" ] ; then
menuentry 'UEFI Firmware Settings'{
	fwsetup
}
fi

	# custom menu
	if [ -f /custom.cfg ] ;then source /custom.cfg ;fi

menuentry 'Previous  menu'{
	configfile /grub-prev.cfg
}

All files in sda1 are-

screenshot_2022-10-11_1366x768_000.png (30.1 KiB) Viewed 962 times

But when I try to boot KLV-Airedale, I get the grub screen for KLV. I select the default option (that RAM0 one). But after selecting it the screen would get stuck and waiting for a lot of time wouldn't help. The screen at that time would be having just the grub splash screen's background image and no text on it.

I think that the problem is that that I'm just copying the files over and not really installing anything.

And yes, I am on a 64-bit laptop.

Where am I going wrong, and how can I correct it?

[Caramel]

@user1234, the grub stanza needs the option w_boot=

Here i think it should be
linux /vmlinuz w_bootfrom=eb279000-9497-49fb-a461-68a3551a4908=/ net.ifnames=0

[rockedge]

@user1234 You are close to having it correctly setup to boot!

It appears that the boot stanza's are incorrect and using Puppy Linux kernel command line options. Some small changes will get you going.
Open the ISO file and copy all of the KLV-Airedale files to /mnt/sda7/KLV-Airedale (use which ever directory name you prefer)

Now modify the Grub2 boot stanza's to reflect the correct partition and location of the KLV components:

This entry is wrong:

Code: Select all

menuentry 'KLV-Airedale'{
  search --no-floppy --set=root --fs-uuid eb279000-9497-49fb-a461-68a3551a4908
  configfile /boot/grub/grub.cfg
#  linux /vmlinuz/initrd.gz root=UUID=eb279000-9497-49fb-a461-68a3551a4908 quiet splash
#  initrd /initrd.gz
}

This example uses the UUID of the partition that KLV is located on:
in a terminal use blkid to identify the UUID and the LABEL names of all the partitions on the system. Then use your UUID or LABEL and replace those in the examples.

Code: Select all

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /KLV-Airedale-beta20.2/vmlinuz w_bootfrom=UUID=eb279000-9497-49fb-a461-68a3551a4908=/KLV-Airedale-beta20.2 net.ifnames=0
  initrd /KLV-Airedale-beta20.2/initrd.gz

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /KLV-Airedale-beta20.2/vmlinuz w_bootfrom=LABEL=KLV-airedale=/KLV-Airedale-beta20.2 net.ifnames=0
  initrd /KLV-Airedale-beta20.2/initrd.gz  
  
  

or for Grub4Dos ->

Code: Select all

title KLV-Airedale-beta20.2 (LABEL)
  uuid 8a8ea99d-a1b0-4c43-b1a0-d4ce5c9c7dfa
  kernel /KLV-Airedale-beta2120.2/vmlinuz  w_bootfrom=LABEL=psystem=/KLV-Airedale-beta21 net.ifnames=0
  initrd /KLV-Airedale-beta21/initrd.gz

[user1234]

@user1234 You are close to having it correctly setup to boot!

It appears that the boot stanza's are incorrect and using Puppy Linux kernel command line options. Some small changes will get you going.
Open the ISO file and copy all of the KLV-Airedale files to /mnt/sda7/KLV-Airedale (use which ever directory name you prefer)

Now modify the Grub2 boot stanza's to reflect the correct partition and location of the KLV components:

This entry is wrong:

Code: Select all

menuentry 'KLV-Airedale'{
  search --no-floppy --set=root --fs-uuid eb279000-9497-49fb-a461-68a3551a4908
  configfile /boot/grub/grub.cfg
#  linux /vmlinuz/initrd.gz root=UUID=eb279000-9497-49fb-a461-68a3551a4908 quiet splash
#  initrd /initrd.gz
}

This example uses the UUID of the partition that KLV is located on:
in a terminal use blkid to identify the UUID and the LABEL names of all the partitions on the system. Then use your UUID or LABEL and replace those in the examples.

Code: Select all

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /KLV-Airedale-beta20.2/vmlinuz w_bootfrom=UUID=eb279000-9497-49fb-a461-68a3551a4908=/KLV-Airedale-beta20.2 net.ifnames=0
  initrd /KLV-Airedale-beta20.2/initrd.gz

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /KLV-Airedale-beta20.2/vmlinuz w_bootfrom=LABEL=KLV-airedale=/KLV-Airedale-beta20.2 net.ifnames=0
  initrd /KLV-Airedale-beta20.2/initrd.gz  
  
  

or for Grub4Dos ->

Code: Select all

title KLV-Airedale-beta20.2 (LABEL)
  uuid 8a8ea99d-a1b0-4c43-b1a0-d4ce5c9c7dfa
  kernel /KLV-Airedale-beta2120.2/vmlinuz  w_bootfrom=LABEL=psystem=/KLV-Airedale-beta21 net.ifnames=0
  initrd /KLV-Airedale-beta21/initrd.gz

Thanks @rockedge for explanation. I will surely try the above solution.

Just to take into your consideration that-

Code: Select all

menuentry 'KLV-Airedale'{
  search --no-floppy --set=root --fs-uuid eb279000-9497-49fb-a461-68a3551a4908
  configfile /boot/grub/grub.cfg
#  linux /vmlinuz/initrd.gz root=UUID=eb279000-9497-49fb-a461-68a3551a4908 quiet splash
#  initrd /initrd.gz
}

here the linux and initrd lines are commented, but rather the grub configfile in sda7 is set as the configfile which opens that grub menu. But I had not changed anything in the grub configfile of KLV, so I think that w_bootfrom must not be correctly setup.

Also, I don't particularly understand that syntax of w_bootfrom. So can you please post the w_bootfrom which needs to be set if KLV-Airedale files are located at the top level directory of sda7, i.e. no subdirectories contain the KLV-Airedale files?

Thanks!

Edit: Ok, so I got it right. Found that KLV-Airedale-beta20.2 that you wrote in the answer was just the directory name, so I removed it and got my computer booting.

What I understand w_bootfrom must be written as is like this-

Code: Select all

w_bootfrom=UUID/LABEL=name/uuid of partition=directory containing KLV

Is this right?

Another question
How do you pronounce KLV-Airedale-
KLV-Airy-dale or KLV-Air-re-dale .

[rockedge]

try:

Code: Select all

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /vmlinuz w_bootfrom=UUID=eb279000-9497-49fb-a461-68a3551a4908=/ net.ifnames=0
  initrd /initrd.gz

menuentry "KLV-Airedale-beta20.2" {
  insmod ext4
  search --no-floppy --fs-uuid --set  eb279000-9497-49fb-a461-68a3551a4908
  linux /vmlinuz w_bootfrom=LABEL=KLV-airedale=/  net.ifnames=0
  initrd /initrd.gz 

[user1234]

I am facing an issue-https://unix.stackexchange.com/question ... ot-present. Please help.

[fredx181]

I am facing an issue-https://unix.stackexchange.com/question ... ot-present. Please help.

Yes, it's included in the rootfs as a character device, shouldn't be, apparently something went wrong in this build (edit: also in latest beta21 btw).
EDIT: a character device here works similar as in Puppy .wh file (will "mask" a file).
It shows in filemanager in the rootfs mountpoint:

Screenshot.png (28.4 KiB) Viewed 741 times

[user1234]

So @fredx181, any solution for removing that, in puppy terms "whitelisted" file, and replacing it with a fit one.

Also, I am now not able to connect to bluetooth (I am very new to void linux and likes... just 3 days of experience ). When I try to do rfkill list all, it lists only this-

Code: Select all

0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Which of course is not having bluetooth in it. And yes, I am booting directly (not on qemu) on my laptop. Bluetooth seems to work on puppy, but is not listed here. I have tried installing bluez (and blueman as well) from OctoXBPS, and sym-linked bluetoothd's directory to /var/service/ (as explained here, first command). I have even tried to reboot, in case reboot was needed. Here is my grub.cfg KLV menuentry-

Code: Select all

menuentry 'KLV-Airedale'{
  search --no-floppy --set=root --fs-uuid eb279000-9497-49fb-a461-68a3551a4908
  linux /vmlinuz w_bootfrom=UUID=eb279000-9497-49fb-a461-68a3551a4908=/ net.ifnames=0
  initrd /initrd.gz
}

I doubt if net.ifnames=0 is the culprit here (just guessing, no idea really). How can I connect to bluetooth?

Edit: net.ifnames=0 doesn't seem to be the culprit, as it is defined here. Still would try to change it to 1 and see what results does it yield.

[rockedge]

@user1234 I have not done much yet with Bluetooth. I have one laptop left that has Bluetooth. I see what it takes to get Bluetooth connectivity going in KLV.

This moment I am looking to solve what happened to libgioenvironmentproxy.so to cause it to be whitelisted!

[rockedge]

@fredx181 I also can see the file! How and why did it get whitelisted? A mystery. I will see how to fix it!

[fredx181]

So @fredx181, any solution for removing that, in puppy terms "whitelisted" file, and replacing it with a fit one.

Tried to figure out which package this file belongs to, but couldn't, in most distro's it's in "glib-networking" but apparently not in void.
(it would be a matter of re-installing the correct package then, I guess)

EDIT;

@fredx181 I also can see the file! How and why did it get whitelisted? A mystery. I will see how to fix it!

Yes, very strange indeed, I don't have any idea how that can happen.

EDIT: Do you know how to find out which package a file belongs ? Tried xlocate but didn't work.

[fredx181]

So @fredx181, any solution for removing that, in puppy terms "whitelisted" file, and replacing it with a fit one.

Tried to figure out which package this file belongs to, but couldn't, in most distro's it's in "glib-networking" but apparently not in void.
(it would be a matter of re-installing the correct package then, I guess)

EDIT;

@fredx181 I also can see the file! How and why did it get whitelisted? A mystery. I will see how to fix it!

Yes, very strange indeed, I don't have any idea how that can happen.

EDIT: Do you know how to find out which package a file belongs ? Tried xlocate but didn't work.

[user1234]

So @fredx181, any solution for removing that, in puppy terms "whitelisted" file, and replacing it with a fit one.

Tried to figure out which package this file belongs to, but couldn't, in most distro's it's in "glib-networking" but apparently not in void.
(it would be a matter of re-installing the correct package then, I guess)

EDIT;

@fredx181 I also can see the file! How and why did it get whitelisted? A mystery. I will see how to fix it!

Yes, very strange indeed, I don't have any idea how that can happen.

EDIT: Do you know how to find out which package a file belongs ? Tried xlocate but didn't work.

I tried reinstalling glib-networking. Seems to show the file now. Try running in a terminal

Code: Select all

xbps-install -f glib-networking

[fredx181]

I tried reinstalling glib-networking. Seems to show the file now.

Well, I did too reinstall glib-networking and it's not showing that file for me (and also not as character device file anymore):

Code: Select all

root# ls -l /usr/lib/gio/modules
total 565
-rw-r--r-- 1 root root    318 Oct 14 17:29 giomodule.cache
-rwxr-xr-x 1 root root  55280 Apr  9  2021 libdconfsettings.so
-rwxr-xr-x 1 root root  22440 Sep 26 18:48 libgiognomeproxy.so
-rwxr-xr-x 1 root root 124968 Sep 26 18:48 libgiognutls.so
-rwxr-xr-x 1 root root  18344 Sep 26 18:48 libgiolibproxy.so
-rwxr-xr-x 1 root root 108544 Jul  5 18:42 libgioremote-volume-monitor.so
-rwxr-xr-x 1 root root 203016 Jul  5 18:42 libgvfsdbus.so
-rwxr-xr-x 1 root root  34728 Dec 31  2020 libxfconfgsettingsbackend.so

But.... the "not found' error that some commands (e.g. yad and earlier reported error msg by @Sofiya ) gave is gone, so maybe the file libgioenvironmentproxy.so doesn't belong in void anyway ?

[rockedge]

@fredx181, @user1234 I feel like the rolling update removed it between beta20 and beta20.2. Just like the original gtkdiallog was in Void Linux then removed from the repo's and that's why we have the SFS addon to supply it. I wonder now if the larger rolling update had depreciated the libgioenvironmentproxy.so component

[user1234]

I tried reinstalling glib-networking. Seems to show the file now.

Well, I did too reinstall glib-networking and it's not showing that file for me (and also not as character device file anymore):

Code: Select all

root# ls -l /usr/lib/gio/modules
total 565
-rw-r--r-- 1 root root    318 Oct 14 17:29 giomodule.cache
-rwxr-xr-x 1 root root  55280 Apr  9  2021 libdconfsettings.so
-rwxr-xr-x 1 root root  22440 Sep 26 18:48 libgiognomeproxy.so
-rwxr-xr-x 1 root root 124968 Sep 26 18:48 libgiognutls.so
-rwxr-xr-x 1 root root  18344 Sep 26 18:48 libgiolibproxy.so
-rwxr-xr-x 1 root root 108544 Jul  5 18:42 libgioremote-volume-monitor.so
-rwxr-xr-x 1 root root 203016 Jul  5 18:42 libgvfsdbus.so
-rwxr-xr-x 1 root root  34728 Dec 31  2020 libxfconfgsettingsbackend.so

But.... the "not found' error that some commands (e.g. yad and earlier reported error msg by @Sofiya ) gave is gone, so maybe the file libgioenvironmentproxy.so doesn't belong in void anyway ?

Didn't check if the file was found or not. Just saw that applications didn't report any error this time, so posted without checking . I think @rockedge has got the right answer.

[rockedge]

I copied the usr/lib/gio/modules from beta19 to beta21 which fixed the libgioenvironmentproxy.so missing error, for now.

Odd was in a QEMU machine I just installed glib-networking and that fixed it there but on a bare metal machine the install did not have the same result. Some mystery still surrounds the exact fix but for now beta21 seems alright.