ArchPup woof-ce January 2023 Beta 1

[wiak]

If Archpup giving problems or not fixed or supported, if anyone wants frugal installable small distro there is always Arch fully compatible KLA distros. Sofiya's KLA-OT2baseCE is particularly user friendly and polished and it's package management totally Arch official reliable.

[nnriyer]

If Archpup giving problems or not fixed or supported, if anyone wants frugal installable small distro there is always Arch fully compatible KLA distros. Sofiya's KLA-OT2baseCE is particularly user friendly and polished and it's package management totally Arch official reliable.

Please provide download link also

[Sofiya]

If Archpup giving problems or not fixed or supported, if anyone wants frugal installable small distro there is always Arch fully compatible KLA distros. Sofiya's KLA-OT2baseCE is particularly user friendly and polished and it's package management totally Arch official reliable.

Please provide download link also

viewforum.php?f=193

[nnriyer]

Is it compatable with Limine Boot Loader ?. Anyway I will try Arch KLA-OT2baseCE.

[wiak]

Is it compatable with Limine Boot Loader ?. Anyway I will try Arch KLA-OT2baseCE.

I've never used boot loader limine but it will be compatible. You need to check the provided grub2 stanza and with same kernel line options convert that to limine format of the same. This assumes you already have limine installed on your boot media.

KL distros use frugal install so can sit in own boot directory along with Puppy distros and similar.

[nnriyer]

Not booting from Limine Boot Loader. I have already installed easyos with Limine. While booting it says path is not ready.

[wiak]

Not booting from Limine Boot Loader. I have already installed easyos with Limine. While booting it says path is not ready.

Basically that probably just means you don't have the Limine boot stanze in its menu correct for booting a KL distro. I'm sorry, I'm only familiar with grub2 boot menu stanzas.

I suggest you post your Limine KL-boot-stanza here so someone can help you with its contents. If Limine boots other OS distros from here it surely would successfully boot any KL or Puppy distro too - you just need to get the boot stanza correct for the particular distro you are trying to boot. As you know, computers are fussy beasts, if something like that is even slightly imperfect there is pretty much no chance it will boot...

Though I don't know Limine, if you post the boot-stanza for Limine you have used for KL distro along with working stanza for easyOS or some other distro I might be able to spot why KL isn't booting for you. Somebody else from Kennel Linux section of forum will no doubt be able to help get it going for you anyway. I'm not going to be around so much in the coming weeks so best to get this sorted out soon if you want to.

[nnriyer]

QUIET=no
TIMEOUT=20
GRAPHICS=no
DEFAULT_ENTRY=1
EDITOR_ENABLED=yes
INTERFACE_BRANDING=EasyOS Limine Boot Manager

:EasyOS Kirkstone64 (partition nvme0n1p6, path easyos)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=8f0dc1a3-ef22-48b1-97d7-80cf42195846 wkg_dir=easyos
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/initrd

:Linux Debian GNU/Linux (partition nvme0n1p7)
COMMENT=Linux bootup
PROTOCOL=linux
KERNEL_CMDLINE=root=PARTUUID=b44c818b-3204-4292-b7e9-b79c5ab6c07f rw
KERNEL_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/boot/vmlinuz-5.10.57-antix.1-amd64-smp
MODULE_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/boot/initrd.img-5.10.57-antix.1-amd64-smp

:Puppy Linux s15pup64 (partition nvme0n1p8, path spup15)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=spup15 pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/initrd.gz

:Puppy Linux vanilladpup (partition nvme0n1p8, path vaniladpup)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=vaniladpup pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/initrd.gz

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=arch pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

:Windows 10
COMMENT=Windows bootup
PROTOCOL=chainload
IMAGE_PATH=guid://21e3bf30-0631-40c4-a470-537756576dcc/EFI/Microsoft/Boot/bootmgfw.efi

[rockedge]

Shouldn't the directory name be the same in the path? I am not familiar with this boot loader but am interested in how it works with Kennel Linux distro's.

Currently is:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=arch pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

Should be?

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=arch pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/vmlinuz w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/initrd.gz

[wiak]

Well KLA is not a Puppy so KERNEL_CMDLINE is definitely wrong. Looks to me, if bootfrom directory is ArchKLA then the stanza should probably be something like:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/ArchKLA
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/initrd.gz

Of if you want save-on-demand (save2flash) mode:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/ArchKLA w_changes=RAM2
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/initrd.gz

[nnriyer]

Great.Last one worked. However, getting error while booting. May be issue other than boot parameters?

:Puppy Linux Arch (partition nvme0n1p8, path Arch)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/arch w_changes=RAM2
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/arch/initrd.gz

. Please see the error screen below

[nnriyer]

See the folder view of frugal installation

[wiak]

No idea sorry. Looking at other stanzas would have imagined it would have booted. It obviously found the kernel and it loaded the initrd.gz, by the way (it is the init inside the initrd.gz that is saying "Seeking boot partition". But it couldn't find the boot partition thereafter which suggests it doesn't have the correct driver modules available for it to mount your /mnt/nvme0n1p8 drive where the needed sfs files are stored in /arch- (Limine has its own driver modules and hence could load vmlinuz and initrd.gz, but Linux then takes over and needs appropriate Linux driver modules to see the partition).

That would suggest the vmlinuz, 00modules sfs, and 01firmware sfs you are using don't work on your system. Are these the ones supplied from KLA-OT2 iso?

As an alternative you could instead try this other combination fetched via wget from firstrib gitlab repo:

Code: Select all

wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/initrd-latest.gz -O initrd.gz  # FR skeleton initrd
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup_22_04/vmlinuz
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/00zdrv_upup_22.04.sfs  # modules
wget -c https://gitlab.com/firstrib/firstrib/-/raw/master/latest/build_system/huge_kernels/upup22_04/01fdrv_upup_22.04.sfs  # firmware

Move the old ones somewhere out of bootfrom directory (/arch) and replace with above and then try booting it with these new alternatives.

No idea otherwise, sorry.

[rockedge]

I would try to launch in RAM0 mode with no persistence partition being looked for:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/ArchKLA w_changes=RAM0
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/initrd.gz

[nnriyer]

Dear Gurus

Thank you for the prompt reply and extending your support. I feel only slight issue in the boot process. You may be aware that I had reported very long back that none of puppy varients and Easyos was booting from my internal nvme SSD. Upon my frequent requests, our Barry Sir pinpoint the issue and solved the problem. Afterwards booting Easyos including Puppy. I don't know the exact technical issue. It may be related to VMD configuration?.
He enabled something in kernel?. I will see his remarks about that and let you tomorrow from my office.

The ISO was downloaded from location given by Sofiya.

Anyway I will apply your suggestions and get back to you. Please note that now I have come to my workplace after 4 days leave without my home laptop. Consequently i cannot test your solution now. I will try as soon as possible and come back again with output. Sorry for the trouble. Thank you all for excellent support.

[wiak]

I would try to launch in RAM0 mode with no persistence partition being looked for:

Code: Select all

:Puppy Linux Arch (partition nvme0n1p8, path ArchKLA)
PROTOCOL=linux
KERNEL_CMDLINE=w_bootfrom=UUID=f6d0c5d3-ea46-411c-a374-14a7e629e78f=/ArchKLA w_changes=RAM0
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/ArchKLA/initrd.gz

Yes, that crossed my mind also (using w_changes=RAM0) since obviously trouble with nvme0n1p8 partition. Still need ability to read from it, but with RAM0 mode writing is all done only in RAM so 'might' help. Otherwise, yes, it is something to do with kernel used unable to access that drive/partition. Way out in the end might be to use EasyOS kernel/modules/firmware if that was huge-kernel type like a Puppy Linux, but I haven't really used it so don't remember.

[rockedge]

@wiak I have seen this on QEMU VM's that sometimes RAM0 will start normally and RAM1 (regular), RAM2 will fail because the partition for creating then read-writing to upper_changes can't be accessed if there is no Partition Table and formatted partition. The boot to system start will hang up and stall because of the write-able partition search timing out. Occasionally it will cause a kernel panic and I am not sure what the difference is that causes that and not just to stall.

In RAM0 the locating of the partition is not required so it will boot, then run GParted and format the partition and the next boot in RAM2 will work.

Sometimes I have seen it boot regardless and go automatically to RAM0. I don't know how that is achieved on purpose yet.

[nnriyer]

Please see the below link . This was culprit for not booting EasyOs and other puppies.

https://bkhome.org/news/202211/kernel-5 ... iltin.html

I don't know whether it has any relevance to arch KLV ?

[nnriyer]

Is it possible to interchange the kernel (vmlinuz) between EasyOs, Spup or vanillapup with that of archKLV and compatible with arch?

Formating by GParted of existing partition is not possible as I have already many other puppy linux running smoothly from particular section ie. nvme0nlp8.

[wiak]

and RAM1 (regular)

RAM1 isn't the 'regular' save direct back immediately mode. It is an early RAM mode I was experimenting with so I hardly mention it nowadays nor use it. It is actually a little bit like RAM2 except instead of simply mounting the on-media persistent upper_changes for use during boot (as RAM2 mode does), it actually physically copies all of that external upper_changes contents into RAM upper_changes. So it is easy to save back at the end with a very simple rsync script. However, the disadvantage is of course that if the external upper_changes folder is large then all that stuff getting copied into RAM upper_changes wastes a lot of RAM. Fine therefore for small save persistence upper_changes folders since no whiteout issues to worry about in its rsync, however, RAM2 save-on-demand mechanism is fine nowadays so always used in preference since doesn't fill up RAM.

If you mean by 'regular' mode the case where all changes get saved back to external upper_changes all the time (i.e. not stored temporary in RAM at all) then that is the mode you get if you don't use wchanges= line at all in your grub stanza. Alternatively, using w_changes="" gives you the same direct read/write back to upper_changes on disk (or indeed w_changes="media"); all these are equivalent.

[wiak]

Is it possible to interchange the kernel (vmlinuz) between EasyOs, Spup or vanillapup with that of archKLV and compatible with arch?

Formating by GParted of existing partition is not possible as I have already many other puppy linux running smoothly from particular section ie. nvme0nlp8.

How is that partition formatted?

I haven't looked at EasyOS yet to see if it uses a huge-style kernel. If it did, that kernel/modules/firmware could probably also be used with KL distros. The kernel/modules/firmware don't need to be Arch-official as long as they are compatible with each other (especially the kernel and the modules have to be same release version). The underlying Arch filesystem will still pretty work as normal Arch distro (Arch package manager would work fine, except you wouldn't want kernel updates). In fact KLA distro isos I've published, by default come with old upup kernel vmlinuz/zdrv/fdrv simply because that was simple and I was too busy to use something else; always easy to swap in different huge-kernel/modules/firmware though (or even use official upstream kernel after running a FirstRib initrd modify script we use quite often for that purpose).

Anyway, we don't actually want to hijack this ArchPup thread; maybe the distro will be maintained. Best if you move questions regarding booting KL versions of Arch Linux to Kennel Linux KLA area. Just start a new thread there would be best.

[Amaponian]

ArchPup woof-ce.

arch packages.
I have been wanting to make a puppy with arch packages for a long time.
This version does not have JWM. It is just Openbox with Tint2 panel, jgmenu menu.
The iso is too big because it still has the devx on it. only it is in ydrv_Archpup_10.1.sfs.

It brings pulseaudio, blueman,
Mplayer with Gmplayer interface,
Audacious, Yradio ,pupcontrol , Uextract , PackIt, NicOs-Utility Suite, Frugalpup, Btop and many more programs.

adrv_Archpup_10.1.sfs: Audacious, btop, frugalpup, Gcolor2, Gdmap, Geany, Gpicview, Hardinfo, isomaster, Linux firewall, lxtask, lxterminal, Mplayer, BMplayer, Mtpaint,
nicOS-Utility-Suite, PackIt, Pburn, Pclock, Pcmanfm, pdvdrsab, pmadas, pRun, pup-advert-blocker, PupControl, pupMd5sum, seamonkey, SR_v2.2, tas, trans-tray, Uextrac, weechat, xarchiver, Xlock-lock-screen, Yradio.

adrv_Archpup_10.1.sfs: compiler libraries (devx).

There is a pacman pet package with pamac available, but it is only for testing and bug fixing.
when upgrading the system there is a package that corrupts the system.

ArchPup 64 Openbox with tint2

MD5=299ec2a3a0fc32d8629a6759b6bc29fc

Download ArchPup-beta-1

packages Archpup

Delta file. if you do not want to download the complete iso.
ArchPup Delta.

pacman with paman, it is a trial version.
Upgrading corrupts the system. I have not yet looked at it thoroughly to solve the problem.
this package is not in the iso. below I leave the download in case you want to try it, and if you see the solution to the problem.

pacman-6.0.2-x86_64.pet

I've just read this post of yours and I think I saw your name in other posts talking about distros for 32 bit machines.

Question: Do you know of a 32 bit Distro with packages ready to work. I have a Dell latitude 800 and, in the built in browser (Firefox), I'm getting errors while trying to access almost any site on internet. I'm mostly insterested in Youtube and may be stream sites.

Could you possibly give an advice on that matter?

Than you.
Greetings from Venezuela.

[rockedge]

Void Linux 32 bit runs some of the the latest browsers in 32 bit and does well on older computers.

Have you tried @peebee's VoidPup32 ? Puppy Linux based on Void Linux binaries and repo's.

[josejp2424]

Void Linux 32 bit runs some of the the latest browsers in 32 bit and does well on older computers.

Have you tried @peebee's VoidPup32 ? Puppy Linux based on Void Linux binaries and repo's.

the puppy 32 bits, from @peebee , are the most updated

[Jasper]

@josejp2424

Have you abandoned further development of this OS?

No updates since your initial offering.