KLV-Airedale-sr3 with Void Linux Kernel 6.4.7_1

[rockedge]

KLV-Airedale-sr3
Kennel Linux Void Airedale Stable Release 3 826 MiB download size ↓
KLV-Airedale-sr3
SHA1-MD5.txt
Download from SOURCEFORGE

This is Stable Release version 3
with a complete system update/upgrade and outfitted with a Void Linux kernel 6.4.7_1 on 08/04/2023
Has Firefox 116.0 for a built in browser.

Features full SAMBA support and managed by a modified for KLV Samba Simple Management GUI script, borrowed from F96-CE_4.

This version is equipped with 01firmware-6.1.38.sfs borrowed from Puppy Linux huge kernel 6.1.38-rt13c.

The team fine tuned login/logout with a long term solution utilizing the Void Linux service manager runit to fix a conflict after upgrades to the runit-void package added a service directory agetty-tty1 that conflicts with KLV's custom agetty-autologin-tty1 during logout/login causing difficulty in changing user. Adding a file called : /etc/sv/agetty-tty1/down instructs runit to disable the service which is persistent across reboots.

The initrd.gz and w_init are upgraded to version 7.0.1-rc1 which are constructed from the latest FirstRib skeleton-initrd.

Added the symlink gtk2dialog that targets the binary gtkdialog-8.5 which is compiled against GTK2 which gives access to either gtk2 or gtk3.

@fredx181 has repaired a bug in save2flash and modified swapper.sh to adapt for the /mnt/home device showing directly in Thunar and on the desktop. swapper.sh activates any swap partitions available to KLV-Airedale during system start.

From a suggestion by @wiak added in a modification to w_init that will display icons for /mnt/home partition in Thunar and on the desktop.

New and improved tuning of the /boot directory boot stanza's. improving the reliability of booting in QEMU, Ventoy and S2SG.

Improved and rebuilt initrd.qz including expanded support for SD cards.

Routine system update/upgrade. And wallpapers from @Sofiya are included, replacing some of the stock xfce4 backgrounds.

@wiak has again done more work improving the boot system menus and further improvement to the initrd.gz boot mechanisms :

The iso config file boot/grub/menu.lst is used to boot from cdrom using that internal to ISO provided menu.lst (i.e. he currently uses grub4dos for that purpose).
The ISO config file boot/grub/loopback.cfg is used (per usual) to provide the boot menu for SG2D
The ISO config file boot/grub/grub.cfg is used by Ventoy (but included no Ventoy compatible entries until my alterations below)

I have made some modifications to all of the above (though have left previous entries in place for later experimentation and possible modification or deletion).
In particular I have provided the ability when booting via SG2D or Ventoy of using the FR modes:

a. RAM0 for session changes in RAM only (i.e. no save persistence)
b. RAM2 save on demand mode back to upper_changes folder (or ucimg savefile) in same directory iso is stored (or in subdirectory if symlink manually made to iso).
c. RAM2 save on demand mode back to upper_changes folder in, Clarity suggested, partition with LABEL 'Persistence' and directory 'Sessions'
d. Direct save (not in RAM) back to upper_changes folder (or ucimg savefile) in same directory iso is stored (or in subdirectory if symlink manually made to iso).
e. Direct save (not in RAM) back to upper_changes folder in, Clarity suggested, partition with LABEL 'Persistence' and directory 'Sessions'

No editing of the presented SG2D or Ventoy boot menus will be required to achieve these most useful FR initrd modes. User just needs to put the KLV iso in BOOTISOS (or wherever it is put usually) and boot...

starting of the pulseaudio system for any user that is logged in has been fixed and improved. Thanks wiak, Sofiya and fredx181 for the exact steps.

Upgraded to a new version of @fredx181 's save2flash, and set LANG=en_US.UTF-8 in /etc/environment as default localization.

Thanks to @Sofiya for the poorercputemp and Display Control packages that also have been added to desktop.

• Grub4Dos is now included in the System menu. Making KLV-Airedale capable of setting up a boot-able device using GParted and Grub4Dos.

• CUPS starting as a service has been added and is working thanks to @rcrsn51 spotting missing components!

This is constructed from KLV-Airedale-beta27->rc1->rc2->rc3->rc4->rc4.1 and is equipped with a Void Linux kernel version 6.0.12_1 SMP PREEMPT_DYNAMIC constructed with @wiak 's scripts that will extract the Void Linux kernel for KLV. Also has had a system wide upgrade. Uses an initrd.gz based on the FirstRib skeleton initrd.gz constructed by the kernel/module creation script. Firmware SFS is from a woof-CE kernel-kit built huge 6.0.0-1 kernel.

KLV-Airedale-rc16 is just as at home on FAT32, NTFS prtitions as it is running from ext2/3/4 formatted partitions.

Also included is wiak's generate a set of boot stanzas script. fredx181's mksplash has a menu entry and the remaster script is installed.

With the addition of a xfce4 desktop tiling configuration. A tip from wiak for configuring Tiling windows done with the Super (Windows) key and an up, down, left, right, home, pgup, pgdown or end key.

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.

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.

• included htop, Grub4Dos, CUPS

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

• Debian kernel 6.0.0-3-KLV SMP PREEMPT DYNAMIC 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-beta25 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

[Sofiya]

during a quick test - no sound, devices cannot be found in Pavucontrol no choice of hardware configuration

[rockedge]

I tested it on 2 machines plus a QEMU VM and I have had luck that the pavucontrol is functioning as expected on all 3

Screenshot(35).jpg (26.6 KiB) Viewed 2318 times

[Sofiya]

I tested it on 2 machines plus a QEMU VM and I have had luck that the pavucontrol is functioning as expected on all 3

Screenshot(35).jpg

I have no choice in the configuration section. here is a picture from KLA, but this is not in KLV
AMD drivers are missing along the way

[rockedge]

@Sofiya Is still working in KLV-Airedale-sr2?

[Sofiya]

Apparently I need firmware Upup

[Sofiya]

@Sofiya Is still working in KLV-Airedale-sr2?

I can't say this because I'm jumping from sr1 to sr3

[rockedge]

@Sofiya it was okay with sr1? There have been reports of problems with 6.4+ kernels. Perhaps I will use the same kernel from sr2 on sr3 and wait to see when the 6.4+ series kernels are again stable.

[Sofiya]

@Sofiya it was okay with sr1? There have been reports of problems with 6.4+ kernels. Perhaps I will use the same kernel from sr2 on sr3 and wait to see when the 6.4+ series kernels are again stable.

It was ok with sr1
=======================
Yes, to be honest, in general, something strange is happening, something strange is happening with KLA, a big update has come, I am doing an assembly with updates and strange things are happening with it
________________________
Or you need to wait until these magnetic storms calm down, and postpone for the assembly time

[Sofiya]

@Sofiya Is still working in KLV-Airedale-sr2?

everything is working KLV-Airedale-sr2

[Sofiya]

my disk began to crumble, so with the version of KLV-Airedale-sr3 with Void Linux Kernel 6.4.7_1 maybe even everything is in order, now I can’t even say with certainty that something is wrong with it. so now I’m sitting with a 4 GB flash drive and I’ll rub my head and think what should i do next
A black streak has come in my life.

[geo_c]

my disk began to crumble, so with the version of KLV-Airedale-sr3 with Void Linux Kernel 6.4.7_1 maybe even everything is in order, now I can’t even say with certainty that something is wrong with it. so now I’m sitting with a 4 GB flash drive and I’ll rub my head and think what should i do next
A black streak has come in my life.

It's at times like these that a good old static Traditional Puppy-linux comes in handy!

[Sofiya]

Damn it, reseeding on Puppy, I feel like a monkey with a grenade that is about to explode. I'm learning to walk all over again. habit to (KLA-KLV that my brain just boils Something needs to be done about this

[geo_c]

I feel like a monkey with a grenade that is about to explode...

[mikewalsh]

Afternoon, gang.

I'm aware that I've not really been keeping up with developments here in the way I used to in the early days. A query.....if I may?

Has printing ever been successfully sorted out here in KLV? It's the only thing that's really keeping me from using it more than I do...

TIA.

Mike.

[wiak]

Afternoon, gang.

I'm aware that I've not really been keeping up with developments here in the way I used to in the early days. A query.....if I may?

Has printing ever been successfully sorted out here in KLV? It's the only thing that's really keeping me from using it more than I do...

TIA.

Mike.

I believe it is still being discussed though I had 100% success in the past with rcrsn51's package for KLV-Airedale. I'm however struggling with flaky CUPS printing via Linux Mint, which came as an unexpected surprise. I get the feeling that Linux printing more generally continues to remain a bit of a moving target. I don't know why. Of course that old KLV-Airedale and working CUPS package still works solidly - problem is newer variations suddenly mess up again - I blame CUPS development, but shouldn't since I don't know the ins and outs of what the issues are at all.

Hmmm... Out of curiousity, just quickly installed CUPS on under test Fedora Rawhide build KL. Working fine to my old HP2540P printer. Got to hand it to RedHat and thus Fedora - Rawhide is cutting edge so would imagine it being flaky, but nope - no issues whatsoever thus far - even printing! The package manager dnf is fantastico too. I wonder how much money pours into RedHat and how that compares with Ubuntu/Canonical? I certainly get the impression that Fedora with RedHat behind it is at a different level in terms of professionalism/innovation - well, early days, but that's how it seems to me thus far.

Goodness, I thought I'd need hplip, but didn't even need that. Just cups - printer worked as printerless driver or something like that - via wifi. I presume I need hplip for usb connection? I'll try that tomorrow. I usually struggle getting it to print - but few seconds install on KLF and worked first time... ?!!!

[geo_c]

Has printing ever been successfully sorted out here in KLV? It's the only thing that's really keeping me from using it more than I do...

Printing for me in KLV-Airedale all the way to sr2 was working fantastically, the fastest, most stable and dependable printing I ever got from puppy.

However, due to my development/experimental techniques of incorporating @rockedge's and @wiak's upgrades of Airedale from RC3, RC6, RC13, and finally sr2, I finally ran into trouble with recent dbus upgrades after running the latest Void system update, thereby having to rebuild my upper_changes.

In the process I found I had difficulty getting cups to see my network printer. Could be a simple fix, if anything in cups is simple?

But at any rate, I was flabbergasted by the great printing I was getting from Airedale.

My upgrade issues going south turned out to be a blessing, as I just recently rebuilt two KLV-airedale root file systems using the "psuedo-full-install" technique. Now I have two immutable personalized Airdales, both straight sr2 and KLV-RT13 (real time kernel)

[rockedge]

Could be a simple fix, if anything in cups is simple?

That's for sure.......an example is with F96-CE_4 and CUPS discovery of network printers which sometimes (almost never) worked and configuration is all manual. Hit or miss.

I bought a new Canon PIXMA MG3620 WiFi and AirPrint capable. I could connect the printer to the router using the wife's iPhone and a Canon app, which worked first attempt. But I couldn't get the Puppy's or KLV's to see it and I couldn't "figure out" the correct URI/URL to use so it did not work.

After thinking about it I went and looked with F96-CE_4 package management around CUPS packages
and found one called cups-backend-bjnp-2.0.3-1 -> viewtopic.php?p=96146#p96146
I just happened to have read a blurp somewhere about Canon's bjnp protocol so with nothing to lose I tried it.

Problems over. Immediately using the CUPS function "Find Printers" the MG3630 was found and correctly configured and the driver was already in the CUPS printer drivers collection. Started printing right away! For years I had to manually with hit or miss tactics figure out the correct URL to use.

I did not find yet a similar package for Void Linux but working on it but it must be a similar thing.....

[rcrsn51]

Did you have the firewall running?

I tested a clean install of F96-CE_4 with my networked Canon TS3120. It was detected using the appsocket/jetdirect protocol (port 9100) and printed with the Gutenprint driver.

I can't imagine that an MG3620 would not also work with socket. Run PeasyPort and check that port 9100 is open on the printer.

[geo_c]

I just got my printer working!

The automatic discovery on the wireless network did not work, so I decided to use ipps protocol, and that worked completely.

So now, with hplip installed, printer added with ipps, ALL IS GOOD!

Using a "remastered" KLV-airedale-sr2-rootfs

I'll try it now with KLV-airedale-RT13 install, see if works just as well.

EDIT: Also working in RT13. Easy enough once you know what to do. Automatic discovery is handy to have though.

[rockedge]

@rcrsn51 I did try socket:// during the manual configurations I attempted. I have had success with socket:// and Canon but it wouldn't go this time!
I think my URL/URI was incorrect.

Surprised when the Find Printer found it. HP F4500 will be discovered fairly regularly.

I did not have the firewall enabled (I think and will double check that next time before I add any packages).

[geo_c]

I just happened to have read a blurp somewhere about Canon's bjnp protocol so with nothing to lose I tried it.

Problems over.

I just got my printer working!

The automatic discovery on the wireless network did not work, so I decided to use ipps protocol, and that worked completely.

After reading I suspected it was the bonjour backend (that what that package is, correct?)

Do you think it's a good idea to look for it in the Void repo?

edit: no I guess that's for Canon, I'm using HP

[rockedge]

I suspected it was the bonjour backend (that what that package is, correct?)

It seems to be....and I think bonjour/avahi needs to be present in a lot of use cases

Really trying to hammer out the printing so it's easier setup and reliable. I feel it's really important like a network connection to a router!

[mikewalsh]

See, I can't use any of these modern 'quick-fix' solutions ATM. Although my Epson is approaching its 13th birthday it still works perfectly. Still on the original waste ink pad, and according to Epson's own WICreset utility, is yet only 48% of the way toward needing a change. At the rate I use it nowadays, that'll probably be another 15 years....

Still scans and copies perfectly, too. And even the SD photocard reader slot at the front is still working perfectly, despite my not using it for years!

The point is, it's USB-only. By the time I get around to buying a new one, I suspect ALL printers will be wifi-ONLY.....but I am NOT chucking-out perfectly good, still-functional hardware just to keep up with the latest fads & trends.

Thus, it needs installed drivers. I have never yet found an Epson USB driver in the CUPS database that works properly, and although I tried converting the Epson .debs to .xbps packages some time ago, it failed miserably. And this is my primary snag; the world IS slowly but surely moving to wireless-only for everything. Dinosaurs like me are being left behind on the scrap heap of obsolescence because of a perceived failure to move with the times.

The majority of people WANT to do everything "on-the-go" nowadays, it seems. Thus, it's assumed that everyone wishes to do the same; why maintain drivers for a small minority who don't WANT to comply, and be a good little sheep?

Their loss, is the attitude taken.....and of course, it plays right into the hands of the "planned obsolescence" crowd.

(*sigh*)

Mike.

[rockedge]

@mikewalsh I prefer USB or parallel port cabled printers over WiFi. So unless I have to for positioning I'll take the USB cable over wireless connection. My other 2 printers are over 10 years old from the era before AirPrint and Wifi was not as a usual feature like it is these days.